Kwantuum

9 ms·

1.
by Kwantuum 1mo ago
If you already know the bug is caused by a race between writing and checkpointing then it's easy. I'm unsure how the linked article makes your point at all though.
2.
by Kwantuum 1mo ago
I don't think the people who opposed those things look foolish even today. Most of those things, in their early days, were implemented haphazardly and with an incredible lack of regulatory oversight, and the reason they were not quite
3.
by Kwantuum 4mo ago
The fact that this can happen at all without the security team's knowledge is telling.
4.
by Kwantuum 4mo ago
I trust openAI's marketing team 100%
5.
by Kwantuum 6mo ago
Interestingly, in the company I currently work for, if an employee encounters a problem with the product, the expected way to report the issue is to open a ticket. Not in an different system with different people responsible for handling it
6.
by Kwantuum 6mo ago
Hackintosh refers to doing things the other way around: running MacOS on non-apple hardware. So no, this is not a hackintosh.
7.
by Kwantuum 9mo ago
Both of the things you quoted are basically gone in practice, you just always use const/let and always use triple-equals for equality comparisons and that's that. Most people that write JavaScript regularly will lint these out in
8.
by Kwantuum 10mo ago
I've had to stop using FF as my development browser because it chokes on large source maps. I used to find lots of issues in our web app that were only ever tested on chromium browsers. I don't anymore because the devtools are unu
9.
by Kwantuum 1y ago
> I guess you can attach a debugger for unit tests, but that's not very useful. That is in fact incredibly useful
10.
by Kwantuum 3y ago
Surely this was meant to be cnt += a[i] > 0
11.
by Kwantuum 3y ago
The most egregious problem caused by this that I've encountered is an almost complete inability to use email 2FA on websites because my phone will kill the browser as soon as I switch to my inbox, and when I go back to the browser I&#x
12.
by Kwantuum 3y ago
There are several points in the article which are just plain wrong: - no private properties ( https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... ) - no readonly properties: You can use a gette
13.
by Kwantuum 3y ago
There was not. There is now but for the better part of a decade it was just... Something you were supposed to have learned from a youtube video or a friend or something.
14.
by Kwantuum 3y ago
Pretty sure they're just replying specifically to > you still have guilty parties going free anyways since the wrong person is convicted which is a non sequitur.
15.
by Kwantuum 3y ago
Now you impose sanctions in your jurisdiction to violators and nobody cares because you're not the EU and your sanctions have no weight.
16.
by Kwantuum 4y ago
A lot of the comments seem to talk about the inevitable AI event horizon but unless I'm misreading this article the results are flat out bad. Even the 6 billion parameters model barely scratches a 50% success rate on a tiny problem t
17.
by Kwantuum 4y ago
> (damnit, of course calculating the permutations of a list is n-squared, but this is an interrogation of the random trivia I can manage to recall and I feel like a deer in the headlights) With this statement I'm inclined to believe
18.
by Kwantuum 4y ago
Website is completely broken in firefox when javascript is enabled.
19.
by Kwantuum 4y ago
You are missing the point completely. The IKEA effect is not "self assembly", the IKEA effect is "I think of this piece of furniture more highly because I assembled it myself". The IKEA effect compares how people feel ab
20.
by Kwantuum 4y ago
That's a lot of words to say "to make fraud harder you have to make buying from you harder, the optimal amount of fraud is the amount of fraud you get when any additional measure you could take against fraud would lower your reven
21.
by Kwantuum 4y ago
from the linked PTC proposal in the article ( https://github.com/tc39/proposal-ptc-syntax ): > Unfortunately, the TC39 process at this time did not require heavy implementation involvement and so while many implemente
22.
by Kwantuum 4y ago
> the type of fetch() can't be inferred by static analysis That is preposterous.
23.
by Kwantuum 4y ago
It really isn't, most native/standard APIs do not return Promises. Lots of things use callbacks. Being comfortable creating Promises from a callback-based API is definitely something any competent JS dev ought to be able to do.
24.
by Kwantuum 4y ago
The original article doesn't just suggest it, it claims it outright, and links a study to back up that claim: https://www.annallergy.org/article/S1081-1206(10)60240-2/ful...
25.
by Kwantuum 5y ago
And in fact, there were detours in pretty much all the solutions I've seen posted online for part 2
26.
by Kwantuum 5y ago
The earth has "holes" and as such the proof of that statement for a sphere does not apply to the earth.
27.
by Kwantuum 5y ago
I can see this being useful when you're maintaining multiple versions and forward-porting patches. Some patches only make sense up to a certain version and you don't want to merge them in the next one up.
28.
by Kwantuum 5y ago
It's not just "some" caveats: then auto-unwrapping means that you cannot use then as fmap reliably. In JS there is no such thing as Promise<Promise<Number>>. You cannot await/then the outer promise so that yo
29.
by Kwantuum 5y ago
Your id does not contained a cryptographically signed vaccination status, which this is.
30.
by Kwantuum 5y ago
console.dir does the same thing as console.log in every modern browser. I'm tired of seeing this "tip", and it's a pretty clear indication the article is poorly researched, the only difference is that it pre-expands the

More ›