anonymousCar

Had this happen to me in November when Android 12 corrupted my pixel 5 and I didn't have backup codes. Altogether it took 2 months before I was able to access everything again, the last thing I got access back to was my Xbox lol

I think --watch mode means it's running while developing

My current issue with tqdm is nested progress bars in multi-threading/processing causing dead locks + tqdm.write just being broken in those contexts, either deadlocking or the ui just being wrong. Does pqdm do a better job?

I have no metrics in the frontend, it's reasonably fast for me. It's the interactions with the backend that are slow. This is evident for anyone that's used the api.

There's some rules here that you can use in bazel. It takes a bit of finesse to get some packages working with it. https://github.com/bazelbuild/rules_nodejs

What's the argument here vs. paypal?

First makes 5.9M cars per year and is planning 50k Mach e. That's 0.8% of their line electric.

VW seems to be the only major manufacturer that's really going all in on electric and it's only after wringing their hands from the emissions scandal.

The old automakers seem to only want to do this in the face of bankruptcy.

There's lots of ways to configure the project but you can setup lazy loading routes, components, and stores so that your user only has loaded what they need. Typescript support is OK, there's some helper libraries that make it better. All of those things make scaling just fine.

While experienced python devs will say, yeah that'd how you should do it. The problem is that python by default isn't using virtualenvs. Consider rust or is where you need to specify global installs.

As other's have pointed out, it really sounds like the deno devs were unfamiliar with what's available with build options for typescript. An unanswered question everyone is asking, why do they handwrite the .d.ts that can be autogenerated?

Mapping isn't trivial, but I'm sure it's not what's blocking expanding operations

Curious that Vue threads on HN always have some upvoted post about svelte

There's a lot of assumptions in OPs post, but maybe we can assume they're talking in context of their sensor suite.

Tesla has made a name for over promising, under delivering on fsd, and refuses to consider lidar as a member of their sensor suite.

I don't think you can adequately compare two companies with vastly different approaches.

There's a tiny in-cabin camera above the rear view mirror.

When can we start calling Python 2.7 legacy code?

Waymo is past 8 million miles total, how many miles on the latest version of the software? Certainly there are new features that are there in the last half than the first half? I think miles count is a bad metric and if it wasn't, Tesla would be the front runner.

Tell that to Android

Opened that Atlantic article and it prompted my phone for camera a d microphone permissions.