royjacobs

That sort of proves my point, though. Spring support for GraalVM is ongoing and will likely be quite useable and mature out of the box.

The people jumping to Quarkus or Micronaut are more eager to chase the new shiny and are willing to spend the time debugging not-yet-mature stacks.

Edit: To be clear, the reply mentions fanboyism but we are talking about the maturity of a stack. Spring has been around for 20 years and is not going anywhere. Quarkus just reached 5.

They are moving there because it's new and shiny, not because it's better.

Spring and Spring Boot are incredibly productive and give you a ton of stuff out of the box, whereas some people actually enjoy writing a lot of plumbing code as a distraction/challenge from boring business code. Those people will migrate to "lean" frameworks because it will give them the opportunity to write more low-level plumbing code.

But what's your point? Would you truly want consumers of JSON Patch data to embed a JS interpreter?

Because that would require consumers to have a Javascript interpreter to use it.

The demoscene needs you back, Saffron!

This looks great. I hope it'll get a Switch port.

And in full resolution, too!

I only recently discovered Densha De GO! and apparently the most recent game in the series is based around this very line. Very interesting to see these photos, I love the vibe, and it makes me appreciate all the detail that went into the game.

That's a shame, but there's heavy competition from companies like PCBWay, I suppose.

Incidentally, I read it the title like Shapeways provided some files to somehow 3d print bankruptcy. I'm not sure why.

It's great to see Java Web Start finally being used in anger 24 years after its initial release.

"Should all array types be Copy but not Claim? If not, where is the cutoff, and does it depend on the element type?"

I think it was mentioned that something should be considered Claim'able if it can fit in a cache line. So I would guess that a heuristic could be used to determine which array sizes are valid to automatically implement Claim for.

I really like this proposal. It's fairly concrete, makes day-to-day coding much more ergonomic and, more importantly, doesn't introduce a great many esoteric concepts that are just going to clutter the language.

I'm assuming not everyone will agree with this, since it's more 'magic' but I'd argue it's the right amount of magic to help you with common patterns that you'd otherwise have to spend time manually implementing anyway (like the Dioxus Labs 'context' example).