HNHacker News
TopNewBestAskShowJobs

veidr

8,773 karma · joined July 12, 2010

veidr is my old BBS handle from the 80s (Interzone!)

I sporadically rant at http://masonmark.com and usually see email sent to mason at that domain.

submissionscomments
veidr··on I love Linux, but I can't quit Windows
I agree it sounds like that, but (having that same thought) I kept the temp in the living room 20℃ or less for a week but nah

My best guess at this point is the 2025 LG TVs have some different HDMI ARC something something compared to the 2019 it was plugged into before.

But also my point is that there's no way a human with 3 kids and job could ever know... it either starts working or I get a PlayStation or a different PC or whatever.

Or just tell my kids, "Hey, Death Stranding works on your Mac now, so shut the fuck up until you finish that whole game." ¯\_(ಠ_ಠ)_/¯

veidr··on I love Linux, but I can't quit Windows
yeah — i have my kids on Macs, bc I'm lazy, but just the ones with only two USB ports and nothing else — otherwise never-ending, unresolvable nightmare unless it's just some Apple thing you're plugging in
veidr··on I love Linux, but I can't quit Windows
So true.

I had this gaming PC — and once a year doing excel and dropbox exchanges with my accountant, but other than that, gaming PC — and it never had an issue, from 2020 or 2021 to last month.

So I decided to move it to the living room, and connect it to our big TV, instead of the small TV — same LG manufacturer, same 4K res, mind you — and now it just freezes every 3-4 days. And freeze means just, the screen still shows whatever it was showing when it froze, no USB mouse or keyboard does anything, cannot be RDP'd to cannot be pinged... hold-down-power-button only answer.

(I have swapped all the cabels, just to be sure.)

The only differences: moved it 20 meters physically, connected it to a slightly newer TV. ¯\_(ಠ_ಠ)_/¯

macOS and Linux also do suck, but both are AFAICT way more predictable, and less random

veidr··on Accelerando (2005)
Vernor Vinge has some hits and some misses, but A Deepness in the Sky (best to just take the plunge and read it without googling — it's good either way, but better if you don't even read the back of the paperback).

Then, a bit further afield but for me, at least, exercised what I liked in The Culture series, even though stylistically different: Spin by Robert Charles Wilson.

veidr··on Bun Rust rewrite: "codebase fails basic miri checks, allows for UB in safe rust"
Well "slop" is doing a lot of work there. If it's all incomprehensible garbage-code that no human can understand? Then... yeah very marginal value to me, in terms of hacking on it.

However, I think if it turns out that that's the case, then their port will fail in two ways (to paraphrase Hemingway): gradually, and then suddenly.

I don't think this port can be a success unless they end up — on the other side of it, not necessarily immediately — with maintainable Rust code.

veidr··on Bun Rust rewrite: "codebase fails basic miri checks, allows for UB in safe rust"
I can understand where you are coming from, but I myself am coming from a quite different place. I'm a long-time Deno fan, and to me Bun was less interesting because a.) it seemed like a much-less-ambitious Deno, and b.) I don't want to learn Zig, so I wasn't likely to try to hack on Bun itself, even just recreationally.

But, I warmed up to Bun over the last couple years almost against my own will — trying to maintain a pretty large body of TypeScript code in a runtime-agnostic way (including even Node, since 24.2). I don't want to make any specific TypeScript runtime a requirement for my TypeScript code, unless there are really good reasons to do so.

But Bun (like Deno) kept providing those reasons. Postgres, SQLite, S3, websockets, local secrets (Keychain/wallet), bundling, compilation, killer speed. So I (somewhat grudgingly) started using Bun more, and even made it a requirement for some of my projects (albeit, in ways I could walk back later if needed).

Today, I have a bunch of API servers and frontend app servers which are bun build --compile --bytecode single executables ,that can run and be deployed virtually anywhere.

I've been very happy with it so far. But also, I don’t think that the way I am doing it is super-common, and now that they are doing this, uh... extremely ambitious LLM port, I am perfectly positioned to regret all of my decisions around Bun if this port ends up sucking.

So I'm a little nervous, but... what if it doesn't suck? That would be cool, because a.) they will have shown something interesting about what is possible with LLMs (albeit if you are rounds-to-a-trillion-dollars valuation frontier AI lab, lol, but still). And b.) going forward, Bun will be developed in Rust. We all have our own preferences, obviously, but to me, that's a win.

And if it does suck, though — that's super interesting too! Will be annoying to me to re-architect my Bun-specific shit to Deno, but for the world at large (and me, too) that's still interesting information!

