2,044 karma · joined September 23, 2010
This is all the CSS needed to render almost the entire app from mobile to desktop widths, in both light and night themes. The "utility CSS" is generated by a framework and not something engineers have to be concerned with when writing components.
Having said that, I'm surprised there was only one CSS question, and the suggestion to combine questions with front-end specific knowledge might be a good way to ease into the interview.
http://en.wikipedia.org/wiki/Niche_construction
One of the most significant inadvertent "engineering" events was the biologically-induced oxygenation of Earth's atmosphere:
As this featured project is, in some way, defining itself relative to what it believes HTML5 Boilerplate is and should be, I'm going to chime in with some thoughts.
If someone wants to create a new project after their concerns have not been shared by others maintaining a large, existing, community project (e.g., how Lo-Dash came to be) then that's fair enough. But I'm always disappointing to see people do so before raising their concerns and making their arguments. It would avoid the repetition of errors and discussions that have been addressed previously. We could also work together to adapt HTML5 Boilerplate if there is a good case to do so.
Once-upon-a-time, I didn't appreciate the work and community knowledge that went into HTML5 Boilerplate. However, after I started to open issues against the repo and contribute to the project, I realised that it has always been very open to contributions and changes of direction. I had significantly underestimated how much thought and combined knowledge was going into the project, and how much it was constantly evolving.
It's hard to design a useful starting template that's clear and friendly enough for newcomers, documented enough for explorers, and svelte enough for experienced developers. We're always trying to figure out the best way to present the value of the project while not scaring away too many people. Hopefully, we're doing a decent job of balancing those concerns and making people feel welcome in the discussions.
I hope that developers will continue to work with -- and look to join -- the people developing HTML5 Boilerplate at any given time. If you think something is missing or should be removed, make the case for it. We listen and learn; we're constantly evolving the project.
Thanks
------
> HTML5 BP is maintained by Google people. http://news.ycombinator.com/item?id=4949018
That's not true. Only Paul Irish works at Google.
> "Slim HTML5 Boilerplate" would be a better title http://news.ycombinator.com/item?id=4949635
If that's what you're looking for, just delete jQuery and Modernizr from HTML5 Boilerplate :)
The post also suggests that certain class names are "unsemantic", when they obviously aren't. They just have different meaning to the sorts of class names the author is advocating.
I don't see plugins.js and main.js loading twice. And that CSS warning can only come from other tabs you had open as we don't include any `-o-` prefixed code in the CSS.
If you still need legacy browser support, then use 1.x.
No it doesn't.
Now, he decides that actually this is the way to go. Frustrating.
For reference, in the email linked above, Ian Hickson said:
> So why not just give the UA the characteristics and a template to use to build the file names itself? That way we still give the UA all the same information, but it is much less verbose and still solves all the same use cases. Thus:
<img src="face-600-200@1.jpeg" alt=""
src-template="face-%w-%h@%r.jpeg"
src-versions="600x200x1 600x200x2 200x200x1"></code>This is a nice little tool to help automate the production of the code for simple ones.
Does that mean it will be open to _anyone_ and no longer only to people considered to be "intelligent, creative, and witty"?
I do! But it's using and customising only the parts that are needed (...and a few lines of CSS are a bit old and out-of-date).
Today's HTML5 Boilerplate 3.0 release announcement is here - http://news.ycombinator.com/item?id=3558161 ...but for some reason it is pinned down on the second page.
1. The output CSS contains invalid or unnecessary code. Multiple classes on an elements are incorrectly handled, some form inputs (checkout and radio) are incorrectly referenced, and reference-only IDs are included.
2. The idea is flawed. Writing CSS and creating reusable components is not the same as filling in values for every element, class, and id found in your HTML.
http://www.youtube.com/watch?v=Ik1AK56FtVc
However, the article suggests that if some terrible legislation passed it would ignite people into real action. That clearly failed to happen when the Patriot Act was passed. I'm sure there are many more examples. If the discourse surrounding legislation convinces enough people not to care (or fails to make it into wider public awareness), then there doesn't seem to be much standing in its way.
Source: http://windowsteamblog.com/ie/b/ie/archive/2011/12/15/ie-to-...