I do suspect that OpenAI will be the 'Netscape' of this bubble pop. Early mover that in many ways sparked something significant that got left behind by others that did it better.

I am so eager for a bubble pop to recalibrate expectations to properly leverage LLM as appropriate instead of the current madness. It will be an adjustment, but without the craze it won't be nearly so obnoxious.

Anthropic announces that they have a super awesome AI product that's just too awesome for anyone for anyone to see.

And then immediately OpenAI has the exact same thing.

FOMO on "my technology is too scary to exist" is a fun twist.

I know, it's not the first time, someone even linked an article where OpenAI said the same sort of thing about GPT-2 back in 2019...

... for an absolutely hilarious screwball comedy movie.

I'd want:
- Trivially replaceable battery. This means no glue, and ideally means a standardized battery approach to maximize chances of buying a replacement one down the line.
- Putting ports on a separate board than the CPU and ram and such. Physical damage comes to ports, especially charging ports. Having this delegated off board minimizes risk of having to replace something expensive.
- Replacable keyboard and screen. Again, at high risk of damage and should be replaceable
- Removable storage. If your mainboard does fail, smoothest if you can move your SSD over to the replacement main board.
- Commitment to consistent form factor. If 5 years down the line it breaks, I can accept if I can't get *exactly* the same board anymore, but it would be nice if I could just get a new generation board and replace it without letting perfectly adequate screen, keyboard, case go to waste.

So mostly Framework, Lenovo recently did a think with a Thinkpad also exhibiting most of these, except no indication of generation to generation consistency in parts.

On laptops like the ideapads, yes.

I have not seen a ThinkPad where they did this with the keyboard. The commenter was specifically talking about Thinkpad.

Note that this report might be based on perusing websites more than hands on evaluation.

That said, "Lenovo" laptops include the non-thinkpads, which tend to be *terrible* for repair-ability. For example, in many cases they don't consider the keyboard to be a part worthy of keeping replaceable without replacing half of the laptop, despite it being one of the most likely things for a user to break. You can get third-party parts that is just the keyboard, but you have to destroy a lot of plastic welds to even try, and there was never a design to put it really back together after you did that.

The Thinkpads tend to do pretty well, though increasingly the cpu and memory are "just part of the board now", but honestly that's just the direction of that industry in general. We are pushing physics, it's harder for us to do modular RAM at the speeds we want to interact with the RAM, LPCAMM is a thing, but even then you just have a single LPCAMM and it's less about 'repair' and more about being able to have different memory amounts by swapping the module out.

Couldn't find actual details on *which* models they looked at.

If you look at the non-ThinkPad Lenovo laptops... They are complete shit for repairability.

The ThinkPads on the other hand tend to be very very good.

But other issues make me wonder about their competency in writing the report. Notably they give Lenovo a "lobbying penalty" for being a member of a group that fights right to repair but gives Motorola a pass for not being in those groups.... Lenovo and Motorola are the same company, and they don't seem to realize that.

... that the ultra-tech ultra-capitalist are the ones actually making true marxism possible, recognizing that if all goes as planned capitalism will soon have reached its final goal of making itself superfluos and that we need a post-scarcity post-capitalist measures to handle what's next.

In that regard Zuckerberg, Pichai, Musk and Co. are more woke and progressive than any l00ny noisemaker on the interwebs could ever dream to be. The irony is quite impressive.

Wasn't there an 80186? That literally nobody built anything with? Like, it was almost a proof of concept?

Just today I noted that GIMP 3.2.2 (an application, not an OS) has dropped support for 32-bit x86.

It's not out of date, it's a simplification.

They don't innately understand their capabilities, but information about it's own capabilities may be fed explicitly into it by other means, just like any other data you want to endeavor to put into the context.

The concept of asking if it implements a certain behavior and either it's deliberately lying or it's not actually there relies upon a false assumption that of course it has innate knowledge of it's own implementation without any "help".

The core relevant issue is that the LLMs will generate an answer based on no data. Instead of "Information on that one way or the other is not available to the model" it sees the answer most consistent with the narrative to be "Those behaviors do not exist". LLMs tend to generate output that implies confidence regardless of whether there should be confidence or not. The workaround has been to try to do everything possible to make sure there is actual data in the context window and hope it just doesn't come up that much, but this is only so possible. Some coding has the opportunity to use test cases to add "the output given failed to work" automatically to the narrative to drive iteration and maybe get further.

What's more, you really have to know what you're doing to coax it into re-using code, rather than rewriting the same functionality with each prompt.

Isn't there an API for lazy loading? What's wrong with that? Developers not using it? They should be very careful of trying to outsmart dumb web "developers", the Web is messy enough as it is.

This will help push FOSS gaming and community driven self-hosting of gameservers back towards mainstream. And that's a good thing.

They did, but it's never too late to cheapen how they're current stuff is produced.

Still, I think they know all too well that mainframe is "stuck" doing it the way they always have done it.