That is a lot of words to say that you didn't know that a witticism can become a trope, and you didn't understand my point because you were so busy trying to prove me wrong. Off you go now ...

The problem I am addressing here is that man (most?) people see AI and think it is an alias for LLM. The general term you are looking for is "AI Stack", for which AI is the short form. An AI Stack can (and currently typically does) include a LLM, but there is much more to the stack. One possible layer is the machine vision component you describe. There is a difference between generative and agentic AI, but a complete AI stack these days has both as part of a complete AI system, as well as additional components. IBM has quite a few videos on Youtube that go into great detail about all of this.

It's a common trope, but there are at least two problems with it. The first is that it assumes no two people ever died with a shared secret, which is absurd. The second is that the game isn't over yet unless they are all dead. Someone could still come forward on their death bed to reveal that it was a team.

Who said it is a "single coding style"? Imagine a small team. One is a system architect, another is a domain expert, yet another is the person who authors papers and release emails, and two more people write code. It has been speculated that a single person would have to have deep knowledge in multiple domains, and nobody has provided irrefutable evidence it isn't a team who happens to know what code reviews are and how to use them.

This is a core misunderstanding that is often repeated by people who haven't researched AI system design. The new models are not LLMs, though they do have one component in the stack that is an LLM. What you are doing is talking about a web stack as though it was just a database, then talking about what databases can and cannot do ... essentially saying "databases can't create user interfaces!" ..."I really hope people will stop over-hyping these database thingys." For the record, the linked video doesn't paint the whole picture, but is merely intended to make the point that the picture is much bigger and more nuanced than all of the "LLMs can't ..." types are aware.

All outgoing session negotiations are also incoming traffic. Season negotiation is bidirectional. How do you expect a server to receive the outgoing packets for the client as incoming packets to the server during initial session negotiation?

Anything short of 100% is merely a cost of doing business. This is no victory, this is yet another loss in the long history of losses against corporations.

Optimization is most often a pathway to higher levels of reward. As a result, there is an evolutionary drive that has reinforced the concept of taking the path of least resistance.

Humans are fundamentally at odds with their own nature but this is amplified when you consider which humans are selected for executive positions. As a result of these evolutionary pressures an external force is required to enforce the correct prioritization.

People always seem to assume that Satashi Nokimoto is a single person, and if it isn't then there will always be some evidence pointing to "this is the guy" and some other evidence that "this isn't the guy", but I suspect it is team. Solving a puzzle basing the approach on a false assumption is a great way to guarantee you can't solve it.

I'm not sure what idiots thought it was a good idea but it seems pretty damn irresponsible to connect vital resources to the internet. Frankly, it's past time we had a law where if the NSA can remotely knock your vital infrastructure (for civilization) offline that your company gets to pay a substantial penalty. If it happens a second time within a few years then the company executives get prosecuted for criminal negligence.

I can't wait to hear your answer to this: How do you propose to establish sessions if all inbound traffic is blocked?

I get that you are an idiot. What baffles me is your intense need to tell everyone else what an idiot you are.

It was only a lie of omission if the pertinent information was intentionally withheld dipshit.

There are two categories of realtime: soft and hard. Realtime is complicated, and no OS can guarantee hard realtime if the hardware is not up to the task (excuse the pun.) For example, if you are running an OS written in assembly language on am Intel 8051 microcontroller clocked at 10 Mhz you cannot handle events that could easily achieve hard realtime on a modern system, because the task switching overhead alone precludes such capability, even if your application is just an infinite loop.

You have actually managed to out-stupid yourself. I didn't think it could be done!