server_bot

While this seems like a convincing case, at what point is it morally acceptable to produce new art derived from existing work?

Would it have been fine if Capcom had re-created near identical patterns without use of the book's original digital files? It's a reference book after all.

Not saying Capcom should profit without crediting the original artist. But visual art remixing textures feels more grey area to me than copy/pasting code or someone's writing.

We should encourage PL experimentation and welcome new languages!

But keep in mind that cost of entry for production usage these days is a full suite of tooling (package manager, code formatter, language server for IDEs, etc).

I didn't see a standout feature in this article on Grain that made me think the manpower investment in developing the language and tooling is worth it, but I could be wrong!

Firmware isn't necessarily more difficult than other areas, every domain has serious challenges. But firmware programming has the kind of challenges that require a very deep technical background, something almost impossible to build in an X-week boot camp:

- Insane debugging: you have to debug extremely low-level failures with very limited visibility (e.g. no operating system to catch your segfaults) and proprietary or complex tools.

- A hard language made harder: C is difficult to get right, but embedded C (no dynamic memory, lots of bitwise operations for MMIO register writes, targeting exotic architectures, etc) is even more difficult.

- Extreme constraints: The products you work can have constraints like safety certification, minimal power utilization, or ultra low latency response. Meeting those constrains often means having to deeply understand hardware.

Hmm...I think a lot of this discussion is missing two important points:

1. Regardless of whether or not C++ is going away, your team needs help now. You have an opportunity to get up to speed and add value in the present. That could pay off in social capital, promotion, or just plain old appreciation of your efforts.

2. Say you don't care about your team's needs at all (for the sake of argument, I'm sure you do!). Learning C++ will teach you concepts and patterns that can help you be a better engineer, even if you move on to Rust later (which IMO will be C++'s replacement for new projects eventually). Growth happens outside your comfort zone, this could be a good growth opportunity.

Thanks! You're right about the PC, misread the table.

Love the idea of a minimal retro VM, had a chuckle at the single-byte program counter. Hope this catches on and there's a software ecosystem.

Does anyone know of a list of quirky VMs like this one?

The Pico-8 comes to mind since it's also a fantasy console, but wondering if there are other esoteric emulators - maybe even ones that had real-world use at some point.

A mature take, I applaud the author for overcoming "commitment bias" and being willing to make a change. The lack of a cloud SDK for thier provider seems crippling in hindsight.

Wish them well with whatever the replacement language becomes!

Nice high-level breakdown without pushing one moral stance or another, just focusing on the business-side facts.

I always wonder about the employee-side of the equation - since the pool of job candidates that can hold a government security clearance is small realative to the pool of skilled engineers, what are the implications for hiring/retention/culture for teams that do defense work?

Did you read the same post I read? One of the harassers asserted that she must have traded sexual favors for a CS degree. Do you seriously believe that a male engineer would be sexualized and discredited that aggressively?

Please take some time to reflect. Look up statistics on sexual assault and violence against women. This is not an attempt to bait clicks, its an attempt to stand up against systemic attack.

Sad day, she was a champion of the people - a fighter for both women's rights and civil rights. Her iconic status was earned. Would recommend the 2018 documentary "RBG" for anyone interested in her life and career.

I feel like choosing between the two for a new project comes down to one factor: do you truly need to maximize performance? Be honest.

If yes, Rust: no GC, consider the rayon crate for concurrency. Higher learning curve, ecosystem may not be as mature for certain areas yet (outside of web assembly).

If no, Go: lower learning curve, runtime-managed concurrency, more ecosystem maturity for most enterprise software tasks.