MintPaw

It might be that this is common with new tech, I'm too young to have grown up in the early concert scene. But with video games the curve was similar. People would show up just to see the tech and how much stuff people could put on the screen, It's only pretty recently that part has started getting boring.

I'd imagine similarly there were points in time where people who go to concerts just to see the electric guitars and lighting setups.

To me it looks like the default cmd.exe font that was used up until win10.

> No, nothing deserves this constant whining and crying day in and day out.

Why even try an start a conversation with that attitude? Wayland doesn't get nearly as much hate as Windows, Chrome, or iOS. But I guess literally nothing is worth writing an article that has the word "fuck" in it 7 times, because that crosses some kind of ultimate line?

Yes, inverting the caller/callee direction is one of the hardest control flow patterns to reason about.

Yeah, obviously you have multiple levels of public interfaces, like how CreateWindow calls CreateWindowEx under the hood.

Do people recommend the API surface should be totally flat and the same for all developers?

It solves the problem of your kid borrowing a phone from another kid at school.

What kind of experience you have is about what kinda of developer you are. If you're the kinda programmer who wants to use all the newest versions of stuff because you think it'll be better, then you'll be in an endless quagmire of hitting limitations.

Most web programmers fall into that bucket for example. If you're the type to recoil at XMLHttpRequest, reaching to fetch or other even newer stuff. Then you'll balk at Win32 and be in a never ending pit of new Windows technology. I'd argue this is true of basically all new software. It's worth starting with whatever the oldest most compatible version of your target and ignoring the advertising and hype.

In cursor:

You can copy/paste or drag code snippets the chat window and they automatically become context like. (@myFile.cpp:300-310)

You can click any of the generated diffs in the assistant chat window to instantly jump to the code.

Generated code just appears as diffs till you manually approve each snippet or file. (which is fairly easy to do with "jump to next snippet/file" buttons)

These are all features I use constantly as someone who doesn't vibe but wants to just say "pack/unpack this struct into json", "add this new property to the struct, add it to the serialization, and the UI", and other true busywork tasks.

I've never heard about "Home Assistant Green". Seems like another step down the slippery slope of "work on my machine". First docker, than a dedicated OS, now dedicated hardware. I wonder why is Home Assistant so complex as to require all this.

Because it's not at all obvious. The vast majority of people posting on Hacker News in 2026 probably had extreme exposure to the internet early in life and turned out alright. So they're probably not as concerned about children being exposed to adult content.

But clearly people in other cultures have a huge problem with it. Don't fall victim to survivorship bias + echo chamber.

There's not another obvious solution to the problem, it's debated in every thread. (no laptop + homeschool is not a real option for 99% of people)

I did this too, I have pi that downloads and combined a bunch of rss feeds every 30min (cron) and downloads the vids, I browse them with Thunderbird on my desktop, I inject a special link to the mp4 on my pi. So I can just watch vids at 192.168.1.106/videos/X.mp4 using the Firefox mp4 player.

Did it in ~300 lines of node.js, was trying to learn how to use JS for server stuff, seemed like a good idea at the time. It still works 5 years later, but it stands as a reminder to me to never use async/await.

I've never even heard of C3, I use C++ and Jai.

I've never used Zig either, I just disagree that requiring constant maintenance is a good.

This kind of thought is popular in the web world where browsers get an update every 3 days and you don't control the hosting services, so constant maintenance is unavoidable.

But in the world of desktop development it's possible for a library to be "done", having a 100% stable codebase going forward and requiring no maintenance. And it's not bad, it's actually good.

Requiring every dependency to be constantly maintained is a massive drain on productivity.

An interesting concept that stood out to me. Committing the prompts instead of the resulting code only.

It it really true the LLM's are non-deterministic? I thought if you used the exact input and seed with the temperature set to 0 you would get the same output. It would actually be interesting to probe the commit prompts to see how slight variants preformed.

I think the point is that it's not enforceable.

Not much apparently, although I didn't know about changing symlinks, that could be very useful.

Hm, I know that Safari doesn't support 64bit wasm, which is a very important feature that Chrome and Firefox both have, but this seems to say they have "100% webassembly support".

https://webassembly.org/features/

Everyone discusses better parenting all the time. But some people forget what it's like being a kid, circumventing blocking systems is trivial if you're motivated, and even if they weren't, a cheap phone costs $80 and kids are very willing to share their old devices.

It's not that hard, maybe if you put up a sign with a slur a car won't drive that direction, if avoidable. In general, if you can sneak the appearance of a slur into any data the AI may have a much higher chance of rejecting it.

Seem iquilezles has finally given in. He's been complaining about crawler attacks a lot in the last months/years.

https://x.com/iquilezles/status/1977172864785957340 https://x.com/iquilezles/status/1976866381099679817 https://x.com/iquilezles/status/1838858759336267842

I used to watch his videos early on, but it's been like this for a few years at least.

Seems super light on details, I guess I'm supposed to read the paper that's not linked? Not sure why this has to be new journalist and scientific research, couldn't you just ask Microsoft for some Halo stats and call it a day?

Windows didn't fade in and out in Windows XP.

Bad by modern standards, there was a point in time where even just compositing two images on top of each other with an alpha cutout was considered a complex task.

You say it as a joke, but spell check has replaced certain tiers of editors. And Photoshop has replaced certain tiers of designers.

There are real downsides to even #including C++ headers. And there are certainly downsides to introducing a templated string type. It's not hard to imagine why people would want another solution.

Yeah, but do people like that? It feels pretty patronizing to me in a similar way. Like "Weee! So cute that our website is broken, good luck doing your job! <3"

Reminds me of the old uwu error message meme.

Looks kinda like Rust? How similar is this to geometry shaders?

This has annoyed me a lot, crazy you can't rely on the print functions being the same on different platforms. This is why I always add stb_sprintf and make an allocSprintf() that allocates the right sized buffer first.

I made the opposite choice with Vim, opting to always use GVim instead of the terminal. I was never able to set up terminal colors and mouse compatibility just right, and at 4k Gnome terminal would lag a bit. Terminals use windowing systems too. :P

This was 10 years ago though, before Kitty and the new Windows Terminal.