sidlls

21 ms·

301.
by sidlls 4y ago
I seem not to have communicated my point clearly: inequity in one direction can exist in some areas (e.g., payscales) and in the other in other areas (e.g., social validation in the form of the availability of positive media, toys, and even
302.
by sidlls 4y ago
It can be true that entrenched systems favor males in some areas, and new social and cultural phenomena disfavor them in others at the same time. My wife has made the observation that there seems to be so much more media, events, toys, etc.
303.
by sidlls 4y ago
https://doc.rust-lang.org/stable/book/ch17-00-oop.html
304.
by sidlls 4y ago
I don't think OP was making excuses. It is true that the software vendor's missing test case indicates a poor quality development environment and that humans are the last line of defense. No development process is perfectly resi
305.
by sidlls 4y ago
Multithreading/contention issue? But how would that alter the weights? Off the top of my head: failure to sum values correctly, misreporting the weight to the target plane (reading values from another plane’s weight data).
306.
by sidlls 4y ago
But then there are cache locality issues, etc. Algorithmic runtime performance in practice rarely matches the basic big-O analysis taught in CS classes. Case in point: for small cardinality data in practice it’s often (or at least occasiona
307.
by sidlls 4y ago
Rust supports object oriented programming, and so does golang. In the case of the latter, it’s a fertile ground for all manner of bugs, performance issues, and weird behaviors thanks to the duck typing approach they chose.
308.
by sidlls 4y ago
This is a failure in the development of the software that good process in the purchaser’s handbook saved them from. That there were no tests for this system under high load indicates a poor engineering practice at DynamicSource. They don’
309.
by sidlls 4y ago
First thing I thought of when I saw the original wrong code. I prefer the author's approach, though, as I do believe it is more clear, unless there is something performance critical about it that requires short-circuits for maximum eff
310.
by sidlls 4y ago
We didn’t invent democracy in the US: it has been around since at least Ancient Greece, and before then, too. I am opposed to direct democracy and am absolutely fine with representative/republican democracy.
311.
by sidlls 4y ago
I bring it up because Rust evangelists like to pretend that Rust code with no explicit “unsafe” in it is safe. It’s not safe, though, as long as the dependencies use it. I enjoy coding in Rust. I don’t enjoy the shit name its community give
312.
by sidlls 4y ago
I don't want direct democracy: the problem of voting shenanigans and corruption just expands from a known set of elected officials who vote on laws to...everyone. Aside from that, people in aggregate just aren't that bright: I don
313.
by sidlls 4y ago
"[W]ith "NO unsafe code...."* * except all the unsafe code in the dependencies (e.g. https://github.com/tokio-rs/tokio/search?q=unsafe )
314.
by sidlls 4y ago
It’s not as simple as that. I’ve been hungry and cold (poor, homeless or near enough to it). I’m well off now. I stress about other things than hunger and temperature: but that stress is very real, and just as urgently felt.
315.
by sidlls 4y ago
You’re not stupid: the OP wrote a bunch of jargon that more or less nobody in the industry uses on any regular basis. It’s a similar pattern to functional programming evangelists’ rhetoric. The short answer is this: the compiler enforces ty
316.
by sidlls 4y ago
Most libraries are quite poorly documented (to my taste, anyhow). It is certainly worth spending the time reading at the very least documentation pertinent to the components of the library intended for use.
317.
by sidlls 4y ago
Conveniences like this library and other threading libraries make it easy for people to trivialize something (concurrent programming) that ought not be.
318.
by sidlls 4y ago
A better title would be “Bug lurks in incorrect usage of async Python”. The library documentation clearly calls this out, and incorrect implementations, while buggy, do not mean that async Python is itself buggy.
319.
by sidlls 4y ago
This is unfortunately all too common. I am often dinged by my manager about my throughput when investigating the integration of new libraries because I read the docs, front-to-back, as part of my research and that takes time.
320.
by sidlls 4y ago
I don’t need the media to see that. For one, I lived it as a poor person. For another, not being poor anymore, I still see it on a practically daily basis when I’m at the office.
321.
by sidlls 4y ago
Social and class cliques are a real thing. The so-called networking benefits at elite schools like Princeton and Stanford don’t translate as well or as often to poor students, for example.
322.
by sidlls 4y ago
"Code style" is about more than formatting, and this article isn't identifying "good programmers," it finds a rather weak correlation with people who are good at doing programming contests--the two are not necessari
323.
by sidlls 4y ago
The OP is crapping on people who find Rust hard to learn by broad-brushing them into the "bad programmer" bucket. It's a hallmark of Rust zealots, and one reason why the Rust community has such a bad name. Which is a shame be
324.
by sidlls 4y ago
Hot take: your attitude is why people push back on the Rust community when they're in HN so much.
325.
by sidlls 4y ago
The more I read the "cons" in this article's C++ section the more I scratch my head. Code style is something that should be uniform and enforced. It's bikeshedding, but unless you're using a language with opinionate
326.
by sidlls 4y ago
"Nobody" wants to spend 20 minutes configuring at that granularity: apple's is more than sufficient for 99.9999% of all use cases. All the supposedly superior Android features in this entire thread are things only a minute fr
327.
by sidlls 4y ago
RAII isn't a perfect safeguard against memory leaks. Rust doesn't provide 100% protection against them, either, especially when `unsafe` gets involved. It's better than C++, though, in this regard. There is no fool-proof way
328.
by sidlls 4y ago
Non-trivial Rust code can be just as unreadable as code one would write in any other language. In fact, some of Rust's features (e.g. lifetime identifiers, functional-ish constructs that people use to create huge call chains with closu
329.
by sidlls 4y ago
Apple's notification management is better than what I remember from my last Android phone (years ago, a Pixel, latest version at the time, I think in 2017 or 2018). Apple's app management is definitely mixed, but I find it quite e
330.
by sidlls 4y ago
Yes, you fit in the “rounding error” group of users. Nobody (almost) cares about any of the features you noted. I’m not talking technology-ignorant people, either: the vast majority of phone users, including sophisticated users, use it for

More ›