> The reason Wine/DXVK/Proton works so well is because it didn't fracture itself into a thousand downstream forks to fix one specific game.
Well... it sorta did, on the other hand the scope of the project is just too big for any of those forks to survive more than a few releases. There's a multitude of various Proton releases with a single-game support. The android-oriented builds are even a bigger of a mess.
> AI allows players to have decompiled and in turn ports of games to new platforms, enhanced versions of the game, etc.
We're ten years too early to do what you're suggesting. You need a really, really good understanding of the decompiled codebase and the original game and platform to port or implement new features.
You can't really ask "Claude, make Ocarina Of Time Widescreen" and expect it to work.
We're not ten years early. If you can afford the tokens, and can course-correct the agent when it gets off in the weeds, AI can do 95% of the grunt work of a decomp now.
Also, "widescreen OOT" is probably tweaking a pair of projection matrix floats in the binary so that might not be a great example :)
You could absolutely do that, because it's a narrow, targeted change. I give it 10% odds Claude could make that change to a binary ROM and 70% to a decomp.
It's sad that the community isn't exactly doing their best to separate developers using AI to debug poorly understood quirks and bugs of their emulation projects from those screaming "computah! Decompile me a Super Smash Bros".
MAME is doing some amazing reverse engineering work on some more recent arcade boards by using AI[1] that would've taken decades to do so by hand, and it's being conflated with some rando committing to github the result of 5 hours of Claude stirring over the Golden Eye N64 rom and then publishing on twitter "Done, here's my Patreon link, please and thank you".
> My impression was that PS2 emulation was already solved,
Far from it. PCSX2 is extremely solid for casual playing, but it takes a lot of shortcuts (especially when enabling upscaling and other enhancements) that differences both in gameplay and visuals in games like Gran Turismo and Ace Combat are extremely evident, more so when framebuffer and/or shader-like effects are applied.
Mind you it's not a game-breaking experience, but I feel it's differently enough to be considered closer to playing a port rather than an emulated version of the game.
The PS2 is unfortunately too alien of an architecture to expect BSNES-style accuracy AND an acceptable framerate.
If you spend that much money on ads you should be a Google Ad partner, and you usually get to have a dedicated, on-call support agent directly from Google.
We had a similar situation arise once (big marketing agency in EU), up to that day I've never had heard anyone screaming so loud at someone than my boss to whatever poor soul was assigned to us by Google.
I'm still wondering who's the target audience for something like Gutenberg.
- A bastardized version of React whose state is stored in...HTML comments and WordPress shortcodes. It's extremely brittle and even simply updating an article can put its content into an unrecoverable state.
- Some components are done in javascript client side, some are done PHP server side, there's virtually no clear idea when to use which.
- It's incredibly developer hostile compared to basically any existing WordPress Visual Builder. We're at version 23.9 and it still breaks its API and behavior to the point of forcing full component rewrites (see the changes between Blocks v2 and v3 in WordPress 7.0)
- Its full editor capabilities are basic at best. The default components are incredibly shallow, and to get even a somewhat decent layout you're at the mercy of third-party developers, by that point you could've avoided many issues going straight to Elementor or WP Bakery.
- It's incredibly confusing for the end-users! The default behavior of the editing tools is to appear only when a block is selected, which is kinda difficult when the blocks themselves are invisible. Also, the "everything is a component" approach means that every paragraph, every list, every heading is a standalone gutenberg component with his own properties that could affect every other block on the page. Writing something requires constantly going back and forth from the "Component Tree" view just to make sure there's no empty components floating somewhere disrupting the page when viewed on a tablet.
It's...truly the worst of every possible worlds, and much of its issues are blatantly self-inflicted. I genuinely can't think of any reason to use it compared to any other alternative.
They were targeting Medium-users with Gutenberg, which in my opinion was a misread of the growth and direction of WordPress. Even after blogging died, WordPress was still always focused on being a blogging platform. Back in the early proposal/RFA days of Gutenberg, the debate between Mullenweg, the WP Core steering team, and most vocal of the WP development community was really whether there was this "silent majority" of WP users, or whether the software should cater better to developers/power users. Mullenweg, and most of the other core steering members, believed that the silent majority were interested in an easier WYSIWYG visual editor, and they used SquareSpace and Medium as the benchmarks. Even in 2017 this was kind of justifiable, online writing/publishing didn't really seem like it was being hollowed out like it would be just a few years later.
From what I've seen around it will be a WordPress website still, running some at-best-once-updated version of Divi/Elementor/WpBakery, built using their equally terrible new AI tools.
Complicated psyop? It's called "Personas" and a few of my coworkers wrote a few of them just this morning.
You simply promote or finance marketing materials (blog posts, podcasts, youtube videos) with a clear idea of the kind of people you want to reach, and if your "Persona" (that is, ideal customer or evangelist) model is accurate enough, they will talk endlessly about your product for free without having to directly connect with them.
That's very different from faking a bunch of excited chatter and making up happy customers, which is what the original comment was about:
> Nobody cared about or was using Mac Mini's for OpenClaw, but there were all of these very suspicious posts from accounts that were clearly Apple [...]
The see it as a useful tool to better...manage the population. As many have observed already, this is just another page taken verbatim from project 2025 and applied by the current US government. "Culling the herd" phase.
That document has become the most accurate predictor of USgov future policies.
Well... it sorta did, on the other hand the scope of the project is just too big for any of those forks to survive more than a few releases. There's a multitude of various Proton releases with a single-game support. The android-oriented builds are even a bigger of a mess.
reply