[arcticwombat]

How did it get go this?

Well that's what you get when the "solution" is to embed a webserver, a browser, a native executable to show that browser, and the server runs Node...

The solution is simple, stop shoving square pegs in round holes, and learn an appropriate language rather than shoehorn JS everywhere.

[bdcravens]

> learn an appropriate language rather than shoehorn JS everywhere.

Being that this app's sole purpose is to evaluate JS, this may be a situation where JS isn't being shoehorned

[arcticwombat]

By the looks of it, only the console (Or equivalent) is used for output, so bundling an entire browser seems way overkill for the output.

There's plenty of ide-libraries in other languages to replace the one used by runjs.

[bdcravens]

You'd still have to bundle a JS engine. Presumably you could build a traditional UI app and include V8, but I still think this isn't a bad use case for Electron (but I agree there are many apps where it isn't the best choice)

[arcticwombat]

I'd imagine that the browser is the resource-heavy part of the application, Nodejs doesn't use hundreds of mb's of RAM in my experience, at least not while doing very little background work.

To me it would make sense to build a real desktop application and bundle whatever JS engine you want to use, pipe and process the output as any other application.

You'd end up with a much smaller application (Download size), more resource-efficient, and less reliance on things like the bundled browser.

[qudat]

> You'd end up with a much smaller application (Download size), more resource-efficient, and less reliance on things like the bundled browser.

None of these things I care about. I care about whether or not it serves a purpose to me. If it does, I'll use it. If it doesn't, I won't. You might have other priorities and that's your prerogative.