Incentives Rule Everything Around Me. What incentive does Apple have not to be shit? People aren't going to switch to anything else, they'll just suck it up and shove it in their enormous sack of learned helplessness.
Instead, if you must, add a sleep within the function for 1 ms in the first release, 2 ms in the second release, and so on. But maybe just fix the tooling instead to make deprecations actually visible.
I get the intention but it's a bad idea, same with the article
if people are meant to depend on your endpoints, they need to be able to depend on all of them
you will always have ppl who don't respond to deprecation notices, the best you can do is give them reliable information on what to expect -- if they hide the warnings and forget, that's their business
but intentionally making problems without indication that its intentional results in everyone (including your own team) being frustrated and doing more work
you cannot force ppl to update their code and trying to agitate them into doing it only serves to erode confidence in the product, it doesn't make the point ppl think it makes, even if the court of public opinion sides with you
cover your bases and make a good faith effort to notify and then deal with the inevitable commentary, there will always be some who miss the call to update
this actually seems like an reasonable technical solution to the non-technical problem that causes deprecations to be ignored in the first place
Degrading performance exponentially (1ms, 2ms, 4ms, 8ms...) WILL create a 'business need', without directly breaking critical functions. Without this degradation, there is no reason to remove the deprecated code, from a business perspective.
I think this erases some interesting nuance. The original Gundam is unabashedly a toy commercial--ostensibly marketing to children in the exact same vein as the OG Transformers--except apparently nobody told the director, so it's an extremely emotionally mature show (more so than nearly all YA fiction) where the main character, a teen soldier, is narrowly escaping death, is killing people, is watching everyone around him be killed, is suffering the effects of PTSD, is being openly used as an expendable tool by his superiors, is on the run for his life being hunted by half the world, is coming to terms with the costs of war and the throngs of innocent bystanders being reduced to burning ash for the sake of cruel and ambitous men, and did you know you can buy his cool robo-flail accessory at Toys 'R Us today?
It's not that nobody told the director. It's that the director knew nobody cared what was actually in the show as long as the end product moved units on the shelves.
It's part of the reason the names are so wild. He was actively pushing the envelope with outrageous names during pitches to see how far he could go before producers would stop nodding along without paying attention.
Those names include "A Baoa Qu", "Gelgoog", and a variety of insane character names that sometimes sound cultureless yet futuristic like Bannagher Links and sometimes are just "M'Quve" or "Full Frontal".
A demake would be a reimagining of a modern game into the style and aesthetics of the time. E.g. taking God of War and turning it into a 2D Shinobi-style platformer for Sega Genesis. Or turning Gran Turismo into a Mode7-style racer on SNES.
In this case, the creator wrote a custom 3D renderer and recreated the models/meshes to get as close of an approximation of the N64 experience onto the GBA.
I wouldn't call it a port necessarily ("recreation" seems more apt), but it's closer to that than a demake.
Back in 1930s Germany, there were other boats afloat to escape to.
Here in 2025, you live in a globalized world. The rats are soon to be out of ships to flee to. There's no free society in the Sol system that survives rampant and unchecked authoritarianism in the triad of the US, China, and Russia. Europe is a military vassal of the first, an economic vassal of the second, and an energy vassal of the third (though increasingly of the first two). By all means, I'm happy for Europe to wake up and prove me wrong, but looking at their tepid reaction to being invaded by Russia three years ago I'm not holding my breath.
> Europe is a military vassal of the first, an economic vassal of the second, and an energy vassal of the third.
The UK may be something close to a military vassal, what with its "independent" nuclear deterrant relying on US missiles, but the French deterrant is not and France is not.
Economically, we're all interdependent right now: China depends on the US and Europe, Europe depends on the US and China, the US depends on China and nad Europe. Current US policy is pushing everyone everywhere to disconnect from the US, ironically without even doing the one thing tariffs are supposed to be a tool for which is protrcting strategic domestic industry.
The Russian invasion of Ukraine has pushed the EU away from Russian energy much faster than it would otherwise have done from decarbonisation efforts. Given who the world's factory is, I'd expect a lot of our PV and wind turbine components to come from China, and even if they don't directly for the Chinese supply to substantially impact the price.
> the triad of the US, China, and Russia. Europe is a military vassal of the first, an economic vassal of the second, and an energy vassal of the third.
What an hyperbole.
There are also other places in the world besides Europe, the US and China.
The billionaires seem to have settled on New Zealand as the right combo of “stable-enough liberal democracy that they probably won’t seize my treasure hoard” and “hard enough to reach that climate and political-instability refugee waves cannot get there”.
If you think Europe is a military vassal of the US, I'd suggest a read of the latest US National Security Doctrine.
China, agree.
Russia? Not so much, now the war is 1385 days in - and the US is currently dilly-dally-ing on their stance(s).
This is cope dressed up in the stereotypical Gruber sycophancy.
The decision to align iOS and MacOS with the glassy design of VisionOS was a broader corporate strategy that would have required buy-in from more execs than just the "chief design officer". If you accept that this particular bozo wasn't forced out but instead was tempted away by the scent of lucre wafting from Zuck's pockets, then that implies that there are still plenty of clowns left at Apple to fill out the circus.
The problem is, Liquid Glass isn’t all that closely aligned with the visionOS UI, despite both having glass-like qualities. Most notably, the iOS and macOS versions are missing the usability affordances that the visionOS version has, and more superficially the visionOS version looks nicer.
Yes, but it could have been as simple that the UIs should look like they come from the same company - and that is the correct path IMO. At that point, it's the Chief Design/Product person's responsibility to execute on that order.
At the very least, authors who have been caught publishing proven fabrications should be barred by those journals from ever publishing in them again. Mind you, this is regardless of whether or not an LLM was involved.
> authors who have been caught publishing proven fabrications should be barred by those journals from ever publishing in them again
This is too harsh.
Instead, their papers should be required to disclose the transgression for a period of time, and their institution should have to disclose it publicly as well as to the government, students and donors whenever they ask them for money.
No, this is overly simplistic. The features in the quoted comment are largely things that nobody other than stdlib developers need to understand. There is no bespoke subset-dialect of Rust where people are tossing around the `fundamental` attribute--it is strictly an obscure detail that not even an expert Rust programmer would be expected to have even heard of.
The main issue with "fundamental" is that it's currently unstable, but a stable version of it could definitely be useful for lessening the "orphan rule" constraints on implementing traits. Probably would want a different name such as #[deorphan] though.
reply