"Torvalds groaned and replied, "I never had a vision. I don't want one. I see myself as a plodding engineer." On that note, the interview ended to the crowd's applause."
If only they applied the same rigor to big tech scraping the same content into large language models. I guess the bypass paywall team wasn't big enough to afford the legion of lawyers that Sam Altman and co can summon on demand. We can just wait for chatgpt to serve those articles direct to our search results and nobody will even visit their website, because we live in a world where stealing an article to read is illegal, while stealing all of them for profit is not.
It's very complex with hyper visors and virtualization technology. I don't fully understand it myself in terms of how resources are allocated across something like aws or azure, but take a look at openshift vs openstack maybe. Openshift is for deploying containers and openstack is virtual machines. Openshift is kubernetes with some customizations for enterprise. Openstack is same for vm's.
Instances are virtual machines which tend to host an operating system, and a container is lighter and only hosts an application where the code and dependencies are isolated from the underlying operating system it runs on. k8 is kubernetes, which is container orchestration. I think of virtual machines for jobs that scale vertically, while containers are suited to jobs that scale horizontally. But this isn't necessarily true as kubernetes is starting to get slurm functionality using tools like sunk. But I'm no dev ops engineer and the field is very complicated.
You know you're old when games you still play quite regularly turn up in retro reviews! The community master server is still pretty well populated, as are UT '99 servers. These games are still the pinnacle of their genre. No micro transactions, no DRM, no pay to win. Just you, your shock rifle, and as much amphetamine as your nerve endings will take. As the reviewer says, the level design and game mechanics are legendary at this point, and players of any ability can quickly get into a flow state that modern games can only dream of. These are fine wines in a world of cheap lager. New gamers should drink deep from the pc games of the 2000's.
I'm interested in the same question. There isn't a definitive text because the problem is infinitely broad. My approach is to build crud apps around the tech stack I'm interested in, currently Python with fastapi, arangodb, with some next and typescript for the front end. But you could swap out Python for Go and swagger. For security there is Keycloak. For scalability you could look at building your system as pods in open shift but that adds cost. Personally, I think unless you're Netflix kubernetes is probably overkill. But the biggest problem is that today's tech stack is replaced tomorrow by the next new shiny, and all of them are complex and will be entirely different for every team and every problem. A book for dev ops is almost impossible.
For me, vim is nice to use because it's ubiquitous across any system I log into. Any server will have vi at the least. It's also light and can load a file instantly on any hardware, reducing dependency to zero. Once you have a comfortable config, you're done for the rest of your life. Although, in reality vim config is a lifestyle and not a choice ;)
Hunter was an early sandbox game on the Amiga and was quite good back in the day. Mercenary series too. Daggerfall was/is a huge sandbox rpg. Minecraft was the first to capture the lego style creativity though. Dwarf fortress is probably the closest to Minecraft.
"Torvalds groaned and replied, "I never had a vision. I don't want one. I see myself as a plodding engineer." On that note, the interview ended to the crowd's applause."
Legend.