9 comments

[ 3.0 ms ] story [ 37.2 ms ] thread
Just some complaining about JavaScript and CSS, move along.
Ralph's Rule: "There is no technology so poorly conceived, so inconsistent, so aesthetically offensive, or so woefully untouched by theory that it will not see widespread adoption in the Web community."
The article makes a lot of generalizations but never points to any specific reasons why css and js are actually bad.
> ECMAScript 6 fixes all of that!” The promises never hold water.

No pun intended?

Isn't what google is doing with dart ? I thought they had plan to embed a dart vm inside chrome. As for css i still haven't found a layout framework that would let you design responsive UIs easily. It seems to me that coding in fix positionning is easy in any system and coding for flexible layout is hard no matter what you're using (eg : which of iOS autolayout or CSS 3 is the best ? Hard question)
Because it's there.

Whatever is there, people will push it to do things it wasn't designed for. Any they'll push so hard it will actually work.

Please offer alternatives and examples of "awesome" front-end programming.

Also, the author fails to take into account the evolution of the web browser. In my day we didn't even have CSS. Just HTML.

There is actually a lot being done.