The author is fighting a strawman. Rather than engage with the specific problems these solutions were built to solve they dismissively regard them as just flavor of the week trends purely for the sake of chasing newness. This is true of the entire post, but I'll tackle just one since it's emblematic of my issues with all the rest: The argument for Electron and React Native isn't "it's modern", it's "it's much cheaper…
> The argument for Electron and React Native isn't "it's modern", it's "it's much cheaper". I'd argue it's not cheaper overall, just for the company choosing to do the development. What I mean is, the lost productivity of waiting around for slack to load a channel is essentially outsourcing this cost difference via poor performance.
Is the madness ever going to end?
311–320 of 629 posts
Re: Is the madness ever going to end?
#312No it probably won't end. No you are not a dinosaur, but development has changed. Decades ago you could build an app from the ground up. This gave you a bunch of different layers to compose, and probably made the app overall simpler. Now most developers are given a box to create their feature in whether it's a Spring Bean, a React Component, or a serverless function, with an entire application stack under it. You cou…
That's a great perspective, but are those peeps writing the unused frameworks just wasting their time to solve a question nobody has asked? Take the D language, it's basically a poor man's Java, with a shoddy garbage collector and aspirations at being C/C++... Is that the work of heroes or the misguided?
Like, just about the only thing D has in common with Java is their shared C syntactic heritage, and an object model with single inheritance. But that also describes numerous other languages.
Re: Is the madness ever going to end?
#313Earlier quoted context omitted.
I've been out of the GUI scene for a long time, but I will say I've been hella-impressed with some of the more modern Qt tech. QML gives you JS for the view layer (and some logic if you desire), and a declarative way to lay out your UI. I think it's worth a comparison as a reasonable way to quickly iterate on a UI while having something very lean and portable as the output product.
Wait, isn't Qt proprietary? I feel like that kind of vendor lock-in alone disqualifies it for a lot of use cases... There seems to be a dearth of actually open, native, and cross-platform GUI toolkits.
Re: Is the madness ever going to end?
#314The unfortunate side effect is that capable developers aren’t usually interested in solving simple problems inefficiently. So you won’t find them applying to your jobs.
Re: Is the madness ever going to end?
#315Earlier quoted context omitted.
> HTML/CSS/JS is literally a 10x improvement in iteration speed versus native. When you need to release your application across multiple platforms? Yes. Not much else even begins to compare on that front. Compared to native development on a single platform? Not even close. HTML/CSS/JS development is painfully slow in comparison.
> Compared to native development on a single platform? Not even close. HTML/CSS/JS development is painfully slow in comparison. I find it's often not, largely because the amount of focus on web apps means the native frameworks often are less productive by comparison than what is available for the web.
Re: Is the madness ever going to end?
#316Earlier quoted context omitted.
> These aren't engineering decisions, they're business decisions All engineering (including "real" ones like civil or mechanical) is about fitting your requirements within budgets. When one's building a skyscraper, you try to build it in a way that minimizes the cost while satisfying all requirements (it shouldn't fall down given such and such conditions, etc.) Engineering is largely the art of solving problems that…
If HN had an equivalent of Reddit Gold, this comment would deserve a couple of them. Engineering without constraints is easy, but it's not engineering.
Re: Is the madness ever going to end?
#317Earlier quoted context omitted.
> Slack, Spotify, Discord All those examples could or do work just as well as web apps, right? I don't think that's the authors message, but I'd rather have those type of apps be web-based instead of electron-based or native.
They are web apps... open.spotify.com, discord.com, app.slack.com. Even vscode.dev. The desktop product is just a repackaging of the web app with perhaps more OS integrations. If you don't want the OS integrations, use the web app. Some are available as a PWA too, which provides a nice middle ground.
Re: Is the madness ever going to end?
#318What I don't get about the rant is why it matters what the "modern" way is. It's not like any of the old tools have disappeared right? If you don't like Electron/NW, nobody's stopping you from building native apps with Qt, GTK, or you can just draw your own UI raw! If you don't like frameworks with their own templating systems, maybe don't use them? I don't like them either! and yet rather than complain I just don't…
As the end user of those "native" web-repackaged apps, the experience is just subpar. Give me back my native widgets and consistent UX.
Re: Is the madness ever going to end?
#319I don't understand how can you diss Electron when you see something like VS Code or Atom. The benefits are clear. This software could grow plugin ecosystem vastly exceeding anything that was previously possible even after pouring millions of dollars into it. Electron is better than everything else by various engineering metrics. Just not RAM or CPU usage. And despite large RAM and CPU usage it manages to be way faste…
Because you also see things like https://github.com/microsoft/vscode/issues/22900