What is "funny" is that I had the maximum password size thing on several bank websites (and a low one, at that). Fortunately, with 2FA, it doesn't really matter I guess.
I think you're right. I'm not an Apple fanboy (by far), but I'm very excited about that product for nomadic work purpose. I like to move a lot, and being able to work without having a desk or similar is incredible. I'm just a bit skeptical about a few points rn: that it isn't comfortable when the weather is hot, that the battery is bulky or doesn't last a day... but so far I've read everywhere that the tech is incredible.
The first article is funny, because I moved from my native country to the one right next to it, and everybody is confused by my name. They have one given name and 2 family names, while I have 4 first names, and a compound last name.
No need to travel to the other side of the planet to meet a different culture of naming.
Declarative macros are hard to read, same level as regex
Procedural macros require to write a new crate with a ton of boilerplate, sometimes for stuff conceptually really simple (like hash is: apply the same function to every field, then compose the results)
I agree, though, that it's better there're here than nothing. It's just that there is to be a better solution.
For an IC, I think it's mainly about autonomy. The management don't want to be behind you. You get assigned a task, you ought to know how to handle it (including asking to the right persons) and to deliver it on time.
Sorry for the late answer. Those days, I'm interested in Ante. The language creator has some novel ideas for a non-GC memory safe language. And the compiler is written in Rust. It's not finished at all tho.
Uh, they're different, though. There is no C++ tool (AFAIK) providing an exhaustive check of ALL the data lifetimes.
I even think it's impossible, because their semantics are really different. Rust is move by default, C++ copy by default; Rust has no inheritance with its constructors, etc.
Well, I think it's fine for the not-so-near future. They are known to support their hardware for quite a long time. I even suspect that before their support ends, there will be some other groundbreaking new hardware.
It depends if it's a real DevOps role, or an operations role with a DevOps title because it's trendy. In the former case, the role should include some kind of backend development.
This is especially true for steam... what a crappy app