If that CEO thinks the behaviors of the LLMs are "super smart", then I really wonder about his level of intelligence...

IT's certainly novel and different and can handle sorts of things that were formerly essentially out of reach of computers, but they are very much not "smart".

Processing that is dumb but with more human-like flexibility can certainly be useful, but don't expect people to be in awe of some super intelligence when they deal with something that seems to get basic things incorrect, asserts such incorrect things confidently, and doubles down on the same mistakes after being steered toward admitting the mistakes by interaction. I know, I also described how executives work too, but most of us aren't convinced that executives have human intelligence either.

Nicely said.

A favorite quote by Christopher Hitchens, describing Martin Luther King, Jr:

Even though it sounds brusque, the first time I read it I found it to be incredibly encouraging and uplifting. And Hitchens was no opponent of personal vice, so it's really not quite the insult some might take it as. There are no perfect humans - every one of us is a physical creature with unique and personal baggage bestowed on us by our flaws, circumstance, and the times in which we live. The whitewashed saints often presented for emulation are uninteresting and useless as genuine role models.

Lincoln was a Free Soiler. He may have had a moral aversion to slavery, but it was secondary to his economic concerns. He believed that slavery could continue in the South but should not be extended into the western territories, primarily because it limited economic opportunities for white laborers, who would otherwise have to compete with enslaved workers.

From an economic perspective, he was right. The Southern slave system enriched a small aristocratic elite—roughly 5% of whites—while offering poor whites very limited upward mobility.

The politics of the era were far more complicated than the simplified narrative of a uniformly radical abolitionist North confronting a uniformly pro-secession South. This oversimplification is largely an artifact of neo-Confederate historical revisionism. In reality, the North was deeply racist by modern standards, support for Southern secession was far from universal, and many secession conventions were marked by severe democratic irregularities, including voter intimidation.

The current coalescence of anti-science attitudes and neo-Confederate interpretations of the Civil War is not accidental. Both reflect a willingness to supplant scholarship with narratives that are more “correct” ideologically. This tendency is universal—everyone does it to some degree—but in these cases, it is profoundly anti-intellectual: inconvenient evidence is simply ignored or dismissed. As in the antebellum South, this lack of critical thought is being exploited to entrench an economic elite. It keeps people focused on fears over vaccinations or immigrant labor while policies serving elite interests are quietly enacted.

Broadly speaking, a lot of the 'cloud native' stuff are complex solutions to potentially complex problems that fit within the parameters that those approaches can handle.

If you don't have those complex problems, then it's a premature optimization that is painful. If your use case is not the sort of use case resembling the bread and butter of the applications that instigated these approaches, then it's all pain, no gain.

