voidnullnil

7 ms·

31.
by voidnullnil 5y ago
The slice is simply unsynchronized, so a user of the slice may pull out one array but a length that was for a different array. https://blog.stalkr.net/2015/04/golang-data-races-to-break-m...
32.
by voidnullnil 5y ago
Disregarding memory models, OOPSLA is not a good source for PL research.
33.
by voidnullnil 5y ago
What's wrong with my comment? Quite literally: Cloudflare has been adopted by 50% or whatever of the web and they run a rudimentary WAF type product that is IP block happy. This is a recipe to get every VPN and Tor node in the world bl
34.
by voidnullnil 5y ago
And it marks your IP some points toward "evil hacker" and now you know why Tor has been ruined for 10 years. Collary: CloudBleed.
35.
by voidnullnil 5y ago
It's a big problem in Java at least. In Go you have value types by default and they try to make zero a meaningful value.
36.
by voidnullnil 5y ago
Go's errors have basically all the problems of exception handling in previous generation languages (and a few novel ones). This explains it (tl;dr nobody bothers to formally define what errors they return, and the blindly propagate suc
37.
by voidnullnil 5y ago
Channels and an alt operator are much more powerful than locks but eh I can't remember the edge cases in Go's channels so you might be right,
38.
by voidnullnil 5y ago
I've never bothered to look up the hoare thing, but null as a member of all types increases the amount of time spent studying any given API (and of course, there are lots of null pointer bugs from people who didn't bother to study
39.
by voidnullnil 5y ago
So what's the motivation for the article? Presumably someone complained that the compiler optimizing atomics broke their code.
40.
by voidnullnil 5y ago
>will inevitably lead to trampling the user's freedoms People keep saying this but it happened 20 years ago. This reminds me of shit like the postal service requiring photo ID to receive a package and people complaining about NSA hu
41.
by voidnullnil 5y ago
Aimbots were already using "smoothing" methods in the original CS. Snapping to headshot is more to piss people off.
42.
by voidnullnil 5y ago
You will see it after it's gone due to persistence of vision, even at <10ms (no idea what the actual number is). Mind 20FPS is longer than a frame on even a 60Hz monitor.
43.
by voidnullnil 5y ago
Thinking on: "[data races] are straightforward to identify" It's a the same as the problem of knowing what data is used in what thread, which is hard and unsolvable by automation, so I doubt it's an easy problem.
44.
by voidnullnil 5y ago
Okay, well your (wrong) semantic argument that "GMM violation = UB" is irrelevant, so I'll stop arguing against it other than hinting that there is not one single mention of the word "undefined" in the GMM spec. Bac
45.
by voidnullnil 5y ago
> because if you violate the memory model, literally any consequence is fair game. Any consequence is _not_ fair game. "Memory Models" only involve stuff like tossing out sequential consistency [1]. They never say or imply some
46.
by voidnullnil 5y ago
> Like, all of that code violates the memory model, and? > so whatever it accomplishes is irrelevant. I have no idea what point you are making. _Of course_ there has to be a bug in the code for there to be a buffer overflow vuln. Or a
47.
by voidnullnil 5y ago
Not sure why people keep deducing this point I have not made. I said Go markets to dilletante programmers, which is a reason to make it simpler, not more complex. Any language with "the memory model" is complex. I do not fully gra
48.
by voidnullnil 5y ago
https://blog.stalkr.net/2015/04/golang-data-races-to-break-m... The "Exploiting the slice type" section.
49.
by voidnullnil 5y ago
As usual good advice but shouldn't be law.
50.
by voidnullnil 5y ago
Guess how can I tell this thread is bait without even opening it.
51.
by voidnullnil 5y ago
> To solve that problem, the practitioner only needs to know that "mutex.lock()" This is true, but they do not know that. If you do not give some kind of substantiation, they will shrug it off and go back to "nah this thin
52.
by voidnullnil 5y ago
How many programmers do you know put locks around polling varibles for seemingly no reason (as they are not cognizant of the memory model)?
53.
by voidnullnil 5y ago
> This "Memory Model" discussion is only for people who want to build faster systems: for people searching for a "better spinlock", or for writing lock-free algorithms / lock-free data structures. Actually, most
54.
by voidnullnil 5y ago
These "memory models" are too complex for languages intended for dilettante developers. It was a disaster in Java/C#. Not even more than a handful of programmers in existence know in depth how it works, as in, can they unders
55.
by voidnullnil 5y ago
Coming up with this "return $this" pattern to emulate a composition operator seems like a very AI thing to do.
56.
by voidnullnil 5y ago
Blogs about "return" inside "finally" in Java and the likes were common in the 2000s. The fact that languages have so many simple things like this that surprise people indicates that there is a problem somewhere. I'