p1necone

One non-obvious reason might be that it's the only handheld console with a natively 240p height screen. This means all the 2d ui elements will remain crisp at the same size as they would be on original hardware.

I've long thought that pure desire/drive is much more important than intelligence in just about everything, including things that stereotypically require intelligence like programming, math etc.

> "Sweden's clean energy capacity is fixed"

This is a weird assumption to make. Why would you assume they wouldn't just build out more capacity as demand increases?

They certainly aren't buying electricity from Texas, this feels like a tortured argument you're just making to retroactively support whatever opinions you have on the pros or cons of clean energy.

Have you tried letting AI agents make design decisions on their own? (technical or otherwise), in my experience you still need to properly understand what you want to get good results - you would need to have a deep understanding of all the potential warts, security holes, usability issues etc - developing a CMS via AI is still a substantial project.

More detail: at current prices gold is $133k USD per kilo - at that price transport costs would be such a tiny fraction of the value of the cargo that it wouldn't make any sense to pinch pennies - you'd want to go with the absolute fastest, safest option.

Gold is heavy sure, but its $/weight value is still much higher than basically any other cargo - the plane vs ship choice would be even more weighted towards the plane with gold than with most other cargo.

That'll teach me for trusting pricing information from Google ai summaries...

>I'm sure someone will point out some spec that's better on the PS5

They're not even in the same ballpark - the PS5 is more than an order of magnitude better in GPU performance.

Despite how much it does matter, RAM is not the only thing you need for running LLMs - that N150 is not going to run anything but really tiny models at any sort of reasonable speed - certainly nothing that approaches using all of its ram. The GPU in the PS5 is ~25x faster. And if you're running games the RAM doesn't really affect performance at all once you have "enough" for a given game.

You're right that you probably could build something quite a bit faster than a PS5 for the same price though - if you can build/find everything but the GPU for ~250 USD and slap a 16gb 9060xt (~25tflops @32bit compared to the PS5 gpus ~10tflops @32bit) in it for another ~350 USD it should theoretically do a better job - the GPU in the PS5 was on par with mid-high end PC GPUs on launch, but that was like 5 years ago.

Post it note in a drawer somewhere baby

The cost of the tokens used to output a typical academic paper length document is on the order of cents, even for frontier models. The vast majority of the cost is in the discussion leading up to that final output - there's no reason someone would try to produce a shorter paper just to save tokens.

My weird take: I wish Nintendo would ship an even less powerful system.

The switch and switch 2 are both just powerful enough that developers can release straight ports of their AAA titles that were developed for other systems, but at the cost of significantly degrading framerate/framepacing, visuals, nothing ever running at native resolution etc.

I would much rather it was more like the Wii and all their previous handhelds where the performance gap between it and the other contemporaneous systems was so big that developers had to develop bespoke games for the system, and ports had to be ground up rewrites.

Everything was so much more playable, and by buying those systems you had access to an entirely different library of games to choose from, rather than the current situation where it's just the first party Nintendo titles that differ from what's available on all the other more powerful systems.

Yeah I tried to daily drive Nix at one point pre AI and the ergonomics were just not a good match for me - perhaps I should try it again.

> The only insane thing about UB is that compiler writers took what everyone understand meant "the compiler emits what it emits and you get what you get" and turned it into "since it's undefined it means it can never happen so we can delete your null check".

This is the bit that seems insane to me. Some of the behaviour of C/C++ compilers when they encounter undefined behaviour seems less like 'this is undefined, we'll just do something vaguely reasonable given the context/produce an error' and more like 'ahaha, the user has fallen into our trap, lets fuck them up'.

Hence the 'specific to C/C++' part of that sentence. 'Undefined behaviour' is a probably unavoidable part of programming language design. The way that C/C++ interpret/handle it is batshit insane.

The concept of undefined behaviour specific to C/C++ has always seemed batshit insane to me, and I'm yet to read anything about it that has made it seem any less so.