vinkelhake

Give me a ping Vasily. One ping only please.

Sad.

I've seen variants of this comment for many years. The alternative to "web UI slop" would presumably be one of the many native toolkits.

I see it in a different way. The fact that "web UI slop" has managed to make great inroads on the desktop is an indictment of the state of native toolkits. If you think it's a problem that desktop apps are being written with web toolkits, the solution for that isn't to shame (as the term "web UI slop" clearly tries to do), but rather to figure out how to improve the native toolkits.

The opportunity to improve those toolkits was always there, and the ball was dropped.

I grew up with and absolutely adore The Last Ninja series. I'm not going to comment on the size thing because it's so trite.

Instead - here's [0] Ben Daglish (on flute) performing "Wastelands" together with the Norwegian C64/Amiga tribute band FastLoaders. He unfortunately passed away in 2018, just 52 years old.

If that tickled your fancy, here's [1] a full concert with them where they perform all songs from The Last Ninja.

[0] https://www.youtube.com/watch?v=ovFgdcapUYI [1] https://www.youtube.com/watch?v=PTZ1O1LJg-k

This is "just" about providing the official Chrome binary to ARM64 "desktop" Linux.

You've been able to build and run Chromium on ARM Linux for a long time (I'm running it right now), it's just that they haven't provided an officially branded Chrome.

This is a good thing. While Chromium works well, there are a few things (like syncing) that is a bit of a pain to set up.

I did something similar a few years ago. I put together a Pimoroni Interstate 75 (which is an RP Pico with an integrated LED matrix connector), a 32x64 matrix, a NES controller port, designed a simple case for it and made a Tetris. It was a fun project and the first time I had really done anything with hardware.

I've been meaning to do a write up of the project, but I keep putting it off. I wrote the software bits in C++. To speed up iteration (i.e. not have to deploy to real hardware for every tweak to the game code), I made a small web harness that ran the core logic as wasm.

https://imgur.com/a/tetris-HoXenDg

FWIW, and errors aside, I think I agree with the general sentiment. Things added to the C++ library ossify. The ABI concerns, and the general unwillingness to do anything about it, is a big reason why Google largely exited the C++ standard business.

But the conspiracy brained part of me can't help to think that part of this is sour grapes. Vinnie contributed a lot to the failed proposal to add networking (loosely based on ASIO) to the C++ standard. That proposal eventually lost out to the sender/receiver library[0] which is getting added in C++26. That still doesn't have actual networking, but lays the groundwork.

It remains to be seen how well sender/receiver turns out. Given ranges (another Niebler addition), I'm not super optimistic.

[0] https://en.cppreference.com/w/cpp/experimental/execution.htm...

Is there an equivalent to Godwin's law wrt threads about Google and Google Reader?

See also: any programming thread and Rust.

I recently had my Framework Desktop delivered. I didn't plan on using it for gaming, but I figured I should at least try. My experience thus far:

    * I installed Fedora 43 and it (totally unsurprisingly) worked great.
    * I installed Steam from Fedora's software app, and that worked great as well.
    * I installed Cyberpunk 2077 from Steam, and it just... worked.

I later got a hankering to play Deus Ex: Mankind Divided. This time, the game would not work and Steam wasn't really forthcoming with showing logs. I figured out how to see the logs, and then did what you do these days - I showed the logs to an AI. The problem, slightly ironically, with MD is that it has a Linux build and Steam was trying to run that thing by default. The Linux build (totally unsurprisingly) had all kinds of version issues with libraries. The resolution there was just to tell Steam to run the Windows build instead and that worked great.

This felt like a blast from the past. At a few times reading this article, I had to go back and check that, yes, it's actually a new article from the year 2025 on STM in Haskell and it's even using the old bank account example.

I remember 15 or 20 years (has it been that long?) when the Haskell people like dons were banging on about: 1) Moore's law being dead, 2) future CPUs will have tons of cores, and 3) good luck wrangling them in your stone age language! Check out the cool stuff we've got going on over in Haskell!

That would depend on your idea of "good". It would be an upstream swim in most regards, but you could certainly make it work. The Asahi team has shown that you can get steam working pretty well on ARM based machines.

But if gaming is what you're actually interested in, then it's a pretty terrible buy. You can get a much cheaper x86-based system with a discrete GPU that runs circles around this.

Besides the box art, I miss the days when 1) the graphics card didn't cost more than the rest of the components put together, 2) the graphics card got all of its damn power through the connector itself, and 3) MSRP meant something.

Which format are you saying the Chromium team made and wants to push in favor of jxl?

