In the world we have now, limiting XMLHttpRequest and Fetch to the same host as the current page would be great. But if that had always been the limitation, I fear that the adware peddlers would have just gotten proficient at shipping PHP packages/extensions that you could run on the same server as your site, and we'd be in largely the same situation, except that blocking the stuff would be harder than it is for us today.
The sex in that sex scene is supposed to be cringingly bad. Supposed to be uncomfortable to read. Did you think it was poorly done, or was it just too uncomfortable-on-purpose?
The Affinity apps being slow to adopt improvements has nothing to do with “enshittification”. They’re not actively doing user-hostile stuff for the sake of their stock price, or anything in that ballpark.
The fact is that different things are “essential” to different users. Whenever they ship a new feature, some users are like “I wanted this!” while many are like “Still not shipping what we’re asking for!”
I do think Affinity should pick up the pace (and they maybe have, a tiny bit, since V2?) and address recurring forum topics more openly. But they’re not “enshittifying” their apps, they’re just not doing what some people wish.
There's also a tradeoff between implementing features and controlling stability that Adobe regularly gets wrong. Show me a professional-- supposedly their target demographic-- that would prefer to have the latest whiz bang sloppy neural network feature or some cockamamie 3D bolt-on before fixing their huge list of shitty bugs.
reply