8 ms·
It's crazy and destructive that we are still using the unix paradigm in the cloud. In the 70s we have transparent network fileststems, and by the 80s I had a m
by gumby 4y ago
It's crazy and destructive that we are still using the unix paradigm in the cloud.
In the 70s we have transparent network fileststems, and by the 80s I had a more advanced cloud-native environment at PARC than is available today.* The Lispms were not quite as cloud native as that, but still you could have the impression that you just sat down at a terminal and had immediate window into an underlying "cloud" reality, with its degree of "nativeness" depending on the horsepower of the machine you were using. This is quite different from, say, a chromebook which is more like a remote terminal to a mainframe.
I was shocked when I encountered a Sun workstation: what an enormous step backwards. The damned thing even ran sendmail. Utterly the wrong paradigm, in many ways much worse than mainframe computing. Really we haven't traveled that far since those days. Cloud computing really still it "somebody else's computer."
There's no "OS" (in the philosophical sense) for treating remote resources truly abstractly, much less a hybrid local/remote. Applications have gone backwards to being PC-like silos. I feel like none of the decades of research in these areas is reflected in the commercial clouds, even though the people working there are smart and probably know that work well.
* Don't get me wrong: these environments only ran on what are small, slow machines by today's standards and mostly only ran on the LAN.
- crazygringo 4y agoS3 is a transparent network filesystem. Unix is only the paradigm for computing servers. Which makes sense because different apps have wildly different ways of scaling. There's no effective paradigm for abstracting away 1,000's of CPUs in a general purpose way. I really don't have any idea what you're looking for here, that is possible, that cloud services don't already do.
- gwm83 4y agoS3, yes a network accessible FS. Unix - only is a telling word - it is the /defining/ paradigm for that. Is there a better one yet? 1000 CPUs? I mean, uh Hadoop, spark, etc etc. What?
- imwillofficial 4y ago
- gumby 4y ago> Unix - only is a telling word - it is the /defining/ paradigm for that. Don’t be ridiculous. We had networked distributed file systems over both the arpanet and lans before Unix even had networking. I even mentioned this in my root comment.
- fragmede 4y agoThe paradigm for abstracting away a thousand CPUs is AWS Lambda/GCP or Azure functions/K8s' implementation of serverless. It's not a total drop in replacement because a plain lift-and-shift can't change your paradigm, but cloud functions are very much a Cloud 2.0 (or at least 1.5) paradigm.
- m463 4y agoI completely understand what you're saying. I'm sort of reminded of how the US government is the worst (except for all the rest), when having an absolute ruler should be so MUCH more efficient. Problems would be fixed by fiat. Or maybe, why does lisp persist with its horrible user-unfriendly syntax? :) I guess we will just have to invent it. (and you should do your part by reminding people with examples of old systems that elegantly solved the papercuts of today)
- deleted 4y ago[deleted]
- mellavora 4y ago> why does lisp persist with its horrible user-unfriendly syntax? why persists lisp if user-unfriendly else horrible syntax? sounds more like python :)
- rsync 4y ago"It's crazy and destructive that we are still using the unix paradigm in the cloud." # ssh user@rsync.net "test -f fileThatExists" #echo $? 0 ... from my cold, dead hands ...
- verisimilitudes 4y ago
- gwm83 4y agoOkay, tell me how you do it much better in k8s
- deleted 4y ago[deleted]
- verisimilitudes 4y agoI don't use k8s or whatever garbage gets thrown around nowadays. I well remember my disgust when I learned AWS was just using UNIX virtual machines or whatever, rather than something simple, such as allowing people to run little functions floating in the void. I know nothing about AWS, but I've not been mistaken, right?
- gwm83 4y agoWell AWS has been quite clever, using both Xen originally and also now KVM VMs, but everything else is based on that yeah. But that's gotten really complex over the years. They now use a container execution environment called firecracker or something that is open sourced and might be totally separate from their virtualized environment - or at least on top of it where they do let you just run little jams. Cloud isn't bad, I just mean you do have to transfer octets somehow from exec to exec. There are more and less efficient ways of doing it, and also more and less secure ways too - and abstract ways. Not all bad.
- 4y ago
- hinkley 4y agoPeople forget that a good deal of “cloud” logic existed in a form on mainframes as well.
- gwm83 4y agoamen, and those principles still serve us well today. software developers are still as bad at writing code, maybe worse.
- vbezhenar 4y agoMainframes are very expensive. You can buy mainframe with very fast CPU and RAM interconnect and scale it by buying more hardware. Or you can spend 100x less and buy a number of server blades. Interconnect will be very slow, so you can't just run some kind of abstracted OS, you need to run separate OS on every server blade, you need to design your software with that slow interconnect in mind. But in the end it's still 100x cheaper and it's worth it. Also mainframes have growth limit. You can buy very powerful ones, but you can't buy one that's as powerful as entire datacenter of server blades.
- hinkley 4y agoThat's why I both hope Oxide Computers succeed and worry they may not. They are effectively building a mini computer. The smallest unit you can buy from them is an entire rack. Modified rackmount hardware with better software to make it more cohesive. I really hope they go to half-racks, but I've no idea how you'd stack them.
- gwm83 4y agoGood replies by others here. "crazy and destructive" that you have no idea about how computers work today, or how computers are still computers. Your ignorance about things like Sun workstations as it relates to literally everything today, I mean you have no idea about modern computing lol
- imwillofficial 4y ago“by the 80s I had a more advanced cloud-native environment at PARC than is available today.*” This statement is entirely false as admired in your footnote.
- gumby 4y agoArchitecturally and conceptually more advanced. There's a lot of literature about that environment so you can read what I was referring to.
- imwillofficial 4y agoThat’s a hand wavey way to make a claim that can’t be backed up. What you had then was in no measurable way more advanced architecturally or conceptually. Name one facet in which it was more, could do more, or faster, or better. You can’t because it couldn’t. No part of your setup was cloud native. Nothing was abstracted away, a core tenant of the cloud. You can’t just redefine words however you want.
- gonehome 4y agoHave you heard of urbit?
- klibertp 4y agoI did. Its use of intentionally obscure language that makes APL seem readable and consistent in comparison just because "only smart folks should be able to code in this" is something I simply can't accept. And I love obscure langauges!
- gwm83 4y agoExcuse me sir, are you going to pay for those?
- gumby 4y agoYou don’t pay per packet even though a huge amount of computation is done on devices between you and the machine you’re connecting to in order to transmit each one. See my comment about tollbooths above.
- fulafel 4y agoUnix did make it work much better a bit later, organizations used to run NFS and single sign on with Kerberos to workstations, automated from scratch reprovisioning of workstations (so you could just reinstall from tftp server with org specific SW customizations included if previous user had messed the box up), smooth remote access to all machines including gui apps, etc. It just went away due to Microsoft crowding it out.
- otabdeveloper4 4y ago"Treating remote resources truly abstractly" doesn't work in practice. Too many points of failure in our systems, and you really, really don't want to paper them over with abstraction if you want to build a fault-tolerant system.
- gumby 4y agoThat has been true for as long as I have been programming. But: Similar statements have been made about high level programming languages. Nowadays most devs don’t understand how the CPU works, but write on the top of a tower of abstractions and nobody bats an eye. Many of those abstractions are quite complex! I can imagine that the same could apply to certain kinds of network activities. Look at how ppl use http as a magical secure and robust inter process communication channel with no understanding of how it works at all. Lambda is a half a baby step in this direction. Another problem is tollbooths. The phone system uses a lot of bandwidth simply to charge the customer money. My phone company charges me overseas rates if I make a phone call outside the country, even if both endpoints are using WiFi, not the cellular network! I’m afraid of the same with fine-grained and abstract distributed computing, but perhaps the magical hand wave abstractions I posit above can help. This tollbooth nightmare btw is the dream of the web3 bros.
- theamk 4y agoWe cannot afford the seamless distributed systems, and I don't think we ever will. I use Python because I don't care if adding two numbers is taking a microsecond instead of a nanosecond. But if netwotk call suddenly takes 1 sec instead of 10mS? well, thats a huge problem, let's add a memory cache and rack-level cache and a parallel fetch and a whole bunch of monitoring. The local compute is growing much faster than internet, and even faster than local network. I sure hope we get better abstractions, but caring about remote vs local call is not going away.
- TuringTest 4y agoYou could design a OS with abstractions built around latency, instead of physical machines. It would still allow you to find and use resources according to their constraints of use, but wouldn't force you to keep track on which exact machine they are located.
- zasdffaa 4y agoAbstractions usually (always?) have a cost because physics. > The damned thing even ran sendmail and? > Cloud computing really still it "somebody else's computer." That's the definition of 'the cloud'. Unless you run it locally in which case it's your computer. What's your point. > There's no "OS" (in the philosophical sense) for treating remote resources truly abstractly It's unclear what you're asking for. Treating stuff truly abstractly is going to get you appalling and horribly variable scalability. If you're aware of that, why don't you tell us what you want to see instead. Edit: ok, this is from gumby, now I recognise the name. This guy actually knows what he's talking about, so please tell us what things you would like to see implemented.
- gumby 4y ago>> Cloud computing really still it "somebody else's computer." > That's the definition of 'the cloud'. Unless you run it locally in which case it's your computer. Forget the stupid framing of idiotic marketers in the early 00s and go back to the original “cloud” definition (that engineers were still using in those ‘00s but was distorted for a buck). The term was introduced (by Vince Cerf perhaps) in the original Internet protocol papers, literally with a picture of a cloud with devices at the edge. It was one of the revolutionary paridigms of IP: you push a packet into the cloud (network) but don’t need to / can’t look into it and the network worries about how to route the picket — on a per-packet basis! You don’t say “the cloud is other peoples’ routers”. Today’s approach to remote computing requires developers to know too much about the remote environment. It’s like the bad old days of having to know the route to connect to another host.
- pjc50 4y ago> Utterly the wrong paradigm When you emerge from the jungle, you may notice that not only UNIX conquered the world but even ""worse"" paradigms of Windows and iOS have proliferated. You have to ask why the situation that is so much worse is so popular: is it really everyone else who is wrong?
- gumby 4y agoThere are still a lot of fossil-powered automobiles being driven around by people. Doesn't mean they are the future.
- pdimitar 4y agoAppeal to the currently incumbent solution is not convincing. Very often the majority of people simply choose the lesser evil -- not what's of the best quality or with the biggest productivity. Or need I remind you that hangings at sunrise and sunset were commonplace and people even brought their kids to them? I'm sure back then people defended it as well, and it's likely that if you heard their arguments you'd facepalm.