Hacker Newsnew | past | comments | ask | show | jobs | submit | shye's commentslogin

I suspect this says more about KPMG accountants than AI.

this is a cute comment, but the reality is a similar analysis could probably apply across literally every profession

Certainly within large corporations where the best survival skill to have is not asking inconvenient questions.

literally every profession

literally. every. profession.

Worse: now that they know, there's personal liability for the directors that no insurance would cover.

For questions about Apple products, I've often had multiple models answer by websearching discussions.apple.com.

But the solutions on the Apple Support Community are often inaccurate, and I've often seen models confidently parrot those inaccurate solutions.

s/But/And/

That's one issue. There's also safety as LSV regulation do not require any crashworthiness tests, so such trucks may be more dangerous to passengers and others (or may not - as there's no mandated bar, we can't really tell how good/bad they are).

I'd think these are not any more unsafe than any other cab-over truck?

We can't tell without comparable tests, which we don't have, and probably won't have: I suspect the reason this is to be sold as LSV is to avoid such.

Results from crash testing of the Japanese model aren't great (scored 1 out of 5 in JNCAP; higher is better), but since results are only comparable to similar weight vehicles, we can't compare to bigger cab-overs directly, only to passenger Kei cars, where some reach 4 out of 5, with a few scoring the full 5.


The thing is, heavier trucks are exempt from any of it in the US. 2006-2009 Chevrolet W-Series were frontal collision death traps as kei trucks and nobody cared.

Selection bias: you don’t see the spam that get rejected at HELO.

My server doesn't reject anyone, but does greylisting. That's a default setting in Postfix. It means the first time an IP address connects it gets a temporary error. If it retries later the message is accepted. That's the only anti-spam measure I have.

Maybe 1 in 5 emails I get is spam, and because I use a different address with every sender I know who sold "my" address to a spam list.


Omarchy is even less production ready than racking up laptops.


Plus there's the issue that DHH is a racist twat.


That's one of the reasons to keep it as far as possible from anywhere you need trust (like prod): software, like soylent green, is made of people. And you can't trust people like him.


A dead serious question: why?

There's a lot to hate about Java, but it also does some things extremely well. It's valid if you don't like the aesthetics, but that's a you thing. Are there any objective reasons you believe Java is not fit for purpose here?


Fair question. With C/C++/Zig/Go available we don't need another layer of abstraction; we have enough. Why do we need another VM? Let's keep thing simple.

Which things does Java do extremely well. Curious.


That's kind of a weird list of languages. C and C++ are both memory unsafe languages. Every Android patch round about half of the vulnerabilities are memory safety bugs in C or C++ applications. Both Google and Microsoft independent from each other concluded that most vulnerabilities are caused by memory safety issues. Zig is also not fully memory safe and Go has a garbage collector just like Java. The Go garbage collector situation is probably worse than Java because it only has a single implementation and you have no choice. Meaning it had better fit your scenario or otherwise your screwed.


I'm not really buying that whole safe/unsafe narrative. Every language is safe if you're using it right.

Using Java because it's safe punishes the best case (i.e. using it right) in complexity, performance, and inter-op due to potential worst cases (i.e using it wrong).

It also doesn't allow you to grow because you're _safe_ already.

In general, world is unsafe at it is, but we don't _invent_ a safe version. We just adapt and learn how to deal with it.


> I'm not really buying that whole safe/unsafe narrative. Every language is safe if you're using it right.

Microsoft and Chromium each reported that roughly 70% of their serious security bugs were memory safety bugs. That's not a problem of beginners misusing the language. Like I said, just take a look at the Android security bulletins and count how many of these come from memory safety issues and how these numbers have improved in recent years with migrations to Rust. PHP last week? Memory safety issue.

The amount of high impact vulnerabilities coming from memory unsafe languages C and C++ proves there are too many people who "can't use it right". And these people apparently include very skilled people working at companies like Microsoft and Google on high profile projects.

We wouldn't need seatbelts if everyone would just drive safe. We wouldn't need hard hats at a construction site if everyone would just work safe.


I can't care less about æsthetics tbh.


This effort is relevant to "breaking cryptography" about as much as publishing the script for a 40 years old movie would break the film industry.


They are throwing Claude at questions around cryptography.


I wouldn’t call it “tech”, nor rare. But maybe that’s why I am not in marketing.


In their current scale, I believe Oxide are like Rolce Royce: if you have to ask for the price before taking a test ride, you can't afford it.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: