1. WSL is effectively Linux. 2. Most importantly, Linux support is mediocre at best (I owned 10+ laptops) - for developers who don't want to pull their hair on hardware incompatibilities, or want to be bound to a small part of the laptops/desktop parts, it's either that, or a Windows-only machine.

Fun (in a sad way) stuff: even the Ubuntu certification is a joke - Canonical is allowed to use customized versions of Ubuntu that they aren't required to release to the public; as a consequence, even hardware certified by Canonical as Ubuntu-compatible, can effectively be incompatible. I've been bitten by this twice.

If they just decided to invest, say, 20% more on quality, they'd have very competitive products - but they just don't.

There's actually a very simple answer to that! A laptop is a mobile device with the set of functionalities that macOS has, but iPadOS hasn't :)

I wish this was ironic (I'd love to use the iPad Pro as laptop), but it isn't.

There are a few problems though, primarily, a GPU with lots of VRAM and very high bandwidth is inherently very expensive (on top of which there is also the CUDA premium); AI use cases are better served by SoCs with lower (but still high) bandwidth and more RAM.

Using the published bandwidths, the math is 170 * 1 and 153 * 8.

If an implementation is "a black box that works," absolutely, LLMs are fine. They can create complex programs in full.

But if one expects a tight implementation... it's a horror. LLMs vastly overengineer code (I believe they're intentionally designed to do so). I really struggle to make LLMs generate lean code.

In the best case, they generate bloated designs (in terms of complexity, not necessarily performance), but in the worst case, they generate gaps in the specification. And even in the first case - cognitive load is a problem also for LLMs, not just for humans (although obviously at a larger scale).

I think LLMs are essentially modern compilers, with similar problems, but designed more like "deoptimizing compilers" than optimizing ones. :)

If you're experiencing a bug that pegs you're CPU, fair enough. But RustDesk is video-stream based (in many formats), while TightVNC is image(-region) based. This is actually similar to why you watch movies in, say, H.264 rather than Motion JPEG¹.

¹=similar, not same.

If a package doesn't have particular build requirements, setting up a PPA is overall simpler than hosting a personal repo (I do both).

There are Canonical PPAs for that, which make distribution much simpler (it's still not as simple as it could, but with AI's help it's simple).

- Meta is commissioning or sponsoring rage-bait

- Controversial creators are earning money through Facebook's content monetization program

The title is ambiguous (at first, I thought it was the first case), and that's where the clickbait lies.

No doubt that also the second case is a serious problem, but that's orthogonal to the ambiguity of the title.

For those who also lived in southern countries, what I mean with "rigid" and "humorless" (among the other things) will sound very familiar. I've talked about this topic recently with a few friends from southern cultures, and they also shared the fact that (among the other things) expressing themselves the same way they did in their own culture, would be considered crass/inappropriate (to say the least), and in some contexts even abusive (happened to me).

Sibling poster highlighted how culture can be intended "in the sense of "expected norms and behaviors"; that's also part of it.

When I personally want tight code, I have to spend a considerable amount of time adjusting it manually:

- It needs to be trimmed down. In my experience, at least one agent I use struggles to produce minimalist designs, and it's very frustrating

- I need to consider whether there are solutions based on higher-level assumptions, that AIs typically miss

- I need to check whether there are off-the-shelf solutions - AIs like to reinvent the wheel

IMO, software production has become a mass-produced commodity in every sense - it's much more expensive to produce software manually, but the quality is not the same.

(1) https://simpsons.fandom.com/wiki/The_Homer

> All we see out of mainstream AAA gaming is abused devs, private equity scalping, and mindless remaster regurgitation. Basically going through the same problems as Hollywood is with major films. You get a massive banger of a production every few years, and the rest is just endless money burning and developer harm.

The production ethics and the product are two distinct aspects.

Regarding the product itself, definitely the AAA gaming industry is, like Hollywood, a dysfunctional production model, but that doesn't mean that it's dead in terms of quality - some franchises do maintain high quality (Doom has been exceptional in this sense) but even in terms of new IP, in average, there at least couple of high quality entries in average, every year. Things could go better, but they're certainly far from "dead".

One gets the impression that gaming is dead when one's only contact with modern gaming consists of reading headlines about a handful of AAA games.

In reality, the gaming landscape has never been better, as game production has expanded in several directions:

- The barrier to entry into game development has been lowered; People who are talented in design but not programming now have the opportunity to create games

- AAA budgets have increased; those who enjoy large-scale productions will find increasingly large games

- There is still a market for old-school games, so plenty of (especially smaller) companies produce retromodern games

Heck, they even still produce commercial Commodore 64 games o_O

Of course, there is less room for radical innovation, but people do not play only radically innovative games. And regardless, innovation still exists today, especially in smaller-scale productions.

This is progress in the same way that a man climbing a tree is making progress toward reaching the moon.

This project is essentially the MoE-of-the day, with some platform-related optimizations.

> Keep going! I personally can't wait for the day when a 1t param model runs off a $200 SSD instead of a $50k rack of Nvidia chips.

That won't happen. Projects like this just give the illusion that that will be possible.