You can write a WASM program today that touches the DOM, it just needs to go through the regular JS APIs. While there were some discussions early on about making custom APIs for WASM to access, that has long since been dropped - there are just too many downsides.

I first watched it back when it came out. At the time I was living in a different country and San Francisco was just another US city to me. I just happened to re-watch it yesterday (it still holds up) for the first time since moving to the bay area.

It was interesting hearing the names of the locations and bridges that previously meant nothing to me (except the golden gate).

It's free to watch on youtube at the moment: https://www.youtube.com/watch?v=Qy9XYQBBIJ4

I live in the bay and occasionally ride Waymo in SF and I pretty much always have a good time.

I visited NYC a few weeks ago and was instantly reminded of how much the traffic fucking sucks :) While I was there I actually thought of Waymo and how they'd have to turn up the "aggression" slider up to 11 to get anything done there. I mean, could you imagine the audacity of actually not driving into an intersection when the light is yellow and you know you're going to block the crossing traffic?

A simple example is `toJSON`. If an object defines that method, it'll get invoked automatically by JSON.stringify and it could have arbitrary side effects.

I think it's less about side effects being common when serializing, just that their fast path avoids anything that could have side effects (like toJSON).

The article touches briefly on this.

It's unfortunately not (yet) as good as in MacOS, but acceptable.

An alternative that is available right now is to get an M1/M2 MacBook Air and run Asahi Linux on it. The older models are pretty cheap, but still quite fast. There are some missing features, but it runs really well. I've been using it as my home driver for over a year and it's really solid.

I used yaml for some things back in the stone age (shout out to why the lucky stiff and syck). The more I used it, and the more I came in contact with it I started to dislike that it has so many features, and tries to be overly clever. I'm kind of surprised to see that it's making a comeback (or maybe it never went away).

https://noyaml.com/

That kind of reasoning makes sense if you have a single publisher controlling the entire market and they don't want to undercut their own business. But that's obviously not the case. There are plenty of publishers that want to publish games like Terraria, especially if they go on to sell more than 60 million copies.

While reading this, the old ARexx (Amiga Rexx) popped into my head. It was a scripting language that in itself wasn't very noteworthy. However, it also made it easy for applications to expose functionality through an ARexx port. And again, offering up an API itself isn't noteworthy either. But it shipped by default in the system and if an application wanted to open itself up for scripting, ARexx was the natural choice. As a result, a ton of applications did have ARexx ports and there was a level of universality that was way ahead of its time.

Come to think of it - I don't know what the modern equivalent would be. AppleScript?

LIDAR pulses are in the order of a few nanoseconds.

One reason which matters with libraries is that slapping constexpr on a function is, in a way, a promise by the author that the function is indeed meant to be constexpr.

If the author then changes the internals of the function so that it can no longer be constexpr, then they've broken that promise. If constexpr was implicit, then a client could come to depend on it being constexpr and then a change to the internals could break the client code.

Disclaimer: this is not a normative statement.

It’s too bad you still can’t cast a char to a uint8_t though in a constexpr expression.

Uh, what? That has worked fine since the introduction of constexpr in C++11.

Google already has custom ASICs for video transcoding. YouTube has been running those for many years now.

https://streaminglearningcenter.com/encoding/asics-vs-softwa...

That game would cost $90 today with inflation.

Speaking of $90 - Nintendo recently announced the Switch 2 and physical copies of the games will be just that, $90.

You're looking at constructs mostly related to C++26 reflection. It's very new, so that might be why it looks like it's from a different planet. They necessarily had to invent some new syntax for it.

I think C++26's reflection is likely to be one of the most important changes to the language in a very long time.

Just a heads up - it looks like the "Path Tracing Off" shots have ray tracing disabled as well. In the shots starting at 1:22 (the car and then the plaza), it looks like they just have the base screenspace reflections enabled. Path tracing makes a difference (sometimes big, sometimes small) for diffuse lighting in the game. The kind of reflection seen in those scenes can be had by enabling "normal" ray tracing in the game, which is playable on more systems.

I don't get where the author is coming from with the idea that a diffusion based LLM would hallucinate less.

dLLMs can generate certain important portions first, validate it, and then continue the rest of the generation.

If you pause the animation in the linked tweet (not the one on the page), you can see that the intermediate versions are full of, well, baloney.

(and anyone who has messed around with diffusion based image generation knows the models are perfectly happy to hallucinate).

I'm sad to see this happen. I bought an M2 Air a year ago and I've been running Asahi on it since the day I got it. It hasn't been without hitches, but that was something I signed up for.

I'm incredibly grateful for all the work Hector and the others have done on this project. The Air is my dream hardware (I'm a sucker for sleek fanless laptops) and getting to run Linux on it is quite amazing.