TermKit + HTTP
Loading...
36,225
Loading...
Uploader Comments (unconed)
Top Comments
-
Amazing! Cant wait to use it..
-
@tiagotrinidad Because maybe the PDF is a status overview of your server farm, generated with a vector tool.
see all
All Comments (31)
-
It is termkit, bitches :D
-
enjoy your aids, hipster
-
How come someone develops something like this and just releases it for the mac... that's just stupid.
Put the first release on linux where it would be used most and then make it cross-plattform compatible
-
... too much information
in other words, this demo doesnt show much actual workflow improvements.
Something like typeing helper context menus would be nice, but
I can't see why I would like to watch pdf inside of my terminal.
-
BURN THE HERETIC!
-
What the fuck is this shit
Loading...
I think it's a great idea.
But it's incredibly stupid to do this using web technologies. Sorry.
dziltener 9 months ago 2
@dziltener Node.js is not a "web technology" per se. It's a JIT VM with excellent asynchronous Unix bindings and networking. As for the front-end, you could re-implement it in GTK, QT, or any other toolkit if you wished. But it would simply be easier to embed the WebKit control everywhere. It runs on Windows (.NET TermKit now exists), Linux (QT, GTK, ...), Mac, Android, iOS, etc.
unconed 9 months ago
@unconed actually I don't understand why you didn't used v8 without nodejs
the result is pretty amazing by the way :)
fraev 9 months ago
@fraev Because node.js comes with a standard library that interfaces traditional Unix with V8 in a very awesome way. Child processes, asynchronous file I/O, networking, buffers, etc. TermKit would not be TermKit without node.
unconed 9 months ago
This is so dope. Can it run on Linux?
MuncherOfSpleens 9 months ago
@MuncherOfSpleens In theory, yes. It's 99% WebKit and Node.js. Can run in a browser, but it needs something to provide OS services like icons.
unconed 9 months ago 2