News for hackers. Stuff that matters.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by bluetomcat on Friday May 03, 2019 @12:25PM (#19819764)
We need entirely new OS abstractions to replace the dated notions of hierarchical file systems built around the metaphor of file cabinets, I/O as streams of bytes, terminals, process hierarchy. Essentially, say goodbye to the Unix model after 50 years. It would open up an entirely new world of software experimentation and craftsmanship.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by sytelus on Friday May 03, 2019 @12:39PM (#19819926)
I am doubtful if hierarchical file systems have anything to do with slow disks. It a design pattern that you encounter all over in real life for human mind to manage large quantity of information. Using tags is another pattern but with its own pro and cons. Same goes for I/O steams, process hierarchy etc. There may be better designs patterns out there but I don’t see why these existing design patterns would become obsolete even if disks become as fast as RAM.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by AnimalMuppet on Friday May 03, 2019 @01:12PM (#19820219)
Then... what? Do you have a positive to recommend, or just "not what we've been doing"? (It's not necessarily bad if you don't - when you're doing the wrong thing, the first step to improvement is to stop doing it.)

But it seems to me that much of this can be done within the existing structure. You don't want I/O as streams of bytes? Great. Whatever new thing you think it should be, you can build that on streams of bytes. Knock yourself out. (It may not be as fast as it would be if it were directly supported by the OS, but you can prove the value of the concept by building on top of the OS.)

Same thing with the metaphor of file cabinets (I presume you mean the hierarchical file system.) Well, does your OS let you read and write raw disk sectors? No? Fine. Create one giant file that takes up the whole disk, and manage it yourself. Try out whatever different way of managing that space that floats your boat. Again, it will be slower, but again, you can experiment and prove out your concepts right now. You don't need to wait.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by garmaine on Saturday May 04, 2019 @12:00AM (#19824358)
E.g. use the relational model for data storage instead of files (SQLite is a purposeful step in this direction).

Use a single system image with no distinction between network, processor, or core communication unless needed.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Spivak on Friday May 03, 2019 @12:48PM (#19820014)
What would you replace it with? At the very core you need two things: the notion of a unit of data and some metadata to address it. To be as flexible as possible that unit of data would probably modeled as a sequence of individually addressable bytes but it could be more structured. Such a thing is dangerous because if your structure isn't sufficiently expressive 20 years down the road people will end up imposing their own structure on top of obj.binary and there goes all the work.

Once you have data and handles to access it you might start wanting some convenience features like access control, locking, namespacing, constraints, relationships.

I don't disagree that we can drop many of the current filesystem semantics but fundamentally all that really means is changing is the query language to access objects and manipulate their metadata.

I also don't disagree about process hierarchy. Being able to express relationships between processes beyond parent-child natively without farming out to an external scheduler would be awesome.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by stcredzero on Friday May 03, 2019 @01:09PM (#19820192)
What would you replace it with? At the very core you need two things: the notion of a unit of data and some metadata to address it

There were some experiments along these lines. Instead of files, just make everything an object and have orthogonal persistence for every object. In a way, this was what the early Smalltalk implementations were working towards.

I don't disagree that we can drop many of the current filesystem semantics but fundamentally all that really means is changing is the query language to access objects and manipulate their metadata.

One thing which Smalltalk demonstrates, is that the query language can simply be the same language used to implement the OS. Activity which looks a lot like database querying, but for objects, not database rows was just an expert level debugging trick of Smalltalk programmers.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by scroot on Friday May 03, 2019 @12:57PM (#19820089)
Object systems
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by silversconfused on Friday May 03, 2019 @01:49PM (#19820591)
Ok, but what does the level below that look like?
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by scroot on Friday May 03, 2019 @02:20PM (#19820893)
I'm not sure there has to be a lower level at all, aside from asm and machine language
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Spivak on Friday May 03, 2019 @02:49PM (#19821166)
Okay so you have a device driver that exposes your underlying hard disk as a single contiguous segment of blocks of a given size. You have objects which are blobs of heterogeneously sized arbitrary data with an addressing scheme.

The software that marries these two things is basically a filesystem driver (in that you can implement filesystem semantics on top of it -- hell Ceph does it right now).

Nothing about a modern Linux/BSD system really stands in the way of doing this.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by scroot on Friday May 03, 2019 @03:21PM (#19821417)
Of course, you need some agent that can communicate with the hard disk and that knows how to manage memory. Maybe its one driver, maybe its several, but these can also just be objects. Live objects, I mean. Not just blobs of data, but actors that have behaviors and are always "running." You don't even need the concept of files or filesystems. And if you do, better left to a higher level
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by laughinghan on Friday May 03, 2019 @05:02PM (#19822247)
Isn't the whole point of persistent storage like hard drives to deal with the fact that computers shut off sometimes, and nothing can be "always 'running'"?

Something below the object level (possibly part of the object system, possibly a layer below that) needs to read from disk and bootstrap all those agents/live objects/actors into existence.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by fragmede on Friday May 03, 2019 @08:48PM (#19823526)
The storage on disk doesn't have to be a traditional hierarchical filesyste,m for anything after the kernel is loaded (+drivers), as long as the kernel is able to recombobulate the agents off the block addressable storage device, it can store them however it wants. Simply serializing swaths of memory to/from disk may not be the most efficient, but that should show its possible.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by scroot on Friday May 03, 2019 @05:27PM (#19822449)
Well of course they aren't running when the computer is off. And yeah, you'd need something to bootstrap the system the same way you need a bootloader
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by olliej on Friday May 03, 2019 @01:25PM (#19820329)
...except humans instinctively organize things by hierarchies (even something as counting is done hierarchically).

Just saying “we need to change this” without saying what the short comings you want to address isn’t a super useful statement. Multiple platforms have attempted to have the user interface to their data be tag based, but that simply doesn’t scale for the amount of data people can manage with hierarchies.

Finally what the heck are you talking about in that last sentence: how does changing representation result in a new age of experimentation and (???) craftsmanship? Why is craftsmanship gated on the user level abstraction to bytes? Experimentation already happens today, what does this change?

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by fragmede on Friday May 03, 2019 @09:34PM (#19823711)
PalmOS had this! Applications connected to databases and read and wrote records. Sqlite acts similar for the more modern era, with a traditional hierarchical filesystem underneath the sqlite DB.

Looking at modern app-based "file" access using Google docs and its ilk are that reimagining. The UI is a list of recent files, a small number of features, and then a search box. There's not File -> Save, nor am I forced to pick using a folder metaphor, where I want to put it.

That there's (likely) an underlying hierarchical filesystem somewhere below, in the stack seems like an implementation detail. As a programmer there's a library/middleware to be used to access resources, but once inside, object based access already exists. Looking at video game save files, that's been the case for a while, with the state of objects (in fact, visible objects that the user interacts with) being saved and restored from disk.

I agree it's not as satisfying as a total paradigm shift in computing on every single level, but the notion that file system, byte stream access is a holdover from a previous era ignores practical, user facing progress we've made since.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by dorlaor on Friday May 03, 2019 @01:56PM (#19820649)
At Scylla we initially defined a new filesystem which adheres shard-per-core and thus a single physical hyperthread has the sole access to the data and thus there is no contention.

While it will be better than current XFS, we've made aio improvement to the later over the years and today it's good enough for ScyllaDB.

Practically, even though Scylla has its tcp/ip stack in userspace on top of DPDK, we learned over the years that it's ok to use the less efficient kernel tcp stack. Most of the overhead and the optimizations can still happen within the DB itself as long as it controls the memory, the cache and manages the networking queues

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by jnurmine on Friday May 03, 2019 @01:00PM (#19820107)
I think I don't understand. Is there something preventing people from experimenting and craftsmanship at this very moment?
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by thaumaturgy on Friday May 03, 2019 @12:35PM (#19819869)
I would like to see an updated file system architecture that's closer to a database, with tagging and all that. And I could see that extending to processes too.

But what are you imagining as alternatives for i/o and terminals?

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by bluetomcat on Friday May 03, 2019 @12:49PM (#19820023)
What if we surpass file systems completely? Imagine every process having its own "non-volatile" memory area, where all persistent state is kept between restarts, with a clean OS interface to share that state to other processes?

Terminals and process hierarchy are a complete no-go in a fresh design. Every entity in the system can be identified through unique IDs which can be handed down to other processes based on different OS policies.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by thaumaturgy on Friday May 03, 2019 @01:04PM (#19820148)
> Imagine every process having its own "non-volatile" memory area, where all persistent state is kept between restarts...

I'll treat this seriously: as software development practices are just now beginning to mature, with more emphasis on test coverage being considered best practice, sure ... maybe.

But there's still a lot of software out there for which "restart the application" (or even, "restart the stinking OS") is the only practical solution when it's behaving badly.

> Every entity in the system can be identified through unique IDs which can be handed down to other processes based on different OS policies.

Okay, but how do you write a process which is capable of communicating with any other process?

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by bluetomcat on Friday May 03, 2019 @01:22PM (#19820288)
> But there's still a lot of software out there for which "restart the application" (or even, "restart the stinking OS") is the only practical solution when it's behaving badly.

Which, in principle, doesn't prevent a program from crashing or misbehaving when it encounters a corrupted file left over from its last run. In the imagined system, the application developer would be fully aware whether he is putting a data structure in the "volatile" or in the "non-volatile" memory areas, with some safety guarantees from the OS. Restarting would zero only the volatile area, enabling a clean starting state.

> Okay, but how do you write a process which is capable of communicating with any other process?

Why would you need to communicate with any process? Maybe I need to communicate with the currently running instance of "HTTP Server App" or "Database Engine App", not with an unrelated process my program knows nothing about.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by thaumaturgy on Friday May 03, 2019 @01:51PM (#19820609)
> Which, in principle, doesn't prevent a program from crashing or misbehaving when it encounters a corrupted file left over from its last run.

Of course. But saving state to nvram also has this problem, plus the additional problem of saving broken program state. Like I say, I'm not totally pessimistic on this anymore: there are some promising trends that make me think we might get there in the not distant future. But we're not there yet.

Maybe supporting some way for a user to manually reset broken program state would be a good enough compromise -- as long as application developers didn't do something dumb, like store their license information in their program state. Autodesk immediately comes to mind there.

> Why would you need to communicate with any process?

Because some other process wants to communicate with you.

Composability and common interfaces and loose coupling is a huge advantage in Unix-like operating systems or any other software architecture that embraces those principles.

They mean that you can write software with a much longer lifespan, and usually for less effort. In your example, someone may come along wanting to write "Firewall App" long after you've abandoned your software. If your software is extensible and supports standardized IPC, "Firewall App" is possible. If it doesn't, then it gets thrown out and replaced with something else.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Khoth on Friday May 03, 2019 @02:04PM (#19820735)
> Why would you need to communicate with any process? Maybe I need to communicate with the currently running instance of "HTTP Server App" or "Database Engine App", not with an unrelated process my program knows nothing about.

Today, I piped the output of some process I was running into grep. Neither of these programs knew about the existence of the other.

Later, I used an image editor to create an image, then used a web browser to upload it to a website. The web browser and image editor were unaware of each other's existence.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by bluetomcat on Friday May 03, 2019 @02:19PM (#19820884)
> Today, I piped the output of some process I was running into grep. Neither of these programs knew about the existence of the other.

Only because "an unstructured stream of bytes" is the way for Unix processes to communicate. It allows for composability, but a very fragile and unsafe one, requiring programs to spit out and read free text, with all the crazy filtering and guesswork needed.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by jnurmine on Saturday May 04, 2019 @01:41AM (#19824686)
Free text? You can just as well pipe structured binary data (such as audio or images) through one or more processing elements. The processors need to understand the data, of course.

There are also other IPC mechanisms, like D-Bus.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by garmaine on Saturday May 04, 2019 @12:13AM (#19824398)
You could pipe structures data. See: PowerShell.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by AnIdiotOnTheNet on Friday May 03, 2019 @11:16PM (#19824182)
Plan 9 did a pretty good job.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by stcredzero on Friday May 03, 2019 @01:11PM (#19820204)
Imagine every process having its own "non-volatile" memory area, where all persistent state is kept between restarts, with a clean OS interface to share that state to other processes?

People have been thinking about this for decades. (Probably because it's a compelling idea.) Google "orthogonal persistence."

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by wongarsu on Friday May 03, 2019 @01:56PM (#19820656)
Currently my mother has a Pictures folder which contains her pictures, where she can open them with the default photo viewer, with an editing program, and where she can trivially add files or make backups with the Windows Explorer. Any alternative interface I can imagine that offers the same flexibilty of using the same picture in multiple programs just ends up mimicking files.

There's room to replace traditional folder structures with paths or anything else, and most traditional file system implementations have really slow search. But I don't see a future in replacing the notion of a file, it maps too well to the intentions of the user.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by laughinghan on Friday May 03, 2019 @05:43PM (#19822559)
Well, in a traditional file system, the basic unit of data is a specific notion of a file which is an untyped blob of octets with limited metadata like size, filename, some timestamps, and some very coarse access controls.

You could quibble about whether this counts as "replacing the notion of a file", but I could certainly imagine it might be useful to have a system that talks directly to disk whose basic unit of data has much more useful metadata, such as a canonicalized MIME type, much more granular access controls, much more granular access and edit history, etc. Has your mother ever downloaded a file with the wrong extension and been unable to open it? I know I have.

Similarly, the abstracted "everything is a file" notion of a file without random access, which includes sockets and named pipes and stuff, is an untyped, unsized stream of octets. Message-oriented protocols like WebSockets and HTTP can and in fact are built on top of that, of course, but it could have been the reverse: instead of a stream of octets, TCP could have been a stream of arbitrarily-large but finitely sized messages. There almost certainly would have been advantages to such an approach, and applications that didn't want the message framing and just wanted a stream of octets could have easily ignored it.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by the-rc on Friday May 03, 2019 @02:54PM (#19821210)
That's the design of the System/38, AS/400, iSeries and System i. The unique IDs are 128bit pointers or capabilities.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by warrenm on Friday May 10, 2019 @06:56PM (#19883044)
>Imagine every process having its own "non-volatile" memory area, where all persistent state is kept between restarts, with a clean OS interface to share that state to other processes?

So ... something Docker-esque?

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by the_af on Friday May 03, 2019 @01:53PM (#19820624)
Wasn't this kind of filesystem an abandoned plan for one of the (now old) versions of Windows? Like Windows 2000 or XP? I don't remember why they ditched this plan. Maybe it wasn't such a good idea after all, who knows.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by thaumaturgy on Friday May 03, 2019 @02:12PM (#19820820)
There have been a few toy filesystems which have explored this. BeOS back in the late 90s came the closest to broad adoption, even though it didn't fully embrace the paradigm, just aspects of it.

I think there are a few reasons it hasn't happened:

1. Filesystems are hard. Every new filesystem architecture ends up requiring a large pool of talented developers.

2. Nobody wants to break backwards compatibility. Current filesystem design is so integral to all kinds of software that you just can't expect all software in the world to be updated just to work with a new filesystem paradigm.

3. Databases are also hard, so a database-like filesystem is doubly so.

4. Current filesystem architecture is good enough for most stuff. The pain of continuing to use it isn't as great as the pain of changing it.

None of these reasons make a database-like filesystem inherently bad. It's just not practical right now.

I think we're moving in that direction though, with things like object storage.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by the_af on Friday May 03, 2019 @02:28PM (#19820972)
I agree and didn't mean to imply database filesystems are necessarily bad. Just wondering.

I forgot about BeOS! Do you remember which version of Windows was going to do it, or at least had preliminary plans for it? I distinctly remember reading about it. Was it an early version of Windows XP or what? I can't remember...

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by thaumaturgy on Friday May 03, 2019 @02:38PM (#19821062)
Are you thinking of WinFS? I think that was sometime between XP and Vista.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by the_af on Friday May 03, 2019 @02:42PM (#19821092)
Yes! WinFS. Thank you!
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by snazz on Friday May 03, 2019 @02:44PM (#19821112)
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by MathematicalArt on Sunday May 05, 2019 @12:12PM (#19833478)
See: “Designing better file organization around tags, not hierarchies”[1]

The author has done a thorough preliminary exploration on this matter. [1] https://www.nayuki.io/page/designing-better-file-organizatio...

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by strictfp on Friday May 03, 2019 @12:44PM (#19819972)
One idea I've been throwing around is to replace files with HTTP resources; everything is a resource. Effectively Plan9s idea, but the time might be right.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by worble on Friday May 03, 2019 @12:52PM (#19820051)
I don't know much about the OS and designs, but is that similar to how Redox is approaching it with "everything is a url"[0]?

[0]https://doc.redox-os.org/book/design/urls_schemes_resources....

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by PeterCorless on Friday May 03, 2019 @03:30PM (#19821492)
If you go that route, bind unique objects to Uniform Resource Names (URN), and then have a mapping to instantiations (URLs), so that the same resource can be found in its multiple locations. Would help immeasurably for a distribution model.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by BGyss on Friday May 03, 2019 @01:03PM (#19820140)
Believe it or not there was a system at Sony Pictures Imageworks that worked like this - no idea what it was doing under the hood though. Worked great in practice though - every possible production resource was a URL that started with spref:// iirc.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by taborj on Friday May 03, 2019 @12:40PM (#19819936)
Every system is driven by user adoption. At this point, it will be nearly impossible to dethrone the current methodologies.

Not saying it shouldn't be done, just that it might fail.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by zwkrt on Friday May 03, 2019 @12:57PM (#19820088)
The classic way that this has always happened in the past is by solving a specific problem in a hacky-but-cheap way as compared to existing tech. The issue I see here is I can already run Unix on a smartwatch or a car radio, so it seems difficult to understand where new computing paradigms will come from. Google's Fuchsia is a contender, but I wonder how realistic it is that it would ever become 'the standard'. Maybe the future is a world of truly heterogenous operating system design, but more likely we will employ a one-size-fits all approach just like every other industry. All car engines are about the same, all shoes are constructed with similar parts, all stoves are basically interchaneable, it is unrealistic to expect that software will be any different.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Razengan on Friday May 03, 2019 @12:57PM (#19820090)
> Every system is driven by user adoption. At this point, it will be nearly impossible to dethrone the current methodologies.

iOS, when the iPhone first came out, turned many of the entrenched perceptions about computing devices around on their head, and people embraced it.

Even without the celebrity power of someone like Apple, an experimental system could still thrive today in the shadows with a small cult of followers nurturing and developing it, until it breaks out.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by robbyt on Friday May 03, 2019 @01:25PM (#19820330)
Correct me if I'm wrong, but isn't this what Plan 9 does?
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by AsyncAwait on Friday May 03, 2019 @01:41PM (#19820492)
I think Plan9 still has the notion of files, folders and such?
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by notduncansmith on Friday May 03, 2019 @03:51PM (#19821661)
Why are these insufficient? What abstractions should we building on?
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Ericson2314 on Friday May 03, 2019 @12:27PM (#19819786)
Amen to that. Unix was never a good design, and now is severely out of date. We can no longer afford to hack around it.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by FussyZeus on Friday May 03, 2019 @12:39PM (#19819927)
What a ridiculous statement. Yeah if it was possible to just jump to the best solution each time then we'd benefit massively, but that's not how any science works. The new awesome thing is always built on the back of what was done before. Electric cars have been around since the inception of the internal combustion engine but we didn't have electrical supplies with the energy density of gasoline to make electric cars possible until decades later, and modern life would've been (and remains, unfortunately) impossible without the energy density of fossil fuels. Hopefully someday we'll get past that, but when that happens, that doesn't then mean that fossil fuels were just a bad idea, they were the only stepping stone to what replaced them.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Ericson2314 on Friday May 03, 2019 @05:13PM (#19822335)
The other OSes from Unix's era were already as good or better (or at very least there was a diversity of ideas). Then the regulation that prevent AT&T from being sold like the others causes Unix to win prematurely.

Maybe that's how Ford beat the earlier luxury cars in raw profit, but that's not how the ICE beat electric cars.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by jaas on Friday May 03, 2019 @12:35PM (#19819868)
"Unix was never a good design"

Nothing's perfect. Unix was a great design that served its purpose well for a long time, and evolved a bit along the way. Saying it was "never good" is trivializing and, in my opinion, arrogant.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by dllthomas on Friday May 03, 2019 @01:00PM (#19820111)
There were always objections.

"Unix went from being the worst operating system available, to being the best operating system available, without getting appreciably better."

https://news.ycombinator.com/item?id=19416485

Which isn't to say that those POV were necessarily correct, just that it isn't all hindsight.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by the_af on Friday May 03, 2019 @01:59PM (#19820693)
To be fair, there are always objections to any working piece of technology.

It's not helpful to claim "it was never good design". It was a working design that drove technology to the point it is now, and in that sense it was hugely successful. What kind of perfect and pure tech do some people want, anyway? Pick anything, whatever they like -- say, Plan 9 or OS/2 or whatever -- and I can bet you in a parallel universe where that tech won, someone on para-HN will claim that it sucked and it was never a good design and if only Unix had won.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by dllthomas on Friday May 03, 2019 @05:10PM (#19822308)
I certainly don't disagree that it was successful, and (coming into technology when I did) I've always personally liked it. I just found the writings around what came before interesting.

> I can bet you in a parallel universe where that tech won, someone on para-HN will claim that it sucked and it was never a good design and if only Unix had won.

I'd take the same side of that bet as you :-P

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by thaumaturgy on Friday May 03, 2019 @12:38PM (#19819916)
Yeah, Unix was a terrible design. Composable architecture combined with standardized i/o and IPC models. I can't imagine anything worse, especially compared to today's proliferation of data formats and inscrutable APIs.

It's a good thing nobody uses it anymore.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by pjmlp on Friday May 03, 2019 @12:44PM (#19819981)
Had Bell Labs been allowed to sell it in first place and that would have been exactly its outcome.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by jstimpfle on Friday May 03, 2019 @04:14PM (#19821853)
missing the sarcasm?
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Ericson2314 on Friday May 03, 2019 @05:09PM (#19822300)
I think you are.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by taborj on Friday May 03, 2019 @12:43PM (#19819968)
My Online Sarcasm Detector(tm) is beeping wildly
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by wongarsu on Friday May 03, 2019 @02:04PM (#19820743)
Which is why we have Windows with the NT family of kernels. It's a reimagining that contains great ideas like a flexible file system stack that allows you to dynamically add drivers that add encryption, compression, antivirus checks etc, and a few bad ideas like a flexible file system stack that's orders of magnitude slower when working with small files than unix implementations.

Windows is a mainstream OS that is very different from Unix in many regards (even if it still has files). And it really shows that the grass isn't greener on the other side: some parts are great, some parts are terrible, but there aren't a lot of things that offer a universally better tradeoff.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Ericson2314 on Friday May 03, 2019 @05:06PM (#19822276)
The VMS people Microsoft poached and then straightjacketed with legacy concerns did have good ideas, yes.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by dekhn on Friday May 03, 2019 @12:52PM (#19820053)
UNIX was a great design for a wide range of people. FOr example, multiple domains of science were transformed because UNIX made it easy to implement microcomputers for data collection on realtime data and share the resulting software among a pool of other researchers.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by ncmncm on Saturday May 04, 2019 @12:08AM (#19824385)
There are only two kinds of OS: the ones people complain about, and the ones no one uses.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by pzs on Friday May 03, 2019 @12:39PM (#19819921)
Would you care to elaborate why Unix, in your opinion, was never a good design?
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by pjmlp on Friday May 03, 2019 @12:50PM (#19820029)
It was re-written on an unsafe language that completely disregarded what has happened outside Bell Labs since 1961, at Burroughs, IBM, MIT, Xerox and other research cathedrals.

It only took off thanks to Bell Labs being forbidden to sell it, so it got offered for a symbolic price, alongside source code to major universities, which then decided to build on top, instead of paying OS street prices.

Had UNIX been sold in the same vein as other mainframe OSes and no one would be talking about whatever quality it might have had.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by systemBuilder on Friday May 03, 2019 @01:09PM (#19820190)
I worked on the xerox product OS (Pilot) written by my manager, and was on the team with the designers of Multics and Swift, MIT's OSes. At MIT we all ran 4.15bsd and then 4.2bsd and UNIX was so far ahead we focused on improving it, mostly. Pilot, Multics, CTSS, were nowhere near as powerful or developer friendly as UNIX. UNIX killed off OS research for a long time!
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by pjmlp on Saturday May 04, 2019 @04:22AM (#19825180)
Given what I know from XDE and Cedar, I fail to see how a text based CLI, without the graphical debuggers, REPL and GUI workflows was more developer friendly.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by Ericson2314 on Friday May 03, 2019 @05:05PM (#19822270)
Thank you for being a breadth of wisdom in the UNIX-worshiping wilderness.

You can always get mindshare being first massively underpriced thing to market.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by jstimpfle on Friday May 03, 2019 @05:26PM (#19822438)
Only that this doesn't even touch on design, or what parts could have been done better.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by pjmlp on Saturday May 04, 2019 @04:15AM (#19825152)
Sure it does, not using C to start with.

Or in another form, C should have done the same as other systems languages, do proper bounds checking, arrays and strings without implicit decay into pointers.

Second, having a proper UI story like NeXTSTEP or NeWS, and not the X11 Frankenstein.

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by jstimpfle on Saturday May 04, 2019 @12:47PM (#19827584)
Equating kernel design with choice of implementation is a stretch.

Also, Unix is not X11, and weren't the other ones running on top of Unices as well?

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by mypalmike on Saturday May 04, 2019 @08:45PM (#19830374)
Just walk away.

"The language runtime is the OS." - https://news.ycombinator.com/item?id=15468395