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

31–40 of 118 posts

Re: Bootstrap 2.3 Released

#31

Post by zopticity »

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 styles -- which makes all website look the same. I'm not sure whether I feel that we're losing creativity for people who want to play with colors or we're losing the ability to actually code up some CSS to make things pretty. (Just my opinion).

Dropping support for IE7 was a good idea. I believe that is the next browser we're killing after IE6, right? After all, who keeps versions of browser these days? I mean I lost count when Chrome updates for me -- and Firefox is on rapid release (18) now. I can't keep up remember all these numbers and browsers!

Please keep up the good work! Bootstrap is an awesome framework for the web!

Re: Bootstrap 2.3 Released

#32

Post by logn »

blowski wrote: post #19
shantanubala wrote: post #9

Earlier quoted context omitted.

There are some work environments where using "shit" and "fuck" would be a turn-off -- not all places are very relaxed about that stuff. On a more personal note, it feels immature -- titling a section "Oh shit what" just for the sake of irony dilutes the meaning of what they're conveying. The info would be equally effective without it, and it's just filler. I know people just want to have fun, but why not save the swe…

I agree, it's gratuitous. Anyone with a swear filter (families, corporates) can't look at the documentation, and religious organisations may feel uncomfortable. Being open source, perhaps there's a fork opportunity for 'Bootstrap without the swearing'.

VelcroStrip?

Re: Bootstrap 2.3 Released

#33

Post by likeclockwork »

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?

I'll work with either, but kebab-case(or snake-case with dashes if you prefer) is a lot more readable in HTML source for me.

Also, all their CSS classes were kebab-case anyway, so it makes sense that they'd change their variables to match. It's a nice move towards consistency.

Re: Bootstrap 2.3 Released

#35

Post by rgo »

fat wrote: post #24
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.

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.

Re: Bootstrap 2.3 Released

#37

Post by roel_v »

rtpg wrote: post #22
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?

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.

Re: Bootstrap 2.3 Released

#38

Post by mullr »

fat wrote: post #24
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.

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

This is the correct rationale, and should be used to end every argument about naming conventions.

Re: Bootstrap 2.3 Released

#39

Post by human_error »

likeclockwork wrote: post #34
rwl4 wrote: post #6

Earlier quoted context omitted.

And it's quite gratuitous too. Take for example: Modals are all responsive and ____ now. How random.

It's just a word.

Yes but it's unprofessional way to use it to describe context in this case. He's not talking with a friend. He's making an announcement.

Re: Bootstrap 2.3 Released

#40

Post by Sandman »

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.

Why is it important that your code is visually set apart from the rest of the language?
Post reply on HN