Live data from Hacker News

Zurb Foundation 5 Released

foundation.zurb.com

131–140 of 174 posts

Re: Zurb Foundation 5 Released

#131
Can you explain the benefit of defining media queries with em's rather than pixels? It seems like an unnecessary layer of mental translation for developers, given that you deem it necessary to list px-equivalents in the CSS comments. [1]

Also, the medium/large screen sizes in Interchange don't align with the media query sizes. Interchange says 1024px wide is large, [2] but the media query says 1024px wide is medium. Or is it just a documentation error?

[1] http://foundation.zurb.com/docs/media-queries.html

[2] http://foundation.zurb.com/docs/components/interchange.html#...

Re: Zurb Foundation 5 Released

#132

I'm more curious about this which is mentioned on the page: https://github.com/hcatlin/libsass/ has anyone got it working with rails? Faster SASS compilation would make life much better (especially when bootstrap or compass are involved).

https://github.com/hcatlin/sassruby - Written by the same guy, ruby wrapper around libsass. I am pretty confident that a Rails gem is the eventual goal.

Re: Zurb Foundation 5 Released

#133
post #39

Earlier quoted context omitted.

Maybe I'm misunderstanding what you're saying, but how does Bootstrap's popularity make it better for backend design?

Backend as in administration systems, rather than frontend which is client-facing?

That's my interpretation of the comment, and real-world experience. I've written two admin sites with Bootstrap because it has all the widgets and plugins I might need on short notice.

Re: Zurb Foundation 5 Released

#134
What's the recommended way to use this with a python dev environment?

I'd rather not have to install ruby too just to rebuild the css. When one of these is announced I usually find myself navigating the various poorly-maintained python modules that process the source files, get lost, give up, and go back to plain css.

Perhaps I could just add a bit of css to a static build instead? Are there any shortcomings to that?

Re: Zurb Foundation 5 Released

#135

Earlier quoted context omitted.

How would you even expect this to be cited? Seriously, does someone need to crawl every Javascript project on Github and compile statistics on naming styles before they can make an obviously true statement like this? The fact that camelCase is the norm in the language and browser environment is obvious to anyone who has written even a modest amount of JS. notQuantified != false

notQuantified !== false to avoid type coercion here

S/he was using CoffeeScript, obviously! :)

Re: Zurb Foundation 5 Released

#137

I looked at the project on Github [1] and the latest tagged release is 4.3.2. It seems odd that they'd release 5.0 for download on their website before tagging it on Github; is there a particular reason for that? 1: https://github.com/zurb/foundation

Yep, I thought it was weird. The foundation gem is using this repository https://github.com/zurb/bower-foundation though (not tagged, but 5.0 nonetheless)

Re: Zurb Foundation 5 Released

#139

I'm puzzled about the switch from camelCase to snake_case for JS as shown in http://foundation.zurb.com/docs/upgrading.html#javascript-va... . The clear convention in JavaScript is camelCase, why switch away from it? (I say this as someone who in normal life using Python and Rust uses and prefers snake_case but who uses camelCase when writing JavaScript.)

This is insane. I have literally never seen a large-scale open source project or JS style guide that uses snake_case. The DOM is camelCase. jQuery is camelCase. Node APIs are camelCase. Why on earth do Zurb think their library is any different?

> This is insane.

Really? Why on earth would you care? What if they were to indent their code with 3 spaces? Would that be "insane", too? What if they don't like putting in unnecessary braces around one line "if" statements? Insane?

It's a (very common) stylistic choice. It's hardly insane.

Re: Zurb Foundation 5 Released

#140

Earlier quoted context omitted.

This is insane. I have literally never seen a large-scale open source project or JS style guide that uses snake_case. The DOM is camelCase. jQuery is camelCase. Node APIs are camelCase. Why on earth do Zurb think their library is any different?

> This is insane. Really? Why on earth would you care? What if they were to indent their code with 3 spaces? Would that be "insane", too? What if they don't like putting in unnecessary braces around one line "if" statements? Insane? It's a (very common) stylistic choice. It's hardly insane.

It's a public API meant for consumption by other developers, 95-99% of which are going to be use camelCase.

I don't care what their code looks like internally. I do care about the public interface to it.

Post reply on HN