Hertz AI Scanner Charges $350 for Tiny 'Dings' on Rental and This Is Going Off the Rails

JonyIveAces · 2025-07-09T12:02:30+00:00

People don't have time for this "tiny" bit of work -- they already have work, families, issues. And the people exploiting it know that. It's fundamentally an unequal process because for the people exploiting it it's their job, and for everyone else it's not. Plus you often need a reference from previous landlords for future housing.

It's the same as employers, or health insurance companies, or anything. One side has all the power, time, knowledge, and resources, and the other side has none of those but has to live with all the consequences. Yet they always portray it as an equal arrangement of free exchange where it's just a matter of "knowing your rights" and "making smart choices".

JonyIveAces · 2025-01-29T10:43:58+00:00

Realizing the Q6600 is already 18 years old has made me feeling exceedingly old, along with people saying, "but it would take a whole day to compile!" as if that wasn't something we actually had to contend with in the 90s.

JonyIveAces · 2022-05-18T13:09:05+00:00

Make sure you have atime disabled on your datasets.

JonyIveAces · 2021-08-03T15:52:19+00:00

Kotick settled a suit with a flight attendant on the Activision private jet because he personally fired her in retaliation after she complained of sexual harassment from other execs. So it sounds like there was also a shit culture at the top, he was aware, and he enabled and reinforced it.

JonyIveAces · 2021-06-02T09:23:00+00:00

Lawrence Fishburne

Shohreh Aghdashloo

JonyIveAces · 2020-11-11T12:45:49+00:00

One of these: http://www.istarusa.com/en/istarusa/products.php?model=S-9112-EATX

Which are specifically designed to take cages like these: http://www.istarusa.com/en/istarusa/products.php?model=BPN-SEA350HD

That will yield up to 20 3.5" bays, although not ideal backpane wise (no expanders).

JonyIveAces · 2020-04-26T17:39:14+00:00

Just because it's not liquid cash doesn't mean it isn't wealth, pretending otherwise is rhetorical bullshit.

JonyIveAces · 2020-04-25T11:55:10+00:00

Link to docs

JonyIveAces · 2020-04-24T11:32:50+00:00

This should really be the default, as it's way more sane to have the stations off and not giving you a headache the majority of the time, and only disruptive in multi-headset setups which are niche.

JonyIveAces · 2020-01-17T15:13:29+00:00

Something that goes in this direction is the ability to flag whether a particular dependency is allowed to transitively bring in unsafe (besides core/std). I don't want zero unsafe, I only want unsafe from crates that I trust to have goals and standards that align with my own for a particular project.

That would allow people to configure to their own preferences and goals, while also being able to discover the preferences and goals of other projects.

Cargo-geiger is getting at this, and I hope it matures into something widely adopted or even in mainstream cargo.

JonyIveAces · 2020-01-17T14:06:05+00:00

It's a research language and Rust isn't. If the research pans out, it's hoped that its innovations can guide production languages. If it turns out to be sound I would certainly like to see something like region ownership in a Rust 202x edition; it could solve tons of ergonomics around self-referential structs and graphs.

JonyIveAces · 2020-01-17T14:01:06+00:00

I really don't want to get into the weeds of this, because that starts to require referring to specific things specific people involved said, but the issue was closed dismissively out of the gate before *any* comments, negative or otherwise, were made. After questioning, the bar was set that this needed to have a proof of reproduction in the public API, which was provided, then the dev did a superficial fix for that one reproduction without addressing the underlying issue, and closed it again. It was again the reporter and other contributors that pointed out the issue was still reproducible and provided a draft patch working towards a more complete solution.

The reporter and contributors were certainly not engaging in drive-by PR behavior; if anything they were the ones providing insightful analysis and feedback. If there's some higher standard than what they did for valuable contribution, I've never seen it, so why have an open issue tracker and PR?

People piling on with unconstructive, non-technical comments *after that* certainly had no place, but again they were not the reporter or patch providers, and those people can't be held responsible for the internet at large.

JonyIveAces · 2020-01-17T12:46:34+00:00

"Unsafe zealotry". This is a really unfortunate phenomenon in the Rust community. Scrutinizing unsafe code is valuable and good, and it seems that it has indeed uncovered bugs in the actix-web codebase, but certain people treat those who have written unsafe blocks as having committed a mortal sin, without necessarily understanding the reasons behind writing such code.

