HN user

dep_b

3,877 karma
Posts1
Comments1,568
View on HN

Loss or breakage.

I had the original AirPods and vowed to never buy them again because replacing the battery was so expensive.

Just ridiculous to throw away expensive audio equipment because battery replacement is as expensive as 50% of a new pair.

While good headphones from the 70s are still good, maybe with some foam replacements.

“…if you give it good context…” that’s what the architect session is for basically. You throw around ideas and store the direction you want to go.

Then you execute it with a clean context.

Clean context is needed for maximum performance while not remembering implementation dead ends you already discarded

I think stable API versions are going to be really big. I’d rather have known bugs u can work around than waking up to whatever thing got fixed that made another thing behave differently.

It’s almost like they reject the parts of the bible featuring Christ, and only cling on to the Old Testament and the parts after Christ as their guide.

In lack of a better word, that sounds more like anti-Cristian

Internet connections on devices are an anti feature to me. I need something to work reliably without internet. And then maybe add some extras through internet access through open and secure protocols, so I can always write my own implementation.

“In the EU” only because some countries might have individual laws, unless you have more information about the EU specifically causing that?

The country with the worst “bad opinion, police comes knocking” is the recently seceded UK.

And I guess Germany has something against nazism?

Problem with SwiftUI is that it only works well on macOS 26, maybe one version prior. AppKit works well on all macOS versions.

Building a macOS 26 only app in SwiftUI today is a great UX, just as fast as AppKit.

But it takes quite some effort to turn an iOS SwiftUI app into a real macOS experience. Though most macOS optimizations help for iPadOS as well.

I had similar experiences working with the RAW data API's that appeared a few years ago in iOS. My photos were barely better than the stuff I would take with my old Nokia!

I have a lot of respect they manage to get pictures to get to look as good as they do on phones.

Worse is the Git UI, where random English words that seem to have a clear meaning in the context of source control don't do at all what you think they do, or five different things, or are really just a bunch of other commands wrapped together for less typing (like "pull").

I would rather have fantasy names than wrong names.

Running Xcode

You can use it as a glorified internet terminal with some light office apps within 256GB.

But it’s a pain in the ass to swap applications constantly, clear caches, delete large files and so on once you exceed those use cases.

512GB is a bit better, but then I shouldn’t have multiple toolchains or other large applications installed, multiple versions of Xcode, etcetera.