What I really like about containers is quickly being able to spin one up without having to specify resources (e.g. RAM limit). I hope this would let me do that also.
Recently an xAI recruiter reached out to me for a position at xAI. They mentioned that they had been impressed by my GitHub profile and wanted to fast track me to an interview.
Fun fact: I have not a single repository on my GitHub.
I think the position was about creating training data and realistic coding scenarios or something.
It kind of seems obvious that people would rather share their content on the pre-established platforms.
I believe OpenAI didn't actually want to create an alternative platform. Instead, they wanted (and needed) to be in control. This is really due to the experimental nature of the technology and platform. They wanted to do market research yet retain the power to pull it at any time.
Arguably they were successful in that given that they now have the ability to stop it.
This made me immediately think of the Elm architecture.
To an extent this is how react works internally. There is a function which takes state and produces UI. In order not to have to re-render the whole UI if only a small part of the state changes, there is a diffing algorithm and "virtual dom" that is diffed against. Maybe it doesn't work exactly like that anymore but that's the gist of it.
reply