f3408fh

I have a question for those who turn off _anonymous_ telemetry. What are you worried about?

How do you define functional?

This is saying you'd be ok with books being only permitted to be read at the library, behind a sealed kiosk screen, because otherwise people might post spoilers online.

Ah, well, I take it back then. Sorry dist-epoch!

Bullshit. He describes the actual reasons here: https://go.dev/talks/2012/splash.article#TOC_4.

And anyway, since when is not liking something a bad reason to try your hand at creating a better thing?

Yep, it's super useless. The label is so general. Was AI used for one image in the 10 minute video? Is the voiceover AI? Is the entirety of it generated with AI? No way to know.

I don't know. From what I see every idea accessible to a solo developer either already has 10 VC-funded startups or relies on big platforms with closed-off APIs.

Now make a user script that blocks posts titled "I was tired of X, so I...".

Saying that VS Code is terrible for Go is simply false. The Go extension is regularly updated and works extremely well. Sure, it lacks some advanced refactoring features available in IntelliJ, like function parameters reordering, but gopls supports most refactoring you'd need to do day to day..

For the record Neovim has built-in LSP support and Vim supports LSP with plugins. Why use Ctags that you have to manually generate?

I always found the Severus Snape - ALWAYS (Live at Hogwarts) video to be really good for AI. The video was probably created by prompting for each scene, instead of letting the model generate the whole thing. It's a cool of example of what's possible nonetheless.

https://www.youtube.com/watch?v=SlsEDkavoso

What will you be replacing it with, if anything?

This is so cool. Congratulations! Have you considered opening operating costs as well?

With that lens your career before this device was a few colors and 104 keys?

Interesting. App store asked me for proof of permission from the first party to use a reverse engineered BLE protocol.

How did you get this through App Store review? My understanding is Apple tends to be pretty strict about apps that rely on reverse-engineered private APIs.

That's cool. I tried it out and the movement is very floaty, so much so that it's hard to navigate the first room without running headfirst into a wall every time I try to go somewhere. Is it true to the original? Performance is great though.

Considering how difficult it can be to get certain versions of the game running nowadays, it's nice to have another option to explore the world! I tried and tried to get EQ1999 running on different Linux distributions (Fedora, Bazzite, CachyOS) but just couldn't. Only version that worked is the official Steam client.

And entirely AI generated

Case closed.

"Most is doing a lot of work".

So, 90% isn't most in your book?

I always wonder how a solo developer can source high quality assets like these, plus develop a full game with them. In this case did the dev create the assets or did they purchase them from a freelancer? How much would purchasing this many assets cost?

Nowadays most games will run on Linux thanks to Valve's Proton compatibility layer.

I don't doubt it. One time I was on Youtube Shorts and it randomly showed me a weird birth defect intervention/autopsy/idk what. Ruined my day. Very traumatizing to be flashbanged by disturbing material like that unexpectedly.

Out of curiosity, how does something like "But wait..." get rewarded?

Lol! Good point. I did use Claude to write the rule, and it ironically wrote the exact thing I asked it to avoid. I agree that it might be best to use the model as-is, to get the intended experience.

Yes! It's infuriating. I've tried prohibiting them in my AGENTS.md but it's not 100% effective.

--- AGENTS.md ---

## Plain words, not jargon

Don't use jargon-as-shorthand. Say what you actually mean.

- Don't say "load-bearing assumptions". Say "the assumptions the xyz depends on".

- Don't say "cross-service". Name both services, e.g. "whether the X service can derive duration without calling the Y service". "Cross-X" is confusing because it hides which things are involved.

- Don't deliver verdicts as abstract noun-phrases like "Cross-RCA double-counting is unfounded". Say it plainly: "I checked whether the same root cause gets counted twice across RCA runs, and it doesn't."

## No earth-shattering declarations

Don't hype findings. Skip "a critical finding changes everything", "now I have the full picture", "this changes the game", etc. Just state what you found plainly. Most findings are ordinary; report them that way.

## Don't reflexively hedge a "yes"

When the answer is yes, say yes. Don't soften every positive answer with a caveat: it erodes confidence in the "yes". Only add a caveat when there's a genuine, specific uncertainty worth flagging.

No genius. Just too much time on this site :)

Git worktrees

They are indeed everywhere, but it's possible you don't have a need for them. For example, every time you buy something online using Stripe, the seller receives a webhook indicating that a purchase was completed.

Uhhh apart from OP I don’t see anyone commenting on the content quality?

Also OP didn’t even praise the content. They said it “seems interesting.”