Before the advent of LLMs, ML was used in upscaling the assets and pre-rendered backgrounds of the first 3 classic Resident Evil games: https://www.reshdp.com
Makes one wonder, why should anyone embark on learning this intricate and time-consuming art of reverse engineering when LLMs are on their way to automate it in seconds...
It's not just corpo talk. The ultimate goal in LLM and AI progress is "replacement" of professional knowledge workers. In the march of the 9s of the accuracy of the generated LLM output, the engineers role would matter less and less.
It's asking engineers to "adapt" to being efficient in filling out the last 10% then 1% then 0.1% then 0.01%.
Please explain this "adapting". The LLM sellers' holygrail is * you just need to crank our model bro *. With this mindset, there is no adaptation needed, save a couple of weeks of getting up to speed with nuances of using the models, the / commands and integration of their APIs into your workflow.
Like imagine editor is on ws2, you open a terminal to /tmp/ to check something quick, it scrolls to the right, then jump to ws3 for your file manager and other stuff and go back to your editor.
Now you want to access that terminal on /tmp/ again. Where was it?
In i3, I just spam-switch workspaces in this case, but at least I can find them. With scrollable wms, every ws can potentially hold that target app.
Didn't Google say that they're gonna provide an escape hatch for students and hobbyists? So, best case scenario, we just need to tap some label 5 times to enable side-loading again.