The worst thing about LLMs getting commoditized and becoming cheaper is seeing slop like this pollute every meaningful discussion on the internet

I'd love to try it, could you please share an invite? My email is on my profile page.

That's $800 for a family of 4. With the median household income at under $80,000, it's ridiculous to think the average person can afford to spend that much just to skip a line a couple times a year.

But a family of 4 is not the value proposition here. They are explicitly targeting frequent flyers that stand in the queue so often that the time saves add up.

If you're only traveling once a year, you can handle a 45 minute wait twice (although yes, it still sucks). If you're traveling once a week, it's a completely different ballpark.

It is not. Your partner is discounted abd kids go free.

You seem to have missed the obvious Tharakaari (the Kannada word for vegetables)?

Unfortunately, you don't always know if on-call will be involved until you start at the job. Often many companies don't even hire you with a particular role in mind, instead you are matched to a team after you're signed on. (Especially for new grads). And sometimes on-call is introduced in an existing role, it can be difficult to refuse, especially for people in more junior roles.

But definitely ask about on-call when interviewing, in case they say they have it you can bail out before you sign.

I ask about it repeatedly to all interviewers to the point that some companies disqualify me. Call it a survivorship bias in reverse. It doesn't always work, amazingly, but it always sends a strong signal.

Hey, I used one of those vaccine booking projects to get my own shot in India, and it made use of kvdb.io. great work!

Perhaps you're talking about jpackage - https://openjdk.java.net/jeps/392

That sounds close, but I thought you got a plain executable out rather than an installer.

What's your opinion on svelte?

One big selling point on vue is that you can just use a tag script and map a vue object on your regular HTML page.

Ne need for build steps. No need for html in the JS script.

It feels like JS from the 2000, simple and light, but with reactivity and speed.

Of course, once you need it, you can just use the awesome ViteJS to get your backend build with SFC files.

This makes vue scale up, but also scale down, which is equally important.

Svelte seems to be set on having a server side build process for the front end. That is an even bigger no-go for me.

The complexity of React and the OPs framework at least be contained in the frontend. With a server side build step, the complexity of the frontend spoils over to the backend.

A tab retains the history (could hit back and go to the page that led me there), a booknark does not.

That sounds a bit excessive. If your project is going through a lot of changes and refactoring, the multiple architecture.md files will be hard to keep up-to-date