Waymo cancels cars when they are unable to get to you in a reasonable time. The service will not resend a car automatically, so the user needs to babysit the app until they’re actually in the car. I’ve seen this twice in the last week. In Phoenix and SF we have preferred ride share or taxi when the car showing up is important, like getting to a medical appointment on time.

> Is there a good reason browsers could and or should not support ts out of the box?

Because it’s a Microsoft product and Microsoft still follows Embrace, Extend, Extinguish process. Once every browser supports TS, what prevents Microsoft from revving TS with a license change? Who’s going to take over the TS fork?

Bill Hicks was a comedian. It's not advice.

to be fair he does say in the bit that its not a joke.

> The real question isn't "do you need a database" but "do you need state" — and often the answer is no.

This is a solid takeaway and applies to a lot of domains. Great observation

But if you have state, and that state needs to persist between program executions, then for the love of resiliency and all that is robust, consider using a SQL database!

How could the user expect consistent behavior from the back button if web apps can no longer leverage it like web sites?

Un/mute button throws a fetch error in Safari, fails to toggle audio.

Top comment on the previous thread was someone complaining about the writing style of kids these days. Huh.

> Pass references around to objects, not recreate them each time at some function boundary.

Non-primitives are always pass-by-reference. There's no mechanism to pass a non-primitive by value except edge-cases like giving ownership of a buffer to another process.

> destructuring

What about it? What backs the assumption that destructuring is inherently worse than dot and/or bracket syntax? Is there a behavior you think is unique to destructuring? Or maybe a specific report from one engine years ago?

> Non-primitives are always pass-by-reference.

it's a good thing. pass objects by reference.

> Is there a behavior you think is unique to destructuring?

depending on exact syntax, will collect values in another array or object. it's often used as the mirror-pattern of using named variables, which allocates an object for each function call.

in isolation these are not inherently wrong, at scale they start to add up. and should not be used in tight loops.

> pass objects by reference.

It’s not an option. That’s how JS must behave.

> depending on exact syntax, will collect values in another array or object

Not in JS. Maybe you are referring to rest syntax? That is not specific to destructuring i.e. functions accept rest parameters.

> which allocates an object for each function call.

No, in JS non-primitives MUST be pass by reference.

You're being pedantic and doing gotcha argumenting.

Pass objects by ref, I said that to underscore its better than create new objects. I get it, its the only way, but theyre still passed by ref.

Yes, [a,b,...rest] =... is restructuring and creates new object.

Named params create new objects, it's better to pass args individually, the ref creation under the hood is not comparibly impactful.

Do you test this against password managers? Seems like this approach could generate false positives

The AI generated illustration and satire of the poem hurt my soul. Tom doesn’t even have pupils! This output is low quality even for AI generated content.