<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: tele_ski</title><link>https://news.ycombinator.com/user?id=tele_ski</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 13 Apr 2026 08:34:43 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=tele_ski" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by tele_ski in "Ask HN: What Are You Working On? (April 2026)"]]></title><description><![CDATA[
<p>Very nice, the movement and snapping of the tiles is very nicely done, enjoyed today's puzzle!</p>
]]></description><pubDate>Mon, 13 Apr 2026 00:32:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=47746106</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=47746106</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47746106</guid></item><item><title><![CDATA[New comment by tele_ski in "Zig's New Async I/O"]]></title><description><![CDATA[
<p>This sounds like running an event loop per thread instead of 1 event loop with a backing thread pool. Or am I misunderstanding you?<p>It works great for small tasks but larger tasks block local events and you can get weird latency issues, that was the major tradeoff I ran into when I used it. Works great if your tasks are tiny though, not having the event loop handoff to the worker thread is a good throughput boost. But then we started having latency issues and we introduced larger tasks which would hang the local event loop from getting those events.<p>I think Scylladb works somewhat like this but does message passing to put certain data on certain threads so any thread can handle incoming events but it still moves the request to the pinned thread the data lives on. One thread can get overwhelmed if your data isn't well distributed.</p>
]]></description><pubDate>Fri, 31 Oct 2025 12:36:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=45771347</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=45771347</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45771347</guid></item><item><title><![CDATA[New comment by tele_ski in "Kafka is Fast – I'll use Postgres"]]></title><description><![CDATA[
<p>Been using valkey streams recently and loving it. Took a bit to understand how to to properly use it but now that I've figured it out I'd highly recommend trying it. It's very easy to setup and get going and just works.</p>
]]></description><pubDate>Thu, 30 Oct 2025 00:55:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=45755134</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=45755134</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45755134</guid></item><item><title><![CDATA[New comment by tele_ski in "Io_uring, kTLS and Rust for zero syscall HTTPS server"]]></title><description><![CDATA[
<p>The suggestion is c# class vs struct basically, with explicit globals which are just class with synchronization</p>
]]></description><pubDate>Fri, 22 Aug 2025 15:07:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=44985539</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=44985539</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44985539</guid></item><item><title><![CDATA[New comment by tele_ski in "The Core of Rust"]]></title><description><![CDATA[
<p>reminds me of the classic <a href="https://xkcd.com/927/" rel="nofollow">https://xkcd.com/927/</a> not exactly identical to Bjarne's quote but similar.<p>I'm quite familiar with C++ as well and this just jives so much, each standard is just almost exponentially more complicated than the last, and while there are good changes they don't necessarily fit well with the prior version and its just a mess, I still maintain two OSS libs but I don't use the language anymore.. so its a question of how long I put up with it at this point.<p>Rust is such a breathe of fresh air coming from c++11/14/17/20 but its still a behemoth if you don't know the entire thing, I think this article is pretty spot on with that.</p>
]]></description><pubDate>Fri, 22 Aug 2025 00:43:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=44979909</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=44979909</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44979909</guid></item><item><title><![CDATA[New comment by tele_ski in "Vibe code is legacy code"]]></title><description><![CDATA[
<p><a href="https://danluu.com/everything-is-broken/" rel="nofollow">https://danluu.com/everything-is-broken/</a><p>Always has been and always will be. This article was eye opening to me because I didn't even realize how often I was working around buggy software.</p>
]]></description><pubDate>Wed, 30 Jul 2025 23:14:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=44740657</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=44740657</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44740657</guid></item><item><title><![CDATA[New comment by tele_ski in "Kilauea volcano errupts, lava more than 1k feet high [video]"]]></title><description><![CDATA[
<p>I've always thought that it seems like a silly way to measure it.. Everest also goes to the sea floor, technically.</p>
]]></description><pubDate>Sun, 22 Jun 2025 19:42:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=44349689</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=44349689</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44349689</guid></item><item><title><![CDATA[New comment by tele_ski in "Andrej Karpathy: Software in the era of AI [video]"]]></title><description><![CDATA[
<p>It's an interesting idea, but reactive, and could cause big delays due to bisecting and testing on those regressions. There's the 'old' saying that the sooner the bug is found the cheaper it is to fix, seems weird to intentionally push finding side effect bugs later in the process because faster CI runs. Maybe AI will get there but it seems too aggressive right now to me. But yeah, put the automation slider where you're comfortable.</p>
]]></description><pubDate>Thu, 19 Jun 2025 12:47:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=44318168</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=44318168</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44318168</guid></item><item><title><![CDATA[New comment by tele_ski in "Accumulation of cognitive debt when using an AI assistant for essay writing task"]]></title><description><![CDATA[
<p>Isn't it both on LLMs? The input is your ability to craft a prompt, the output is checking if the prompt worked.</p>
]]></description><pubDate>Tue, 17 Jun 2025 22:32:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=44304700</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=44304700</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44304700</guid></item><item><title><![CDATA[New comment by tele_ski in "Software development topics I've changed my mind on"]]></title><description><![CDATA[
<p>It's a decent idea, but it's weird reviewing code you wrote in saying GitHub, it looks totally different. Imo not a show stopper but a side effect you have to get used to.</p>
]]></description><pubDate>Wed, 05 Feb 2025 15:24:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=42949766</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=42949766</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42949766</guid></item><item><title><![CDATA[New comment by tele_ski in "Hyper – A fast and correct HTTP implementation for Rust"]]></title><description><![CDATA[
<p>We interestingly ran into issues with actix and the AWS lb.  The lb takes some liberty with how it handled connections and actix seems to be "to the spec" so we were seeing a lot of dropped connections.  Placing nginx between the two resolved the issue but it's fairly disappointing that we need that layer when it should be unnecessary overhead.  I'd love to give axum a try if we could find time and see if it behaves better.</p>
]]></description><pubDate>Fri, 12 May 2023 20:51:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=35922228</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=35922228</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35922228</guid></item><item><title><![CDATA[New comment by tele_ski in "Building a Cloud Database from Scratch: Why We Moved from C++ to Rust (2022)"]]></title><description><![CDATA[
<p>I do appreciate that you write tests. I find it's like pulling teeth with most devs to get them to write anything but the most basic of tests.<p>I tend to think more than write code, so usually my first go is reasonably close to what I need.  But there are always edge cases you just never think about.  I'd rather have a strong debugger than a repl imo</p>
]]></description><pubDate>Fri, 10 Feb 2023 15:03:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=34740518</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=34740518</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=34740518</guid></item><item><title><![CDATA[New comment by tele_ski in "The pool of talented C++ developers is running dry"]]></title><description><![CDATA[
<p>I like you're analogy, but I do think there are features of c++ that are big hills as well.  To me it would be SF to LA with some big ups and downs on that long ride.<p>I'm also curious what's difficult about pin in rust?  It basically just disables moving of the object for the lifetime of the pin.</p>
]]></description><pubDate>Wed, 02 Nov 2022 21:04:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=33442891</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=33442891</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=33442891</guid></item><item><title><![CDATA[New comment by tele_ski in "C++20, How Hard Could It Be"]]></title><description><![CDATA[
<p>Yikes, I was so excited for modules back when I was still writing C++17 and a bit of early 20.  Sad they have so many problems with them and/or are just plain not implemented still.  Honestly I'm happy I'ved moved on from the language</p>
]]></description><pubDate>Sun, 25 Sep 2022 18:20:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=32974289</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=32974289</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32974289</guid></item><item><title><![CDATA[New comment by tele_ski in "Show HN: Can you lose at Wordle if you tried?"]]></title><description><![CDATA[
<p>What if you had to earn your undos?  As opposed to starting with N of them in the beginning.<p>What if you scored like wordle but based on undos? 1 undo used, 2 undos used... Up to 5 undos used.  This incentivizes the user to try and not undo if possible.<p>I think the eliminated score method is kind of redundant with the wordled scoring, just make the player guess the 1 word left and be wordled?<p>Really cool and fun idea, we had a great time playing with it and probably will add it to our daily rotation.</p>
]]></description><pubDate>Wed, 01 Jun 2022 01:25:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=31576995</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=31576995</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31576995</guid></item><item><title><![CDATA[New comment by tele_ski in "Announcing Actix Web v4.0"]]></title><description><![CDATA[
<p>I've used both very extensively and while I like the direction c++ is headed, I know a lot of people don't, I couldn't disagree with you more.  Writing reasonably fast rust that doesn't crash is far easier than writing any kind of c++ that doesn't crash.  Copies are a real problem in rust though, they are definitely difficult to avoid without jumping through hoops sometimes but I haven't hit any yet that are a real world show stopper with good upfront design and architecture.  C++ just has too much baggage and footguns to make it truly productive on larger teams osit</p>
]]></description><pubDate>Fri, 25 Feb 2022 22:15:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=30473001</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=30473001</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=30473001</guid></item><item><title><![CDATA[New comment by tele_ski in "Announcing Actix Web v4.0"]]></title><description><![CDATA[
<p>Anecdotal but my company is using it for a new project and we just hit production about a month ago.  So far it's been great with 10+ million requests handled per day.  Looking forward to upgrading to 4.0</p>
]]></description><pubDate>Fri, 25 Feb 2022 22:08:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=30472948</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=30472948</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=30472948</guid></item><item><title><![CDATA[New comment by tele_ski in "Things that used to be hard and are now easy"]]></title><description><![CDATA[
<p>I think you're point is correct around rust in that writing rust is harder than writing C due to the constraints the compiler places on what you can do.  So far I'm happy with this tradeoff because I've had some very gnarly C concurrency bugs that took weeks to understand and debug.  If the rustc compiler can point out that I'm doing something stupid and save me two weeks for a bit of pain immediately I'm all about it.</p>
]]></description><pubDate>Sun, 20 Feb 2022 17:55:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=30407594</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=30407594</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=30407594</guid></item><item><title><![CDATA[New comment by tele_ski in "Things that used to be hard and are now easy"]]></title><description><![CDATA[
<p>I've been on teams that haven't used docker for dev envs and teams that do in the last 5~ years.  The teams that used docker were significantly more productive since each dev env was a replica and forced the team to maintain a common env.  The dev env drift without it is huge and causes so many "it works on my machine".  I can see a one man show or maybe two not needing a docker dev env but any sizable team IMO it is absolutely required now.  You're absolutely right that it is a hoop to jump through, but its a hoop I find very necessary.</p>
]]></description><pubDate>Sun, 20 Feb 2022 17:42:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=30407462</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=30407462</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=30407462</guid></item><item><title><![CDATA[New comment by tele_ski in "Monoio – A thread-per-core Rust async runtime with io_uring"]]></title><description><![CDATA[
<p>As much as I like deving only on Linux, this I'm pretty sure would be awful for rust's continued adoption.</p>
]]></description><pubDate>Thu, 09 Dec 2021 15:59:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=29498911</link><dc:creator>tele_ski</dc:creator><comments>https://news.ycombinator.com/item?id=29498911</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29498911</guid></item></channel></rss>