Live data from Hacker News

Electron considered harmful

drewdevault.com

221–230 of 256 posts

Re: Electron considered harmful

#221

Earlier quoted context omitted.

That's true, but I don't see anything in that list that needs to use multiple hundreds of MB of RAM. To witness, we had GUI apps in 1995. They look a bit nicer these days, but not multiple-100-MB nicer. :)

Emacs is far older than 1995 and still eating 250Mb :)

And there was a time when "Emacs" expanded to "eight megabytes and constantly swapping". :)

Re: Electron considered harmful

#222

Earlier quoted context omitted.

Dropbox itself takes 200Mb and its a simple python app. Google drive takes 300Mb. VSCode takes about 100Mb of ram with a project opened right now. Even my Emacs takes 250Mb and I literally live inside it. All of them have at least 2Gb of virtual memory being mapped to them. Yet I still have 9Gb of free ram. If you want to go against bloat, you might just as well uninstall every single software from your computer, inc…

>VSCode takes about 100Mb of ram with a project opened right now. I call bullshit on that one.

I currently have VS Code running with 7 files open, and it's using 83Mb. Like a browser, I imagine the RAM goes up with each tab, so it all depends on how many files you have open.

Re: Electron considered harmful

#223

Earlier quoted context omitted.

>Electron allows the world's most popular layout system (HTML+CSS) to be used with one of the world's most popular programming languages Just wanted to name the most obvious alternative: embedded browser component like QtWebKit, which allows to code most of the application logic on the language of your choice. Embedded browsers are the way people have been doing it since circa 2000 (by then, Windows was dominating pl…

I'm fairly certain electron could easily be modified to be installed once and used as the launcher for its applications. I'm also fairly certain we'll see this in the future. Therefore all claims that electron bloats 200Mb are just temporary. Its still a relatively young technology with huge potential (which also means huge potential for misuse!) I spent 5+ years writing native GUI apps in half a dozen frameworks, I…

Didn't Chrome already used to have that feature where you could install an application and it would put an icon on your desktop and open it in a browser window without tab/url bar?

Re: Electron considered harmful

#224
post #3

This had me for the first half, where the author walks you through the 'case study' applications that offer minimal functionality despite shipping with an entire browser inside. But then the essay turns into a rant. It's 2016, people, the ship has sailed on pretending JS isn't a real programming language. Phrasing the argument the way he does just betrays his smug elitism. The fact is, for many types of applications,…

On the topic of tiny apps that shouldn't need electron, I found another one - catlight.io

This is a status bar icon that notifies you when your build is broken. Cool idea, but what the heck does it need electron for?

http://catlight.helprace.com/i15-why-is-setup-so-big

Electron is useful for some cases, but this is not one of them

Re: Electron considered harmful

#225
We need to stop reading such posts. "Everything sucks because I say so". Technology is really fair. At the end we WILL use what matters the most and has the overall best tradeoffs. I don't like it when people use the expression "best tool for the job". Like you used every other available tool out there and you found the best one...no you haven't.

Re: Electron considered harmful

#226

Earlier quoted context omitted.

The only languages I can think that share those properties are Perl (5, don't know about 6) and the retired Visual Basic. There is more there than dynamic typing.

Not sure what I'm missing. Ruby? Python?

You are missing this part: nor are types associated with properties.

Ruby and Python do not fit it.

Re: Electron considered harmful

#227
post #187

Earlier quoted context omitted.

First, X-only programmers are obviously wrong, whatever is the value of X. That said, yes, somebody ought to love JS in a not blind way. Big numbers work that way. If that's you, I don't think those comments are for you. All languages have different flaws, every flaw relevance varies by context, and contexts are incredibly subjective. Yet, some contexts are much more common than others, and many people preach in supp…

I did C, C++, Java, PHP, VBA and JS and can't tell why so many people have constant beef with JS. I mean especially after all major platforms have adopted ES2015.

For me, IO in JS is still kind of a hack. It still imposes an structure on my code that is different from the one I want.

Re: Electron considered harmful

#228

Earlier quoted context omitted.

Not sure what I'm missing. Ruby? Python?

You are missing this part: nor are types associated with properties. Ruby and Python do not fit it.

You can assign values of different types to the same property in those languages, no?

Re: Electron considered harmful

#229

Earlier quoted context omitted.

What are your problems with Qt? I was using PyQt, and I found it nice (Qt's integration is good).

C++ Qt, I've found, is an entire separate beast. It goes out of its way to not rely on the STL, so that std::string and QString are separate, non-convertible classes. QList and std::list are the same, same for QMap and so on and so forth. So data communication is already a pain. We then have further issues with function invocation. Slots and sockets are simple with python, because functions are first-class in python.…

When having to deal with compilers that barely support a mix of C++98 and C++03, Qt is quite good.

STL wasn't always here and still isn't in some embedded platforms.

Re: Electron considered harmful

#230
post #187

Earlier quoted context omitted.

I did C, C++, Java, PHP, VBA and JS and can't tell why so many people have constant beef with JS. I mean especially after all major platforms have adopted ES2015.

For me, IO in JS is still kind of a hack. It still imposes an structure on my code that is different from the one I want.

IO in what? The browser? Node? If you mean node, what IO specifically? `http.createServer`? `fs.readFileSync`? `fs.createReadStream`? `fs.open`? `fs.readFile` with node callbacks? Promises? Streams? Observables?

Without context it sounds like you saw a bunch of nested callbacks in a Node.js example and judge the entire language based on that.

Post reply on HN