HN user

glhaynes

8,549 karma
Posts98
Comments2,202
View on HN
forums.swift.org 8mo ago

Swift on FreeBSD Preview

glhaynes
235pts156
forums.swift.org 8mo ago

Roadmap for improving the type checker

glhaynes
89pts60
orgchart.mit.edu 9mo ago

Regarding the Compact

glhaynes
2pts0
machinelearning.apple.com 1y ago

Apple Intelligence Foundation Language Models Tech Report 2025 [pdf]

glhaynes
8pts2
www.macrumors.com 1y ago

Epic Games CEO Tim Sweeney Calls Apple's Find My Super Creepy Surveillance Tech

glhaynes
5pts0
www.thrillingtalesofoldvideogames.com 2y ago

Where did you go, Ms. Pac-Man?

glhaynes
137pts58
www.swift.org 2y ago

Swift 6.0 Nightly Development Snapshots

glhaynes
1pts0
www.bloomberg.com 3y ago

Intel Is in Talks to Be an Anchor Investor in Chip Designer Arm’s IPO

glhaynes
5pts1
sporks.space 5y ago

RISC-V isn’t as interesting as you think

glhaynes
121pts151
www.newyorker.com 6y ago

The Contrarian Coronavirus Theory That Informed the Trump Administration

glhaynes
34pts7
twitter.com 7y ago

Hi-Ten Bomberman, the first HD video game, has been found

glhaynes
3pts0
nepis.epa.gov 7y ago

Can We Delay a Greenhouse Warming? (1983) [pdf]

glhaynes
40pts52
forums.swift.org 7y ago

Swift on Windows Progress

glhaynes
4pts0
stories.appbot.co 7y ago

Experimenting with Pricing Lifted My App Revenue Almost 500%

glhaynes
2pts0
all3dp.com 7y ago

Most Common 3D File Formats in 2019

glhaynes
2pts0
kaomorphism.com 7y ago

How to Predict Any Three Events More Accurately

glhaynes
4pts0
nickjanetakis.com 7y ago

Using WSL and MobaXterm to Create a Linux Dev Environment on Windows

glhaynes
1pts0
www.washingtonpost.com 7y ago

‘Carbon removal is now a thing’: Radical fixes get a boost at climate talks

glhaynes
6pts1
blog.timac.org 7y ago

Apple’s use of Swift in iOS 12

glhaynes
184pts139
matt.diephouse.com 7y ago

Value-Oriented Programming

glhaynes
87pts58
www.youtube.com 7y ago

Mac OS Mojave Marzipan's Internals (video)

glhaynes
1pts0
baltazarstudios.com 7y ago

A Z80 from the Ground Up (2014)

glhaynes
75pts10
nymag.com 7y ago

How Did the Climate Apocalypse Become Old News?

glhaynes
2pts0
www.ralfj.de 8y ago

The Tale of a Bug in Arc: Synchronization and Data Races

glhaynes
2pts0
www.macworld.com 8y ago

WWDC 2018 is probably going to be boring, and that's the way it should be

glhaynes
1pts0
www2.dmst.aueb.gr 8y ago

Dgsh – directed graph shell

glhaynes
28pts1
9to5mac.com 8y ago

Apple’s Secret Star Project Revealed

glhaynes
18pts3
duo.com 8y ago

Apple iMac Pro and Secure Storage

glhaynes
182pts57
blog.emojipedia.org 8y ago

Apple Proposes New Accessibility Emojis

glhaynes
6pts0
blogs.msdn.microsoft.com 8y ago

Visual Studio for Mac Adds Editor Support for Razor, JavaScript, and TypeScript

glhaynes
2pts0
PCjs Machines 2 days ago

As a kid who hadn't seen anything else, the mechanic of "save early, save often" made perfect sense to me (and I've always wished I had a similar mechanism IRL!), just as I imagine it did to the Sierra authors. And in fact I think there's a lot to like about it -- it's not "good game design", but imo it does provide stakes and a sense of danger in a way that the Lucasarts/etc stuff doesn't. But, yeah, a kid who's had more than passing experience with modern games certainly might not see it that way!

