StressedDev

You can run software on bare metal without an OS. The downside is you have to write everything. That means drivers, networking code, the process abstraction (if you need it), etc.

One thing to remember is an operating system is just another computer program.

You would end up blocking every network then. Almost no one wants malware on their machine or network. Unfortunately, people get hacked and network operators cannot always determine which machines are hacked (hackers are not known for letting people know that they have taken over a machine).

Security is hard and there are no easy solutions. People often do not know they have been hacked or even know if a computer on their network has been hacked. Also, it is often not easy to determine if traffic is legitimate, illegal, malicious, or abusive.

Wire-fraud is a United States legal concept. It's probably not applicable to Germany (although Germany might have its own laws which cover this issue).

I wish these companies luck. That being said, I would not recommend working all of the time to almost all people. Here is why:

1. According to Rapid Development or Code Complete (I can't remember which book said this), for most people, working more than 40 hours a week does not increase productivity in the long term. Basically, you can spend more time at work but you will not get more done. There are a few people who this is not true for but those people are rare and they usually are extremely driven because there is something about the project is really really interesting to them.

2. I strongly suspect most humans are just not built to work all of the time. It's not that there is something wrong with them, they just can't deliver more than about 40 hours a week of work. This isn't because they aren't committed, don't care, are lazy, etc. They just can't do it. I think this has to be accepted.

3. I have tried for decades to make the live at work lifestyle work and I have failed. I have repeatedly burnt out. It has taken me decades to realize that it is not a question of what you want to do, it is a question of what you can actually do and what is sustainable. Basically, you or your boss may want you to work 60 hours a week for months on end but that is probably impossible and it's better to accept reality than to keep on trying to do something which does not work.

Note that when I hear employers demanding crunch time, it tells me the leaders do not understand how people work because they don't understand that 99% of their employees probably cannot given them any more than they are already giving. This means crunch time does not improve productivity, but it does make everyone on the team more miserable because they are spending too much time at work and they are wondering why they can't seem to force themselves to get more done.

I am not sure what your point is. If Boeing went bankrupt, someone could buy them and the company would continue running. Also, Boeing is not the most important defense contractor in the US. They don’t make the F35 and they don’t make the new B21 Raider. The world is not going to end if Boeing disappears.

Tariffs, imports, and exports are controlled by the Federal,Government of the United States of America. The states have no power in these areas.

The easiest thing is stop installing the apps and stop looking at the feeds.

You are right that this is not an io_uring issue.

  I think you under estimate the value of anti-virus.  Anti virus software is a good second line of defense.  It’s not perfect but it will stop a lot of known malware.  This has value.

That is not my experience. Every US company I have worked in spent a lot of time training employees to follow the relevant laws. I have even been on teams which had to do work to comply with the European GDPR. The message I have always received is follow the law and don’t break it.

Real life people use AI. A good example of this is the lawyers who submit court filings with AI generated legal citations. The get caught because the citations are fake (the case cited does not exist).

Probably because there are services (AKA web services, software listening on a network port, etc.) out there which accept arbitrary Parquet files. This seems like a safe assumption given lots of organizations use micro-services or cloud venders use the same software on the same machine to process requests from different customers. This is a bad bug and if you use the affected code, you should update immediately.

I suspect that an MCP is just a rebranded API. We have also seen these sorts of extensibility mechanisms before. Browser extensions, Object Linking and Embedding, Dynamic Data Exchange, and Visual Studio Code extensions are all examples of having a standard API which allows lots of different things to plug into it.

My last iPhone’s battery lasted about 5.5 years before it needed to be replaced. Replacing it cost about $90 + tax at the Apple store. The bottom line is Apple products do last and if you need a new battery, you can get one.

I suspect the moral of the story is devops and operations staff need to keep all payments, secret rotations, certificate expirations, etc. on a calendar so no one forgets to pay the bills. I hope the employee who forgot to pay the bill learns from this.