pwdisswordfish8

13 ms·

61.
by pwdisswordfish8 5y ago
https://archive.ph/obOb2
62.
by pwdisswordfish8 5y ago
WTF is a slash command?
63.
by pwdisswordfish8 5y ago
It’s almost as if Doom were a go-to example to demonstrate running arbitrary code on obscure devices. https://i.reddit.com/r/itrunsdoom
64.
by pwdisswordfish8 5y ago
I have never used Discord, never mind writing bots for it, so most of these explanations are pretty incomprehensible to me.
65.
by pwdisswordfish8 5y ago
Try StackOverflow. This sort of question doesn't really fit the Ask HN format.
66.
by pwdisswordfish8 5y ago
Against forking an inactive project? Why?
67.
by pwdisswordfish8 5y ago
> written in a garbage-collected language where the original implementation is written in C > ‘tiny’
68.
by pwdisswordfish8 5y ago
Surprising how few people mention an email addressed to oneself, particularly for those concerned about getting their thoughts out quickly. (Maybe a side effect of how many people use Gmail and it being slow and clunky?) Not saying it&#x2
69.
by pwdisswordfish8 5y ago
I prefer <img> elements never to animate at all, regardless of format. Animations should use <video>.
70.
by pwdisswordfish8 5y ago
I mean, just look at < https://github.com/ytdl-org/youtube-dl/issues/29809 >. They don’t even bother removing spam.
71.
by pwdisswordfish8 5y ago
Or use that language’s native HTTP client and cut out the shell middleman.
72.
by pwdisswordfish8 5y ago
Indeed, this has been years in the making. Maintainer activity has been slowly dwindling while would-be contributors were driven away by the maintainers’ lack of communication and abrasiveness. I myself have had pull requests languishing th
73.
by pwdisswordfish8 5y ago
Non-cookiewalled: https://text.npr.org/1030442282
74.
by pwdisswordfish8 5y ago
> I suppose .onion was not fine either, till cca 2015 when it got special-use status? You are correct.
75.
by pwdisswordfish8 5y ago
> The RFC may expire, but it quotes the ISO3166 This is not the argument you think that it is. > zz is safe for personal use. Those guidelines will not change Right. Safe for personal use within the range of uses for ISO 3166—guarant
76.
by pwdisswordfish8 5y ago
HN's capacity for intellectual dishonesty knows no bounds. That's a dishonest attempt to bankrupt the term "single-pass compiler", and remove its value to communicate something meaningful. By that token, the Amsterdam
77.
by pwdisswordfish8 5y ago
When citing collective written works (like conference paper collections), the editors’ names are usually listed. I don’t see why not do the same here: cite the maintainers’ names when citing the whole, and also specific authors when citing
78.
by pwdisswordfish8 5y ago
s/better/worse/
79.
by pwdisswordfish8 5y ago
Don’t worry, their government is so much in shambles they aren’t even going to notice
80.
by pwdisswordfish8 5y ago
Immigration and Customs Enforcement, made with <3 by Govly uwu
81.
by pwdisswordfish8 5y ago
What is House of Twitch?
82.
by pwdisswordfish8 5y ago
Single-pass to me also implies a code generator that writes the object file directly, rather than compiling to C or assembly (or some other language) as an intermediate format. But words don't mean anything anymore, so long as people
83.
by pwdisswordfish8 5y ago
Not exactly. The RFC that would make it safe is draft status, and the draft is set to expire in <2 months and does not come off as particularly confident itself: https://tools.ietf.org/id/draft-ietf-dnsop-private-us
84.
by pwdisswordfish8 5y ago
Have you read Knuth’s article? It is a bit more nuanced than a wholesale defence of GOTO in preference to structured programming. It surveys various control flow structures that are not easily expressed in terms of IF conditions and WHILE
85.
by pwdisswordfish8 5y ago
> We do not recommend use of unregistered top-level > domains at all, but should network operators decide to do this, the > following top-level domains have been used on private internal > networks without the problems cau
86.
by pwdisswordfish8 5y ago
> Do not use undelegated domain names like .lan OpenWRT: *glances aside nervously*
87.
by pwdisswordfish8 5y ago
It’s supposed to be resolved to a loopback address. Chrome forces it to 127.0.0.1, because Google knows better than you. Obviously. < https://bugs.chromium.org/p/chromium/issues/detail?id=489973 >
88.
by pwdisswordfish8 5y ago
Delegating .dev was fine. Sick of hearing about this. As the meme goes, "well, well, well, if it isn't the consequences of my own actions." Everyone who got burned by .dev got what they deserve and needs to grow up already
89.
by pwdisswordfish8 5y ago
"When you fail... pretend you had... a different goal... all along." Okay, got it.
90.
by pwdisswordfish8 5y ago
C++ with new(std::nothrow)?

More ›