4 ms·
I disagree with the first part (they are real developers!), but agree with the second. We have grafted an application platform on top of a document delivery pla
by icedchai 7y ago
I disagree with the first part (they are real developers!), but agree with the second. We have grafted an application platform on top of a document delivery platform.
- amiga-workbench 7y agoI should probably rephrase that part, because yes you are right, they are real developers. But there is this misunderstanding that what they do is simple and it couldn't be further from the truth. So off they go and try to prove that perception wrong by piling on the complexity.
- adt2bt 7y agoI don’t think added complexity is a ‘feature’ us front end devs strive for. Instead, there are a lot of useful UX abstractions that are increasingly expected by users and are becoming extraordinarily tricky to roll on your own. Yeah there’s tons of extra crap, but the 8000+ projects in most node_modules has become more or less the standard library for that projects developer. It’s nuts, but JavaScript is the Wild West so it’s what we deal with.
- buboard 7y agoi think it is more likely that "real" developers who started working as web devs missed the hierarchical ecosystem and built up one out of straws. Of course, that's a cargo cult.
- adt2bt 7y agoWhat would an application platform look like that isn’t a ‘document’ delivery platform? In my opinion, the ability of your browser to be essentially the OS of the web was responsible for the second great explosion in usefulness of computers (the first being the PC itself). Mobile apps were the third, but it’s unclear to me if there’s any benefit to rewriting many (most?) web applications as desktop applications. Discoverability, complexity and debugging costs all go up in such a world.
- icedchai 7y agoIt's hard to imagine given we've been stuck in this world for so long. However, I have to believe there is a better way. Building an app with HTML/CSS/JS just feels like a mess. I'd start by looking at some good ideas from the past... Sun NeWS perhaps.
- ng12 7y ago> We have grafted an application platform on top of a document delivery platform. The problem is this is incredibly valuable and we have no good alternatives. There is simply no better format for deploying applications than the web.
- BlueTemplar 7y agoThere is: it's the Internet. Also, native applications aren't crippled...
- ng12 7y agoHave you ever tried to support a native application? There's a reason why the web is the preferred mode of delivery over the internet.
- BlueTemplar 7y agoSure, I do. And it doesn't seem that people that still have to support Internet Explorer have a much easier time considering that they seem to have settled on using a whole additional layer of abstraction !
- icedchai 7y agoIt really comes down to ease-of-updates. Web apps are trivial to update. No build / cross-platform / deployment issues that you encounter with native apps.
- BlueTemplar 7y agoUpdates are a problem that has been solved decades ago by package managers ?
- icedchai 7y agoVelocity of updates is also important. If I update a package, it can take weeks, months... maybe years... before end users update. If I update a web site, it's instantaneous.
- buboard 7y agothere is a UI framework on top of a document platform, running on a VM inside a browser program running in a sandbox of a host operating system . Occam would be furious, and i think this extreme duplication of UI functions is bad for the environment, bad for the users' nerves and bad for the MTBF of computers.