> Another CEO with AI psychosis [1]. LLMs are not true AI, they lack common sense (or whatever it's properly called).

If you read the article, you'll find that the it indeed relies on this claim:

> Within a couple of years, possibly much sooner, AI may achieve so-called closed-loop recursive self-improvement (RSI): the capacity to rewrite its own code to become more capable, without human intervention. Should that happen, the result could be an intelligence explosion of a kind for which there is no precedent and no map.

This may be optimistic and/or simplistic, but not impossible.

>the result could be an intelligence explosion of a kind for which there is no precedent and no map.

Or it will simply reach the end of the softmax faster.

Flashback came considerably later (1992) than PoP (1989); a single year back then was a lot more significant than it is today. A classic game in between was Another World (1991).

Just out curiosity, PoP ran on 8088/8086, while Flashback on 286/386.

OpenAI and Anthropic are certainly strong drivers, but there's a large demand from many other players: cloud provider, accelerator vendors, and so on. I think there's no end in sight.

Slight?? It has 3g of salt per liter, which is very high - not least because 1g of that is sodium. Having said that, I like it very much.

Confirmed. Minibooks are amazing in cramped locations (for example, airplane seats), or just to always keep in the bag for support.

There's nothing in the market like them, which is a shame - I think a slightly better quality Minibook (Chuwis are plain crap) would be a very solid laptop.

I just responded above, but you might want to look at the GPD Pocket 4.

It is NOT cheap ($1300 min spec) but it's also quite a bit more powerful and with better ports (full size HDMI and Ethernet). It's not for everyone, but it blows my mind how little competition it has given how useful its been for me over the years.

8.8" is a bit too small for my use case, but... oh my, their Win Max 2 is a very impressive machine (10.1") - I'm really shocked at the size. I'm confused by the price, though - 6500$??

a Steam deck with a small form factor keyboard?

I so wanted to love the Steam Deck, but it's a device with a 7 inch screen that occupies a massive volume on your bag. Unless you know you're going to play a fair ammount, it's not worth carrying around.

It's a fantastic console, but a mediocre general purpose computer.

A Steam Deck is a bit more lumpy than the Minibook. I find it a lot easier to put my Minibook into a rucksack as it's thin, so it can just slide between stuff. The Steam Deck is quite a lot bigger, though I often take both on holiday as they fill different needs.

Legion Go (1st Gen with the removable controllers) would be better. Without the controllers, it's basically a 8.8 inch PC tablet. Would be a great portable machine. With an added bonus of the controllers converting to a desktop mouse.

It isn't realistic to expect a design to be "proper in first place" because requirements change; my opinion is indeed the opposite - I find it natural for programming languages to have a (sort of) lifespan, and for new ones to (sort of) take their place.

Sure but literally everyone and their mom said these features were needed and then Go team said "nuh uh!!!" But, as it turns out, they are needed because they solve real problems, and are not just fake complexity like some people strawman.

Hopefully next they can add some error handling syntax and controls.

Indeed, in 2012, it was not clear to anyone that generics were needed /s

> Not everyone needs that fast RAM access but for those who do it could be nice to have an option. The writing is on the wall for years now.

There is an option already, at least from AMD, in the HEDT segment - Threadripper/Pro has 4/8 channels (although the bandwidth is not a high as Apple chips).

> I think the use of AI is really missing the point here. The point is that small in-house teams can deliver a lot more quickly and to a higher quality and at a lower cost than large outsourced teams from the big consultancy companies.

This assumes that small in-house teams are inherently effective/efficient, which is not necessarily true.

In this sense, the difference between proven engineering leads (as the article states/assumes) leading a small team versus AI is that the latter is entirely under their control, which minimizes the risk.

So AI vs. small teams is about controlling/guaranteeing effectiveness/efficiency.

EDIT: the leads are, in practice, managing a small team, although their exact technical background is unclear ("experienced practitioners who know how to design and deliver digital products", not clear if they're professional software engineers).

The article argues that although this is an asynchronous process:

> Long running work: an agent doing a 10 minute task isn’t a ‘request’, it’s a long-running async process.

it should not be stateful at the database/storage level:

> Stateful compute: an agent might run multiple turns of a conversation, might process multiple tool calls, and relies on accumulated context. That state is not really ‘database state’, it’s the agents memory.

According to the author, the problem is already solved, but implemented with the wrong design assumptions.

(Uploading a file for conversion could be framed as a slightly different problem from the author's, though, due to size constraints)

Because the speed increase is - on modern, properly tuned filesystems - surprisingly small, due to how RDBMS's manage their pool; by working on large container files, they avoid most of the filesystem overhead.