11–20 of 45 posts
Bootstrap, like jQuery, was a great thing at one time. It still is a great thing to some people. Whenever I see default Bootstrap styles out in the wild though, I get pretty disgusted. Never trust a company that uses default Bootstrap styles in their production apps. It just shouts "I don't care" or "I don't know any better."
Why do you need Bootstrap? You can write a grid system in less than 10 lines of code with Sass. You can also do a typographic mixin in 5 lines of code then customise it as you need. You can also have a icon web font set only for tag in 5 lines of code. What else is there? Forms. You can reset the forms in another 5 lines of code then add stuff for [type=submit] and so on. Why do you need thousands of lines of code wh…
Earlier quoted context omitted.
Actually, to me it screams MVP by a backend focused developer. It signals the exact opposite to me as long as it is a company of only 1-2 people. They know what they are doing but have no design chops...which is much better than the reverse.
Or "they invested time in their product rather choosing to reinvent the wheel on their marketing website". Sounds like a pretty positive indicator to me.
Bootstrap, like jQuery, was a great thing at one time. It still is a great thing to some people. Whenever I see default Bootstrap styles out in the wild though, I get pretty disgusted. Never trust a company that uses default Bootstrap styles in their production apps. It just shouts "I don't care" or "I don't know any better."
For example - I think many of the templates here: https://wrapbootstrap.com/ are rather lovely. Do they elicit your disgust?
Bootstrap, like jQuery, was a great thing at one time. It still is a great thing to some people. Whenever I see default Bootstrap styles out in the wild though, I get pretty disgusted. Never trust a company that uses default Bootstrap styles in their production apps. It just shouts "I don't care" or "I don't know any better."
I've seen a bunch of stuff submitted here to HN that was nothing more than a landing page with a sign up form. I've rarely (if not never) signed up.
However, give me a page with a working proof-of-concept, I'll likely sign up regardless if it's built on default Bootstrap styling.
Reminds me of the days when people's biggest complaints about Reddit was that it looked bad.
Why do you need Bootstrap? You can write a grid system in less than 10 lines of code with Sass. You can also do a typographic mixin in 5 lines of code then customise it as you need. You can also have a icon web font set only for tag in 5 lines of code. What else is there? Forms. You can reset the forms in another 5 lines of code then add stuff for [type=submit] and so on. Why do you need thousands of lines of code wh…
Sure you can make your own hammer, and you can even use a non-hammer you find sitting right next to you. But you'll quickly find out that some non-hammer won't accomplish everything you think a hammer ought to accomplish. Bootstrap isn't just an invention/innovation — it is a framework.
Your question honestly is no different from "Why do we need frameworks?" And we just need to stop wasting out time asking these bloated philosophical questions that get us nowhere.
"Why do we need dictionaries?" Well, because if everyone went about their own way, they'd all re-invent the wheel a thousand times over, but we'd never see any cars.
Why do you need Bootstrap? You can write a grid system in less than 10 lines of code with Sass. You can also do a typographic mixin in 5 lines of code then customise it as you need. You can also have a icon web font set only for tag in 5 lines of code. What else is there? Forms. You can reset the forms in another 5 lines of code then add stuff for [type=submit] and so on. Why do you need thousands of lines of code wh…
Package all that up so people can just drop it in and have a nice looking site. Then people will use your system instead of Bootstrap.
H5BP is still available and there's a neat little packager, http://www.initializr.com/, that lets you include the parts you want and preconfigure it.
One reason to use a template system (with version control/plugins so you can modify locally and still merge in upstream changes and such) is that you can spend an awful lot of time keeping track of browser changes, standards changes, security issues, accessibility best practice, wide cross-browser testing and all the other niceties that go in to even a default template.
Update : I dropped it in my project followed by s/bootstrap-3.1.1/bootstrap-3.2.0/g . Nothing broken. That's a delight !
Why do you need Bootstrap? You can write a grid system in less than 10 lines of code with Sass. You can also do a typographic mixin in 5 lines of code then customise it as you need. You can also have a icon web font set only for tag in 5 lines of code. What else is there? Forms. You can reset the forms in another 5 lines of code then add stuff for [type=submit] and so on. Why do you need thousands of lines of code wh…
The most popular project on Github is : https://github.com/search?q=stars%3a%3E1&s=stars&type=Reposi...
Clearly there has to be something worth more than 50 lines of CSS.
Bootstrap, like jQuery, was a great thing at one time. It still is a great thing to some people. Whenever I see default Bootstrap styles out in the wild though, I get pretty disgusted. Never trust a company that uses default Bootstrap styles in their production apps. It just shouts "I don't care" or "I don't know any better."
Whenever a web app doesn't look different, complaints flood in.
Consistent styling on disparate web pages is a good thing, in my optinion.