kllrnohj

There's also major not-startups working on it, such as Broadcomm: https://www.broadcom.com/info/ai/3point5d

CGI rendering. To do Pixar quality animations you used to need racks and racks of servers and it still took months. Now anyone can do it, and we saw tons of slick animations on YouTube from indie studios as a result (before the AI slop cloning started I mean)

Regular people aren't buying a $4,500 laptop lol wtf are you talking about?

This is all but certainly a bug in their linux driver and nothing else. It sure as hell isn't some "anti abuse" to enable "regular people" to buy one.

Nvidia's MSRP is full of shit and has been for a long time. You see it with desktop GPUs all the time, even before the AI boom, where Nvidia would make up an MSRP but not offer a card at that price themselves, and none of the AIBs would, either, except for some token amount that rapidly sold out and were never restoked.

If we look at what you can actually buy the 64GB RTX Spark is $4,500 and the 128GB one is $7,000: https://eshop.asus.com/us/31150-us-cnf-auto.html & https://www.dell.com/en-us/shop/laptop-computers/spd/xps16dx...

Hell there doesn't seem to be an RTX Spark that's sub $3,300 when considering the 32GB models even. $2,399 is pure fiction.

Sure, but if you think it's insane to buy a DGX Spark for a datacenter, then it's equally insane to buy an RTX Spark (which is the exact same SoC just with less networking and a screen) for the datacenter.

Because the second level isn't really involved, they are a formality. This isn't unusual, it happens when the range of things a group does has grown so large that it needs to be primarily managed by dedicated subgroups but the rules don't update to delegate all authority to that subgroup.

The members of the broader group that cared strongly about C++ would have just been involved in the WG21 subgroup in the first place, the subgroup that approved it with a 2/3rds majority. So it almost certainly means that a broader group of ISO that normally don't care about what C++ does (and hence aren't involved in WG21) were influenced to vote in the direction the minority of the WG21 wanted.

that seems really hard to believe? If you wanted this running Linux in a data center you'd have just been buying the cheaper and yet also more powerful DGX Sparks.

The only value proposition of RTX Spark at all is the laptop form factor

Nvidia enabled that by offloading stuff that used to be in the proprietary driver onto the still proprietary GPU firmware. Making it, if anything, less open source as it's now harder to inspect what it's doing at runtime since it's now out of reach of even the kernel

> I mean, there is even a paper dating back to 2025 called "contracts concerns" and from 2026 called "contracts fundamental flaws".

Two papers that both have the same authors, one of whom is Bjarne Stroustrup.

Why are you convinced the narrative is that contracts are actually broken and unfixable instead of a few influential people just really hate it for reasons they have been unable to convince anyone else are valid?

Have you read the "contracts fundamental flaws" paper? Looking at it now, it's hard to take it seriously. The biggest complaint seems to be that the marketing of contracts is wrong. Literally: "We would welcome a contracts design that is simple, and “marketed” as just a debug aid, rather than a safety feature."

It really does look like Bjarne is convinced that profiles are the future for C++, and contracts makes it less appealing to get there. And that's something that reasonable minds can just disagree about without it being a conspiracy of some kind. WG21 doesn't seem to believe that profiles are an anytime-soon-if-ever feature, and contracts provide immediate benefit that justifies any future complications with profiles.

I think you're confusing it with Concepts. Contracts are basically just asserts, nothing to do with templates.

I have seen a significant number of excellent engineers just seemingly turn their brain off entirely and resort to just spitting out "but AI said <blah>" or "AI reported <foo> which I found surprising but I didn't analyze or dig into that result whatsoever". So anecdotally, yes, this absolutely matches my experience.

As a percentage of websites, though, Java is far from ubiquitous. It's probably not even double digit percentages. PHP, meanwhile, is some 70% of websites. So in terms of exploit targets, this is 10x that of Log4J, maybe.

> While Go/Node have grown much more than PHP, PHP is definitely alive.

PHP still powers approximately 70% of websites

> xhtml was just a bad idea creating tons of problems and solving none.

Well an XHTML parser (and serializer) is a lot simpler, which is a pretty meaningful problem to solve.

