521 karma · joined December 20, 2025
You choosing to send said clanker to the fight armed with your credit card and no preparation is just you causing yourself harm.
It also happens to be really fun to help you harm yourself in that way.
Considering they're pretty much fully undocumented (officially, that is) and could contain any number of IME equivalents since we know that they already have independent processors like the secure enclave running its own OS: yeah, probably more weird. Just because Asahi did not find one doesn't mean it doesn't exist.
"Oh no, there's a bully. Let me just find a toxic relationship and hope they spend enough time bullying my bully so they forget about me" isn't exactly a recipe for success.
Sure, 3rd party will get some shit. But if Apple neither protected me on their App Store _or_ on the app stores that they extort, what the fuck is their racket for? As long as Apple keeps this behaviour, they deserve to have their cornflakes pissed in.
Yeah, that's the whole fucking point.
Game dev & asset work is probably happy with a 5080 and that's what most rendering/dev machines would have.
The addressable market of "i have 6000 to blow and i need meh performance on anything related to 3D rendering" is small, and benchmarks make it look bigger than it really is.
cool story, but nobody cares about mobile GPUs for blender. A 4080 eats an M5 Max alive for breakfast. The 5080 in my machine that cost me 1500€ runs circles around an M5 Max that would cost me over 6000€. And when in 5 years the 5080 isn't enough, I can upgrade it to a 7080 or whatever, which will remain compatible.
If you're a professional, soldered products like the RTX Spark or Apple's offering are a dead end. They are literally never worth it.
You. Cannot. Win. Against. Capital.
And then you're going to sue, and realize that the system is so massively overloaded that the next available judge and jury are in 32 years. Also they're lobbying to replace those with AI judges where they entirely removed the concept of nuance.
And guess what: stock prices going down is just reallocating capital somewhere else.
If your goal is to get rich, you make more money as an L3 at Google doing absolutely fuck all than an L5 at Epic does bearing the entire responsibility of an entire subsystem on your shoulders.
"Price go down means more demand" applied blindly is a an economic theory so absurdly shit that even the most apeshit libertarians like Ayn Rand know it isn't true. Don't make me defend Ayn Rand.
Shareholders see you as useless meat to dispose, the ideal number of employees to them is ZERO.
"Intellectual" jobs, that require thought were yet spared, as the only way to use capital for that was just to pay for more meat: see Accenture, CapGemini, IBM, etc. You could carve yourself a spot for some people because it was hard for this capital to reach them. Now that AI, a literal machine that automates thought, is here, the costs for reaching bumfuck nowhere to take the clients away from you has dropped drastically for them, but not for you. They get economies of scale, already established patterns, tools, internal databases. You're starting with hopes, dreams and a $20 Claude sub that runs out at 10AM.
There is not infinite need for lawyers, there being more lawyers does not create more legal opportunities and cases past a certain point, and you're then dependent on other things like there being enough judges.
Robots transformed capital into manual actions and killed most manufacturing jobs save for precious few experts or things that are too expensive to automate still. AI will transform that capital into intellectual labor and crush you, take all opportunities away from you.
Framework has to go talk to Intel and AMD, get parts shipped, assembled onto a motherboard that they have to make themselves and ordered in very low amounts then shipped all to their fulfillment center, then fedexed, have to source components... Even not taking into account the fact that Apple already has all of the hardware made or available in-house, just the supply and logistics chain is an easy 10% of the final price.
>there's a large pool of juniors/interns that will accept these low wages just because they want to be a part of something popular.
That's an unbelievably bad _and_ disrespectful take. They accept these low wages because it's their only way in the industry, and because the industry has made sure to keep a steady supply of fresh meat to burn out. "because they want to be a part of something popular" doesn't work when the vast majority work on unknown games in content factories for the first ten years of their careers.
Your LLM has forgotten whatever shit it wrote when you opened a new tab, and that responsibility is now on you. And it wrote absolute dog shit
A full, whole, entire _minute_ ?! Sixty seconds ! Oh no, they must be optimized away, we do not deserve our free time like so, we should toil until we fall over because... Growth?
It's still context switching. Either what you're doing is surface enough that you don't give a shit, it doesn't matter and you don't review it anyways (so the only context is basically the prompt you wrote or the nth SELECT * FROM table CRUD piece of crap), or you're context switching and it's fucking you over. The context isn't about remembering how you write if err != nil, it's the expected behaviour of what you're working on.
You're not getting a promotion from doing this, you're getting burnout.
> Feature branches, as well as most types of branches, is to set aside work fronts that are in progress and run in parallel
They're not running in parallel, unless you use work trees. They were put to the side, because you can't continue or finish the work they're about. Even just three branches in parallel in a modestly active repo that happen to be long lived drift enough that just keeping them up to date with develop makes it a waste of time.
Focus on one or two things, and do them well.
That, or get checked for ADHD.
Your feature branch is to put things aside and send them to CI, or wait and think on them. Not to have four of them running in parallel in your head frying you.
Keeping that many tasks in parallel, running all the time will kill you.
FPS drops in PoE would not be caused by damage recalc: this is done entirely server side and on application of the damage/dot tick. That drop you're seeing is just loading the assets and recompiling some shaders, if anything.
But also: it doesn't need to be realtime. Your damage is a simple math formula, applied against another for enemy defense, for each hit instance. There are definitely some builds that stress servers due to the sheer amount of hits/tick, but that's a matter of optimisation. PoE lowers server ticks when it can't follow.
The post is talking about optimizing for build damage/resistance/etc, crafting a build. Which probably doesn't even take into account conversion shenanigans, over time things like wardloop that requires setup, cwdt and a load of other things. This is not an optimizable thing in any reasonable time, and human application of logic is pretty much faster.
Just so you know, careers as a bootlicker are kind of a dead end.
if skill == cleave and support == focused_edge: make cleave smaller but stronger
if skill == cleave and support == twin_cleave and rule == guarded_arc: quietly move to the woods
>That can work for a demo. It gets rough once the game has lots of skills, supports, items, statuses, and encounter rules.
Laughs in path of building : https://github.com/PathOfBuildingCommunity/PathOfBuilding-Po...
Path of Exile has deeper mechanics than pretty much every other ARPGs out there, PoB covers the vast majority of them, in a beautiful mess of about 20k lines of calculations in various files.
Making it a "Compiler problem" makes it an unsolvable one in acceptable time.
Fun fact: it directly parses mods from their ingame description into a mod database that is basically a stringly typed list of whatever increases also. : https://github.com/PathOfBuildingCommunity/PathOfBuilding-Po...
Second fun fact: that's the one for Path of Exile 2, that has different mechanics. The PoE1 version is the same thing, except even larger.
So yeah, don't bother about making a compiler. Your compiler will figure out micro upgrades and die in three months when the game adds incompatible mechanics. Stay agile and on your feet.
And no, I do not believe that Musk's flabby arms or Bezos' shiny head are a threat of bigger violence to me anyways.