Writing an OS in Rust: Returning from Exceptions

Re:Writing an OS in Rust: Returning from Exceptions by pjmlp on Thursday September 22, 2016 @08:53AM (#12556446)

Because most UNIX users see only this:

http://pubs.opengroup.org/onlinepubs/9699919799/

Everything else is fluff, and could stay just like it was on UNIX System V.

Hence why for macOS, iOS, tvOS, Android and ChromeOS, having an UNIX kernel is just a matter of convenience, given their application models and programming languages.

Apple and Google could eventually migrate to something else as kernel while keeping their Objective-C, Swift, Java and JavaScript APIs.

NeXT based NeXTStep on UNIX as a door into the then new UNIX worksations market, but it never had a CLI culture like the other UNIX vendors.

GUI workflows like on Xerox PARC were always important to Steve.

[ Parent | on HN ]

Re:Writing an OS in Rust: Returning from Exceptions by DblPlusUngood on Thursday September 22, 2016 @09:11AM (#12556552)

I don't understand you.

Is your answer to my question: "Modern UNIX OSes cannot take advantage of said ideas because they are POSIX compatible."?

[ Parent | on HN ]

Re:Writing an OS in Rust: Returning from Exceptions by pjmlp on Thursday September 22, 2016 @10:42AM (#12557093)

No, my answer is that the UNIX clones only bother to achieve POSIX compatibility and POSIX doesn't provide anything related to GUIs.

So, each UNIX clone project ends up replicating POSIX and doesn't move beyond what is actually yet another TWM clone with pretty graphics.

GNOME, KDE, Unity are the only ones that try to somehow modernize the experience and tend to get pretty vocal pushback.

The UNIX culture, is the culture of the command line and something like XFCE is probably the GUI a TWM user is willing to accept to manage its XTerms.

[ Parent | on HN ]