What problems does xhtml create?

The thrusters are primarily pointed rearward and to the ground. It's not capable of doing much at all for a flat spin, the typical scenario of a car spinning out

I don't have a MacOS comparison point, but steam for me is pretty equivalent to the numbers in the article. ~10 seconds for a cold start, half a second for a warm start. Unless you have a very different definition of "take forever"? What are you seeing on MacOS?

> The Steam client is terrible

Things nobody has said since like 2005? A faster startup is certainly appreciated, but steam's 10 second cold launch time is hardly a big deal. Especially when everyone just leaves it running anyway. There's far more significant aspects like memory usage, game library, and general features.

> as long as password-based login remains as an option.

which they have to be, right? since passkeys are "temporary" in that they are easily lost/destroyed/temporarily unavailable, and sites are supposed to support multiple of them?

I don't see anything in those criticisms that are remotely unique to C++.

Linux also built up inefficient abstractions in C that are used simply because they are easy to use. Linked lists being a go-to default choice being an obvious example.

> Fair, but I just wasn't willing to put up with Android TV.

When I bought my Shield TV's I actually liked Android TV. Very nearly every update since then has just slowly made it worse and worse.

Now it's absolutely disgusting as it shows straight up advertisements (not "recommended shows", like literally ads for car insurance or whatever).

So I guess there's really just not much to choose between regardless. It's spyware + adware regardless of price vs. Apple's lack of local backup support :/

The appeal of the Shield Pro is you don't have to deal with custom flashing a "no-name" device and you don't have to dual box to keep streaming services happy.

It's frustrating that nobody else seems to care about attempting to be the all-in-one box given how much Shield is showing its age now. It's really sluggish

I don't get why Apple just refuses to allow audio pass through or DV Profile 7. They're clearly on board with DV in general and don't hesitate to play Dolby's branding games, so why not profile 7 support???

You have that backwards. HEIF is the container format. HEIC is a HEIF file using HEVC.

HEIF is a container not a codec. HEIC is HEIF + HEVC.

AVIF and HEIC both use HEIF

RIFF itself is fine, but in the context of webp it's pointless. WebP doesn't make any use of being in a riff container. Like it still internally has its own chunk system anyway. So you end up with a single RIFF chunk for the webp file that itself then can contain multiple, non-RIFF chunks

well that depends on the size of the image. But a modern cell phone is shooting 50mp+, and at that size you're talking 50-200ms for a jpeg vs. a couple seconds for HEIC. Which is borderline instant-feeling vs. extremely not instant.

hardware-decoded HEIC is around 10x slower than JPEG.

software-decoded HEIC is around 100x slower than JPEG.

WebP is something like 20-50% slower than JPEG, so still solidly an order of magnitude faster than best case hardware-accelerated HEIC decoding.

Only for HEIC realistically, and that only still causes it to struggle to match jpeg or webp performance anyway

Yes, it's important to distinguish annoyances of the codec from annoyances of the ecosystem.

Ecosystem being slow to adopt it is something that can be fixed or improved, but also more importantly (given jpegxl & avif comparisons) are things that will impact any new image format.

Meanwhile annoyances of the codec tend to be things that are dramatically harder to deal with. Like HEIC being a license minefield and also slow as shit. Or that many of these newer image codecs do not have ways to work with them in a memory efficient manner like jpeg does (see eg libjpeg-turbo's sample size & skip scanline options). Or WebP insisted on being in a RIFF container for... uh... absolutely no fucking reason whatsoever afaict. Fortunately RIFF is so trivial that this overhead doesn't actually matter in practice, but then HEIC & AVIF dials up the annoying container bullshit to 11 thanks to their video heritage with ISOBMFF

> Yes us Hacker News users have plenty of use cases for IPv6, like self-hosting

Funnily enough, self hosting is why I can't use IPv6. I want vlan isolation, but only get a /64 from my ISP.

Fortunately the lack of IPv6 also isn't a meaningful loss anyway so whatever

The Snapdragon X2 laptops are typically not fanless, either. Fanless just results in thermal throttling if you ever do push on it.

Fanless just means slower.