Google basically said “here’s a mysterious glowing rectangle” and expected us spec junkies not to immediately start clawing at the walls for a datasheet, and losing sleep for weeks on end until we get them.

I think the topic itself is difficult for everyone involved - there will likely be a lot of uproar for many years as we get closer to finding this happy medium.

1) They’d distract from the main point (I wasn’t aiming to write a benchmarking post), and

2) They can be misleading, since results will vary across ARM hardware and even between Snapdragon X Elite variants.

Instead, I included the PowerShell snippets so anyone interested can reproduce the results themselves.

For a rough sense of the outcome: the Snapdragon VM outperformed the Intel VM by ~20–80%, depending on the test (DNS ~20%, IIS ~50%, all others closer to ~80%).

Comments URL: https://news.ycombinator.com/item?id=47821801

Points: 187

# Comments: 150

The real question is this: While the floppy disk became the standard "Save" icon, what will eventually become the standard "AI functionality" icon?

Co-worker 1: Interesting. I wonder if that voids the warranty. It's Apple you know.

Co-worker 2: May Jobs have mercy on their soul...

Co-worker 3: Not a bad idea. But not sure if that would cause problems with structural integrity of the laptop, like if you drop it or something.

Co-worker 4: The only downside I see is that you can no longer say "Hey, that's a sharp-looking laptop!"

I’ve submitted mine as well - cheers!

It's almost as if someone near the end of a meeting said "Oh crud, we've got to do something to acknowledge our 50th anniversary - can someone put something together, and quick?"

Art is where I choose to draw the line, for both ideation and content generation. That work report I leveraged AI to help flush out isn't art, but my personal blog is, as is anything I must internalize (that is thoroughly understand and remember). This is why I have the following disclaimer on my blog (and yes, the typo on this page is purposeful!): https://jasoneckert.github.io/site/about-this-site/

For me, aesthetics and size are important. That workstation on your desk should justify its presence, not just exist as some hulking box.

When Apple released the Mac Studio, it made perfect sense from a form-factor point-of-view. The internal expansion slots in the M2 Mac Pro didn't make any sense. It was like a bag of potato chips - mostly air. And far too big and ugly to be part of my work area! I'm surprised that Apple didn't discontinue it sooner.

Unfortunately for them, I think hardware vendors will see past the hype. They'll only buy the platform if it is very competitively priced (i.e., much cheaper) since fortune favours long-lived platforms and organizations like Apple and Qualcomm.

The post frames Wayland security as “you can’t do anything,” but that’s a misunderstanding. Even under X11, any app can log keystrokes, read window contents, and inject input into other apps. Wayland flips this to isolation-by-default: explicit portals/APIs for screen capture, input, etc.

Moreover, the performance argument is weak and somewhat contradictory. The author claims there is no clear performance win, and that it's sometimes slower and hardware improvements make it irrelevant. But Wayland reduces copies and avoids X11 roundtrips (architectural win). Actual performance depends heavily on compositor + drivers, and I've found that modern hardware has HUGE performance improvements (especially Intel, AMD, and Apple Silicon via the Asahi driver).

The NVIDIA argument is also dated. Sure, support was historically bad due to EGLStreams vs GBM, but this has improved significantly in recent driver releases.

Many cited issues are outdated too. OBS, clipboard, and screen sharing issues are now mostly (if not entirely) solved in the latest GNOME/KDE.

I've been using Wayland exclusively on Fedora and Fedora Asahi Remix systems for many years alongside Sway (and occasionally GNOME and KDE). Adoption has accelerated in many distros, and XWayland for legacy apps is excellent (although I believe using the word "legacy" here would be a trigger word for the author ;-).

There's no stagnation here... what we're looking at is a slow migration of a foundational layer, which historically always takes a decade or more in the Linux world.

Comments URL: https://news.ycombinator.com/item?id=47394359

Points: 2

# Comments: 0

I'm hoping people catch that typo after reading "every single word, phrase, and typo (purposeful or not)" and smiled every time I've had someone post a PR with a fix for it (that I subsequently reject ;-)