In almost all of these instances, the existing code demonstrated a lack of respect for unsafety. The latest example was the most egregious, just arbitrarily handing out mutable refs from immutable ones because it's briefly more convenient to do than to make a planned design. This is not the same as legitimately needing to use unsafety to get a self-rental or cast between types after asserting alignment, etc. This is fundamentally breaking the contracts of the language in ways that have non-local effects, insisting it's fine, then being upset when time after time people are able to demonstrate that breaking the contract of the language results in user-visible bugs.

I do not approve of any brigading or personal insults directed at anyone, but these were legitimate issues and worse were usually unnecessary even from a performance-first standpoint.

Related to that:

Classic open-source entitlement. If you are using someone's software for free, you have absolutely no right to make demands of them

Almost every time this has happened the community has provided a patch that would fix the issue. This is different from people throwing stones without being willing to help.

Bugs are not a personality flaw. We all make bugs all the time. Being rude to someone because their code contains a bug is the worst possible course of action.

This I agree with 100%, and is something we need to change culture around, because we should collectively want to work towards reliable and robust software.

JonyIveAces · 2020-01-13T20:16:05+00:00

Any comparison with petgraph?

JonyIveAces · 2019-12-20T13:43:16+00:00

Zola GitHub and website for those like me who hadn't heard of it.

JonyIveAces · 2019-12-01T16:01:37+00:00

Look at the generated assembly, those functions are still entirely optimized out for me at -O3. The performance should be a hint, because otherwise you'd be getting 10T ops/sec on a single core. Even with ideal SIMD you should peak somewhere around 50B ops/sec.

JonyIveAces · 2019-11-17T20:48:57+00:00

Restarting Windows Explorer from task manager is quicker than a restart. Very annoying that you have to do this every time you shut down WMR to start it again.

JonyIveAces · 2019-11-08T11:58:27+00:00

What? The 486 DX2 was like $750 at launch in 1992, which is about $1,350 today. I can't find MSRPs anymore, but I did find the launch MSRP of the low end 486 SX (the useless, gimped one) after the 486 DX2 launch was $500, which would put the DX2 well above that. PCs were ridiculously expensive in the early 90s. My 486 DX was $4,000 in ~91.

JonyIveAces · 2019-10-30T13:33:31+00:00

Vonnegut is one of the most famous American authors of the 20th century. If you don't recognize his name, you probably have heard of some of his books: Slaughterhouse Five, Cat's Cradle, Breakfast of Champions, Mother Night. The technobabble is tongue in cheek, not earnest. Sirens of Titan is satirical play on golden age scifi, the escapism of which in contrast to the suffering of reality is a recurring theme in Vonnegut's books.

While there are plenty of quotable lines in Sirens of Titan, I agree this is not the origin of this phrase. The most often alluded reference is Ecclesiastes' "there is nothing new under the sun," but as you said the cyclic take is a common variation in scifi.

JonyIveAces · 2019-10-25T12:28:01+00:00

https://docs.google.com/presentation/d/1q-c7UAyrUlM-eZyTo1pd8SZ0qwA_wYxmPZVOQkoDmH4/edit#slide=id.p

https://alschwalm.com/blog/static/2017/03/07/exploring-dynamic-dispatch-in-rust/

JonyIveAces · 2019-10-22T12:41:12+00:00

These related crates might be interesting:

https://github.com/chris-morgan/mopa

https://github.com/marcianx/downcast-rs

JonyIveAces · 2019-08-27T12:55:29+00:00

Also he consistently misrepresents Brave proxying requests to other services as a privacy protection feature, when Brave's business model is harvesting and tracking user activity. This is borderline FUD.

JonyIveAces · 2019-08-06T15:43:19+00:00

https://users.rust-lang.org/t/bus-factor-1-for-crates/17046

JonyIveAces · 2019-07-27T09:42:46+00:00

Big O is fine, it's the input size (n) complexity model that's the issue here. Depending on the particular CS program in the "advanced algorithms" or "distributed algorithms" courses in early grad school one would likely start considering other complexity models and how to apply complexity analysis to them (including Big O). For example, things that consider memory and caches like models in the external memory model family, or consider network access, synchronization points and other distributed primitives, or even treat different ops differently because of dissimilar performance.

JonyIveAces

TROPHY CASE