lamontcg

18 ms·

301.
by lamontcg 3y ago
After reading about the situation that Lasse Collin was in with xz before their mental health problems were exploited by a likely state actor I'm 100% not fucking apologizing for using that word to describe how unpaid maintainers of cr
302.
by lamontcg 3y ago
Think you've got that backwards, there's nothing fundamental about Dual_EC_DRBG that prevents anyone else exploiting it, while the xz vulnerability is gated with a specific private key.
303.
by lamontcg 3y ago
> ”Progress will not happen until there is new maintainer. … The current maintainer lost interest or doesn’t care to maintain anymore. It is sad to see for a repo like this.” While this might be a sockpuppet deliberately manipulating the
304.
by lamontcg 3y ago
Another old person opinion: the issue tracker of an open source project needs to be firmly anchored into the needs of the maintainers and not the users. The argument that bugs/issues need to be kept open forever unless they're f
305.
by lamontcg 3y ago
I mean that is still social engineering, it is just really long-game social engineering. And IDK that we've entirely ruled out that Jia Tan didn't wind up being blackmailed or coerced or something -- although if they were really r
306.
by lamontcg 3y ago
And ranger rolling your t-shirts: https://www.youtube.com/watch?v=fuD-ZZydsVg
307.
by lamontcg 3y ago
In C# I've been preferring to only use var when the type appears in the expression so that it can be inferred by humans if you printed it out. In rust I've been using type inference per the usual rust coding conventions. I haven
308.
by lamontcg 3y ago
This is one of those cases where I fully stand with the people saying that you should read the writers intent and assume that they just didn't have enough coffee that morning yet to be thinking pedantically. You know exactly what that
309.
by lamontcg 3y ago
https://en.wikipedia.org/wiki/Dual_EC_DRBG
310.
by lamontcg 3y ago
> forces you to think about it forcing people to type something never forces them to think about it.
311.
by lamontcg 3y ago
I've definitely worked for people who violated that rule to the detriment of the company. They could _appear_ competent, but in my view, corroborated later by the view of the market, they were actually not.
312.
by lamontcg 3y ago
If someone autogenerates one way or another all the delgation, then that's just as buggy as embedding. The presence of all the explicit composition in the codebase doesn't mean that anyone actually sat down and thought about it a
313.
by lamontcg 3y ago
Many decision makers only talk to other decision makers across the corporate boundaries, so that the people nominally leading the software devs are never interacting with the people who actually use the software either, just the people who
314.
by lamontcg 3y ago
> I personally would apriori doubt any of your claims from this point on. And I can't stand people who dismiss the entirety of another person's opinions based on managing to find one opinion that they disagree with. That'
315.
by lamontcg 3y ago
Yeah that article was really thin, and at a guess I'd say that the age of great-grandparents has probably been declining since at least around the 50s or 60s and we're certainly not at peak-great-grandparent. This article reads l
316.
by lamontcg 3y ago
> but why do you want cooperative cancellation? I don't. Previous commenter doesn't believe in uncooperative cancellation though and .NET seems to be removing all support for it. I would love to have worker threads with all kin
317.
by lamontcg 3y ago
The future dystopia isn't 1984, it isn't Brave New World, it is Brazil.
318.
by lamontcg 3y ago
1. "Don't fight the Fed" Recessions usually follow the Fed raising interest rates. There's a roughly 6-12 month lag after the fed stops raising interest rates for them to bite. There are short term effects from what th
319.
by lamontcg 3y ago
> My opinion is that cancellation of tasks fundamentally should be cooperative and uncooperative cancellation is more of a misfeature, which is convenient at the surface level, but has deep issues underneath. Cooperative cancellation can
320.
by lamontcg 3y ago
> could help us end this never-ending outbreak altogether. it has jumped to so many other species where it has established reservoirs that it'll never be gone. this virus is going to be with the human race for at least the next hund
321.
by lamontcg 3y ago
> Developers don't like to think about abstractions and naming is a known hard problem. People pick this up and now everything is easy. Every name becomes: DoThis, DoThat, DoThisOtherThing and only answers to `call`. No need to thin
322.
by lamontcg 3y ago
Yeah if you define the utility of C++ so narrowly to these very highly micro-optimized use cases then Rust can easily capture 100x the mind share of C++ because programmers generally just don't need to care that much. And really seeing
323.
by lamontcg 3y ago
The big tech companies own and lease commercial property and are all trying to prevent the CRE landscape from completely detonating on them. They are all incentivized directly towards RTO and to loudly banging the drum about RTO to try to
324.
by lamontcg 3y ago
> hopefully not before I manage to learn a couple badass driver tricks from them. I mean they're probably tailgating and aggressively changing lanes and don't have any awareness of the dangers of differential velocity between l
325.
by lamontcg 3y ago
> The senior engineer who introduced the thing like this inevitably leaves and nobody cares to learn some bespoke abstraction enough to keep using it. They seem to be saying that this inevitably happens and to never use the abstraction.
326.
by lamontcg 3y ago
The previous comment seemed more "thought terminating" to me than the Carlin reference response to it.
327.
by lamontcg 3y ago
the code in the blog post has an error that you fixed in the gist: def step(callable = nil, &block) you're missing the nil default in the blog post so it ArgumentError's when passed only a block
328.
by lamontcg 3y ago
You're assuming a relatively high degree of competency and available time on the part of maintainers and it sounds like a reasonably short backlog. That's great. For overworked, understaffed teams like a large backlog of reviews
329.
by lamontcg 3y ago
Because your change and the formatting change are probably dependent, and between the time you submit the change and the time your PRs are accepted there may be multiple other commits to that file which affected lines that your formatting P
330.
by lamontcg 3y ago
1. Deanonymize users 2. ??? 3. Profit I literally can't figure out what step 2 is supposed to be there, I guess this is why people go get MBAs in order to understand 5D chess moves like this.

More ›