Hacker Newsnew | past | comments | ask | show | jobs | submit | pfg_'s commentslogin

I tried this four times, every time it recognized it as nonsense.

Same

But it's not just good enough, it's optimal. It is equivalent to picking a random deck from the set of all possible decks assuming your random source is good. More random than a real shuffle.

Right and that’s what satisfactory means, the condition was satisfied.

Whenever I use chrome, I'm missing the style editor and multi-line repl mode from firefox. When I switched to firefox from chrome, I didn't miss anything. There might be new features chrome has added since that I would want if I knew about them

While I agree on those counts, the debugger in Chrome handles large files of minified code, deep framework stack traces, and stopping in dysfunctional code better.

Except for infinite loops in JS. Firefox still handles those better.

The whole comment is spoilered, so you need to click on it to reveal that text. Presumably it could also appear in a comment that you need to scroll on the page to see.

It's clear to a moderator who sees the comment, but the user asking for a summary could easily have not seen it.


I saw other screenshots that were not spoilered at all. I thought they had hidden the text after the screenshot and the reddit post had readable text.

Zig has this as std.SegmentedList, but it can resize the segment array dynamically


Even when the bisect points to a large commit, it's usually not too difficult to find the source of the regression. Sometimes I've had to go into the original PR and bisect on its commits which is a bit harder. It doesn't seem worth it to me to try to maintain commit quality within a PR when as long as I commit often enough it doesn't really make a difference.


What is the point of a permissions system that can be trivially bypassed?


> What is the point of a permissions system that can be trivially bypassed?

You seem to be confused. The system is not bypassed. The only argument you can make is that the system covers calls to node:fs, whereas some modules might not use node:fs to access the file system. You control what dependencies you run in your system, and how you design your software. If you choose to design your system in such a way that you absolutely need your Node.js app to have unrestricted access to the file systems, you have the tools to do that. If instead you want to lock down file system access, just use node:fs and flip a switch.


To check a box

> need to demonstrate security compliance.


I can read in my head fine. Reading aloud I'm slow and words come out stilted. It's a skill that takes practice to be good at, and it's rare to need. I don't think that's a useful metric.


That's unsubscribing from an email list, not a paid subscription


Firefox on Android often lags for me with backdrop blur effects


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: