Insufficiently well expressed. Do you mean *ever* or do you mean *soon* ? Because I 100% agree with *soon* and it's quite possible that something even better will come along before Rust gets everywhere; but I don't think it's possible to make an *ever* claim.
Today I learned that when you start to select large numbers of recipients for a mass SMS, android starts to slow down a lot. Selecting the last 10 of my 80+ mass text each took four or give seconds. Wow. Someone has a seriously badly scaling algorithm in there somewhere.
IME anything which is "modern devops" (e.g. docker, docker-compose, kubernetes, and all the related technologies) is "easy once you know how" and a total and utter nightmare to get into if you're not used to it and just need to dip in for a moment to sort something out. *hugs*
Fair enough. Does Java do named arguments? e.g. can you get something like new ModelKey(generating: true, collecting: false, actuallyGenerating: false, modelState: null) ?
the shorthand record definition is nice. Does it imply a nasty constructor though, or do you get typestate builders for free? Eg. ModelData.new().generating().actuallyGenerating()
Functions/constructors/whatever which take a number of booleans greater than one upset me. Does this record make sense if something is false, X, true, X ? If not, then perhaps a enumeration of not/can/is generating would be better?
After a year of recovery / eating my anxiety and stress, I am envious of your ability to run. Still, my hope is to do the equivalent next year once more. Argh bad foot, argh stress, argh anxiety.