<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: Rochus</title><link>https://news.ycombinator.com/user?id=Rochus</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 31 Aug 2026 09:39:54 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=Rochus" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by Rochus in "Come for ENIAC, Stay for UNIVAC and Skeduflo"]]></title><description><![CDATA[
<p>Cool. So at least the work-hours haven't changed much since ;-)</p>
]]></description><pubDate>Sun, 30 Aug 2026 15:59:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=49499850</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49499850</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49499850</guid></item><item><title><![CDATA[New comment by Rochus in "Show HN: ShevtoneAudio Orchestrator – Turning MIDI into Full Orchestration"]]></title><description><![CDATA[
<p>Looks interesting. But I couldn't find any practical examples or tutorials so far. Any hints? Is there a description somewhere how it is implemented, i.e. what technical concepts are used to analyze the Midi, understand the music well enough, and then invent a credible orchestration?</p>
]]></description><pubDate>Sun, 30 Aug 2026 12:07:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=49497964</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49497964</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49497964</guid></item><item><title><![CDATA[New comment by Rochus in "Bootstrappable Builds: How and Why"]]></title><description><![CDATA[
<p>> Rust is an enormously more complex language<p>I have no doubt that a Rust compiler can be implemented in C. But it's a different project to write one in C from start than trying to migrate an existing C++14 based project to C. The former is likely "easier". An alternative approach could be to migrate the C++14 code back to C++98 and get rid of the exceptions, which makes it transpilable to C (using the cfront approach). Though the result might not be maintainable C, but still C.<p>EDIT: if you manage to migrate it back to a sufficiently moderate C++11 subset, or even C++98, you could use GCC 4.7.4 to compile it, which itself is written in C.</p>
]]></description><pubDate>Fri, 28 Aug 2026 15:35:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=49480105</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49480105</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49480105</guid></item><item><title><![CDATA[New comment by Rochus in "Come for ENIAC, Stay for UNIVAC and Skeduflo"]]></title><description><![CDATA[
<p>That's fascinating. I spent significant time with early MUMPS and the machines of the time (<a href="https://github.com/rochus-keller/mumps/" rel="nofollow">https://github.com/rochus-keller/mumps/</a>) which had a comparable amount of memory.<p>Was your whole insurance application only assembler, i.e. no COBOL or RPG at all?</p>
]]></description><pubDate>Fri, 28 Aug 2026 14:58:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=49479536</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49479536</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49479536</guid></item><item><title><![CDATA[New comment by Rochus in "Bootstrappable Builds: How and Why"]]></title><description><![CDATA[
<p>Sounds pretty difficult (if not impossible, see cfront 4.0) to translate C++ code to C89. You have to keep track of all constructors and destructors and their progress along the body yourself, and I assume it must be fit for exceptions as well?</p>
]]></description><pubDate>Fri, 28 Aug 2026 14:51:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=49479398</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49479398</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49479398</guid></item><item><title><![CDATA[New comment by Rochus in "Bootstrappable Builds: How and Why"]]></title><description><![CDATA[
<p>Well, it might not be <i>your</i> actual problem. But there are always people who look a little further beyond the horizon.</p>
]]></description><pubDate>Fri, 28 Aug 2026 14:26:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=49478999</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49478999</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49478999</guid></item><item><title><![CDATA[New comment by Rochus in "Bootstrappable Builds: How and Why"]]></title><description><![CDATA[
<p>This project is not pointless at all. It's not about "reproducible builds", but about building a full present system from "first principles". It would be a way out of a significant dependability problem barely anyone today is aware of.</p>
]]></description><pubDate>Fri, 28 Aug 2026 12:06:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=49477338</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49477338</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49477338</guid></item><item><title><![CDATA[New comment by Rochus in "Bootstrappable Builds: How and Why"]]></title><description><![CDATA[
<p>> If anyone has ideas/cheaper ways to run it I would like to know<p>GCC 4.7.4 was the last version of GCC fully written in C, with full C++98/03 support and a decent subset of C++11. As far as I know it is used by the bootstrap project presented in the article.</p>
]]></description><pubDate>Fri, 28 Aug 2026 12:02:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=49477298</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49477298</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49477298</guid></item><item><title><![CDATA[New comment by Rochus in "Come for ENIAC, Stay for UNIVAC and Skeduflo"]]></title><description><![CDATA[
<p>Thanks for these interesting insights. It's hard to imagine today how scarce computers actually were at that time. The assembler was for the System/360?</p>
]]></description><pubDate>Thu, 27 Aug 2026 21:24:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=49471465</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49471465</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49471465</guid></item><item><title><![CDATA[New comment by Rochus in "DHH: Future of Programming – Lex Fridman Podcast #501 [YouTube, 5 Hours]"]]></title><description><![CDATA[
<p>This is a very interesting talk. I'm amazed to hear how good this AI stuff already is (if I take DHH's statements at face value).</p>
]]></description><pubDate>Thu, 27 Aug 2026 12:26:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=49463678</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49463678</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49463678</guid></item><item><title><![CDATA[New comment by Rochus in "ISO/IEC DIS 26791-1 – The RISC-V instruction set manual"]]></title><description><![CDATA[
<p>Well, since everyone already has the specs, they should release it as a free standard.</p>
]]></description><pubDate>Mon, 24 Aug 2026 21:56:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=49426375</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49426375</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49426375</guid></item><item><title><![CDATA[New comment by Rochus in "MIDI Survivor: play music to defeat monsters"]]></title><description><![CDATA[
<p>"Buy now - 10$"</p>
]]></description><pubDate>Mon, 24 Aug 2026 21:40:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=49426219</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49426219</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49426219</guid></item><item><title><![CDATA[New comment by Rochus in "Show HN: A Modern GUI Library for Ada: CSS Styling, XML UI, SDL3"]]></title><description><![CDATA[
<p>Cool project. Good idea to use SDL3; it brings along much more than SDL2 where you had to use a lot of other libraries to become platform independent with all features. The disadvantage might be that SDL3 itself (as SLD2) is pretty big. Ada got a bit out of fashion (unfortunately) but it's still an impressive, excellent language. Still an interesting choice. Maybe you can give more information about your choice and plans with the GUI library.</p>
]]></description><pubDate>Mon, 24 Aug 2026 21:38:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=49426203</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49426203</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49426203</guid></item><item><title><![CDATA[New comment by Rochus in "The Two Factions of C++ (2024)"]]></title><description><![CDATA[
<p>Have a look at boost::movelib::unique_ptr<T> which works well with C++98/03.</p>
]]></description><pubDate>Sat, 22 Aug 2026 02:29:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=49396046</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49396046</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49396046</guid></item><item><title><![CDATA[New comment by Rochus in "Swiss tourist sentenced to year in jail for insulting Bali sacred Day of Silence"]]></title><description><![CDATA[
<p>I guess people will avoid this country/island alltogether when these such sentences get commonly known. Maybe that was the intention, i.e. to reduce overcrowding due to tourism?</p>
]]></description><pubDate>Fri, 21 Aug 2026 15:09:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=49389307</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49389307</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49389307</guid></item><item><title><![CDATA[New comment by Rochus in "Pitfalls of Benchmarking on Modern Systems"]]></title><description><![CDATA[
<p>Interesting. Since I have the T480 I have to switch off variable speed when doing benchmarks and switch off all but one core.</p>
]]></description><pubDate>Fri, 21 Aug 2026 14:52:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=49389053</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49389053</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49389053</guid></item><item><title><![CDATA[New comment by Rochus in "The Two Factions of C++ (2024)"]]></title><description><![CDATA[
<p>Have a look at Qt implicit sharing. There is/was also a Boost library which could do most of it long before c++11.</p>
]]></description><pubDate>Wed, 19 Aug 2026 10:57:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=49359809</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49359809</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49359809</guid></item><item><title><![CDATA[New comment by Rochus in "The Two Factions of C++ (2024)"]]></title><description><![CDATA[
<p>For all of my projects it is good enough. C++11 onwards has a few advantages, but I don't need them. Moving ownership between containers to avoid allocations was possible with the standard library even before C++11, and Qt offered "implicit sharing" which has a similar effect without syntax changes and incompatibilities. Even with my C++11 projects (e.g. <a href="https://github.com/rochus-keller/eigen/" rel="nofollow">https://github.com/rochus-keller/eigen/</a>) I had to take care still in 2024 which feature not to use on MSVC because it didn't work or behaved differently. I never have any ownership issues and I implement large compiler projects with different AST and IR layers. All my projects still compile with <a href="https://github.com/rochus-keller/leanqt/" rel="nofollow">https://github.com/rochus-keller/leanqt/</a> on all platforms. I would never trade a tiny language advantage with a whole world of dependability issues. One day I will revive and refactor GCC 4.7 to get a cross-platform C++98 with parts of 11 compiler just written in C, then latest all of my software is buildable "from first principles".<p>PS: it's funny I wrote my comment three days (and not an hour) ago.</p>
]]></description><pubDate>Wed, 19 Aug 2026 09:35:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=49359149</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49359149</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49359149</guid></item><item><title><![CDATA[New comment by Rochus in "The Two Factions of C++ (2024)"]]></title><description><![CDATA[
<p>Very interesting summary of facts and quotations with conclusions. I would say there are even more camps than the two mentioned. Personally I think C++98 and Qt5 just worked and were good enough for all purposes, and C++ since has become an ever moving target with a lot of incompatibilities between compilers. Chasing for the ever latest version of the language and compilers is very expensive and enervating. I prefer how they solved this e.g. in the Ada community; they take their time for the release a new standard version, and until then, most compiler vendors have already updated their products and there was relevant experience with the new features long before the new standard was passed. In computer science, it seems to be a law of nature to keep "improving" good things until they become unusable and people walk away. In C++ I did so; I have a few C++11 code bases (some back ported from newer versions), but most are C++98/03; I even made a fork of Qt5 (LeanQt) with my own build system (BUSY) which is less work to maintain than continuously chasing new compiler/tool incompatibilities among platforms.</p>
]]></description><pubDate>Sun, 16 Aug 2026 13:58:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=49320142</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49320142</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49320142</guid></item><item><title><![CDATA[New comment by Rochus in "CARA – a readiness assessment for Microsoft 365 Copilot adoption"]]></title><description><![CDATA[
<p>Welcome to the "CARA club" (<a href="http://www.cara.nmr.ch/doku.php/Home" rel="nofollow">http://www.cara.nmr.ch/doku.php/Home</a>). Obviously a good acronym ;-)</p>
]]></description><pubDate>Sun, 16 Aug 2026 13:17:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=49319785</link><dc:creator>Rochus</dc:creator><comments>https://news.ycombinator.com/item?id=49319785</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49319785</guid></item></channel></rss>