Hacker Newsnew | comments | show | ask | jobs | submit login

How about Rube Goldberg Virtual Machine of the web? I don't see what people are so happy about.

It looks a bit like the thing that happened with XML. In years 2000-2005 developers got really, really excited about XML, and started to use it for everything. Everything, including things that it was never meant for. And yes, the resulting technologies worked (kind of), but they caused more problems than they solved. SOAP/WSDL. XSLT. All that XML-to-SQL-query stuff.

Right now people are really excited about JavaScript and begin to use it for things that are less and less appropriate for it. Yes, you can compile languages into JS, just like you can use XML to generate an SQL query. But is it really a good idea?




The analogy fails because using XML is, often, a choice. You can't get around JavaScript if you want to make a decent web app. The platform dictates it.

-----


The analogy works in the way that maybe sometimes you shouldn't do a web app but a native client. I don't agree with the conclusion but I think it's what he meant.

-----


We found out about it and started to look for alternatives to XML eventually. Hopefully, if the world does come to believe that compiling to JS is an unnecessary layer of abstraction, we'll have enough force of change from browser vendors to actually implement a lower-level change. At least with XML, we were free to change whenever... in-browser technologies isn't going to change without a concerted effort from just about everyone involved in browsers.

-----


I presume you are talking about CoffeeScript and not something like GWT. The thing about it is that it is not really a layer of abstraction. Just consider an alternative syntax for javascript. The javascript that it produces is really readable.

-----


Just curious, can you give some alternatives to XML? for example like JSON etc.

-----


There is no single alternative to XML, and I don't want to say that all XML is bad. But it's very commonly misused, because someone, somewhere tried to solve the wrong problem and XML happened to be the "default" solution. So, really, the alternatives depend heavily on the context.

What I've seen personally often involved overly complex SOAP/WSDL services for things that could be accomplished with a simple HTTP request. Look at query prams, return the correct HTTP code and you're done.

Another common pathology is problem over-solving. Instead of writing a library to solve some problem and providing a sensible API, people write the library, hide it, then write an XML "driver" that consumes a custom-designed language encoded via XML tags. The alternative in this case is simply providing the original API.

-----




Applications are open for YC Winter 2016

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: