3 ms·
What's the point of POSIX if most of the applications won't compile on it?
by emodendroket 9y ago
What's the point of POSIX if most of the applications won't compile on it?
- loeg 9y agoI mean, I proposed a unix-alike written in a safe language as an alternative to OP's proposal, which was to "kill Unix." What would OP replace Unix with? Windows and Mac OS aren't suitable; they're written in C/C++ too. So any solution here must be a green field, from-scratch OS in a "safe" language. Any operating system written in a non-C language with no C support is going to break all existing C applications. This is inherent to OP's desire to remove all C. For the record: I'm opposed to removing all C. So why not preserve unix-like shells, filesystems, devices, commands, etc? None of those are tied to language of implementation. Potentially existing unix shell scripts could run safely on a purely non-C system. Sysadmins would carry over some familiarity from existing Unix-alike systems. That has some value.
- emodendroket 9y agoIf we're starting from scratch something like Powershell would be way nicer
- loeg 9y agohttps://en.wikipedia.org/wiki/Usage_share_of_operating_systems#Public_servers_on_the_Internet https://en.wikipedia.org/wiki/Usage_share_of_operating_syste... Unix servers make up 68-98% of the internet, depending on who is measuring. There's a huge body of sysadmins familiar with shell who are not familiar with Powershell. So that's exactly my point: I don't think we should start from scratch on things like the Unix shell, filesystem hierarchy, devices, etc. People know them. Throwing out systems people already understand for no reason is a huge anti-pattern. If you think Powershell is superior, port it to Unix and convince Unix sysadmins to use it. I don't think it's going to be very popular.
- emodendroket 9y agoIt's always going to be a second class citizen on Unix, so there is little advantage to picking it up (it's available on Linux already). But in fact, for one thing, Powershell makes a lot of concessions to people with experience in both bash and CMD (for instance, ls, wget, and dir are all built-in aliases, you could probably go a while without realizing pipes work differently, etc), and, for another, by the time you're worried about this kind of thing I can't see why you're trying to make a clean break at all. Once you've learned how it works having an object oriented shell is game changing. Powershell isn't necessarily the ideal implementation but I'm just calling attention to it as an existing, popular example of something better