There was a team that maintained a project that was broadly panned for not being good enough. The developers decided that the cure for what ails them would be changing to 'cloud native' approach, despite the complaints really being about limited functionality, not even about performance or scaling issues. Now on top of having the same functionality complaints *now* they have performance and reliability complaints too, and they have no idea what they are doing, they just arbitrarily carved their single fixed instance of software into a couple of dozen fixed instances of services (they can't figure out how to scale arbitrarily, so they still have exactly one instance of every component). Not one of them is capable of debugging the convoluted network situation they've created, and the logging information is just a mess.

You already had your turn in the late 2010s after big data and before AI. You don't get to come back to the hype line for seconds.

It's different from humans in that human opinions, expertise and intelligence are rooted in their experience. Good or bad, and inconsistent as it is, it is far, far more stable than AI. If you've ever tried to work at a long running task with generative AI, the crash in performance as the context rots is very, very noticeable, and it's intrinsic to the technology. Work with a human long enough, and you will see the faults in his reasoning, sure, but it's just as good or bad as it was at the beginning.

Correct. This is why I don't like the term "hallucinate". AIs don't experience hallucinations, because they don't experience anything. The problem they have would more correctly be called, in psychology terms "confabulation" -- they patch up holes in their knowledge by making up plausible sounding facts.

I have experimented with AI assistance for certain tasks, and find that generative AI absolutely passes the Turing test for short sessions -- if anything it's too good; too fast; too well-informed. But the longer the session goes, the more the illusion of intelligence evaporates.

This is because under the hood, what AI is doing is a bunch of linear algebra. The "model" is a set of matrices, and the "context" is a set of vectors representing your session up to the current point, augmented during each prompt response by results from Internet searches. The problem is, the "context" takes up lots of expensive high performance video RAM, and every user only gets so much of that. When you run out of space for your context, the older stuff drops out of the context. This is why credibility drops the longer a session runs. You start with a nice empty context, and you bring in some internet search results and run them through the model and it all makes sense. When you start throwing out parts of the context, the context turns into inconsistent mush.

The line has muddied, as consoles went USB and console accessories started being PC compatible.

Once upon a time, you popped a game cartridge into a purpose built specialty thing with bespoke capabilities to do the things the game companies wanted, with proprietary connectors and instant boot up and what you get is what you have.

On the PC side, you futzed with config.sys/autoexec.bat to have just the right memory layout, depending on if you needed the maximum conventional memory, ems or xms, and environment variables to match your dip switches.

Now a game console is an x86 box that takes some time to boot to an OS then you select an app, which probably is a game, and good chance it's developed with a game engine that pretty much equally supports Nintendo, PS4, and Microsoft ecosystem.

The PC side you just plug in, often the exact same accessory, and things automatically go. The UI of Windows can be obnoxious, but this is a prime mindset for Valve to take advantage launching their PC that's 10-foot optimized out of the box.

Nintendo held on to console-ness longer, with their Wii and Wii-U gimmicks, and their switch admittedly isn't an x86 box, but it's basically a gaming tablet, which is the other big thing eating into the casual gamer market.

The thing is that while the heat pipes can work in space and may have been used in satellites and then brought to earth, the issue is with the amount of thermal energy and having radiation as the only way to evict heat.

So while the mechanism for heat pipes started in space, the computers are *way* more wattage than the space based applications.

I wonder how the developers feel about that characterization. Now all performance improvements are subject to being attributed to motivated by AI for marketing points...

It probably makes more sense given their scale for them to have their own power generation -- solar, wind, and battery storage, maybe gas turbines for extended periods of low renewable availability.

In fact, you could take it further. You could designate town-sized areas for multiple companies' data centers, served by an electricity source (possibly nuclear) and water reclamation and recycling centers providing zero carbon emissions and minimal environmental impact. It would be served by a compact, robust, and completely sepate electrical grid of its own, reducing costs for the data centers and isolating residential customers from the impact of their elecrical use. It would also economically concentrate data centers for businesses providing services they need,reducing costs and increasing profits all around.

Fair point, I forget how utterly stupid businesses, particularly large businesses can get about boneheaded requirements that they mandate but do not use or do need, but could better solve it in a separate path rather than mandating it on what should be the 'wrong' product category.

Particularly surprising to forget since I'm basically continuously exposed to that in my job, but guess it eventually faded into the background of me not thinking explicitly about it anymore..

Problem with that is thinking it's vaguely new... This has been possible pretty much all along. The Cameyo demos I saw seemed underwhelming compared to almost every alternative I've seen...

Except it is a whole desktop, but with ability to request an app to maximize... It's kind of embarassingly bare bones for this level of claiming it makes ChromeOS just do Windows...

I certainly would agree with that direction, however this has been an option for an eternity and broadly hasn't moved the needle for Windows market share.

Once upon a time VirtualBox made an effort for this to work as a feature, and eventually dropped it in favor of just using Windows RDP to the same end. Doing it via a browser may be somewhat more convenient, but not fundamentally more accessible than RDP...

After watching a demo, I'd say this is in fact a step back from 'seamless' RDP, since you just get a web page with what looks like full-desktop RDP in it.