> I have the most respect for apps I can use on MacOS, Windows, and Linux - with the same hotkey/user experience on all platforms, equitably - and the least respect for apps which 'only run on one of them', since that is of course nonsense in this day and age.

No. I want things like keyboard shortcuts to reflect the platform norms of where the app is running (macOS in my case). A shared core is fine, but the UI framework must be native to be acceptable. Ghostty is a "gold standard" there.

This is why most web apps are lowest-common-denominator annoyances that I will not use.

Indeed, if the framework is sensible, keyboard shortcuts reflecting platform norms is entirely attainable in a manner that developers don't have to bother with it, much, if they don't want to.

There are plenty of examples of cross-platform UI's surviving the hotkey dance and attaining user satisfaction. There are of course poor examples too, but that's a reflection of care, not effort.

New York City seems to be a counterexample - gelato and ice cream stores everywhere that seem to do decent trade year-round...

The simplest answer is they are voluntarily being scum and selling user data to make a quick buck. It’s almost universally true.

> It’s almost universally true.

It’s not. I give a unique email address to every service I register with, which means I can see who is leaking my email address. Very few of them leak my email address at all, and those that do tend to do so involuntarily through data breaches.

The other main factors in spam are the sleazeballs at Apollo, ZoomInfo, et al., services that use my email address internally for more than I consented (if I use my email address to register for a service, this does not permit that service to add me to their product mailing list), and the spammers who guess email addresses based on LinkedIn info (e.g. name + company domain).

The number of services who appear to take an email address I have given them and sell it appear to be extremely rare.

If you dont mind, What kind of unique email address do you use and how do you manage all the aliases?

There’s no real management involved. I set up a wildcard MX record for *.example.com and hand out jim@<some-id>.example.com whenever anything needs my email address. I don’t need to specifically set up an alias. If spam comes in, I look at the To address to determine where they obtained my email address. Fastmail can be configured this way, for instance.

Most mail providers also support plus addresses or wildcard local parts, so you can do jim+<some-id>@example.com or just <some-id>@example.com. Gmail supports plus addresses, for instance. The downside is that some services reject pluses and some spammers strip out the IDs.

I do the same, and seem to have a much higher hit rate (or a much lower acceptable baseline!)

>and selling user data to make a quick buck

Are there actually companies that will pay you $$$ for a list of emails?

Not exactly, but plenty will just sell everything to data brokers.

>but plenty will just sell everything to data brokers.

Again, "sell" implies that there's some company where they'll accept data from anyone and pay them for it, which so far as I can tell doesn't exist. That's not to say there's no selling going on. The fact that data brokers exist means they do, but that doesn't mean every business is in a position to "sell" data.

My boss has paid many people for lists of email addresses in the past.

Im pretty sure he is not a mythical being!

> You think you look good if you say “hey, the Poles had this really good idea, how about we do the same”?

Yes.

> You think if there was any will wouldn’t the whole EU use whatever the Estonians are doing very well?

Using the Estonian system would be vastly preferable.

If politics doesn’t allow that, the political environment is broken.

How is the Estonian system now? I remember when I visited around 2010 our host just had a quite simple smart card reader and could just use it to sign in to government services with their ID and as far as I remember even sign mails and documents. Germany of course could not use normal smart cards but had to use NFC cards with special readers and made the signing feature and additional service you had to pay for on a yearly basis. Of course the Germans system did not went anywhere for years. I do have a reader now and can use it for some governmental services and have very limited appetite to bind the ID to my phone.

Ukraine also seems to have solved this pretty well. NFC in the plastic card, selfie video confirmation, etc.

Hungary is also rolling out a "digital citizenship" app. (Also can be bootstrapped via newer plastic cards, so no need to visit the government office.)

Live Ultimate Edition for Developers.

You can still use it with an OpenAI subscription (for now at least), and the models aren't substantially worse.

> You aren't paying to be using that limit all of the time.

The erosion of the norm of things doing what they advertise rather than being weasel-worded BS is particularly unfortunate, and leads to claims like this.

You can already do that though? [1]

[1]: https://docs.ollama.com/integrations/claude-code

I very much doubt Anthropic devs are metered, somehow.

(I mostly agree with you, but) devils advocate: most people already do that with dependencies, so why not move the line even further up?

There's a reputational filtering that happens when using dependencies. Stars, downloads, last release, who the developer is, etc.

Yeah we get supply chain attacks (like the axios thing today) with dependencies, but on the whole I think this is much safer than YOLO git-push-force-origin-main-ing some vibe-coded trash that nobody has ever run before.

I also think this isn't really true for the FAANGs, who ostensibly vendor and heavily review many of their dependencies because of the potential impacts they face from them being wrong. For us small potatoes I think "reviewing the code in your repository" is a common sense quality check.

Because you trust that your dependencies are not vibe coded and have been reviewed by humans.

Stop trusting any dependency now.

except they are vibe-or-not coded by some dude in Reno NV who wouldn’t pass a phone screen where you work

I'd trust that dude over professional leetcoders any day.

But you're right that trust is a complicated thing and often misplaced. I think as an industry we're always reevaluating our relationship with OSS, and I'm sure LLMs will affect this relationship in some way. It's too early to tell.

I find this relationship fascinating. since the OSS vast majority of the developers will not hesitate to pull in library X or framework Y knowing really nothing about it, who are developers, what is the quality of it, what is their release process, qa etc etc... The first thing I do now as a "senior" for decades when I get approached with "we should consider using ____" is to send them to their issues page ( e.g. https://github.com/oven-sh/bun/issues ) and then be like "spend 60-90 minutes minimum here reviewing the issues - then come back and tell me whether or not the inclusion of this is something we should consider." and yet, now with LLMs there are sooooooooo many comments on HN like "oh they must be supervised, who knows what they will be doing etc..." - gotta supervise them but some mate in Boise is all good, hopefully someone else will review his stuff that is going into your next release ...