Is bootstrap really worth it?

[flippakitten]

Nope.

You can combine all three those stylesheets into one and use media queries especially of it's only 10 classes per query

I know I can but this works for me as the main styling is done and then the styling adjustments are done per screen size.
So if there is a big change like colour scheme, it's done in one place where as the tiny adjustments are done elsewhere and they don't change often. It makes things a hang of a lot more readable and modular meaning I can work on one part and another developer can work on another without touching each other's work.

 

[rward]

I know I can but this works for me as the main styling is done and then the styling adjustments are done per screen size.
So if there is a big change like colour scheme, it's done in one place where as the tiny adjustments are done elsewhere and they don't change often. It makes things a hang of a lot more readable and modular meaning I can work on one part and another developer can work on another without touching each other's work.

I like this modular approach.
If you have an issue with something it makes it easy to know where to look for it.
If its not in the specific override file then create an override for it.

You could use LESS/SASS to compile and minimize it all into 1 file for when you put it on server.

 

[Thor]

I know I can but this works for me as the main styling is done and then the styling adjustments are done per screen size.
So if there is a big change like colour scheme, it's done in one place where as the tiny adjustments are done elsewhere and they don't change often. It makes things a hang of a lot more readable and modular meaning I can work on one part and another developer can work on another without touching each other's work.

I like this modular approach.
If you have an issue with something it makes it easy to know where to look for it.
If its not in the specific override file then create an override for it.

You could use LESS/SASS to compile and minimize it all into 1 file for when you put it on server.

Doesn't this create unnecessary round trips to the server SASS is the ideal and recommended approach for this, but placing all of it in a single css file will be a great improvement already.

 

[flippakitten]

Doesn't this create unnecessary round trips to the server SASS is the ideal and recommended approach for this, but placing all of it in a single css file will be a great improvement already.

Why would it be and improvement? Interested to know why you feel so strongly.
There are two strong arguments for both.

 

[Thor]

Why would it be and improvement? Interested to know why you feel so strongly.
There are two strong arguments for both.

Fewer HTTP requests IS the reason. retaining visitors is priority #1, so if your page loads slow, they are less likely to stay. If you have the ability to combine (which you definitely have) then I would highly recommend doing it. It's the best of both worlds.

 

[FarligOpptreden]

Fewer HTTP requests IS the reason. retaining visitors is priority #1, so if your page loads slow, they are less likely to stay. If you have the ability to combine (which you definitely have) then I would highly recommend doing it. It's the best of both worlds.

Agreed. Bundling and minification are some of your first ports of call in optimizing a site or web app. Anyone who argues otherwise hasn't dealt with high traffic sites yet.

 

[Thor]

Anyone who argues otherwise hasn't dealt with high traffic sites yet.

+1

 

[profeet]

Agreed. Bundling and minification are some of your first ports of call in optimizing a site or web app. Anyone who argues otherwise hasn't dealt with high traffic sites yet.

or round-world-trips; latency.

 

[Thor]

or round-world-trips; latency.

And that.

 

[rward]

Doesn't this create unnecessary round trips to the server

Yes, it does.

SASS is the ideal and recommended approach for this, but placing all of it in a single css file will be a great improvement already.

Yup and minifying or what not.

For dev, it's nice to be able to have that kind of modularity. "Problem with the layout at 720px wide, check the medium-style css file".

 

[Thor]

Yes, it does.


Yup and minifying or what not.

For dev, it's nice to be able to have that kind of modularity. "Problem with the layout at 720px wide, check the medium-style css file".

For dev I can understand that.

Personally I started using sass makes it easy on both dev and production granted I still have a long way to go.

 

[flippakitten]

Agreed. Bundling and minification are some of your first ports of call in optimizing a site or web app. Anyone who argues otherwise hasn't dealt with high traffic sites yet.

Honestly, I am not expecting it to be high traffic, if it becomes that, sweet, I'll optimize more. For now my optimizing comes in the form of "as few libraries as possible" in front and backend and which also makes dev a lot simpler cause I can work on one specific thing without breaking anything else.

Fewer HTTP requests IS the reason. retaining visitors is priority #1, so if your page loads slow, they are less likely to stay. If you have the ability to combine (which you definitely have) then I would highly recommend doing it. It's the best of both worlds.

That being said, thanks for the advice in the end your argument for one file is stronger and my mind has been changed, dev site will have multiple, combine into one for live.

 

[Openhost]

And try to get your server/site ready for http2

 

[Thor]

^ And that

 

[flippakitten]

^ And that

I'll wait thanks, it's like 64bit OS, wait until the bugs get fixed and security flaws patched.