@lauriewired Then we will see a split, where pandery games for the mouth-breathing masses are streamed (GTA, Battlefield), and well designed games with depth remain local.
Fine by me!
@jamonholmgren Yes, but it also creates an opaque data contract that both sides must follow.
Definitely worth it for internal application comms at scale.
But any sort of open API with diverse consumers would at least need to provide an option for JSON
@IroncladDev Yeah, I run my rust apps on tiny 1cpu/1ram nodes, so I have to build the docker image in CI, push to Docker Hub, and then pull the image on the node.
Works fine though!
@davepl1968@Martyupnorth Its mainly the whole, official entrenchment of identity politics thing.
There should be 1 scout program for all. Government should be color-blind in its proactive functions, and perceive color/gender only when defending specific individuals who have been discriminated against
@NobodymrRobert That is a job for a miter saw.
Or, for very short pieces, a table saw with a miter gauge or crosscut sled.
Maybe if it were battery powered, it could be useful out in the field.
@_rygo6@schteppe While Rust cannot solve cross-boundary issues, the methodology of using it is an excellent way to learn these concepts deeply.
The formality you complain about forces the brain to consider these broad issues as a matter of course.
@_rygo6@schteppe The opposite is true of C. You can hammer out C code that works on the happy path on your machine, only for it to blow up with any variance. Not only can you not trust others code, you cannot trust your own. Spooky action at a distance is beyond even the strongest minds.
@_rygo6@schteppe You might be thinking of LLMs: that is what causes the loss of fundamental understanding you describe.
If someone writes a passing Rust binary, they necessarily concocted something with safe structure, traceable ownership, explicit error handling: Rustc only verified.
@_rygo6@schteppe You speak as if Rust does the memory layout design for you, and you can hammer out structures and logic, with Rust abstracting you away from these concerns.
This is not true at all. It does none of these things for you, it simply refuses to compile if you violate ownership rules
@_rygo6@schteppe I wish I was still verified, to have enough characters to fully counter your arguments. Instead, I will use a few consecutive comments.
I do my fair share of GPU (WebGPU) and embedded no_alloc (Rust) programming.
Rust made me much better at both.