Bought a book on bootstrap I liked it.

[Thor]

I like the framework

I was a software developer before Mac existed, so I remember how the tech industry
reacted to it. For the most part, the community reacted with a fair amount of skepticism.
The interesting thing is that the negative things people say about Bootstrap today sound
exactly like the negative things people said about the Mac in 1984. And in both cases,
the things that people didn’t like were what made them important.
Apple realized that there is a set of things that all software has to do, so why shouldn’t
they all do them the same way? If they did, software would be easier to develop and
debug, but more important—it would be easier to use. If there was only one way to
create menus, then once a user learned how to use the menus of one app, he would
already know how to use the menus of all others. The same is true with scrollbars,
windows, the keyboard, the mouse, printing, and sound.
The reason programmers didn’t like it, (and I was one of them) was that they took what
we did and commoditized it. Further, there were limits to the one-size-fits-all approach.
There were some apps that didn’t take to the UI standards very well. What to do about
them? Well, you adapted, that’s what you did.
This is a well-known technical process called factoring. If you see yourself doing something
over and over, do it one more time really well, work on the API so it’s easy and
flexible, and that’s it. You never do it again. It’s how you build ever-taller buildings out
of software. What was the leading edge five years ago is baked into the operating system
today. Progress. It’s a wonderful thing!
The same patterns are observable in the Web. In fact, it’s kind of sad how much of a
repeat it is, how backward today’s development environment is compared to the one
envisioned by the Mac. But at least Bootstrap is out there doing the factoring. If I want
to put up a menu, I can just use the code that creates menus. Sure, my menu looks like
all the others, but that’s a good thing for users. There is no need to learn a second or
third way to use a menu.
vii
That this is needed, desperately needed, is indicated by the incredible uptake of Bootstrap.
I use it in all the server software I’m working on. And it shows through in the
templating language I’m developing, so everyone who uses it will find it’s “just there”
and works any time you want to do a Bootstrap technique. Nothing to do; no libraries
to include. It’s as if it were part of the hardware. It’s the same approach that Apple took
with the Mac OS in 1984.
Like all important technologies, Bootstrap is “good enough” but not too good. In other
words, the designers, Mark Otto and Jacob Thornton, could have factored more than
they did. However, while they could have created something more compact and perhaps
more elegant, it wouldn’t have been nearly as approachable. The great thing about
Bootstrap for a guy like me, who has been busy building software behind websites, is
that it solves a whole bunch of problems that we all have when putting a user interface
on those sites.
However, I think that will turn out to be just the beginning. I see the opportunity for
Bootstrap to become an integral part of the Web—a toolkit that you can count on being
present in every environment you work in.

 

[Thor]

Bootstrap
by Jake Spurlock

 

[satanboy]

tl'dr

 

[Thor]

tl'dr

Ahh sorry, well basically

He said bootstrap will succeed for the same reason Apple did.

There's only one way to do something, 1 menu etc making the code faster to deploy and easier to build complex sites etc.

 

[Thor]

Apple realised that there is a set of things all software has to do, so why shouldn't they all do them the same way.

 

[rorz0r]

Tldr: use bootstrap if you're a backend dev and you don't want your front-end to be ****.

 

[Zarkon]

I like the framework

I just started learning bootstrap,really like it. As someone very new to development still,i feel everything is getting "easier" little code to do big things. I read a lot to see what experienced dev's think about such frameworks and other frameworks,and i always get the answer. Learn to do it the hard way learn responsive design without bootstrap,learn developing without frameworks.

One thing i keep coming across is reading about junior dev's doing jquery and thinking it is javascript,not knowing it is just a framework of javascript,how can someone sitting in a JOB not know that about jquery.I can only imagine that is why experienced devs in the office want to punch these people lol

Just to add,i have yet to start a job as a developer i'm still learning,hoping to get a my first job as a front end dev in the next 3 months

Question for everyone,how do u choose when bootstrap is needed,or when it is not needed,when u get a new project and decide..okay i will just bootstrap this site.

 

[Thor]

Tldr: use bootstrap if you're a backend dev and you don't want your front-end to be ****.

Don't agree at all.

I made so many websites with bootstrap and apply my own styling my own width and defaults you won't be able to tell all the sites are built using bootstrap.

I think a more accurate statement would be :

use bootstrap if you're a backend dev and you don't want your front-end to be ****... Unless you know what the fck your doing and know how to apply your own touch.