4 ms·

That is far, far more than transferring a byte of data. Educate me. It's much more meaningful and useful than "something simple" "running little functions flo

That is far, far more than transferring a byte of data. Educate me. It's much more meaningful and useful than "something simple" "running little functions floating in the void" which just sounds like some vapid marketing pitch. That was a quick response to what I thought would be better than administrating a UNIX system on an Amazon machine. Don't be an ass. I've no experience with the real distributed computing systems created before UNIX. The great thing about Linux as the base layer is that it allows a commodity common ground with a very capable system that also facilitates more specialized layers to be implemented on top of it. No, that's the vapid marketing pitch. The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. Hey, Brainfuck also facilitates more specialized layers to be implemented on top of it. Now, what's stupid about doing that, however?

kortilla 4y ago
> Educate me. You forgot an entire direction of input and focused on just a return code. > The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. No it doesn’t. It’s not random and it’s configurable. Turn off overcommit if you want malloc to fail when memory runs out.
vanviegen 4y ago
> The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. If you want to disable overallocation and the OOM killer, be my guest. You'll want to install some extra banks of RAM though. Or is there a better way, provided by other OSes?
- gumby 4y ago
  Sure, you push the failure into the processes, and most OSes I've used do this. Thus (to use unix terminology) sbrk and fork() fail and it's the program's responsibility to handle that, gracefully or not as it wishes. You also degrade more slowly via paging. You shouldn't get to the point where a perfectly innocent process is killed to reclaim memory. A process can die, or even (in some cases) recover cleanly from running out of memory -- that should be the process's choice.
  - throwawaylinux 4y ago
    Which OSes have you used that do that? In Linux you can do that -- disable overcommit (although I'm not sure if that's 100% foolproof). But that's often not preferred because that way does lead to "perfectly innocent" processes being killed: whoever allocates the next page when memory has run out loses. And how do they get to decide? What if a failure path requires paging in one more page of code from disk? Or causes a store to a COW page?
throwawaylinux 4y ago
> Educate me. Not sure if I'm being trolled... It finds a remote machine by name, and routes a connection to it. It authenticates and establishes a secure connection with the machine. It sends a command to the remote machine, the remote machine executes it, and the result is returned. It then puts the result into a form that can be used programmatically by the local shell. > That was a quick response to what I thought would be better than administrating a UNIX system on an Amazon machine. It was content-free. > Don't be an ass. What's good for the goose... > I've no experience with the real distributed computing systems created before UNIX. And already the expert. Impressive. > No, that's the vapid marketing pitch. No, that's the reality. That's why Amazon, Google, Azure, and everybody else offer it in their clouds and use it on their internal infrastructure. > The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. I'll take that over "running little functions floating in the void", it actually exists and works.
- verisimilitudes 4y ago
  I'm being trolled by someone who finds a DNS lookup and an encrypted TCP connection to send a textual command to another machine is somehow impressive, rather than entirely basic and, again, unimpressive. It then puts the result into a form that can be used programmatically by the local shell. That does sound better than returns one octet with two well-defined values, sure. And already the expert. Impressive. I know UNIX is shit with a legion of cultists. Hey, if we live in the best of all possible worlds, explain the market dominance of Windows. Did MicroSoft give Windows away for nothing, to poor unsuspecting university students who decided to hack on it instead of learn what a real computer is, until none remained?
  - throwawaylinux 4y ago
    You seem quite unhinged for a self-proclaimed expert. Maybe it's time for a break from the internet.
    - verisimilitudes 4y ago
      It's easy to support the status quo, until someone points out numerous issues with it, I know. At least read my website before calling me unhinged.
bakugo 4y ago
> No, that's the vapid marketing pitch. The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. You sound like someone who wants some sort of magical fantasy abstraction level where errors never happen and you can just write code without ever caring about said errors or really anything that happens at a lower level or outside of your code. Sorry, but that doesn't exist and never will. Code runs on computers, it doesn't run in a "void".

kortilla 4y ago

> Educate me. You forgot an entire direction of input and focused on just a return code. > The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. No it doesn’t. It’s not random and it’s configurable. Turn off overcommit if you want malloc to fail when memory runs out.

vanviegen 4y ago

> The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. If you want to disable overallocation and the OOM killer, be my guest. You'll want to install some extra banks of RAM though. Or is there a better way, provided by other OSes?

gumby 4y ago
Sure, you push the failure into the processes, and most OSes I've used do this. Thus (to use unix terminology) sbrk and fork() fail and it's the program's responsibility to handle that, gracefully or not as it wishes. You also degrade more slowly via paging. You shouldn't get to the point where a perfectly innocent process is killed to reclaim memory. A process can die, or even (in some cases) recover cleanly from running out of memory -- that should be the process's choice.
- throwawaylinux 4y ago
  Which OSes have you used that do that? In Linux you can do that -- disable overcommit (although I'm not sure if that's 100% foolproof). But that's often not preferred because that way does lead to "perfectly innocent" processes being killed: whoever allocates the next page when memory has run out loses. And how do they get to decide? What if a failure path requires paging in one more page of code from disk? Or causes a store to a COW page?

throwawaylinux 4y ago

> Educate me. Not sure if I'm being trolled... It finds a remote machine by name, and routes a connection to it. It authenticates and establishes a secure connection with the machine. It sends a command to the remote machine, the remote machine executes it, and the result is returned. It then puts the result into a form that can be used programmatically by the local shell. > That was a quick response to what I thought would be better than administrating a UNIX system on an Amazon machine. It was content-free. > Don't be an ass. What's good for the goose... > I've no experience with the real distributed computing systems created before UNIX. And already the expert. Impressive. > No, that's the vapid marketing pitch. No, that's the reality. That's why Amazon, Google, Azure, and everybody else offer it in their clouds and use it on their internal infrastructure. > The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. I'll take that over "running little functions floating in the void", it actually exists and works.

verisimilitudes 4y ago
I'm being trolled by someone who finds a DNS lookup and an encrypted TCP connection to send a textual command to another machine is somehow impressive, rather than entirely basic and, again, unimpressive. It then puts the result into a form that can be used programmatically by the local shell. That does sound better than returns one octet with two well-defined values, sure. And already the expert. Impressive. I know UNIX is shit with a legion of cultists. Hey, if we live in the best of all possible worlds, explain the market dominance of Windows. Did MicroSoft give Windows away for nothing, to poor unsuspecting university students who decided to hack on it instead of learn what a real computer is, until none remained?
- throwawaylinux 4y ago
  You seem quite unhinged for a self-proclaimed expert. Maybe it's time for a break from the internet.
  - verisimilitudes 4y ago
    It's easy to support the status quo, until someone points out numerous issues with it, I know. At least read my website before calling me unhinged.

bakugo 4y ago

> No, that's the vapid marketing pitch. The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage. You sound like someone who wants some sort of magical fantasy abstraction level where errors never happen and you can just write code without ever caring about said errors or really anything that happens at a lower level or outside of your code. Sorry, but that doesn't exist and never will. Code runs on computers, it doesn't run in a "void".