jjnoakes

25 ms·

241.
by jjnoakes 4y ago
Why do you think that a language with better details would prevent you from opting in to whatever non-default behavior you need? Having the "right" defaults is better for everyone. Folks who don't know or care get a good, saf
242.
by jjnoakes 4y ago
> a crashed program is a crashed program whether I dereferenced a null pointer or was poking around in a slice with multi-byte Unicode characters in it They aren't the same thing though, that's the point. Dereferencing a NULL p
243.
by jjnoakes 4y ago
Maybe it is and maybe it isn't, but your comment would be a lot more useful to the discussion if you pointed out specific issues and/or ways of doing things differently that you think are better, and why.
244.
by jjnoakes 4y ago
I don't think so. If you know where to look then good content is available, but it doesn't get as widely shared because it isn't as interesting to as many people.
245.
by jjnoakes 4y ago
Is this true? I can almost imagine one puzzle that can create two different spanning trees. Maybe I ought to draw it up to verify. Spanning trees may be required but not sufficient for a unique solution.
246.
by jjnoakes 4y ago
And yet the issues in the article are real and non-trivial. Perhaps you just never hit them, or you have a high tolerance for non-trivial solutions.
247.
by jjnoakes 4y ago
> trivially The article covers quite a few reasons why the way things are done without #embed are not quite as trivial as they seem.
248.
by jjnoakes 4y ago
Did you reply to the right comment? I was looking for clarification on a comment made when discussing running pip directly, as a full path to the pip executable, and not via "python -m pip ...".
249.
by jjnoakes 4y ago
Do you mean there might be a 'pip' command in the local directory that might get called by accident, or do you mean the real python pip command might load a python module from the local directory by accident?
250.
by jjnoakes 4y ago
Are you saying that people created the same level and amount of entertainment we have now, but did it for free before copyright, and only started charging for it after copyright?
251.
by jjnoakes 4y ago
They might "handle it" by deciding that you aren't worth pursuing for the small charge, but that doesn't mean you aren't technically liable for it.
252.
by jjnoakes 4y ago
Whether or not they come after you for what you owe, you still owe it.
253.
by jjnoakes 4y ago
This seems like a straw man to me. If we discovered a free and unlimited source of entertainment then we wouldn't need to charge for that either...
254.
by jjnoakes 4y ago
Be careful. I would think that you are still on the hook for the subscription cost until you cancel, even if you use a virtual card.
255.
by jjnoakes 4y ago
Yes that is true. Untrusted code in general computing environments is basically inevitable.
256.
by jjnoakes 4y ago
> I am unclear on how this relates to untrusted code. If you only run code you trust, then (assuming your trust was placed in it properly) it won't steal anything from you.
257.
by jjnoakes 4y ago
I don't follow. Add far as I know, backslash is the "right" path separator on Windows - it works everywhere, is the documented canonical path separator, and has the fewest compatibility issues with programs. And even if it wa
258.
by jjnoakes 4y ago
Point is, why bring up the non-default alternative path separator that doesn't work universally in Windows when the original comment was correct as is?
259.
by jjnoakes 4y ago
How is using forward slash less unnecessary than using backslash? So much more so that it needed to be pointed out without prompting? I mean backslash is the canonical path separator on Windows, so pointing out that one could use something
260.
by jjnoakes 4y ago
Using one of the correct path separators for the OS isn't necessary? And someone using one of the correct path separators needs a reminder that other path separtors exist? There was no more purpose to that than reminding someone that t
261.
by jjnoakes 4y ago
> What does that observation have to do with anything? About as much as the comment I replied to did, I suppose. Since the paths were right as originally written, and since changing from backslash to forward slash doesn't remove the
262.
by jjnoakes 4y ago
> you can write fast code just as easily as you can write slow code I think some people can do this and some can't. For some, writing slow code is much easier, and their contributions are still valuable. Once the bottlenecks are pro
263.
by jjnoakes 4y ago
Except those are completely different paths on the two systems (even if the path separator was the same).
264.
by jjnoakes 4y ago
They are easier for the end user in certain cases. Putting the library in the system library search path requires elevated privileges (usually). Having your application run from a self-contained directory does not.
265.
by jjnoakes 4y ago
So your code calls a function that is named in a way that indicates it might return a set or an integer (and its parameters make sense in both situations), then you take the return value and add() to it ambiguously, and then you do nothing
266.
by jjnoakes 4y ago
Satisfying the interface was just one of the things the article lists as reasons why breakage is quite implausible. Your example doesn't address the others though. For example, how did you accidentally get an instance of "Set&quot
267.
by jjnoakes 4y ago
How is that "the ease of goroutines but without GC" ?
268.
by jjnoakes 4y ago
I stumbled across namy.ai on HN a while back and found it quite useful. No affiliation, it just worked well for me.
269.
by jjnoakes 4y ago
> E.g x = 5, y = 6, x+y does work in many languages. (Untyped languages, or languages with type inference.) > It is an unambiguous command, and many languages would just do what you say It isn't so unambiguous when you use x = 23
270.
by jjnoakes 4y ago
I think for most people, a rarely used account with a strong password would be very hard to memorize for a long time.

More ›