2 companies have functionally similar products, but behaves completely different. One company makes technical decisions with security as the fundamental principal, while for the other company, security is not a consideration.
Having it running on host (!), and the metadata for all guest VMs stored and managed by the same memory/service (!!), with no clear security boundary (!!!).
It's like storing all your nuke launch codes in the same vault, right in the middle of Washington DC national mall. Things are okay, until they are not okay.
As someone who had worked adjacent to the functionally-same components (and much more) at your biggest competitor, you have my sympathy.
Running 167 agents in the accelerator? My gawd that would never fly at my previous company. I'd get dragged out in front of a bunch of senior principals/distinguished and drawn and quartered.
And 300k manual interventions per year? If that happened on the monitoring side , many people (including me) would have gotten fired. Our deployment process might be hack-ish, but none of it involved a dedicated 'digital escort' team.
I too have gotten laid off recently from said company after similar situation. Just take a breath, relax, and realize that there's life outside. Go learn some new LLM/AI stuff. The stuff from the last few months are incredible.
We are all going to lose our jobs to LLM soon anyway.
- Local LLM, with a powerful debugger as its oracle, is now powerful enough to run rudimentary malware analysis without consulting with external sources.
- More complex malwares are still beyond what local LLMs can handle. The local LLM can see all the behaviors by the malware, but the LLM fails to put the analysis together to deduce the true intention of a binary.
- Local LLM is a very lost-cost way to do malware analysis (about 5 US cents of electricity.)
- The biggest killer-app feature is having the LLM writes its analysis back to Ghidra. The more you interact with the LLM, the more data it will write back to Ghidra. This could potentially saves hours per manual debugging by skipping function/resources/variables labeling.
The "NemoClaw vs. OpenClaw" section is absolutely ridiculous.
OpenClaw vs NemoClaw (NVIDIA)
Developer Peter Steinberger (individual project) vs NVIDIA Corporation
Current Status Acquired by OpenAI (Feb 2026) vs Upcoming release (GTC 2026)
Target Market General-purpose consumer AI assistant vs Enterprise AI agent platform
Core Strength Rapid deployment, viral adoption vs Security, privacy, enterprise reliability
Ecosystem Community-driven (NanoClaw variants) vs NVIDIA NeMo & NIM integration
Governance Transitioning to foundation management vs NVIDIA-backed with open-source access
GPU Acceleration Not natively optimized vs Native NVIDIA GPU acceleration
NemoClaw is not even out yet, so who knows what it might look like. I guess if you sprinkle the word 'Nvidia' around enough, your product is automatically better than the rest.
I don't even like OpenClaw, but this is just silly.
Insurance and overhead (eg. safety harass) exist for a reason other than to drain your wallet. Roofing is also a physically difficult job. You won't find many 50+ year old to couch on a rooftop all day, regardless of pays.
Well since the 787 program will very likely never break even, let alone turn in profit, for Boeing, the 737's replacement will be a do or die project for Boeing. They cannot afford another money-losing product.
There are only two¹ major manufacturers of commercial airliners: one in the US and one in the EU. Both are essentially state backed. Both blocs want to have their own manufacturer, for strategic reasons, and they won't let it go under.
1. There will probably be three in a few years, since China is building up Comac.
seeing how much power shifted from legislative branch to executive, and how often executive branch changes its mind, I wouldn’t count on the unwavering government support
>The company is also asking UK government officials to provide emergency support for its suppliers to get through this period, according to people close to the talks.
The support is going to suppliers, who are the true victim, but it's privatize the gain, socialize the cost. JFR screwed up, so they should be the first to step up to assist the suppliers.
>You immediately arrest have any employee interfering with emergency response and throw them in jail.
Imagine that you work for a 3 letter US agency and is storing confidential data on AWS. Would you allow random individuals (yes even for emergency personnel) to have unfetter access to your computation and storage systems? What about health data? What about data belonging to other countries? Do you do a sweep for unauthorized remote access device after the incident?
Then they need to have staff on site that is fully qualified to handle any type of emergency any time there is anyone at all in the facility, which they don't.
I've never experienced it but I've been told that if an emergency responder needs to enter an area where classified information is stored you let them in, escort them, and security will debrief them and have them sign an NDA after the fact if they saw any classified information.
My understanding is that the fire department has pretty broad legal authority to tell you where to shove your policies your if your building is on fire. They can legally smash down your doors, haul you out kicking and screaming, and detain you outside of the building while they put the fire out.
This is largely correct. However, staff also need to be trained and drilled on security policies and procedures. That's often lacking, especially if security is outsourced to third party contractors.
Because there are federal agents with rifles guarding the data center, and they're allowed to use deadly force if the local FD ignores their instructions.
Reading between the lines: yes, certainly. Amazon wouldn't stop firefighters from getting into a normal datacenter, nor would they have the authority to stop them if they wanted to. A private corporation can't demand background checks from emergency responders; a letter agency can.
Oh yeah I used to play on T3Houston all the time, back in ~2003 (as Undead). There weren't that many W3 mod servers that had a consistent player population. I lived in PNW though so the latency was always around ~80ms.
2 companies have functionally similar products, but behaves completely different. One company makes technical decisions with security as the fundamental principal, while for the other company, security is not a consideration.
reply