Remove prefixing

[corysimmons]

Everyone could/should be using Autoprefixer (or some similar/lesser tool) in their development environment. It's usually a bad practice to have prefixing in libraries.

[ConnorAtherton]

I didn't know it was bad practice. Could you elaborate?

I don't see the down side including prefixes here. In the case that they don't use autoprefixer (I agree, they should) the styles will work and if they do then it works anyway, no harm done.

[corysimmons]

I used to think that way but I got chewed out by the community for doing it and now I'm a convert.

The idea is, it's not Loaders.css' job to prefix. It adds repo bloat for no benefit. I promise you won't have many issues from this change.

[ConnorAtherton]

Okay, I can see the sense in that. I've just uncommented it out for now.

[corysimmons]

👍

[jpcmf]

I dont use autoprefixer and I use SASS. Too bad remove the prefixer 👎

[corysimmons]

You should be using Autoprefixer in your build process though. :\

[rictorres]

You are assuming that whoever uses this library must have a build process in their project.

Are you sure this is the correct approach?

Also, Autoprefixer will add or remove prefixes according to your settings.

[corysimmons]

It's a pretty fair assumption to say that most people will have some sort of build process, and that in that build process they'll be using Autoprefixer.

On the flip side you're assuming they want prefixes baked in - I for one don't. I'd rather have personal control over what prefixes are added with my Autoprefixer settings rather than some heavy handed prefixes applied that may or may not be relevant in a month.

[rictorres]

I disagree. Imagine jQuery publishing a ES6-only version hoping that most users are using Babel or similar.

If you're using Autoprefixer, you have personal control over the prefixes: it'll add or remove prefixes according to your settings :)

[corysimmons]

Ultimately it's up to the maintainer of the lib. I'll personally never prefix a single library I create and continue assuming people are using Autoprefixer, and if they aren't, help them to use it.

@ConnorAtherton Some of your users have expressed concern about this change and I seem to be the only one against it, so maybe it's time to reconsider prefixes.

Here's some further reading about when I used to argue for prefixes and the community asking me to remove them:

• Too much vendor prefixes mojotech/jeet#227
• Scss version does not handle vendor prefixes mojotech/jeet#211
• Add vendor prefixes to lib mojotech/jeet#114

Here's typically what happens when someone who isn't using Autoprefixer comes along (pretty rare):

• Vertical Alignment Broken in Safari? mojotech/jeet#394

[ConnorAtherton]

Thanks for the input guys. I especially appreciate the links @corysimmons.

My original thoughts on this topic can be summed up with this comment. Apart from the extra bloat, I saw no harm adding prefixes for reasons outlined in that comment. And as @rictorres mentioned earlier, you still have control over which prefixes to keep and which to remove.

It requires extra effort to add a build system to run through Autoprefixer whereas it requires no effort to run it through your current build system because you will have already configured the settings.

The main argument against adding prefixes by default is that the library would then be making decisions it shouldn't, as well as violating the single responsibility principle. I think that's a fair argument if you assume that most - if not everyone - using the library will be running it through some build step to add the prefixes before using it. From my experience with the node community, this is the case. However, I'm not sure about other other communities out there and I don't want to rule people out from using this just because I assumed they had a particular build step in their system.

Adding them does add extra bloat but I think in this instance this is justified because the unprefixed browser support is so low (22.3%).

For now, I want to keep them in and revisit this in the future when I've asked around a bit more.

[corysimmons]

I personally disagree with this decision, but I think it's a really good idea to listen to your users so 👍

[rictorres]

good call, @ConnorAtherton 👍

[jpcmf]

Don't worry about me, I just remove the loaders.css from my project :)

[mustaqsheikh]

I agree with rictorres.