And that's where I closed the page. Though the ideas are nice.
And that's where I closed the page. Though the ideas are nice.
Electron is a memory-hog and I see how the trade-offs it does wouldn't suit an application which is likely to keep running in the background with multiple instances, and stating that would be much more constructive IMHO.
Let's hope author/poster doesn't close the HN tab immediately after seeing your comment :)
Who these "us" you are referring to?
As the old saying went back in Fido/BBS times - "unlearn to speak for everyone".
"Us", here, refers to the HN readers.
> As the old saying went back in Fido/BBS times - "unlearn to speak for everyone".
I didn't say that we all thank the author. In that sentence, the person who is thanking is me, let alone the whole thing being a figure of speech.
But I really don't see much potential in Electron for any kind of heavy app. And even if it was acceptable, I'd still prefer it to be native.
Well, what I implied was: I don't think this will go anywhere as long as its tied to Electron.
It might be OK for exploration of the UX space, but not for any kind of practical everyday terminal replacement (and I've used the one in VS Code).
Also, if it's that obvious, why are there many people up-voting this and even then, why would you keep stating the "obvious"? Do you think the scenario you described, written as a "how to blend..." article, would attract attention here?
Just because something is obvious, doesn't mean people also consider it obvious.
So, one reason to "keep stating the obvious" is to inform those people.
A blender that emitted harmful radiation would be unsuitable for anything too.
Electron is to semi-technical+ users as Beats headphones are to audiophiles.
I think it is a blender that does same thing what most other blenders do but consumes 10 times more power. However it comes in 100s of colors so cool people like this innovative product.
It also appears to take over lots of the autocomplete/history functions from BASH, which also means it will either not play nice with ZSH or carry over that functionality when used with ZSH.
Going over the screenshots there also appear to be a bunch of hand populated options/descriptions(unless it's auto filling based on man) which would take away a lot of the modularity.
Also, it appears to be coded in Node and the Read Me mentions Visual Studio, and REE M$ and all that comes in.