I actually find that starting a 'raw disk partition' virtual machine for Windows is one of the best ways to run it. Stops it from fucking up your BIOS and EFI when it does an update. You can restart into it when you want the 'native GPU' for games.
Of course, the even better way to stop Windows from fucking up your hardware is to not allow it anywhere near your hardware in the first place...
The Android dev kit includes a copy of QEMU that's set up to emulate ARM with a selection of popular screen sizes and revisions of the OS, so that you can test your app on a variety of 'potential phones' before you upload it to the marketplace. Snapdragons are amazingly performant CPUs for how gently they sip at the battery, but they're not that strong in the big scheme of things - any random x86 processor should be able to emulate them while using fifty times the power. A Steam deck ought to be able to do it; the request will then be 'we'd like to play Android games better', which to me is a much more reasonable ask.
I'm still trying to make 'sloppers' happen. Perfectly describes the lack of thought that goes into what they produce.
The ability to do some basic calculations is what was missing in CSS from the start, IMHO. You don't want paragraph text to be too narrow or too wide as it would become unreadable, so a rule like "at least 20 ems, and then whichever is smaller of 100% or 80 ems centered on the page". But that required either really convoluted layout and rules, or just to work it out with JS after the page is loaded.
Would have been even better if we'd got Donald Knuth involved in the early CSS efforts, with some LaTeX-like attention to the details. There's no reason that computers can't render beautiful text, but it's rare for one person to be an expert typesetter and an expert programmer.
You can turn off "delete", but modification is a danger, it's true.
Turning off delete makes it excellent for eg. backing up photographs on your phone. I've got it doing this from my Android to my raspberry pi, which puts them on my NAS for me. Saves losing all my pictures if I lose my phone.
The 'traditional' way of storing a database is on a mainframe or supercomputer, where all the information is stored in tables with the information all uniquely stored, frequently containing id references to other tables. For instance, an 'orders' table would have a customer id in it, and the 'customer' table would have their name and address. The programming language for databases like that is SQL - PostGres and Oracle are examples. That model gives you a lot of advantages - the data is always consistent, changes are either made completely or not at all - but every query has to go through one machine, so performance can suck, and you waste a lot of time 'joining' tables together for certain kinds of query.
If you're storing eg. a blog with comments on it, that model doesn't make sense. Each page has a varied selection of comments, comment will have a username and maybe their icon, which will rarely change, but will need to be evaluated by the database every time. It would make more sense to output the pre-rendered page as a JSON blob, and you could have a hundred machines with a few pages each to share the load. Updating people's icons and adding new comments would need to be done by telling each machine to make a certain update if they've a copy of that page; you'd 'eventually' be consistent, but if you don't care about that then you get a very scalable robust solution quite cheaply. Examples of such 'NoSQL' databases are MongoDB, Hadoop and DocumentDB.
Linux foundation have looked at DocumentDB's license and said 'yes, free enough for us', so they'll adopt it.
Yeah, some of the answers it produces are very questionable. The implementation of a lot of the stat functions is super-naive and not very stable in borderline cases. Take the standard deviation of three identical numbers, get an answer which is nearly-but-not-quite zero. They've also refused to improve their algorithms as it might break existing customer worksheets.
A CD with RedHat on it? Pretty fancy. My first RH installation came on about three boxes of floppy disks, took hours to unpack it all. And damn right, been all uphill since.
Seeking a technical solution to a non-technical problem. Rather than having one set of company-hosted servers that they then struggle to police, just let everyone host their own, and they can be responsible for banning anyone that doesn't follow the community rules.
Actually makes it easier to write aimbots and triggerbots, since you'll have the video feed and can respond with the right inputs. Skips the step where you've got to film the monitor on the machine that's 'playing' the game, which is protected by the HDCP between the PC and the screen.
That's why I like make basic grammatical mistakes, speling erors, and include a few fucks in my internet writing. Nobody's not gona mistake me for no got dagned robot.
Speaking as a developer; I've a 4K screen which is amazing for having loads of source files open at the same time, and also works for old or undemanding games. Glorious Eggroll's version of Proton has all the FSR patches in it, so you can 'upscale anything'. Almost any modern game, I'm going to be running at lower resolution, usually either 1440p or the slightly odd 2954 x 1662. Generally, highest-quality graphics and upscaling looks better than medium-quality native to me, for games where I have to compromise.
I would be interested in an 8K display for coding, as long as the price is reasonable. I'm not spending five grand, that would be crazy. But I'd still be upscaling for playing games, as basically no GPU could drive that many pixels.