"All that time babysitting the AIs just to be a little faster" doesn't seem like an accurate/unbiased portrayal of what they said: "The v1 feature feels more like a v3 given the amount of iteration it already went through."

Sometimes I think the main value in AI-maintained code being “high quality” is when the structure can enforce invariants. If invalid states aren’t representable, then the AI can’t easily add bugs in the future.

Of course that just leads to: what’s the best way to achieve that goal? Through elegant code or adding lots of tests? Which is a debate from long before LLMs existed.

I look at such things similarly, and have never felt like "team building exercises" were particularly valuable. I'm working with these people on the products we build for hours every day; I don't need to do an escape room with them to "team build".

That said, I have to recognize that this may be partially because of my personality. I don't "do great" at mixers like this. I'd rather go home and be with my family than drink beer—regardless of label—in a corporate setting. People describe me as charismatic and engaging one-on-one, but I'm awkward and unhappy at a big crowd event.

But there are other people whom I think get a lot of value and connections out of them! So it's kinda hard for me to say.

Downgrades in quality, though, stick out like a sore thumb. "I didn't really like going to these things before, but at least they had good beer." It can also be a real "it's the thought that counts" sort of thing. When you show me that you're willing to spend less on me, it sends a signal, sometimes stronger than if you'd never spent anything on me in the first place.

Seems like there's a good argument to be made that we'll have plenty of opportunities for valuable growth and learning, just about different things. Just like it's always been with technology. The machine does some of the stuff I used to do so now I do some different stuff.

Yeah, good point. For a little hobbyist site of no importance, I'm not too worried about vendor lock-in, but that calculus changes as it gets more important.

It'd be interesting to prompt it to do the same job but try to be innovative.

To your point, yeah, I mostly don't want AI to be innovative unless I'm asking for it to be. In fact, I spend much more time asking it "is that a conventional/idiomatic choice?" (usually when I'm working on a platform I'm not super experienced with) than I do saying "hey, be more innovative."

Yes. I'll go down a wrong path in 20 minutes that'd have taken me half a day to go down by hand, and I keep having to remind myself that code is cheap now (and the robot doesn't get tired) so it's best to throw it away and spend 10 more minutes and get it right.

No install fuss — download and start designing immediately.

also

Gatekeeper blocks the app immediately. You'll see either "TUIStudio cannot be opened because it is from an unidentified developer" or "TUIStudio is damaged and can't be opened" on newer macOS after quarantine flags the binary. To get past it: right-click the .app → Open → Open anyway — or go to System Settings → Privacy & Security → "Open Anyway".

If you're addressing this to me: you need to separate my description of how I perceive things from any effort/desire on my part to make that come to pass. I don't expect to stand to gain if AI continues to get better at coding — most likely just the opposite; this is the first time in my career that I've ever felt much anxiety about whether I'd be able to find work in my field in the future.

There are many others like me who share this expectation, and, while we certainly may be wrong, it's not because of some sinister plan to make the prophecy come true. (There are certainly some who do have sinister/profit-seeking motives, of course!)

An argument that I have some sympathy for, while still being moderately+ in favor of gun control (here in the USA where I'm a citizen).

It seems that gun control—though imperfect—in regions that have implemented it has had a good bit of success and the legitimate/non-harmful capabilities lost seem worth it to me in trade for the gains. (Reasonable people can disagree here!)

Whereas it seems to me that if we accept the proposition that the vast majority of code in the future is going to be written by AI (and I do), these valuable projects that are taking hard-line stances against it are going to find themselves either having to retreat from that position or facing insurmountable difficulties in staying relevant while holding to their stance.

Why Objective-C 5 months ago

The "Swift has too many keywords now" meme makes me want to go insane. The vast majority of Swift code never runs into any of that stuff; so, what advocates of it are saying is in effect "we don't want Swift to expand into these new areas (that it has potential to be really good at) even if it's in a way that doesn't affect current uses at all."

That said, the Swift 6 / Strict Concurrency transitions truly have been rough and confusing. It's not super clear to me that much of it could have been avoided (maybe if the value of Approachable Concurrency mode had been understood to be important from the beginning?), and the benefits are real, but my gut feeling is that a lot of the "Swift is too complicated" stuff is probably just misplaced annoyance at this.