foobazgt

As near as I can remember, my first real programming experience was when I was eight years old, writing basic programs on an Apple IIc at school in 3rd grade. (I was too poor to afford my own computer until my senior year of college). It was awesome.

I have never found computers disappointing, and I have spent most of my career/life learning about them - from processor design through to distributed systems. Mostly I've been disappointed in the disparity between the number of interesting things I'd like to do, and the number of lifetimes I have available to me.

Different strokes for different folks, I guess.

It'd definitely be my preference to lean on existing law where it makes sense (law is already too complicated). Unfortunately, IANAL, so I don't know what makes the most sense. Whatever we have doesn't seem to be doing a great job against the mass spread of cameras and abuse.

Yeah, as a human race, we've clearly reached the technological era where deep, ubiquitous surveillance is both technologically and economically feasible. For a few years now, I've been thinking we need a constitutional amendment to restrict the mechanisms, deployment, and use of mass automated surveillance.

Human beings don't empathize well with situations nor people they never have to personally face. That's a well-lit path to fascism. We're one step closer to 1984.

This is how pedagogy works. You must simplify something.

For a Tesla, the estimates are around $2K. For a Waymo, the same estimates are ~$25K (down from $125K!!!). There's not a clear timeline for Waymo-style kit at a price consumers can afford and in a form factor they'd accept.

(FWIW, the business story for Waymo has never been about its hardware making its way to consumers. It's always been about whether Waymo continues to run its own taxi service or leases out hardware and operations to other taxi businesses).

Studies seem to favor waist to height over waist to hip for a stronger correlation to better outcomes.

Nah, as titzer said, it's really about general-purpose code being branchy (a good match for CPUs) vs numeric code being heavily parallelized and non-branchy (a good match for SIMD/GPUs). Only a small subset of very specific languages / instructions target the latter (e.g. CUDA and SSE4).

Maybe you drive into flood waters, but I don't. That's not a difficult skill to pull off.

We're still in the early days of self driving cars, and as much simulation and miles as they have, they're still constantly getting exposed to real world conditions that are new to them. The world is dynamic, so this will always remain true.

It remains to be seen where we'll converge on capability, incident rate, and acceptance.

My most enjoyable and productive experiences with AI so far have looked more like pair-programming than agent-based vibe coding. That is to say, I care about the details, and I want to read, understand, edit, and curate the codebase. I find that if I'm not limiting AI to relatively small enhancements per request-review cycle (100 or so LOC), then when things inevitably go off the rails, I'm in a deep hole that takes a long time to climb out of.

I haven't tried out Junie yet, but the concept seems pretty compelling to me. I want a good IDE for the language I'm using, and I'd like an AI that's well integrated and trained on delegating to it for algorithmic/deterministic transforms (e.g. IDE-driven refactorings).

They take about the same time as with an ICE. I stop and charge for 20m whenever I need a restroom break or some food (every couple hours or so). My car generally goes longer without stopping than I do.

If you're stopping often or long, something is wrong with your setup.

> I like Teslas a lot, but gave you ever been on a road trip in one? It's pretty brutal.

Maybe 50 road trips? Usually hundreds of miles, with the longest at 1000mi. Literally the easiest road trips I've done in my life.

I routinely traverse Monteagle with no substantive loss in efficiency. Sounds like something goofy with the mach-e?

I just drove 100mi in freezing temps (around 25F) at mostly interstate speeds (70+) mph. I completed my trip around 95% of EPA. Maybe a function of the quality of your EV.

I know congestion can be an issue at some sites, but I have never waited in line to charge in seven years of EV ownership.

In addition, for superchargers, you can see real-time stall availability, so if a particular site was crowded, you could just opt for the next. (Easy enough to do since there are so many).

Is that legally enforceable? If a mod doesn't contain code / assets from the game itself, what legal rights does Microsoft have over the distribution of that mod?

Teslas illuminate brake lights based on deceleration (until reaching a stop), which is the desired behavior. I use regen braking aggressively to slow down, and different light behavior would give people seizures or make them brake-light-deaf.

If you're annoyed by the braking lights on a Tesla, it's because you're following too (dangerously) closely.

Slava mentions both bidirectional inferencing and overloading as two of the big culprits.

I've been doing some language work recently, and I'm quite sympathetic to bidirectional inferencing. I think, though, that modern PLs need better solutions for adhoc overloading. It's notorious for its complexity, blowing up algorithmically, and confusing users with surprising results (why oh why did the compiler select this function over the one I intended). That said, I haven't discovered a good alternative (for my purposes) yet.

No joke, that's just wild. I'd expect an expression like that to type-check literally a million times faster - at the least. Even after reading the article, it's not clear why that particular expression is so egregiously poor.

At first I read this as "Apple doesn't implement Touch ID, because they found it to be insecure", which really confused me. Was that the intent?

On second reading, I'm thinking this might mean, "since Apple only implements Face ID, biometrics on Apple devices is less secure", which makes more sense (to me).

JOOQ (http://jooq.org) is pretty fantastic for this, and it's my go-to for working with RDBMs' on the JVM. It provides a DSL-like API that lets you write pretty much any SQL you need in a type-safe way (without string concatenation).

It sounds like you can't find a used minivan-like EV, with 250+mi range. A 2022 model y has 330mi range new (probably around 300mi now). You can get them for $23K after federal rebate. Seems like a good deal that would be "doable" for you.

Can you elaborate?

> Also if there is an explicit split there will be groups of people who "game" it (spend disproportional amount of time to "train" their kids vs actual natural talent - not sure if this is good or bad).

The idea of tracking out kids who excel due to high personal motivation when they have less natural aptitude is flat out dystopian. I'm drawing mental images of Gattaca. Training isn't "gaming". It's a natural part of how you improve performance, and it's a desirable ethical attribute.

Nothing lasts forever, and eventually you have to port, emulate, archive or otherwise deal with very old applications / media. You see this all over the place: physical media, file formats, protocols, retro gaming, etc.

There's a sweet spot between giving people enough time and tools to make a transition while also avoiding having your platform implode into a black hole of accumulated complexity. Neither end of the spectrum is healthy.

[Hey I own one of those]. Nah, the majority of people buying those specific vehicles should be buying an EV instead. In fact, this article is targeted specifically to them.

Rather, the biggest need for hybrids are people who frequently tow long distance at highway speeds. The combined aero drag is ridiculous: about 25% of typical EV efficiency. You'd need to drag a humongous 300kwh battery around to get range comparable to a typical sedan while towing.

Instead, some of the new EREVs are more like a BEV + hybrid, in that they have a BEV-sized battery (e.g. 100+kwh) for all your non-towing driving, along with a generator to handle the long distance towing.

No, when you privately sell your vehicle, you transfer it through Tesla.

> first off that's not the case

It's objectively the case. They literally have the data to back it up, regardless of what anecdata you might have seen on some forums.

> And the context above

Their fleet data says 85% battery average capacity at 200K mi and that battery degradation slows down over time. That's a far cry from 70% at 9 years.

This isn't a thing, and as a concrete counter-example:

https://www.tesla.com/support/vehicle-warranty

"Yes. Your New Vehicle Limited Warranty will follow your vehicle and be transferred to the new owner when a vehicle ownership transfer is performed through Tesla."

> 269mi after 10 years is catastrophic

I have taken multiple 1000+ mi road trips with great ease on 280mi range. I would describe it as the exact opposite of catastrophic. And they've only become easier since then (e.g. more charger deployments).

Can you please share some (non-byzantine) trips that you can't make with only 80% battery capacity? Let's assume 240mi (80% of 300), since that seems to be about the average EV range nowadays.