Because Bun is perfectly positioned to do a huge LLM-powered port. They are one of the premier TS/JS runtimes, it's obviously and insane marketing pillar for the AI lab that bought them, they have unfathomable resources and access to the cutting-edge models that all of us don't get to play with yet, and for all intents and purposes, they have unlimited money to do this.

So if they can't do it — which will be really obvious, I think, if true — then it really just isn't possible yet, and all the naysayers were right.

veidr··on Bun Rust rewrite: "codebase fails basic miri checks, allows for UB in safe rust"
No, and there's been a lot of confusion about that on this website.

They did cite Rust's safety as a motivating factor for the port. That doesn't imply trying to achieve that simultaneously with the language change — which is good, because that would be insane. (Or, if you prefer, even more insane.)

You cannot faithfully port a codebase to a new language while also radically re-architecting it. You have to choose.

They want the safety benefits of Rust going forward; i.e., after it's finished, when they then write new code in Rust.

veidr··on Rewrite Bun in Rust has been merged
You could do, but maybe they never will. I have no idea.

But the point is, in 2027, 2028... your new code doesn't have to suffer from these frankly 1970s issues

You could also gradually fix the internals — if you wanted to

veidr··on Rewrite Bun in Rust has been merged
You have no idea if it was a lie or not. I routinely have my clanker fleet spend a couple days toiling on some crap that I assume I will throw away, but it turns out pretty awesome, so I keep it.

It's entirely plausible that when that comment was posted, he doubted it would work well enough to keep.

(Sensible default for LLM code, btw. But sometimes it works great.)

veidr··on Rewrite Bun in Rust has been merged
I don't think you want to achieve any benefits of Rust in the initial port. Because at this scale you will definitely introduce new, and probably subtle, bugs that are not present in the Zig version.

You just want it to be the same, to the maximum extent the language allows. E.g. 1000+ unsafe is the right move, for now.

Reaping the benefits of Rust is for _future_ development.

