101 karma · joined May 17, 2015
I'm not asking for them to send me a GPU, just to let me use a GPU instance, you know, like people often do in cloud computing. I'm guessing you've never heard of it. More of a kitchenwares guy?
You must be using some of the higher priced GPUs(which they offered me), but I'm looking for something in the <$1k/month range.
While accurate, it's a bit of an understatement :) Thanks for all your work, Jose.
My advice is don't be attracted by the shiny toy that is SwiftUI. It's a steaming pile to dung, unless you just want some basic forms/tables/text.
Every human artist that ever lived(to my knowledge), heard, or saw someone else create a similar piece of art, from which they were inspired. If I create a song right now, how is that any different than an AI doing the same from being trained on copyrighted music. Certainly my song will be entirely made up of elements i've heard before, however large or small. An ML model is doing the same thing. There is nothing truly original in art. Artists are just filter and amplifiers of what they've heard, seen, and like. Your copyright does not permit you to restrict others from being inspired by your work, or using it for inspiration.
So the model they came up with was high isolation, via processes(no OS processes, but super tiny, like a few hundred bytes processes, all managed by the VM), and distribution(can't have reliability if one node can knock out the system).
The other unique part is the supervision trees that manage those processes. Let's say you have a chat server. You may have a process per device connected to the server, a supervisor for each chat room(group of processes), and a supervisor for all the chat rooms(supervisor of supervisors). Supervisors are themselves processes, but with a specific job.
If your phone's connection/process on the server has some issue, it'll just crash, that's the erlang philosphy "let it crash". You as the user likely can't fix it. The code can't magically fix itself. But presumably through testing we know that initial connections with a clean state are stable, so let it crash, your phone reconnects. Then it crashes again. Reconnects. Crashes again. (This isn't the ideal state obviously, but a worst case for demonstration). Eventually that'll trigger some limit, where the chat group supervisor will notice, somethings wrong here, there's some state that's in a mess, it's time to crash so we can get a fresh try at this. So it'll crash. Usually the first phone reconnection would have been enough to fix it and the group supervisor wouldn't need to restart, but for demonstration purposes we'll say it does, and let's pretend when it comes back up it crashes again. This will propagate up, until enough restarts have fixed the state of the system to the point where it's stable again.
I believe Erlang was the first system to achieve nine 9s of reliability, which is 31.56 milliseconds of downtime a year. Not saying this lib will get you that, but that's the spiel for Erlang.
Just because something CAN be done, that doesn't mean it's trivial. Someone's PK "can" be guessed, it's just incredibly unlikely. So for people, like myself, not 100% knowledgable on this type of tech, if someone goes through all the trouble to get the keys, but doesn't complete the final step of actually removing coins, it looks like either for some reason they can't or they are just completely naive and assuming everyone else knows exactly what they've done.
What exactly makes you say that Rails is a clear win over Phoenix for CRUD stuff?