21–30 of 137 posts
Basically, I added a 'proper' target that 'bootstrap' depends on. This target simply adds the semicolon to the end of the file. Hope it helps those of you having problems.
Thanks for drawing my attention to this. Currently, I maintain a separate branch simply for adding the missing semicolons so that I can link the individual bootstrap files with my project. It's been quite annoying and I now know that the annoyance may not go away anytime soon. I hate these ideologues. But this is the trouble with JS I guess. I actually love javascript because of the highly dynamic nature of it. But t…
Thanks for drawing my attention to this. Currently, I maintain a separate branch simply for adding the missing semicolons so that I can link the individual bootstrap files with my project. It's been quite annoying and I now know that the annoyance may not go away anytime soon. I hate these ideologues. But this is the trouble with JS I guess. I actually love javascript because of the highly dynamic nature of it. But t…
problem here is ruby.ruby developers hate semicolons. They ignore the decades old history opf the semicolon, and assert that the ruby/python/haskell way of indentation and semicolon-less code is the better way. They COULD be right, but im too deep seated in C/C++/Java/JS. One of the problems with javascript is the fact that it gives the choice.
This code:
do a do {
a do { a do { a If you're going to use JS, you're not allowed to change things like this. It just causes problems for people. Easy solution, use CoffeeScript and have it compile down to JS. My favorite feature of CoffeeScript is the ruby/python line conventions spacing (2 spaces, no tabs), and no semicolons. They're already compiling the CSS from Less. Seems natural to add CoffeeScript to the chain.
I hate unnecessary semicolons too. Though I deal with them by including them everywhere, but making them hard to see in my editor ;)
Thanks for drawing my attention to this. Currently, I maintain a separate branch simply for adding the missing semicolons so that I can link the individual bootstrap files with my project. It's been quite annoying and I now know that the annoyance may not go away anytime soon. I hate these ideologues. But this is the trouble with JS I guess. I actually love javascript because of the highly dynamic nature of it. But t…
Relying on multiple different parser's implementation of the "auto semicolon insertion guesser" feature seems insane to me. I'm a python/haskell guy too, I hate semicolons. But I'll put up with them because javascript needs them, it doesn't enforce them, but to write sane, maintainable code it really needs them. Javascript is enough of a mess, this kind of thing just throws gas on the fire. Have you published your br…
problem here is ruby.ruby developers hate semicolons. They ignore the decades old history opf the semicolon, and assert that the ruby/python/haskell way of indentation and semicolon-less code is the better way. They COULD be right, but im too deep seated in C/C++/Java/JS. One of the problems with javascript is the fact that it gives the choice.
Actually, Haskell lets you do it either way. It's the best of both worlds :) This code: do a can also be written as: do { a or: do { a I've even seen it like this: do { a
Earlier quoted context omitted.
Actually, Haskell lets you do it either way. It's the best of both worlds :) This code: do a can also be written as: do { a or: do { a I've even seen it like this: do { a
JavaScript also permits you do it either way. That's what this whole argument is about!
Thanks for drawing my attention to this. Currently, I maintain a separate branch simply for adding the missing semicolons so that I can link the individual bootstrap files with my project. It's been quite annoying and I now know that the annoyance may not go away anytime soon. I hate these ideologues. But this is the trouble with JS I guess. I actually love javascript because of the highly dynamic nature of it. But t…
You can do it in Ruby and lots of other languages
https://gist.github.com/1815639
Of course, unless you're the sole writer and reader of the code, it's generally good to follow the common practices that evolved around the particular language.