veidr··on Rewrite Bun in Rust has been merged
We have hundreds of projects that run on Bun. (Some are Bun-specific for whatever reason, but most are "runtime-agnostic TypeScript code that runs on Bun, Node 24.2+, and Deno, but that means they run their test suites on Bun, in addition to the other two.)

Out of curiosity, I installed the canary Bun and just ran a bunch of them. It didn't take me long to find one that works on stable Bun and crashes on "canary" Bun.

      schematic git:(main)  bun upgrade --canary
    [1.55s] Upgraded.
    
    Welcome to Bun's latest canary build!
    
    Report any bugs:
    
        https://github.com/oven-sh/bun/issues
    
    Changelog:
    
        https://github.com/oven-sh/bun/compare/0d9b296af...19d8ade2c
    
      schematic git:(main)  bun run main.ts serve
    Schematic Editor running at http://localhost:4200
    Bundled page in 25ms: src/web/index.html
    frontend TypeError: Cannot destructure property 'isLikelyComponentType' from null or undefined value
        at V0 (http://localhost:4200/_bun/client/index-00000000ac7e3555.js:24:2534)
        at reactRefreshAccept (http://localhost:4200/_bun/client/index-00000000ac7e3555.js:21:6090)
        at http://localhost:4200/_bun/client/index-00000000ac7e3555.js:8766:27
        at CY (http://localhost:4200/_bun/client/index-00000000ac7e3555.js:21:8973)
        at nY (http://localhost:4200/_bun/client/index-00000000ac7e3555.js:21:9285)
        (...more like this...)
        at m (http://localhost:4200/_bun/client/index-00000000ac7e3555.js:21:8773)
        at http://localhost:4200/_bun/client/index-00000000ac7e3555.js:24:6482
        at http://localhost:4200/_bun/client/index-00000000ac7e3555.js:24:6548
        from browser tab http://localhost:4200/
    ^C
      schematic git:(main)  bun upgrade --stable
    Downgrading from Bun 1.3.14-canary to Bun v1.3.14
    [2.02s] Upgraded.
    
    Welcome to Bun v1.3.14!
    
    What's new in Bun v1.3.14:
    
        https://bun.com/blog/release-notes/bun-v1.3.14
    
    Report any bugs:
    
        https://github.com/oven-sh/bun/issues
    
    Commit log:
    
        https://github.com/oven-sh/bun/compare/bun-v1.3.14...bun-v1.3.14
      schematic git:(main)  bun run main.ts serve
    Schematic Editor running at http://localhost:4200
    [browser] Version mismatch, hard-reloading
    Bundled page in 20ms: src/web/index.html
    
    # working fine as usual... ¯\_(ಠ_ಠ)_/¯
I mean "passes test suite" is one thing. And a good thing. But... "doesn't break any (or even, say 99.5%) of the apps deployed around the world that are built on bun" is a pretty radically different thing.

It's hard to feel like this is responsible behavior, but I will reserve judgement for now, and see how long they persist this "canary" phase.

If they extend it for a lengthy period, and even like, fix bugs on the Zig version and the Rust "canary" version, then... I would be mollified to a great extent, since it is so easy to switch between the Zig stable version and the Rust canary version.

As a pretty heavy user of Bun, I'm actually pretty psyched for it to switch to Rust... but given the abruptness and speed so far, I can't quite shake the "new AI dealer getting high on his own supply" vibe.

But I hope they enter an intensive phase of prioritizing any and all "canary" bugs, and come out on the other side with a better product, and an even faster rate of improvement (which has honestly been pretty wild already).

(Yes, of course, I will have my clanker file a bug report with repro... but that may take a few days.)

veidr··on Rewrite Bun in Rust has been merged
It's also a recipe for failure for ports in general. Same goes for the "not idiomatic Rust" comments above — that would be nonsense.

You want to port it as faithfully as possible to the original, porting it bug-for-bug, quirk-for-quirk. Then, over time, after the port has been proven to be as identical to the original as possible, you can gradually fix those kinds of internals.

That's why TypeScript's tsgo native port is so good.

veidr··on Rewrite Bun in Rust has been merged
By having Codex port Deno to Zig, you mean?
veidr··on GitHub Copilot code review will start consuming GitHub Actions minutes
This is funny, but Copilot is still an interesting case-study and (probably) failed predictor of where we are headed.

We all know, and have known for a long time, that the AI labs selling dollars for a nickel are going to pull that rug, and up that price, at some point.

Copilot, though, has been consistently the weakest mainstream AI coding offering. Inferior to Cursor or Windsurf at editor completions, inferior to Codex, Claude, OpenCode, blah blah blah, at agentic coding and also the old-school chat-style...

And now, it's no longer cheap AND now sucks even more than it has all along — the new $39/month plan is not only worse than all its competitors, but worse than its own $10 plan was a month ago — by a lot.

The thing is, you can't jack the price up unless you're good enough — at least on some axis, to some customer segment — to jack the price. And when you're not good enough, and you have vastly superior competitors who are not doing that yet... you're just forfeiting the game.

Which I agree, Copilot should do — it's the Windows Phone of AI coding assistants, after all — it still seems weird to me to just commit humiliating suicide rather that trying to make some deal with one of those superior competitors.

Instead of just jumping into a dumpster and lighting yourself on fire.

veidr··on NSA is using Anthropic's Mythos despite blacklist
turns out it was spelled "lusage" the whole time
veidr··on NSA is using Anthropic's Mythos despite blacklist
Exactly the same way that the `cancelled` of my youth became `canceled`. By being misspelled so often that the misspelling won.

In this case, it's not clear who wins yet — "lose" may loose, or mount a comeback, resulting in "loose" being the one to lose.

veidr··on Tailscale's new macOS home
Well I mean, recently because they have no idea how to make good UIs, and have not read their own enormously detailed (and excellent) Human Interface Guidelines tomes from 10, 20, and probably 30 years go, and have basically regressed to barbarism.

But before that relatively recent fall-off-a-cliff event (whatever it was that caused it, most of us will never know), it was pretty clear that they didn't want to implicitly endorse the lazy/anti-user/Windows-equivalent-UX antipattern of having apps that intentionally made themselves accessible only from a menu bar icon.

I hate the App Store shite that goes wildly too far the other way, but I don't quite understand wwhy they couldn't figure out a way to enable the menu bar widget API in a way that failed if your app didn't also have a way to open via all the normal ways (double-clicking the icon in /Applications, asking Siri to launch it, etc)

veidr··on Tailscale's new macOS home
It's true this is a mess, but no application should have a menu by icon as its only means of access. It's OK to offer that as an option, but all applications should be capable of presenting a user interface when launched from the Applications directory (or (rarely) ~/Applications, etc).

There's really no exception to this rule. For an (tiny) minority of applications, it makes sense to hide the dock icon, and to typically access the app via hotkey or menu bar widget. But those apps should still have an icon and should still be able to be invoked by opening it using any of the standard ways to do that. That's just how the Mac works.

veidr··on I quit. The clankers won
It absolutely is, but the fundamental misunderstanding around this seems to be that "effectively using coding agents" is a superset of the 2023-era general understanding of "Senior Software Engineer".

At least when you're talking about shipping software customers pay for, or debugging it, etc. Research, narrow specializations, etc may be a different category and some will indeed be obsoleted.

veidr··on [dead]
Who's seeing this in the wild?
veidr··on Dario Amodei calls OpenAI’s messaging around military deal ‘straight up lies’
I don't think that's what is being said, mainly? Like that's why Anthropic wants to have it in the contract(s) with the government?

At the same time, it is expressly illegal in some circumstances; that was the whole core of the Snowden revelations. The NSA and CIA are expressly curtailed from doing that by law — there are cases where they may surveil citizens with a court order, but not "mass" surveillance. There are some restrictions on the military along those same lines.

Keywords: Executive Order 12333, FISA, National Security Act, Posse Comitatus Act

veidr··on Dario Amodei calls OpenAI’s messaging around military deal ‘straight up lies’
crazy take

like saying kids having internet-connected devices with built-in cameras doesn't increase the probability of sexting, they could do the same with film cameras and a fax machine

veidr··on Dario Amodei calls OpenAI’s messaging around military deal ‘straight up lies’
Nobody gives a shit about jumping to #1 in the app stores, at this scale.

If US & A really goes full-Huawei on Anthropic, they can't IPO. It's an existential crisis for them. I think they can survive in some form, somehow, because their model is really good, probably the best.

And in other times, I would think the US government had sufficient intellectual horsepower to not cut off its own dick, and the golden goose's head, over some idiotic morning-drinker road-rage type beef. But these are not other times. These are these times.

veidr··on Dario Amodei calls OpenAI’s messaging around military deal ‘straight up lies’
That fear proved well-grounded. While it probably doesn't seem as big of a deal now — in this era when we just serially assassinate heads of state we don't like without any pretense otherwise — the US indeed did direct its European allies to intercept the plane of Bolivian president Evo Morales, based on the (incorrect, as it turned out) suspicion that Snowden was on board.

https://en.wikipedia.org/wiki/Evo_Morales_grounding_incident

veidr··on MacBook Pro with M5 Pro and M5 Max
I don't have that problem (new Safari window in < 100ms) but I believe you, LOL.

Because I have the problem on 7+ Macs (as in all mine, my kids', my sister's and my dad's (all of which I am primary tech support on)) where if I press ⌘+ to increase the font size on a website, it increases — and then immediately reverts back to the previous size.

Every single time. But only the first time. I just did it on this site to be sure it still happens.

Do it again, and it works.

It's been happening for at least one or two years, across more than one major OS upgrade. ¯\_(ಠ_ಠ)_/¯

veidr··on MacBook Pro with M5 Pro and M5 Max
No, that difference is the 5090, not the 3090.
veidr··on New iPad Air, powered by M4
You can thank short-sighted, busy, unprincipled-asshole parents (like me and my wife) for this.

Would I buy each of my 3 kids an iPad every 2-3 years[1] if they had this capability? Hell fuck no. I'd let them use my iPad, which I myself don't even use that much.

But as soon as my kids started texting weird shit to business contacts, or accidentally declining meeting invites because they were playing ROBLOX and the notification was annoying — there was no choice. They'd already experienced the iPad, and I'm too busy to do the super-dad job of weaning them off screens in favor of paper books. Plus, iPads are actually really cool for kids, in a lot of ways.

But the lack of multi-user on iPad is unforgivable user-betrayal. It feels a lot like the gas station charging $25 for a 2L bottle of water right after the earthquake.

Might not be illegal, but... fuck you. The iPad is a great product but it leaves me with a burning napalm hatred for Apple in my heart, just the same as when I try to cancel a US newspaper subscription. Fuck you.

[1]: because, while admirably durable, kids do just wear them out and break them

veidr··on America could have $4 lunch bowls like Japan but for zoning laws
What do you eat?
veidr··on America could have $4 lunch bowls like Japan but for zoning laws
concerning
veidr··on America could have $4 lunch bowls like Japan but for zoning laws
I think the problem is more like:

When in American history have we had more things that are more engaging¹ competing with civic participation for our free time?

¹: and I think the terrifying answer might be:

    LOL, never, so? Hurry up and die.
← PreviousPage 2 of 34Next →