Pixel artists dominate the indie scene, these aren't the people losing their jobs to AI. Major developers at the behest of fans dissuade the use of AI for art generation (at least the art that gets published with paid games), and Steam requires developers to flag when AI art is used.
Game devs are losing their jobs for plenty of other reasons, but AI art isn't one of them.
For HN, it would be better to point to the website rather than an app - https://www.oddsrabbit.com/. Looks like it has the same poisonous new reddit-style infinite scroll/low post density where any discussion is a secondary activity.
Why is an oft-wrong rumor site which churns out clickbait left and right being pushed up on HN? There's no story, here. It has no reliable source and nothing coming directly from Apple.
macrumors.com, 9to5mac.com should have been [dead].
Why? They are incredibly amusing news sites that have been around for years, absolutely more correct than not correct. And it is called Mac RUMORS, not Mac CONFIRMED_PRESS_RELEASES. Alas, you should not blindly trust every leak and rumor.
Yes and in the wild believe it or not you'll find windows 7 and windows 8.
We had just deprecated support for XP in 2020 - this was for a relatively large app publisher ~10M daily active users on windows. The installer was a c++ stub which checked the system's installed .NET versions and manually wrote the app.config before starting the .net wrapper (or tried to install portable .NET framework installer if it wasn't found at all).
The app supported .NET 3.5* (2.0 base) and 4 originally, and the issue was there was a ".NET Framework Client Profile" install on as surprising amount of windows PCs out there, and that version was incompatible with the app. If you just have a naked .NET exe, when you launch it (without an app.config in the current folder) the CLR will decide which version to run your app in - usually the "highest" version if several are detected... which in this case would start the app in the lightweight version and error out. Also, in the app.config file you can't tell it to avoid certain versions you basically just say "use 4 then 2" and you're up to the mercy of the CLR to decide which environment it starts you in.
This obviated overrides in a static/native c++ stub that did some more intelligent verifications first before creating a tailored app.config and starting the .net app.
I feel for those who have to support an OS no longer supported by the vendor. That's a tough position to be in, not only if a customer comes across a bug that is due to the OS, but it keeps you from advancing your desktop application forward.
You can always have legacy builds for older systems and use shiny new features inside conditional compilation blocks. Or check at runtime and let newer operating systems use the new features. Yes it takes care and a little more testing to keep supporting older operating systems but your users will love you for it.
I’m always kind of sad when a developer says to a customer “your OS is too old. We are dropping you on the floor.”
reply