Earlier quoted context omitted.
Why is everything written in rust nowadays? Apart from the safety it provides.
That is like a big deal. Also speed.
>That is like a big deal
Why you think it is "a big deal"?
GitHub – nushell/nushell: A new type of shell
31–40 of 411 posts
Re: GitHub – nushell/nushell: A new type of shell
#32Earlier quoted context omitted.
Good package manager, broad ecosystem of packages, no header files, helpful compiler messages. It offers a good alternative to C++ for native applications.
Not to mention excellent support for algebraic datatypes and pattern matching.
ADT and pattern matching really does it. Older languages certainly have their pull and can do a lot but with many modern coders having an interest or even education in higher level mathematics, easily being able to do that will put you way ahead of the competition. Even the hyper-pure Haskell now runs its own ecosystem and has actual systems written in it.
Re: GitHub – nushell/nushell: A new type of shell
#33[deleted]
Re: GitHub – nushell/nushell: A new type of shell
#34Found this handy git cheat-sheet https://picc.io/p/xM2wenl.png
Re: GitHub – nushell/nushell: A new type of shell
#35Similar to "bourne shell" and "bourne again shell" aka bash
I can see the evolution now. "nushell". Next iteration: "nuer shell" (newer) or "renushell" (renew)
Re: GitHub – nushell/nushell: A new type of shell
#36Earlier quoted context omitted.
That is like a big deal. Also speed.
>That is like a big deal Why you think it is "a big deal"?
Why do you not? No memory leaks, no security issues stemming from such. No random crashes from memory misuse, no issues debugging the issues that exist. It's like a higher level language but lower. You get to do things your way, except when your way is fundamentally unsafe. The code is then easier to debug as it actually describes what's happening and issues are mostly algorithmic, while the application gets a massive boost in reliability and security.
Security is like the issue now, along with reliability. That's what people need and want. Rust offers that.
Re: GitHub – nushell/nushell: A new type of shell
#37I stopped reading at "rather than thinking of services and input as a stream of text", horrified. Why would we do that ? KISS !
Re: GitHub – nushell/nushell: A new type of shell
#38Need some description up front, not in the 5th section ("Philosophy" https://github.com/nushell/nushell#philosophy ). Some ideas: "powershell for unix", "structured pipes", "pre-parsed text", "small, useful, typed tools loosely coupled."
powershell for unix is ... powershell: https://docs.microsoft.com/en-us/powershell/scripting/instal...
PowerShell from Microsoft is looking too alien on Unix. Just looking at the syntax I already feel uncomfortable.
It's hard for me to criticize it because I haven't used it, but it looks like it was designed by a committee and overdesigned. I.e. it wasn't created from the need, like someone at Microsoft wanted to automate his work and created PS to solve his problem. It looks like some boss decided: "They have shells, so we should have it also. But we will make it much cooler. So, let's gather a committee of 500 of our best managers and let's decide what features it should have".
It looks artificial and inconvenient to me unlike Unix shells. Maybe I'm wrong. But I'm pretty sure that even syntax of PS makes it harder to type the commands. Unix commands are very short (many are 2-4 letters long), all lowercase and do not contain characters which are hard to type (e.g. `-`).
Re: GitHub – nushell/nushell: A new type of shell
#39I wonder if this could be accomplished in a more general way with a fourth standard file descriptor for structured data. stdjson basically.
Re: GitHub – nushell/nushell: A new type of shell
#40I stopped reading at "rather than thinking of services and input as a stream of text", horrified. Why would we do that ? KISS !
By the same reasoning: Would you not use databases because they have a schema? or JSON...? Heck, even utf-8 could be too complicated.