News for hackers. Stuff that matters.

A comment on Curl’s backdoor threat. Parent comment

Re:Curl’s backdoor threat by pdimitar on Tuesday September 12, 2017 @09:36AM (#15227146)
Me over-reacting is most likely true. Been dealing with people dismissing unquestionably life-improving tech for far too long lately.

Sorry.

I do believe most of Linux userland has to be rewritten though. Be it Go, Rust, Nim, D, doesn't matter much as long as it's a memory-safe language.

[ Parent | on HN ]
Re:Curl’s backdoor threat by moxious on Thursday September 14, 2017 @03:40PM (#15251796)
> I do believe most of Linux userland has to be rewritten though

Why? I'm sympathetic to the argument that 2017 computing shouldn't be on the basis of 1970s UNIX limitations and mindset, but changing that would require a lot more than just rewriting the user land applications, and would require a bigger re-think.

But assuming that the shell's functionality is OK as it is, what's to be gained in a re-write?

[ Parent | on HN ]
Re:Curl’s backdoor threat by pdimitar on Thursday September 14, 2017 @07:45PM (#15253431)
For one thing, piping being mostly text-friendly is limiting in many scenarios I stumbled upon. A modern shell should allow arbitrary objects to be piped and processed, much like the functional programming paradigma. The UNIX idea was and still is wonderful, but we're past the text-only thing.

In any case, I feel (and I don't have tens of facts, I admit) we're dragged by the past for far too long. Others have documented their gripes with the current incarnation of Ops / sysadmin problems much better than I could. Here in HN (but I think years ago).

[ Parent | on HN ]