Why are so many people here on HN so eager to throw away html/css/js, just because they're a little icky and you don't like to use them?
Do you not realise that means throwing away the entire web, and its history going back to the early 1990's? Backwards compatibility and platform stability are GOOD THINGS that we need more, not less of. Lest we perpetually build content for doomed platforms, and leave no mark, no history on the world.
the better course is evolution, not revolution.
Mozilla has been through every revolution, first hand. They know what they're doing.
edit: I'm flattered but please vote up the comments relevant to the actual post.
In my opinion HTML/CSS/JavaScript is the best interface design technology ever invented. I believe it gets a lot of hate because:
1) Amateurs can use it easily and poorly
2) It is not taught in computer science class
3) HTML/CSS is not programming
4) HTML docs attempt to be responsive/liquid as opposed to traditional screen painters.
These are actually good things (and #2 can be fixed) but they represent a significant philosophical shift that most traditional developers don't want to accept.
> In my opinion HTML/CSS/JavaScript is the best interface design technology ever invented
i thoroughly agree with this if you say "interface implementation technology" instead of "interface design technology". i also believe anyone who disagrees has never fully explored the various print/console/mobile/mfc/actionscript worlds. i mean... have you ever even USED something like pagemaker?
I am an expert in web technology (approaching 15 years of experience) and I absolutely disagree that that's is the best we have.
Edit: damn, it is more than 15 years already. I've brought home the first HTML spec printout in 1996 and got first money for the website I've built in 1998. Still remember fixing <center> bug in IE3 when it came out…
I used the web in 1993, in the fall, with mosaic, and grey backgrounds. On a 286. With windows 3.1, and 16 colors.
So that makes it 20 years. (dangit!)
Anyway, I think javascript made a mess of it. The point of the web was to link documents. JS makes links obsolete, as they now are relegated to JS-app entry points.
before I get too much in the weeds, I'm gonna go read the article.
The problem is not that JS is worst than links or forms. It's the most potent hypermedia technique (code-on-demand) but it lays behind the Turing horizon: you can't statically determine what it's doing.
What do you feel is the best that we have? I'm not preparing to raise an argument, merely asking for information. My own experience with user interface development outside of the web is pretty limited; I've created a few winform apps and done some OpenGL stuff in college, but that's basically it. Compared to those, I prefer the web stack.
you'd think if something were the most successful content platform since the invention of movable type, the scientific approach would be to figure out why, instead of trying to destroy it.
One huge benefit of HTML/CSS/JS is this: you are downloading the actual source code. This allows different platforms to interpret it as they will. It also allows developers to learn from each other in an open way. Of course, it allows for security audits as well, since JavaScript can be profiled. Overall, it's the most communicative form of programming.
If XAML some open source project made by some hippie group of developers, HTML/JAVASCRIPT/CSS would be in the toilet today. It is miles ahead of the barely moving technologies held back by the standards committees.
I'm not sure where you are going with that, but if you think you're going to convince millions of people to rewrite their websites because $NEW_TECH is now on the market, think again.
He is politely giving an example of a superior mark-up language. Just because developers are effectively forced to eat shit we shouldn't pretend it's a piece of a nice cake. Things like angu-bootstrap-whatever are just a thin layer of icing on the top of a big pile of manure.
That's not what parent is saying. Parent is claiming that the only thing preventing us from welcoming our new XAML overlord is that it's made by Microsoft and not an "open source" project made by "some hippie group of developers". That's hogwash.
It's hogwash because nobody is going to invest billions to remake the Internet with a non-backward compatible technology, wherever said technology comes from.
I think you're making a great number of assumptions.
There's no reason we can't keep backward compatibility as long as it's desired.
No one is "throwing away the web", what ever that even means.
We can always put the current stuff in a nice museum and pay tribute to the technological importance it achieved during the evolution of the web! vs an evolution of any seriously flawed specific piece of technology.
Also, this really is not a "want", rather the real problems are creating real needs.
"I would have thought ditching HTML, the box model, CSS and JavaScript to be a more important objective that should come sooner than this. Or another way to put this would be: Wouldn't development efficiency/simplicity be more important than running the current junk in parallel?"
Does "ditch" and "junk" mean something other than the common usages of these terms to you? The only assumption I'm making is that you're writing in english.
Right. You can use xhtml 2.0, you can use flash. you can use java applets. you can use ios apps. you can use android apps. You can use director. you can use axr. you can use activex. you can even use xaml, xul or silverlight.
Go on. Use them.
I dare you. See how long you last.
or invent your own platform and see how quickly everyone switches over to it. I'm sure the only thing stopping this from happening is nobody has tried. Sure!
Why are you taking this so personally? When centering a div on vertically and horizontally is such a hassle, there can definitively be some improvements in the system. HTML lacks many semantics that would cut down on div.content or .main or any number of similar classes. CSS lacks any sort of inherit structure (like SCSS gives or taking it further with SMACSS) and quickly can become a huge mess. JS is still a terrible language with no support for basic things classes or importing.
why are you taking it so personally?
why are you reading such things in? it's totally irrelevant.
I didn't say that html/css/doesn't need improvement. that's changing the subject. The question is: why do the people here so eager to "ditch" (as in totally discard) html/css/js.
> Mozilla has been through every revolution, first hand.
> They know what they're doing.
Oh yes, I do remember those nice <layers> in NN4 and that CSS wannabe mingled with JS.
For what I am grateful is Firefox (before the rise of chrome). However I think the proper mindset left Mozilla together with Blake Ross and all that's left is posturing and politics.
Mozilla is making Firefox and helping keep the web open with new APIs, standards. It is helping with the politics side regarding net neutrality. It is helping millions learn how to build web pages thru webmaker.org program that teaches web literacy and moving onward to teach app making with Mozilla Appmaker. Mozilla is helping bring the next billion people online by working with partners to offer affordable mobile devices on emerging markets where people can't afford computers or high end devices. Thats more than posturing.... Thats the result of a global community of volunteers, staff and partners working together to make the web and the world a better place for everybody.
HTML etc get flack because they're badly designed. What do you want? Semantic markup, document layout or distributed programming? Sorry but the web people got _everything_ wrong. We don't have a platform that does any one thing well. The whole thing is a laughable dog's breakfast with no layering, no foundations or unity of design. The better course is evolution.. for Mozilla, who have been very good at maintaining their market position while endlessly bungling platform design.
and yet despite its flaws it's become the most successful platform for content since moveable type.
Java failed to do that.
iOS, despite its financial success, is failing to do that.
android is failing to do that.
flash failed.
Aren't you the least bit curious why it succeeded despite not being to your taste? Do you think it's just accidental? That the laws of physics and rationality were suspended for one brief glorious moment in the 1990's? Are you a web creationist?
I think portions of it were wide availability of web browsers, combined with the explosive adoption rates of internet usage... as time moved forward, entrenchment of the existing sites (and their quirks) got buried in...
If we'd started with xml compatible markup (all tags must close in order), and no browsers supported a quirks mode... we'd have much cleaner web browser engines and a much more usable web today.
I think that JS has a few quirks as well... so does CSS.. JS and CSS came after HTML, and even then have grown/distorted a bit. XHTML broke too many things, so we went pragmatic with HTML5. Just the same, no "new wheel" will get adopted in this space whole-sale. People have ditched XHTML and run back to HTML5.
I think a lot of things could be better, and will get better... so long as there are billions of pages/sites out there as-is, quirks mode browsers aren't going away.
well-formedness? _that's_ the problem with the web? Not slow performance? Not no realistic offline story? Not a loosely-typed, dynamic language? Well-formedness.
How much of a browser's time is spent in JS vs. rendering? How much overhead is spent of parsing/rendering? JS isn't even 25% of overhead in most sites, or even dynamic applications. Rendering of reflows, and other UI elements is. Understanding this in the scope of JS is important, as this is where it gets triggered. Hell, having something like AngularJS out of the box in the browser earlier on would have helped a lot.
Just the same, it started with well-formedness being loose, and continued from there.
Sure, slow rendering/layout/performance would be a perfectly reasonable complaint about the web platform.
The well-formedness thing is, sorry to be blunt, a totally crazy thing to complain about.
Every single platform that has any popularity introduces rough edges like this over time. It's impossible not to because every single bug that introduces relaxations gets baked in as content comes to rely on it. It is impossible to ever remove those relaxations, and really, it's totally fine.
There is a cost to lack of well-formedness, but on the list of problems with the web it is waaaaay waaaay down there.
"Content" is the key there. But I am at loss what exactly iOS and Android are failing to do? I think they do very well with music, movies, books, etc, thank you very much. Hypertext content? Well, we do have web for that.
oh, iOS and Android are doing just fine, as of this moment. Check back in 5-10 years though.
Just how exactly do you archive that content anyway? Anything you "buy" on those platforms is not something you own. It's something you're licensing for short term use. Doesn't sound like a great outlet for culture to me. It sounds like a death trap.
Well, how do you explain the fact that Web did not win on desktop? I am still puzzled why people think web should take over mobile for some reason, but never mention desktop.
> Just how exactly do you archive that content anyway?
Why should I archive anything? I don't archive web pages I visit either.
> Anything you "buy" on those platforms is not something you own.
I don't care if I "own" something. Owning for the sake of owning means nothing to me. If I pay for the book it is because I want to read it. If I pay for the music, it is because I want to listen to it. Even CDs I do own are now represented by their cloudy ghosts using iTunes Match. Why? Because they are always there. I don't have to walk with backpack full of CDs just in case I'd like to listen to particular song. I can get it on any of the devices I use.
Yeah, I don't have a install DVD for every app I bought. I don't care. I change my phone: they are already there. I get new Mac: I go to App Store app and just click "Install" for every app I want to have on that machine. Maybe to some it is a death trap, I don't know.
"Well, how do you explain the fact that Web did not win on desktop? I am still puzzled why people think web should take over mobile for some reason, but never mention desktop."
Define "win". From my point of view, the web has not only won desktop, but utterly dominated it, and relegated the rest of the OS to a mere substrate for webpages. The only things it hasn't really replaced are photoshop, final cut and protools. It's only a matter of time.
"Why should I archive anything? I don't archive web pages I visit either"
oh boy.
Paging Jason Scott.
Jason Scott on aisle 12.
" I don't care. I change my phone: they are already there. I get new Mac:"
I'm glad you can thrive only on corporately produced content you license for brief periods of time. Many people out in the world are not corporations, and produce things that they care about. Many use computers to do this. Most care about the thing they made, and not about the tech they made it with. And so it ends up in these closed off little data silos and proprietary formats- not only are these things not backed up, they can't be backed up.
And then those people die, and there is nothing left of that person except what they made on the iPad with iOS6. The apps the things live inside are not compatible with the newer iOS. When that iPad dies, it's like the father, the lost son, the missing daughter- they die for a second time.
But you know, it's good that owning that stuff doesn't matter to you, and therefore should not matter to anyone else.
The web did win on the desktop. New desktop apps are web apps, except for clients to sync your files with a cloud service. The popular desktop apps all predate the rise of the web.
Also, having books and movies stuck in your amazon or apple account is convenient for consumption, but horrible for creation. You can't DO anything with that content. I've wanted to extract interesting stuff from books I own before and was forced to make screengrabs. If you don't understand what's wrong with the media rental model, go read "the right to read" by stallman.
It is not clear what you refer to when you say ``buy".
By the way, you have drifted away from discussing the technological aspects of the Web. This line of argument doesn't help establish why HTML/JavaScript/CSS are better.
The man accusing me of "web creationism" jumps from "HTML etc suck and were poorly designed from the start" to "there's no explanation for their success". And in the same breath you engage in magical thinking regarding cause of the popularity of the web (indeed, I would bet you aren't capable of mentally separating "the web" from implementation details like HTML, CSS etc). Creationism was highly "successful" for the longest time too. Bravo on looking an absolute fool.
Simple, because they have personally experienced better. They are tired of libraries, CSS/JavaScript compilers and hacks to try to drag old clunky technology into new paradigms.
>Do you not realise that means throwing away the entire web, and its history going back to the early 1990's? Backwards compatibility and platform stability are GOOD THINGS that we need more, not less of. Lest we perpetually build content for doomed platforms, and leave no mark, no history on the world.
the better course is evolution, not revolution.
Candles oil lamps, and torches were pretty good at providing light at night in the 18th century, then there came electricity and the light bulb, everyone slowly threw away their candles for something better. Many people tried to design better candles instead of switching over. Candles that would burn brighter and longer, candles that would not blow out as easily and did not put off as much smoke, but you know what? These were was mere evolutionary changes and could not "hold a candle" to the revolutionary benefits of the light bulb.
Sure it took a lot of work for people to take their oil lamps and candle fixtures off of the walls and ceilings. It was a lot of work to run wiring and put up new electric fixtures. But the time spent was an investment. Eventually it led to a lot better solution and a lot less effort in total.
You are one of these guys who was using and evolving candles and oil lamps. You just can't see the bigger picture.
These HNers who are not happy with still being forced to use candles are the real innovators... The technologists. You who are happy with the candle are merely paint and canvas artists.
Paint and canvas artists in the 80s and 90s started to scoff when computer art and graphics began to gain prominence. These artists lacked the skills to do art with new technology, and lacked the ambition and any passion which was required to learn something new that would have diversified their artistic talents. They had their tools and they didn't want new ones. Their opposition actually was a result of a fear of being displaced, they wanted to stay in their stagnated comfort zone.
Many web designers today are much the same. You want to make art with your old tools and are not really technologists at all, perhaps with new brushing techniques (JS libraries) in some instances, but never with any major evolutionary change.
This stagnates innovation, even worse you are actively supporting the suppression of choice because you are afraid that you may become obsolete in your complacence with the technology behind your art.
Do you not realise that means throwing away the entire web, and its history going back to the early 1990's? Backwards compatibility and platform stability are GOOD THINGS that we need more, not less of. Lest we perpetually build content for doomed platforms, and leave no mark, no history on the world.
the better course is evolution, not revolution.
Mozilla has been through every revolution, first hand. They know what they're doing.
edit: I'm flattered but please vote up the comments relevant to the actual post.