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

Hulk: I'm always angry

AI: I'm always guessing


Hating the player is a integral part of the game.

Think of it as spatial input, not visual. Blind people do have spatial inputs, and high spatial intelligence.

Visual intelligence is a near meaningless term as it's almost entirely dependant on spatial intelligence. The visually impaired do have high spatial intelligence, I wouldn't be surprised if their spatial intelligence is actually higher on average than those without visual impairment.

They have enough lawyers that they can easily find another criminal avenue that doesn't step on the previous path.

Your opinion isn't particularly important in our legal system. Since your comment expresses a preconceived notion of the accused's guilt. It would disqualify you from a jury, and undermine your legitimacy in a judicial, defensive and even prosecutorial function.

Though I respect it as a human opinion.


As usual the company is going to financially shield those responsible, while they in turn shield the company from societal blame.

I'd much rather they get personally fined and/or banned from holding leadership positions in the field (with varying timeframes depending on the level of responsibility).

Naming and shaming won't do much good. It could backfire and serve as a positive mark on their resume for other morally corrupt leaders.


Short prison sentences would be a good deterant for white collar crime, rather than fines.

I think it depends on the level of responsibility. If orders came from above, then sure through those most directly responsible for the order in prison. I also think the lower level leaders should be held accountable for relaying the orders, which is where I think a "can no longer hold this position of authority for ~2 years" punishment might be appropriate.

Incredible research. I wonder how close we are to outputting the universal language into it's own reasoning context (which skips encoding layers). Then using the later decoding layers to lazily inspect the reasoning context.

You can avoid the serialization in WASM by pushing structured bytes to the SharedArrayBuffer, then do serialization in JS which should be relatively cheap compared to pushing JSON strings across the boundary.

It's not an unsuitable application for WASM. They could've drastically reduced the WASM boundary impact if instead of mapping to JSON in Rust they streamed out structured bytes to JS then mapped to JSON there. And the streaming fix was language independent.

So it's more so a story about architectural mistakes.


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

Search: