200 karma · joined July 12, 2023
Terrible description IMO. a query should not need approval. Should use mutation or edit or update or modification. Even if query is technically correct it just sounds wrong and confusing.
cursed code. people might say "oh that's normal idiomatic C", I don't care. I am glad Go does not allow code like this
I get that you want to keep up to date with security, but the entire crypto tree is basically a playground for Filippo Valsorda at this point. Meanwhile stuff that I actually need like CMAC is "won't fix"
Netflix wants managers to ask themselves whether they would rehire their current employees
https://github.com/3052/blog/blob/main/2024-06/ublock-origin...
"this gun will shoot you in the foot in some cases. It's better that I don't name an example as you should always be on the lookout for (until having shot yourself in the foot) them"
"most" is doing a lot of work here. don't forget you probably don't want to live next to an airport, railroad, chemical plant
what a ridiculous comment - every single programming language has this or similar syntax for iterating a slice.
Will never happen. Best you can hope for is new functions
thats the whole point of the article. this change trashes that. now many loops are going to have hidden magic
I dont mean that as a statement against the author, I mean it as a statement to the language designers. people are gonna start writing code like this, or worse, and Go is gonna end up like many other unreadable languages. shame.
I dont mean that as a statement against the author, I mean it as a statement to the language designers. people are gonna start writing code like this, or worse, and Go is gonna end up like many other unreadable languages. shame.
Nope. Not on Android.
wow great idea, why didn't I think of that
I used C/C++ for years, and it was always a nightmare to build something, unless it was completely self contained. When your "packaging" is so bad that everything has to be vendored, that should be a red flag.