Eric Schmidt Blames Google's A.I. Struggle on Remote Work | Hacker News Reader

Eric Schmidt Blames Google's A.I. Struggle on Remote Work

observer.com

6 pointskkfx4 comments

When I first read this headline, I though Eric's statement would be something like "we balance work & life, and are okay with losing the AI sprint race in favor of winning the long term". BOY was I wrong. It sounds like Eric is looking for an excuse to fire people to boost the stock, which is typically the motivation behind any "CEO complains about working from home" quote.

If you’re still under the impression that network and server design wasn’t about enabling remote work from the start, then you’re simply not seeing the bigger picture. The entire foundation of these systems was built to break down geographical barriers and enable people to work and collaborate from anywhere. This was never just about sharing resources—it was always about laying the groundwork for what would evolve into remote work.

From day one, the goal was clear: create networks that connect people regardless of their physical location, setting the stage for the flexible, remote work environments we have today. The evolution of these technologies wasn’t a happy accident; it was a deliberate move towards a world where work isn’t confined to an office.

If you disagree with this, you’re not just missing the point—you’re denying the very essence of what these innovations were designed to achieve. The idea that remote work wasn’t central to these developments is, frankly, shortsighted. The fact is, the potential for remote work was embedded in these systems from the beginning.

So, if you still don’t see that enabling remote work was the core outcome of these advancements, it’s time to wake up to the reality. To deny this is to fundamentally misunderstand the direction and purpose of network and server design from its inception. It’s not just about what these systems can do—it’s about what they were always meant to enable. And if you can’t grasp that, you’re not just behind the curve—you’re lost in the past.

Very true BUT yet in hw terms most systems are NOT designed for LOM indeed, and that's on purpose because LOM means also the need of open standards for interoperability and OEM likes to keep their own lock-in.

Hell, most people even fails to understand how ridiculous are 99% of "modern" OSes who offer no option for a declarative config or a SIMPLE automatic deploy, relaying on classic "archives unpacking on a filesystem" for installers/packages, no built-in replication, no built-in orchestration. No mobos ready to "offer a 'BIOS' access via built-in LOM if a dedicated cable is plugged in, plug and play" etc.

Not to talk about the sorry state of conferencing where from a legacy but at least universal SIP/RTP standard we have switched to walled gardens, walled gardens TO COMMUNICATE, because as anyone know to talk to others walls are good tools.

Just take a looks at how many companies push remote desktop simply because they have no easy solution to properly manage remote workers desktops natively.

Yes networked desktop computing was lost in time on purpose, pushing "cloud+mobile" to push substantial lock-in and no personal ownership, for the sake of giants who NEED THE OFFICE to keep the city up where they can handle people like puppets, but so far they almost succeed everywhere and most people allow them to succeed.

Well... Just another one who try to save financial capitalism at the expense of innovation and human wellness, stating without even try to prove the statement that what financial capitalism need it's needed to win, while this model actually fall all over the world.

Of course firing talents it's definitively not to blame I imaging, trying to be bureaucratic, managing people like sheep etc are normal things and as usual it's always someone else fault.

Reply on news.ycombinator.com