7 ms·
Holy freaking crap that's amazing. I love how the video all of the sudden starts to show 9000 features/ways it can be used. Looks like the paradigm adapts well
by azinman2 12y ago
Holy freaking crap that's amazing. I love how the video all of the sudden starts to show 9000 features/ways it can be used. Looks like the paradigm adapts well to many different common workflows.
It's really great to see someone really thinking from scratch about the shell -- something that very rarely goes through any meaningful changes like this. I hope this project goes far and becomes the new default.
- shurcooL 12y agoYeah, reminds me of https://twitter.com/korkyplunger/status/485729264432472065 https://twitter.com/korkyplunger/status/485729264432472065.
- noinsight 12y ago> It's really great to see someone really thinking from scratch about the shell Arguably, PowerShell is shell reinvented too. But IMO someone definitely should revamp the Unix shell. If we're not talking about the actual functionality (commands etc.) but the "building blocks", I actually like PowerShell more than traditional Unix shells at this point. This shell however fails to impress me, I don't see the point.
- DanBC 12y agoWhat features would you like to see in a Unix-like shell that are not available?
- Tomte 12y agoI think passing around real objects instead of character strings is cool. It's less brittle, and you don't have to have an ad-hoc and flawed parser at every step.
- copperx 12y agoSo, shell commands that produce and consume JSON?
- skrebbel 12y agoNo, objects. Non-text. Real data. Plus methods. Read a PowerShell primer to better understand this. PowerShell is geniusly designed and horribly implemented, so there's little point actually using it, but UNIX could really really use some of its ideas.
- sigsergv 12y agoIt's impossible to “redesign” shell fundamentals in Unix because it will be incompatible with all other old-style utilies. And classic pipes are not so bad as PS evangelists saying. PS “objects” are basically .Net objects and you can't easily write python or perl applications compatible with PS features.
- coldtea 12y ago>It's impossible to “redesign” shell fundamentals in Unix because it will be incompatible with all other old-style utilies So? For one, you could redesign the basic utilities too. Or offer a sumplementary revamp versions of some. Second, you could use them in a less capable "text mode" and still get all the other benefits from the new shell. >And classic pipes are not so bad as PS evangelists saying. Well, they are not that relevant to 2014 either.
- skrebbel 12y ago> It's impossible to “redesign” shell fundamentals in Unix because it will be incompatible with all other old-style utilies. This is not true. In fact, despite its many flaws, PowerShell did solve this particular one: any object stream can also be rendered as a string. This is exactly what happens when you just type `ls` into a PowerShell window. I can completely imagine that a UNIX `ls` implementation would return a stream of objects (not necessarily .NET objects - just some runtime's native object format) that, when called .toString() on, would return exactly the same textual output as common UNIX `ls`. Then, you'd need a way to differentiate between two pipes. Maybe with syntax (i.e. | for string pipes, [] for object pipes, whatever) or maybe through magic ("hey, these two processes both have the capability to pipe objects instead of characters, let's tie them together as objects" somewhere at the shell level). I'm not sure how feasible either are, but I'm sure you can imagine that this problem could be solved. Then, if the shell sees that whichever process accepts the output of `ls` doesn't understand objects, just text, then it calls `.toString` on every object and renders that to oldschool character stdout.
- csandreasen 12y agoSomething like a Python/Ruby/whatever REPL with shell functions? Something like 'ls' would return an array of objects describing files, like: def name(text): return lambda file: file.name.find(text) > -1 ls().filter(name('.txt')) but less clunky?
- lloeki 12y ago> Something like 'ls' would return an array of objects describing files You probably think of type-safe pipes similar to Go channels.
- spacemanmatt 12y agoI was actually thinking I'd like a Go-like CLI. Realistically, I probably more want to convert a couple shitty shell scripts into proper Go programs and keep on using bash where it is appropriate.
- deleted 12y ago[deleted]
- skj 12y agoksh allows you to define and return types - their declarations are very close to those of C++.
- Rapzid 12y agoAs someone who thinks powershell and objects are really great.. Until you want to create a firewall rule with a principal exception using the docs: http://technet.microsoft.com/en-us/library/jj554906.aspx http://technet.microsoft.com/en-us/library/jj554906.aspx. :|
- Already__Taken 12y agoI love PS too but creating a new ACL is very sucky too. I think PS is so good it exposes the really shit bits MS built decades ago but covered up with a pretty UI. I'm sure they'll eventually make a pass over these crap parts and refactor them. This must be what they mean by an API driver vs Text driven OS. At least anything nix you just have to spit out a text file and you're good.
- anko 12y agoThis reminds me of ACME http://en.wikipedia.org/wiki/Acme_(text_editor) http://en.wikipedia.org/wiki/Acme_(text_editor). To me it doesn't look like something new at all. The cool thing about this project is it doesn't interrupt how you use your mouse. Using acme makes you learn how to use a mouse again like going from vim to emacs makes all your keybindings screw up. Not that i'm saying copying acme is a bad thing, that editor is really underated.
- biftek 12y agoI played with Acme the other day and was blown away. The everything as a command idea is really powerful. Definitely underrated, would be great if it got a modern reboot. For the unfamiliar this video by Russ Cox covers it pretty well. http://research.swtch.com/acme http://research.swtch.com/acme
- claar 12y agoActually, that's exactly where the video lost me. A few additional shell capabilities? I'm interested -- cool! But throw in a database editor and a million other unrelated-to-the-shell features? I've been down that road before, and it's a maintenance nightmare. Unless this project has huge community backing, it seems inevitable that the development resources will be stretched too thin. Then it won't work on my next computer and the bug report will sit in the queue for months while I return to bash. I don't think I want to play this game.