I don’t know about ChatGPT, but in Claude Code I _have_ been able to do a side-by-side comparison of API-based metered billing vs subscription billing, in the same UI. You just switch from one to the other using /login.

You should probably not be so quick to dismiss what people say as nonsense.

I like how you compared car drivers to toddlers in terms of behaviour change

Compared with the other examples you gave, I think one of the differences with micro- and nanoplastic and their growing bioaccumulation, is that if/when we discover that some level of concentration of it causes noticeable issues, it will be very hard to reverse, and it will be globally abundant (i.e. throughout the entire food chain). We'll be stuck with the problem for a very very long time.

It's not like we'll be able to just outlaw it and be done with the issue after a few years. So for this specific polluant, it feels right that we should be cautious and look for solutions as quickly as we can.

Honestly curious: what makes you hate it so much?

I found it hit a strange position between trying to be friendly and trying to be powerful. Things felt very inconsistent. After learning a few patterns in the language, other things I would expect to follow the same patterns went off in their own direction. I wish I could conjure up more specific examples but that's about all I remember from it.

It felt like a language that was built for the singular purpose of supporting Flutter (which I actually did enjoy learning) instead of something that needed to exist in its own right. I wish they'd just picked something already baked.

Well, it was created before Flutter, so it wasn't built for that purpose. They did however steer Dart's direction in a way that would be more suitable for Flutter than as a JS replacement which is what it was created for. I don't think it's fair to criticize Dart in the way you have without giving any examples. I haven't found it to be trying to be powerful at all. For example it uses async-await, defaults to dynamic arrays and doesn't focus on classes as much as eg. Java. So I find it to be simple on all accounts. And the developers have specifically stated that their intention with the language is to be as intuitive as possible with the smallest amount of surprises. And I've found that to be the case. I almost never need to actually look at the documentation. Meanwhile I always find myself in MDN looking at some strange JS API (`Date`, for example) despite using it for much longer. And don't even get me started on Java.

Let’s not forget about how the new Dart 3’s patterns can help with parsing and validating JSON: https://dart.dev/language/patterns#validating-incoming-json

At our company, out of the 8 engineers I hired, only 2 had specific experience with our backend (Elixir) or frontend (Flutter) stack. I hired for apparence of talent, experience in some other equivalent stack and the right attitude towards learning.

All of them got productive rather quickly and had PRs shipping to prod in the same week, if not within a couple days.

I’m not saying it _will_ go as smoothly for anyone else, but if you have the right environment and pick the right people, as an employer you’re better off being flexible with experience.

I’d go further: Reading someone else’s writing is akin to mind reading.

reading is mind reading

How do you even force weight lost?

Or recycle it. Don’t pollute the rivers!

Looks awesome! Quick note about the landing page: the GIF captures in the "How it works" section are a bit vertically stretched, weirdly pixellated and really too quick to understand what's going on.

Thanks for pointing out. Will update the GIFs soon.