foundajob

Spoiler alert: The chicken went bad.

> an ecosystem that prioritizes safety etc.

Idiomatic Rust code is just as cavalier regarding NPEs as Java or Python code. Because the language starts to look really gross when you make your code panic-safe. So you have an `expect` here, an `unwrap` there, and now you're going to have the exact same runtime issues as the more expressive managed languages. No Rust programmer thinks their `expect` will panic, just like no Java programmer expects something will be null. Rust does not force you to "exhaustively match".

TIL skepticism of US war propaganda ≈ belief in "democrats drinking infant blood in the basement of a pizza parlor". No, I think you've perfectly illustrated the problem, thanks.

Well, no, the prudent choice for someone concerned with "safety" in this context is any high-level memory managed (GC) language. It's any boring language that has no `unsafe` at all. What you're actually saying is "I'm willing to sacrifice safety for performance," as invariably the objection to a high-level GC language by Rustaceans is that it lacks the necessary lolspeed.

Oh, oh, you don't disagree! The class of memory management bugs caught by the borrow checker only manifest as memory leaks when developing in any boring, garbage-collected memory safe language. Not buffer overflows. Not use after free. None of the excitement advertised on the Rust tin. These things do not occur in boring GC languages. Oh, and in-process data races which must be caught for Rust to be safe at all. Any engineer willing to sacrifice that much productivity based on a theoretical whinge, that is practically treated simply by periodically restarting application nodes, is a total joke. Tolerating memory leaks in high-level development cannot be reasonably extrapolated to "the idea that moving fast is more important than correct and safe code" which is nonsense fearmongering.

Uh, okay then.

I had a similar experience working on a large Hanami app. There's a lot of hidden complexity, but unlike with Rails nothing felt intuitive. There's a lot of emphasis on monadic thinking (see, dry-rb) without much payoff, and it's kind of a round peg/square hole deal with Ruby the language anyway. Very much a feeling of "reinventing the wheel."

It sounds like you're saying that anybody who diverges from your status quo opinions is some sort of mental terrorist. Excuse me, "stochastic terrorist."

Any high performer who could resist the temptation to send a detailed narrative of their latest significant poop, with photos, along with a curt resignation, is a stronger person than me. It really seems like he's asking for it.

Probably not, OP hasn't left a single reply. Just dropped trow in our brains and moved on, classic HN move.

Yea, where's the "outrage"? Need more outrage. I mean, by golly, I have these *kiddos* who need their dad 24/7! What's with these young people who want to go into the office?