jjnoakes

11 ms·

91.
by jjnoakes 3y ago
> no programs will change behavior due to simply adopting the new Go toolchain Seems like they thought about that. I think it's a good change.
92.
by jjnoakes 3y ago
I haven't really had this experience. Usually a subtle reorg of how I iterate, for example, allows the compiler to eliminate bounds checks, effectively giving me full speed without unsafe in tight loops.
93.
by jjnoakes 3y ago
> it is not a language that lends itself to quick prototyping Maybe it depends on your perspective, or maybe it is simply personal preference, but I find rust pleasant and quick to prototype in.
94.
by jjnoakes 3y ago
It depends. Sometimes you have no choice but to deploy to an old machine with back-leveled tls libraries, and static linking can save the day. Of course that tends to be the exception (hopefully).
95.
by jjnoakes 3y ago
> unrecoverable panics Panics are recoverable.
96.
by jjnoakes 3y ago
I addressed this above. See the coin flipping example.
97.
by jjnoakes 3y ago
> The problem is not about the game overall > The Monty Hall problem is not about "the whole game". The Monty Hall problem is about the whole game. That's the difference, and that's why the 50/50 claim doesn&#
98.
by jjnoakes 3y ago
> Can a gf shoot her exbf that she gave the keycode to last month? How is this different from a physical key?
99.
by jjnoakes 3y ago
I'm not sure why you keep asking the same question. The answer to the second one is here: https://news.ycombinator.com/item?id=36752870 and the answer to the first one is basically alluded to here: https://n
100.
by jjnoakes 3y ago
That's about as relevant as this: "I claim the odds of flipping a fair coin 100 times in a row and getting heads every time is 50/50, but only in the situation where you happened to flip 99 heads in a row already". Of co
101.
by jjnoakes 3y ago
The original situation covers all scenarios. Any choice of door you make and all possible doors the host might open. The odds are the same every time. The proposed 50/50 scenario only makes sense for some possible situations - those wh
102.
by jjnoakes 3y ago
That's the point though, no? The only way to justify the 50/50 claim made above that I can see is that the host must choose the door to open at random from among all 3 doors. So scenarios do arise where the host opens your door an
103.
by jjnoakes 3y ago
Right, in the world where the door he already opened was done randomly (i.e. it could have been a goat or it could have been a car, and it could have been the door you also chose), then if he happened to both (a) open one of the doors you d
104.
by jjnoakes 3y ago
> If the game show host is opening a door at random (i.e. it's possible that he opens the door with the car behind it OR the door you already picked) then the outcome is 50/50 whether you switch or not. I don't think this
105.
by jjnoakes 3y ago
I've always just used ssh host 'single command string "with regular shell quoting"' and that avoids the problem.
106.
by jjnoakes 3y ago
I don't think so.
107.
by jjnoakes 3y ago
Storing executables on file systems shared across operating systems or architectures gets a lot easier if you don't have to have special paths for each os+arch combination.
108.
by jjnoakes 3y ago
The moves described in the video seemed like they were decent analogues to me. The bishop moved along the same color and could attack rooks and knights from safety and could slide between pieces. Rooks could attack bishops and knights safel
109.
by jjnoakes 3y ago
This isn't true.
110.
by jjnoakes 3y ago
Right, but in rust, not using one is a compile time error. In Java (as you can see by the article), not using one is a silent bug at runtime.
111.
by jjnoakes 3y ago
The install method itself is not unsafe when compared to most other install methods. It gets a bad rap for no reason.
112.
by jjnoakes 3y ago
If you trust the author of tool you are installing and the installer is by the same author, then why wouldn't you trust the installer too? > It's 100% trivial to have it run rm or shred on all files you have access to while sim
113.
by jjnoakes 3y ago
> My understanding is that Red Hat Enterprise Linux can be thought of as Fedora + stability + patches, and that the patches themselves should be released downstream as part of the GPL. > What's now changed is that these patches a
114.
by jjnoakes 3y ago
> There's not a single smart plug on market that won't connect to cloud to control plug from anywhere. Don't ZigBee and zwave smart plugs work locally only?
115.
by jjnoakes 3y ago
I see where you are coming from, but I've found it beneficial to my business to trade the minor inconvenience of free subscription management for the stability and long-term support for RHEL. I get that others may not like that trade-o
116.
by jjnoakes 3y ago
> I was using CentOS for prototype development. No way would I be able to get RHEL for this. Why doesn't the free RHEL developer subscription work for this use case? (Honestly curious, as I use it for similar prototype development a
117.
by jjnoakes 3y ago
> If the loop doesn't terminate, then you obviously cannot show it. I don't think this is true for all loops either - some can be proven to never terminate, just like some can be proven to terminate. And some can't be pro
118.
by jjnoakes 3y ago
> Tell me when my loop terminates. I think the point is that even though one can't determine loop termination for all loops (easily provable), there are a huge number of useful loops that do useful work and for which you can prove p
119.
by jjnoakes 3y ago
Agreed. I don't know why, but I expected more from HN commenters.
120.
by jjnoakes 3y ago
Thanks for the details!

More ›