HackerTrans
TopNewTrendsCommentsPastAskShowJobs

foobazgt

no profile record

comments

foobazgt
·23 วันที่ผ่านมา·discuss
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).
foobazgt
·2 เดือนที่ผ่านมา·discuss
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.
foobazgt
·3 เดือนที่ผ่านมา·discuss
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).
foobazgt
·7 เดือนที่ผ่านมา·discuss
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.
foobazgt
·7 เดือนที่ผ่านมา·discuss
> 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.
foobazgt
·7 เดือนที่ผ่านมา·discuss
I routinely traverse Monteagle with no substantive loss in efficiency. Sounds like something goofy with the mach-e?
foobazgt
·7 เดือนที่ผ่านมา·discuss
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.
foobazgt
·7 เดือนที่ผ่านมา·discuss
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).
foobazgt
·8 เดือนที่ผ่านมา·discuss
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?
foobazgt
·8 เดือนที่ผ่านมา·discuss
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.
foobazgt
·8 เดือนที่ผ่านมา·discuss
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.
foobazgt
·8 เดือนที่ผ่านมา·discuss
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.
foobazgt
·9 เดือนที่ผ่านมา·discuss
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).
foobazgt
·10 เดือนที่ผ่านมา·discuss
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).
foobazgt
·10 เดือนที่ผ่านมา·discuss
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.
foobazgt
·11 เดือนที่ผ่านมา·discuss
Can you elaborate?
foobazgt
·2 ปีที่แล้ว·discuss
> in which case it's all monitorEnter and monitorExit, regardless.

Oops, I need to correct myself!

ReentrantLock doesn't depend upon monitorEnter/Exit, but rather AbstractQueuedSynchronizer and LockSupport, which ultimately delegate to Unsafe methods like park/unpark and CAS (*compareAndSet*). Don't know why I had that confused in my head.

In any case, the point holds that "synchronized" as a language feature has mostly a zero cost for code that doesn't use it. It's a red herring when discussing modern Java concurrency.
foobazgt
·2 ปีที่แล้ว·discuss
"every synchronized function"

Right. Synchronized is the key word here. The vast majority of code doesn't involve synchronized, and therefore the vast majority of objects don't have locks associated with them. That's quite important.

Those classes which do use synchronized were just going to create a ReentrantLock held for the duration of the call anyway, in which case it's all monitorEnter and monitorExit, regardless.

> This is going to put a damper on any further conversation.

Sadge.
foobazgt
·2 ปีที่แล้ว·discuss
> because every object is its own mutex.

Not true in any practical sense.

> And you end up having to trade single core performance for multi core by deciding to speculatively calculate the object.

What is the alternative you suggest? If you care about having the predicate actually hold, and you also don't want to have to hold the lock while constructing the object, then you're going to end up in an optimistic-concurrency scenario where you check the predicate under lock, compute the object, and check again before swapping the value in. You may end up having to throw your work away when you discover the predicate changed. Java is no better nor worse at doing this than anything else.
foobazgt
·2 ปีที่แล้ว·discuss
Every abstraction is about outsourcing the thing it's abstracting away. If using a queue solves your problem, you no longer have to deal with all the headaches that you can run into using a bare mutex.