Not sure how I feel about the swearing on the page.
If 'shit' and 'clusterfuck' makes you feel uncomfortable, don't visit NY. You'll have a terrible time.
Bootstrap 2.3 Released
111–118 of 118 posts
Re: Bootstrap 2.3 Released
#112Re: Bootstrap 2.3 Released
#113Re: Bootstrap 2.3 Released
#114It would be awesome if someone built a Bootstrap version converter. I'm currently using v2.2.2, and I simply don't really have the time to go through all the code to get it upgraded to the extent of making sure nothing breaks. Does anyone know the best way to do things like this, if a converter doesn't exist? It would be nice if the docs still had old versions, sort of like WordPress or PHP docs do, where you can see…
We haven't announced it yet, but we're working on this as part of what we're doing at BootstrapHero - http://www.bootstraphero.com We were targeting to have it out more for 2.x to 3.0 as that will be a bigger jump.
Re: Bootstrap 2.3 Released
#115Not sure how I feel about the swearing on the page.
And it's quite gratuitous too. Take for example: Modals are all responsive and ____ now. How random.
Re: Bootstrap 2.3 Released
#116Earlier quoted context omitted.
Why is it important that your code is visually set apart from the rest of the language?
When someone, particularly a beginner, is reading the code and come across, say, an unfamiliar function name, then they know straight away whether to look for it in the language docs or a definition somewhere else in the code. Not essential, but handy.
Re: Bootstrap 2.3 Released
#117> Renamed all of the variables to use dashes instead of camelCase. I absolutely detest camelCase. It ranks down there with good-old Hungarian notation. So, I am now wondering, why this change? Are people finally coming to their senses?
just-testing-this JustTestingThis Hmm. I think it only matters to me that the author picks one and stays with it. But that means that all libraries he uses has to use the same one. Which is why languages tend to prefer one over the other. e.g. Java using CaMeLcAsE To have them mixed in one code base would be like a micro context switch.
just-testing-this ---> just_testing_this
JustTestingThis ---> justTestingThis
The second one is less dramatic but the first one would in most languages subtract testing and this from just.
Re: Bootstrap 2.3 Released
#118Earlier quoted context omitted.
just-testing-this JustTestingThis Hmm. I think it only matters to me that the author picks one and stays with it. But that means that all libraries he uses has to use the same one. Which is why languages tend to prefer one over the other. e.g. Java using CaMeLcAsE To have them mixed in one code base would be like a micro context switch.
Sorry to be pedantic but these are wrong examples: just-testing-this ---> just_testing_this JustTestingThis ---> justTestingThis The second one is less dramatic but the first one would in most languages subtract testing and this from just .