21–30 of 231 posts
While it was thinkable all the time, it renders me speechless, that finally somebody has put that stack under a terminal. The next big thing will be electron-based smooth-scroll, mouse-animation and finally: a 70mb beep.
I also don't get it. Why would I want a full web browser to power my terminal? Just because we can, doesn't mean that we should...
Pop quiz: what's more ridiculous, nodejs based command line utilities that do the same thing as two existing shell utilities and a pipe or a while loop etc; OR, an electron "shell"... which can then run those same nodejs "utilities"... Oh maybe that's the whole point. They want "it's javascript all the way down". I think I'd literally rather use a shell built on actual turtles. A turtle-shell, if you will.
...god of bloated software and goddess of complex solutions of simple non problems got their blood sacrifice and the sun will rise again.
While it was thinkable all the time, it renders me speechless, that finally somebody has put that stack under a terminal. The next big thing will be electron-based smooth-scroll, mouse-animation and finally: a 70mb beep.
Pop quiz: what's more ridiculous, nodejs based command line utilities that do the same thing as two existing shell utilities and a pipe or a while loop etc; OR, an electron "shell"... which can then run those same nodejs "utilities"... Oh maybe that's the whole point. They want "it's javascript all the way down". I think I'd literally rather use a shell built on actual turtles. A turtle-shell, if you will.
Its a clear example of "We can do it but should we do we?" The answer is NO!
While it was thinkable all the time, it renders me speechless, that finally somebody has put that stack under a terminal. The next big thing will be electron-based smooth-scroll, mouse-animation and finally: a 70mb beep.
I'm just waiting for an electron based web browser.
Maybe I'm missing something... is there a benefit to this over a normal terminal/terminal emulator? (eg xterm, mac terminal etc)? As far as I can tell, putting it in electron would mean that you could embed arbitrary HTML structures inside the terminal (like web page previews or something), but from what I've read, it doesn't look like that's the goal.
Pop quiz: what's more ridiculous, nodejs based command line utilities that do the same thing as two existing shell utilities and a pipe or a while loop etc; OR, an electron "shell"... which can then run those same nodejs "utilities"... Oh maybe that's the whole point. They want "it's javascript all the way down". I think I'd literally rather use a shell built on actual turtles. A turtle-shell, if you will.
The whole electron stack disgusts me. Mainly because of battery usage on my laptop and my phone! Its a clear example of "We can do it but should we do we?" The answer is NO!
Pop quiz: what's more ridiculous, nodejs based command line utilities that do the same thing as two existing shell utilities and a pipe or a while loop etc; OR, an electron "shell"... which can then run those same nodejs "utilities"... Oh maybe that's the whole point. They want "it's javascript all the way down". I think I'd literally rather use a shell built on actual turtles. A turtle-shell, if you will.