Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bootstrap 2.3 Released

blog.getbootstrap.com

Post reply on HN
Print view View original

51–60 of 118 posts

Re: Bootstrap 2.3 Released

#51

Post by [deleted] »

easytiger wrote: post #26
robomartin wrote: post #15

> 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.

[deleted]

Re: Bootstrap 2.3 Released

#52

Post by beagle3 »

roel_v wrote: post #37
rtpg wrote: post #22

Earlier quoted context omitted.

I don't want to start a flame war, but I was wondering if there is a rationale for prefering dash-case? I have a hard time not writing in camelCase by default now.

"I don't want to start a flame war, but I was wondering if there is a rationale for prefering dash-case?" No, there isn't. It's one of those typical things that novice programmers fret about. Consistency within a code base is much more important than which style is used exactly. Having the style be a compile parameter would make sense to me, not switching from one to the other.

> Consistency within a code base is much more important than which style is used exactly.

I know this is a commonly held belief, and I held it too for a short while. But then, I was managing a project that ran on both Linux (lower_case_name libraries), Windows (CapitalizeEachWord), had components in Python (ClassesAreLikeThis but variables_like_this), Java (camelCaseIsAnAbomination) and even some VB6 (don't even remember the convention).

Utterly inconsistent. And it didn't make any difference to readability or maintainability, once people accepted that there actually is no single standard we can use.

In my opinion, it's one of these things like, e.g. significant whitespace or C brace style, that people believe make a difference because they have an example - in which the difference is often not attributable to the feature being discussed.

Re: Bootstrap 2.3 Released

#54

Post by epo »

easytiger wrote: post #26
robomartin wrote: post #15

> 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.

I think most people have enough processing bandwidth to cope with external libraries using a different convention to inhouse code.

Re: Bootstrap 2.3 Released

#55

Post by ZeroGravitas »

zopticity wrote: post #31

Man, I love bootstrap. Not only is it pretty well design from the front end and back end. The less files that are architected are awesome, I wouldn't have thought of it on my own. The guys built it for full customization for advance programmers and dead simple for beginners. Keep up the good work! The only disadvantage to this is that all startups are now 'lazy' and begin using bootstrap default theme colors and styl…

Pretty much everything in Bootstrap is gray-scale , with the exception of things with semantic function: red=error/danger, amber=caution, green=success.

The only exceptions are "primary" buttons (which was blue by default but based on the link color the last time I checked), info which is pale blue, and code samples which are pink.

I'm not in the slightest way artistic, but I feel if those (incredibly easily overriden) usages hold you back from expressing yourself with color then you're probably best not to bother and so it's a net-win either way.

Re: Bootstrap 2.3 Released

#56

Post by ZeroGravitas »

meerita wrote: post #36

I am using the 3.0 branch without problems. I don't know why they don't merge it.

I'm working on a bootstrap 3 based project and tracking their development. They've been making fairly large changes (e.g. badges are gone, replaced with counters, labels are MIA as well but they're supposedly coming back) over the last month or so and have more to make on their roadmap.

If you're not having any problems you must be very lucky and/or are only using a subset of the tools they provide, it's not going to be a drop in update for most people, hence the 3.0 version.

Re: Bootstrap 2.3 Released

#57

Post by [deleted] »

robomartin wrote: post #15

> 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?

[deleted]

Re: Bootstrap 2.3 Released

#58

Post by nemesisj »

RaphiePS wrote: post #4
instakill wrote: post #2

Not sure how I feel about the swearing on the page.

Why does it matter?

For me, it's not so much that the profanity is offensive or anything - I have what many might consider to be a fairly dirty mouth.

It's that their usage of profanity is lame. They're trying to be cool and funny, and it's very much neither of these. If they could actually managed the be humorous with profanity, then maybe I wouldn't mind it so much but this blog post really reeks of someone who is desperately trying to be funny and yet miserably fails.

Re: Bootstrap 2.3 Released

#59

Post by joesb »

RobAley wrote: post #46
Sandman wrote: post #40

Earlier 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.

I guess that only works for really simple project. Once you bring in third party libraries, your own common library, your own multiple layers of abstraction, this naming convention means almost nothing. It pays the price of annoying programmers who are already familiar with the code for not-so useful short term benefit of the very early beginner.

Re: Bootstrap 2.3 Released

#60

Post by joesb »

rgo wrote: post #35
fat wrote: post #24

Earlier quoted context omitted.

fwiw, we generally just try to do what the language does: border-radius document.createElement etc…

I personally prefer using the exact oposite to the language. That way my code or customizations are set apart visually: obj.getSomethingById() Non-native English speakers sometimes prefer to name variables in their native language for the same reason.

English is not my native language but I hate code with non-English variable names.
Post reply on HN