<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: dasyatidprime</title><link>https://news.ycombinator.com/user?id=dasyatidprime</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 12 Oct 2026 02:38:50 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=dasyatidprime" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by dasyatidprime in "The tilde in your PATH may not be your HOME"]]></title><description><![CDATA[
<p>Aside: in Unicode we now have ″ and ′ for that. Also the triple variant: ‴</p>
]]></description><pubDate>Sun, 11 Oct 2026 21:54:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=50048254</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=50048254</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50048254</guid></item><item><title><![CDATA[New comment by dasyatidprime in "C++ Insights – See your source code with the eyes of a Compiler"]]></title><description><![CDATA[
<p>I agree with an overall thrust of “C++ is overcomplicated and has many moving parts and a lot of implicit stuff happening in the background that makes it difficult to understand”. But I do want to briefly note that Lisp environments have macro expansion steppers for a reason too.</p>
]]></description><pubDate>Sat, 03 Oct 2026 19:04:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=49946812</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49946812</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49946812</guid></item><item><title><![CDATA[New comment by dasyatidprime in "Kids turned low-traffic NPR Spotify comments into a secret group chat"]]></title><description><![CDATA[
<p>I think “indoctrinate” is more likely.</p>
]]></description><pubDate>Mon, 28 Sep 2026 18:15:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=49882112</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49882112</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49882112</guid></item><item><title><![CDATA[New comment by dasyatidprime in "C's Flexible Integer Sizes Were Not a Design Mistake"]]></title><description><![CDATA[
<p>Aren't you talking about how expressions are evaluated in #if there? An expression form that shows up in a macro that is then embedded in normal C code just becomes part of the C code that could potentially get evaluated with C rules at compile time; it's not inherently evaluated at preprocessor time.</p>
]]></description><pubDate>Mon, 28 Sep 2026 15:33:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=49879678</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49879678</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49879678</guid></item><item><title><![CDATA[New comment by dasyatidprime in "Telling a Computer to Do Things"]]></title><description><![CDATA[
<p>if table --warble farble; then :; else table_ec=$?; echo "Garble warble farble! :(" >&2; exit $table_ec; fi<p>Works in dash/bash/zsh at least; not 100% sure whether the behavior of $? on the command in an if test is mandated by POSIX and/or portable. Note that you can't replace the empty then-branch with a negated condition because the negation also eats the return code.<p>Also, <i>absolutely</i> correct propagation is essentially impossible (but usually not useful anyway), because some errors might be unexpected signal exits or inability to find the command in the first place, and those will get punned onto other nonzero exit codes. I forget the exact conventions OTTOMH but generally they're in the high half (≥128).</p>
]]></description><pubDate>Sun, 20 Sep 2026 11:48:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=49774854</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49774854</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49774854</guid></item><item><title><![CDATA[New comment by dasyatidprime in "Dream-RSI: Recursive Self-Improvement through Evolving Worlds"]]></title><description><![CDATA[
<p>They wrote “if and why”.</p>
]]></description><pubDate>Wed, 16 Sep 2026 18:44:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=49731221</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49731221</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49731221</guid></item><item><title><![CDATA[New comment by dasyatidprime in "DaVinci Resolve 21.1"]]></title><description><![CDATA[
<p>If there were definitely no legal encumbrances, surely they'd want to keep shipping the version with the proprietary codecs in, because that would make them a superior option for users who need those? AFAICT someone upstream thought that having the toggle to avoid patent issues was important, which if true nixes the idea that VA-API just gives you an automatic unencumbered route and you don't have to worry about it after that.<p>I'm not really sure what actual claim you're making regarding the relevance of “pro-patent views”, but I might interpret it as something like “Red Hat is more likely to play it safe, whereas less IBM-enculturated distributions are more likely to bet on interpretations that let the users take on the risk”. Which I think is probably true; for instance, <a href="https://www.reddit.com/r/linux/comments/xqn20n/comment/iqbmvi0/" rel="nofollow">https://www.reddit.com/r/linux/comments/xqn20n/comment/iqbmv...</a> describes how other distributions chose differently and moved to re-enable the proprietary codecs by default. (Some of them seem to be based in friendlier jurisdictions, mind. I'm not completely sure where BMD is, and I'm not sure how much it matters given they want to sell worldwide, but their full corporate name resolves most strongly to Australia: <a href="https://opengovau.com/business/30098098287" rel="nofollow">https://opengovau.com/business/30098098287</a> and Australia doesn't seem to exclude software from patentability: <a href="https://www.ipaustralia.gov.au/patents/what-are-patents/what-computer-related-inventions-can-be-patented" rel="nofollow">https://www.ipaustralia.gov.au/patents/what-are-patents/what...</a>)<p>Anyway, if that's what you meant, I don't think that distinction is nearly as applicable to the situation with Resolve. BMD isn't a producer of a Linux distribution containing a broad variety of stuff, where “users happen to do stuff with the open source software we provide that violates some patents” can maybe be waved off as not their responsibility. BMD is very obviously directly operating in the commercially-distributed professional video tooling market, so codec licensing will be something they have to deal with as a keystone part of their business. Adding something to their software to actively enable people to do professional-style encoding for those codecs without the patent licenses would be playing with fire.</p>
]]></description><pubDate>Sat, 12 Sep 2026 05:43:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=49669247</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49669247</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49669247</guid></item><item><title><![CDATA[New comment by dasyatidprime in "DaVinci Resolve 21.1"]]></title><description><![CDATA[
<p>That doesn't sound right to me at all. I'm pretty hazy on the specifics of VA-API, but I wasn't under the impression that the graphics hardware carries 100% of the decode implementation nor had codec licenses attached to it, and this Phoronix article from 2022 describing Fedora having to back off from having accidentally shipped H.264 via VA-API without appropriate licensing seems to be evidence in the direction I expected. <a href="https://www.phoronix.com/news/Fedora-Disable-Bad-VA-API" rel="nofollow">https://www.phoronix.com/news/Fedora-Disable-Bad-VA-API</a></p>
]]></description><pubDate>Fri, 11 Sep 2026 03:35:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=49653252</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49653252</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49653252</guid></item><item><title><![CDATA[New comment by dasyatidprime in "DaVinci Resolve 21.1"]]></title><description><![CDATA[
<p>Do you have any information on how the actual patent licensing is set up for Vivaldi? I wasn't able to find much on it, though I see the note in <a href="https://wiki.archlinux.org/title/Vivaldi" rel="nofollow">https://wiki.archlinux.org/title/Vivaldi</a> that it “automatically downloads” the relevant files, which is at least suggestive that they can't just redistribute the binaries normally. The other closest thing I was able to find was <a href="https://github.com/chromiumembedded/cef/issues/3559" rel="nofollow">https://github.com/chromiumembedded/cef/issues/3559</a> which describes a specific proprietary_codecs option in CEF, which is not quite the same thing but ought in some sense to be related… the way they describe having to set ffmpeg_brand=Chrome normally for that to be available doesn't sound promising?<p>I would be moderately surprised if whatever arrangement is going on there allows full use of the codecs for video editing software and not just for consumer decode of Web resources.</p>
]]></description><pubDate>Thu, 10 Sep 2026 12:58:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=49643001</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49643001</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49643001</guid></item><item><title><![CDATA[New comment by dasyatidprime in "DaVinci Resolve 21.1"]]></title><description><![CDATA[
<p>This is one of the the cases where “the language model won't necessarily respect IP law” is really relevant. Individual users may be able to get away with this because they're too scattershot to sue, and users in some jurisdictions may actually be fine regardless, but broadly, the patent licensing around things like H.264 is not something BMD can afford to ignore. AFAIK the biggest reason Google was pushing WebM in the first place was because they, a huge corporation, were balking at being under the thumb of the MPEG LA!<p>I appreciate that it can be confusing for users that patents can still apply to techniques where implementations exist that are both libre and gratis from a <i>copyright</i> perspective, but this has been an issue for Linux-adjacent software distribution for ages—like, see how Debian used to put certain stuff that was encumbered by patents in the US but not in other jurisdictions in special “non-US” repository sections, that sort of thing. It's not Black Magic's doing that the codec space is like this. I wish people wouldn't make so many mocking assumptions sometimes.</p>
]]></description><pubDate>Wed, 09 Sep 2026 04:26:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=49620984</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49620984</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49620984</guid></item><item><title><![CDATA[New comment by dasyatidprime in "DaVinci Resolve 21.1"]]></title><description><![CDATA[
<p>I'm not an experienced video editor, but I don't think the bulk of video editing involves generating new content on the fly except for narrow cases like adding titles, which is where an AI would easily be able to lean on scripting the existing tooling. There's a ton of grunt work involved in fixing up cuts and figuring out where everything is and so forth.</p>
]]></description><pubDate>Wed, 09 Sep 2026 04:14:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=49620870</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49620870</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49620870</guid></item><item><title><![CDATA[New comment by dasyatidprime in "DaVinci Resolve 21.1"]]></title><description><![CDATA[
<p>And to bring up a likely reason: my impression is that H.264 and AAC still have active <i>patents</i> that apply to the major implementations, and those are not licensed gratis for all uses, and that applies more heavily to the encoding side. Raspberry Pi used to (and might still, I don't know) offer add-on license keys to unlock certain video codec support for what I assume was a similar reason. A lot of individual Linux desktop users just do their small-scale FFmpeg runs under the radar, but commercial software delivery is different.<p>With proprietary operating systems, the commercial entity behind the OS can negotiate for licensing. Some commercially-associated Linux distributions have efforts in similar directions, like Fedora for instance has some special secondary-repo stuff around H.264 support, but that's at minimum much more fragmentary as a target for an application developer concerned with the legalities.</p>
]]></description><pubDate>Wed, 09 Sep 2026 03:51:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=49620698</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49620698</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49620698</guid></item><item><title><![CDATA[New comment by dasyatidprime in "DNS abuse and criminal infrastructure"]]></title><description><![CDATA[
<p>My impression is that one of the social effects of domain names being cheap and easy to get (at least among many vaguely technologist-adjacent cohorts) is that failing to invest in a 2LD for a new thing winds up seen as tacky, sort of an “if you weren't willing to invest enough to put a cover on it then what does that mean for whether it's any good” thing (you could see it as a counterparty good-faith deposit versus attentional costs if you like). In some cases this goes down to the level of individual publications. Additionally the way social technology has wound up around URLs seems to mean that both longer URLs and artificially shortened ones wind up losing secondary reach in unpredictable ways. I'm not that fond of this trend but I can see ways it winds up making sense in context. I don't know how widespread it is.</p>
]]></description><pubDate>Tue, 01 Sep 2026 04:56:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=49518118</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49518118</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49518118</guid></item><item><title><![CDATA[New comment by dasyatidprime in "U.S. State Department pauses immigrant visa applications"]]></title><description><![CDATA[
<p>That doesn't follow. I'm pretty sure they're talking about the effect of nominal wage stickiness: you're not constantly renegotiating your rate, so when there's fluctuations in relative value, it matters what unit the original number is denominated in. Compare with the case of a US expat being paid a steady salary in USD and converting to the local currency to make purchases, if you want an example with a similar mechanic but very different intuitive feel and practicalities.<p>(I'm not sure they're right about the overall effect though.)</p>
]]></description><pubDate>Thu, 27 Aug 2026 00:18:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=49457720</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49457720</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49457720</guid></item><item><title><![CDATA[New comment by dasyatidprime in "Queryable Executables"]]></title><description><![CDATA[
<p>A single SQLite ‘connection’ can be ATTACHed to multiple database files (which appear as separate prefixed schemata, but you can do things like joins across them) and it seems to work properly if some are read-only and some are not!</p>
]]></description><pubDate>Wed, 26 Aug 2026 07:56:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=49445420</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49445420</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49445420</guid></item><item><title><![CDATA[New comment by dasyatidprime in "Show HN: Port Zero – How I learned to stop worrying and love PORT=0"]]></title><description><![CDATA[
<p>For those interested in the history of alternatives to port numbers: Chaosnet[1] in LispM/ITS times used names for describing which service was being requested. On the TCP side, a spec for requesting services by name has existed since 1988: TCPMUX[2], using a short initial handshake after connecting to port 1. Just never caught on AFAIK.<p>[1] <a href="https://chaosnet.net/protocol#application_layer" rel="nofollow">https://chaosnet.net/protocol#application_layer</a>
[2] <a href="https://datatracker.ietf.org/doc/html/rfc1078" rel="nofollow">https://datatracker.ietf.org/doc/html/rfc1078</a></p>
]]></description><pubDate>Mon, 27 Jul 2026 03:49:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=49065014</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49065014</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49065014</guid></item><item><title><![CDATA[New comment by dasyatidprime in "git's –end-of-options Flag"]]></title><description><![CDATA[
<p>TeX uses -- (double hyphen) for producing an en dash and --- (triple hyphen) for an em dash, and that's pretty darn longstanding and well-established. And FWIW, the English writing conventions that <i>I</i> learned use em dashes as punctuation without an adjoining space—like this—but allow en dashes surrounded by spaces as an alternative – like this – so I frequently see spaced double hyphen used as the ASCII equivalent of dash punctuation and interpret it as the latter. I've never personally heard of double hyphen for em specifically, only either as en specifically or as a sort of ambiguous whatever-dash.</p>
]]></description><pubDate>Thu, 23 Jul 2026 06:15:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=49017538</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49017538</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49017538</guid></item><item><title><![CDATA[New comment by dasyatidprime in "Which streaming service was that on again?"]]></title><description><![CDATA[
<p>There <i>is</i> an ISBN URN namespace, but I don't know whether anyone maps it to anything. <a href="https://www.iana.org/assignments/urn-formal/isbn" rel="nofollow">https://www.iana.org/assignments/urn-formal/isbn</a></p>
]]></description><pubDate>Thu, 23 Jul 2026 02:17:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=49016014</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=49016014</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49016014</guid></item><item><title><![CDATA[New comment by dasyatidprime in "The Fedora project grapples with change"]]></title><description><![CDATA[
<p>I don't have experience with the Fedora version specifically, but forum/email bridges tend to run into problems with differing expectations of the medium. This is even more true if it's not clear from the beginning that other users are experiencing the same conversation completely differently. For a viscerally annoying example, imagine someone posting “bump” to a mailing list.</p>
]]></description><pubDate>Tue, 21 Jul 2026 06:59:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=48988988</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=48988988</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48988988</guid></item><item><title><![CDATA[New comment by dasyatidprime in "Just Let Me Write Digits"]]></title><description><![CDATA[
<p>I use a layout with an AZERTY-style shifted digit row for coding (and for everything else). A quick check of one C++ codebase I've been working with shows ~20× as many instances of digit-row symbols as digits (18× for QWERTY digit-row symbols, 27× for those in my layout), though C++ is unusually symbol-heavy. A couple of ECMAScript repositories show 3× or 10×. On some Common Lisp, digit-row symbols are 5× as common as digits for my layout and 22× for QWERTY (almost entirely because QWERTY parentheses are terrible). I don't expect to see a lot of code where numeric literals are <i>more</i> common than type modifiers and operators and such… most of the times numbers are being manipulated in code, they're not being typed in directly as digits but going through comparisons and arithmetic and such, and that's symbols.</p>
]]></description><pubDate>Wed, 15 Jul 2026 06:14:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=48916887</link><dc:creator>dasyatidprime</dc:creator><comments>https://news.ycombinator.com/item?id=48916887</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48916887</guid></item></channel></rss>