<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: lomnakkus</title><link>https://news.ycombinator.com/user?id=lomnakkus</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 19 Nov 2026 06:28:38 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=lomnakkus" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by lomnakkus in "How we centralized and structured error handling in Golang"]]></title><description><![CDATA[
<p>In a former life I worked with a codebase that used that style. Let's just say it isn't enough.</p>
]]></description><pubDate>Wed, 18 Dec 2024 12:06:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=42449821</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=42449821</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42449821</guid></item><item><title><![CDATA[New comment by lomnakkus in "How We Centralized and Structured Error Handling in Golang"]]></title><description><![CDATA[
<p>No, but you can easily end up missing some because somebody wrapped them in some sub-type of RuntimeException because they were forced(!) to. This happens all the time because the variance on throws clauses it at odds with the variance of method signatures (well, implementations, really -- see below).<p>A new implementation of a ThingDoer usually needs to do something more/different from a StandardThingDoer... and so may need to throw more types of exceptions. So you end up having to wrap exceptions ... but now they don't get caught by, say, catch(IOException exc). If you're lucky you own the ThingDoer interface, but now you have a different problem: It's only JDBCThingDoer which can throw SQLException, so why does code which only uses a StandardThingDoer (via the ThingDoer interface) need to concern itself with SQLException?<p>Checked exceptions in Java are worse than useless -- they actively make things <i>worse</i> than if there were only unchecked exceptions. (Because they sometimes force the unavoidable wrapping -- which <i>every</i> place where exceptions are caught needs to deal with somehow... which no help from the standard "catch" syntax.)</p>
]]></description><pubDate>Wed, 18 Dec 2024 09:30:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=42449161</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=42449161</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42449161</guid></item><item><title><![CDATA[New comment by lomnakkus in "Stallman Still Heading the GNU Project"]]></title><description><![CDATA[
<p>Parent poster <i>explicitly</i> said "under pressure". What more do you want?</p>
]]></description><pubDate>Fri, 27 Sep 2019 10:07:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=21090189</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=21090189</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=21090189</guid></item><item><title><![CDATA[New comment by lomnakkus in "The ups and downs of porting 50k lines of C++ to Go (2015)"]]></title><description><![CDATA[
<p>> Copying is encouraged. Like I said, having the algorithm there is a good way to make it apparent what the code is actually going to do and the associated cost of the solution.<p>It's also a good way to make bugs proliferate throughout your code base. IIRC bug count correlates well with line count regardless of the language(!).</p>
]]></description><pubDate>Thu, 14 Mar 2019 08:20:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=19387350</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=19387350</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=19387350</guid></item><item><title><![CDATA[New comment by lomnakkus in "Write good git commit messages"]]></title><description><![CDATA[
<p>Present tense -- it's (almost?) always a little shorter, so you can fit more information into the "subject" line.</p>
]]></description><pubDate>Wed, 12 Dec 2018 12:35:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=18663351</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=18663351</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=18663351</guid></item><item><title><![CDATA[New comment by lomnakkus in "C considered dangerous"]]></title><description><![CDATA[
<p>Using min() seems like it could be incredibly dangerous as an "implicit" behavior, not to mention surprising.<p>I'd wager it'd be much better to just specify that abort() gets called in the "overflow" case. (Given that overflow is basically never what you want anyway.)<p>Yeah, it'll crash but at least it won't be suprising/undefined behavior.</p>
]]></description><pubDate>Thu, 30 Aug 2018 09:36:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=17875335</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17875335</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17875335</guid></item><item><title><![CDATA[New comment by lomnakkus in "Whiteboard problems in pure Lambda Calculus (2017)"]]></title><description><![CDATA[
<p>> IMO Lambda calculus should be taught wider in CS programs. It brings useful models, builds (if one likes theory) good background to functional programming paradigms, etc.<p>I'm surprised than anyone thinks this. Unless you're in a very specialized area, it's about as useful as getting practice with writing algorithms using Turing Machines.<p>(Yes, it offers a very different perspective to the usual Von Neumann machine, but learning graph reduction as evalation is just as valuable, if not more.)</p>
]]></description><pubDate>Thu, 23 Aug 2018 20:09:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=17830313</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17830313</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17830313</guid></item><item><title><![CDATA[New comment by lomnakkus in "Jepsen: Dgraph 1.0.2"]]></title><description><![CDATA[
<p>Honestly, it seems like a pretty clear intention to co-opt a term ("commons") which has usually meant "let's share things!" to mean something entirely different. (And shame on them for doing that.)</p>
]]></description><pubDate>Thu, 23 Aug 2018 19:53:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=17830193</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17830193</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17830193</guid></item><item><title><![CDATA[New comment by lomnakkus in "Disable SMT/Hyperthreading in all Intel BIOSes"]]></title><description><![CDATA[
<p>I believe it may be because the email only mentioned Intel explicitly and had a "I won't be buying Intel in future" (paraphrased) comment. However, I personally wouldn't assume that AMDs HT implementation doesn't have similar issues.</p>
]]></description><pubDate>Thu, 23 Aug 2018 19:44:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=17830122</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17830122</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17830122</guid></item><item><title><![CDATA[New comment by lomnakkus in "Craft: A simple Minecraft clone written in C using OpenGL shaders"]]></title><description><![CDATA[
<p>If I were being pithy, I find that when you're doing this type of thing it's more a feeling of "working fun" rather than "working hard".<p>(Of course this means that one is probably not always going to do "production ready" things, but it's for fun, so it doesn't really matter. Sometimes it's fun to just go nuts and sprinkle "undefined"[1] all over the code base and just go from types to implementation as fast as humanly possible.)<p>[1] This is a Haskellism, but basically means any of:<p><pre><code>    assert(false)
    throw new NotImplementedException(...)
    ???
    etc.</code></pre></p>
]]></description><pubDate>Thu, 23 Aug 2018 19:18:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=17829860</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17829860</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17829860</guid></item><item><title><![CDATA[New comment by lomnakkus in "Tiny Plastic Is Everywhere"]]></title><description><![CDATA[
<p>I think you mean the "biosphere" rather than "we". Modern humans have existed anywhere from 50k-200k years. Just to put the time scales into context.<p>EDIT: Just to clarify: As long as disasters happen <i>slowly</i> enough and there are actually local maxima for the species to evolve "into", everything may be fine for "humans"... but those assumptions may be overly optimistic.</p>
]]></description><pubDate>Mon, 20 Aug 2018 23:18:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=17805015</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17805015</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17805015</guid></item><item><title><![CDATA[New comment by lomnakkus in "Liftoff: a new baseline compiler for WebAssembly in V8"]]></title><description><![CDATA[
<p>If the array structure itself were being modified, the "i < a.length" check would have to be done every iteration, but in this case there's no mutation of the array itself, so it's OK to move "a.length" to a constant outside the loop... and from there it's trivial to move bounds checks outside the loop (and from there: eliminate them entirely)</p>
]]></description><pubDate>Mon, 20 Aug 2018 19:24:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=17803027</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17803027</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17803027</guid></item><item><title><![CDATA[New comment by lomnakkus in "Theorists with a Swamp, not a Theory"]]></title><description><![CDATA[
<p>I suppose that's true in some sense, but at least string theorist have done some interesting math?<p>(It may not be math that applies to the real world, but math being math is eternally valid as long as the axioms hold... and sometimes you get surprising applications later on.)</p>
]]></description><pubDate>Tue, 14 Aug 2018 18:00:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=17760288</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17760288</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17760288</guid></item><item><title><![CDATA[New comment by lomnakkus in "Worst Computer Bugs in History: Therac-25 (2017)"]]></title><description><![CDATA[
<p>Damage-by-software usually isn't <i>spectacular</i> (and therefore not likely to get noticed) or not necessarily very directly costly in terms of human lives, but I'd argue it's actually <i>more</i> significant in the long term and in the grand scheme of things. Software rules everything and even slight errors or inefficiencies have absolutely incredible incidental cost.</p>
]]></description><pubDate>Sat, 11 Aug 2018 19:04:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=17741058</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17741058</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17741058</guid></item><item><title><![CDATA[New comment by lomnakkus in "A timesyncd failure and systemd's lack of debugability"]]></title><description><![CDATA[
<p>Um, mix in a second randomly-chosen UUID?<p>My point wasn't so much that I had the perfect solution and that I'd thought of everything. It's that there are much better systems and that we should actually strive to get there.</p>
]]></description><pubDate>Sat, 11 Aug 2018 17:09:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=17740520</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17740520</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17740520</guid></item><item><title><![CDATA[New comment by lomnakkus in "What the interns have wrought, 2018 edition"]]></title><description><![CDATA[
<p>I can second that recommenadation.</p>
]]></description><pubDate>Sat, 11 Aug 2018 17:08:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=17740506</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17740506</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17740506</guid></item><item><title><![CDATA[New comment by lomnakkus in "1/0 = 0"]]></title><description><![CDATA[
<p>Indeed. Java is in fact a sort of worst-of-all-worlds in that it's even possible to catch things that are really unrecoverable errors like StackOverflowException or OutOfMemoryError. To to uninitiated it might not like appear that catching these is <i>that</i> bad, right? In addition to the problems with finally clauses not necessarily running to completion under such circumstances catching these exceptions can cause extremely hard-to-debug deadlocks because object locks won't be released properly.<p>This is an area where the design of Java/JVM is badly screwed up.<p>[1] JVM, really. It's pretty unavoidable on most (all?) JVM languages.</p>
]]></description><pubDate>Sat, 11 Aug 2018 14:18:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=17739758</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17739758</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17739758</guid></item><item><title><![CDATA[New comment by lomnakkus in "A timesyncd failure and systemd's lack of debugability"]]></title><description><![CDATA[
<p>Personally, I think even having to choose a UID at install time <i>or</i> dynamically is a pretty sad indictment of just how broken the user system on Linux (and pretty much every UNIX-like) is. It leads to a huge amount of incidental complexity where there's a much simpler way: User IDs should just be randomly chosen UUIDs -- either generated by upstreams or by the distros. Any metadata attached to the user UID could just be preinstalled for all possible daemons[0] -- and it should be separate from the <i>mutable</i> /etc/passwd stuff.<p>Obviously there's so much inertia in the existing system that it could realistically never happen at this point, but one can dream, right?<p>[0] Kind of like e.g. /etc/services but with UUIDs.</p>
]]></description><pubDate>Thu, 09 Aug 2018 07:59:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=17722371</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17722371</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17722371</guid></item><item><title><![CDATA[New comment by lomnakkus in "Grain: A strongly-typed functional programming language for the modern web"]]></title><description><![CDATA[
<p>Did you read what I said at all?<p>"Order total: undefined" is hugely different from "There was an error -- maybe just leave the page, yeah?".</p>
]]></description><pubDate>Wed, 01 Aug 2018 20:07:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=17666453</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17666453</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17666453</guid></item><item><title><![CDATA[New comment by lomnakkus in "Thieves escape by motorboat after royal jewels heist in Sweden"]]></title><description><![CDATA[
<p>For the hard of hearing, non-native speakers who are used to subtitles from non-dubbed movies, etc. etc. I suppose.<p>I do know that, as a non-native English speaker, I've always appreciated having English subtitles for English-speaking films. It helps immensely if you miss a word, there's a little too much mumbling, or whatever. One of the best (in both ways) examples being the movie Snatch.</p>
]]></description><pubDate>Wed, 01 Aug 2018 19:58:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=17666376</link><dc:creator>lomnakkus</dc:creator><comments>https://news.ycombinator.com/item?id=17666376</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17666376</guid></item></channel></rss>