Live data from Hacker News

The Web’s Declarative, Composable Future

addyosmani.com

31–32 of 32 posts

Re: The Web’s Declarative, Composable Future

#31
post #30
post #29

Earlier quoted context omitted.

These are legitimate concerns to have. There are many new technologies at play in this space and a lot of new concepts. > What really remains to be seen is whether this reduces or increases complexity. One word: scoping This is an important concept in software development that we've severely lacked on the web. We're used to creating global documents of HTML, CSS, and JS and hoping it doesn't explode. Frankly it's a m…

Yeah, good thoughts, time will tell. We could go back and forth on some of the finer points, but that's better over a beer than a forum. The scoping and the interface-definition are certainly the most promising aspects of this. I'm still very skeptical of using the DOM for non-UI purposes, but it could work out and that would be great. But even if not, even if it's just for GUI tasks, it's a win. I know bootstrap's c…

Beers!

It's 100% bizarre to think about elements that don't render UI. Honestly, I'm still wrapping my head around it.

If you think about it though, there are plenty examples today that don't render UI (directly) but serve a specific purpose: , , , , , , , ....

Search for "display: none": http://src.chromium.org/viewvc/blink/trunk/Source/core/css/h...

Interesting times indeed.

Re: The Web’s Declarative, Composable Future

#32
post #28
post #22

Earlier quoted context omitted.

You can use npm modules on the client via Browserify. And there is a dedicated to client-side package manager called Bower.

Those are some pretty cool projects. This sort of thing really needs to be supported natively in the browsers and written into the ECMAScript standards, though. It looks like what both Browserify and Bower are doing is basically a macro expansion that outputs regular Javascript, which is interesting, but really shouldn't be necessary. Basically the current state is that everyone knows that HTML/CSS/JS sucks (by sucks…

JavaScript is all about lack of standard solutions. Take any aspect of the development and you will get a million of possible solutions, whether they are classes implementations, package managers or build tools.
Post reply on HN