<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: lukemerrick</title><link>https://news.ycombinator.com/user?id=lukemerrick</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 30 May 2026 20:56:32 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=lukemerrick" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by lukemerrick in "Show HN: Tiny-vLLM – high performance LLM inference engine in C++ and CUDA"]]></title><description><![CDATA[
<p>I am not super familiar with C and CUDA, so I read solely for the README and enjoyed it supremely. The blend of cheerful walking through instructive examples and your philosophical takes on how to approach the exercise to get the most out of it put me in a great mood. You captured that special upbeat attitude that comes about when you're doing something as well as you can just because it's so legitimately interesting to you.</p>
]]></description><pubDate>Sat, 30 May 2026 15:25:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=48337238</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=48337238</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48337238</guid></item><item><title><![CDATA[Are We Entering a First-Order Optimizer Renaissance?]]></title><description><![CDATA[
<p>Article URL: <a href="https://lukemerrick.com/posts/first_order_optimization.html">https://lukemerrick.com/posts/first_order_optimization.html</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44566313">https://news.ycombinator.com/item?id=44566313</a></p>
<p>Points: 4</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 14 Jul 2025 23:01:37 +0000</pubDate><link>https://lukemerrick.com/posts/first_order_optimization.html</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=44566313</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44566313</guid></item><item><title><![CDATA[New comment by lukemerrick in "Sharing new research, models, and datasets from Meta FAIR"]]></title><description><![CDATA[
<p>Meta is a very large organization, and I'm willing to believe that a good chunk of Meta FAIR (the lab releasing all of this stuff) truly do care about innovations for advancing AI safety and are doing great work along these lines. I'm not disagreeing with your point about the company being led by its financial incentives as a unit, but let's also allow ourselves permission to celebrate this work by this group of people.</p>
]]></description><pubDate>Fri, 13 Dec 2024 23:07:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=42413144</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=42413144</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42413144</guid></item><item><title><![CDATA[New comment by lukemerrick in "Cosmopolitan v3.5"]]></title><description><![CDATA[
<p>Looks like there is both an ARM and x86 version according to the docs. Probably need two different binaries, but you still get cross-OS for each architecture.</p>
]]></description><pubDate>Mon, 24 Jun 2024 07:09:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=40773233</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=40773233</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40773233</guid></item><item><title><![CDATA[New comment by lukemerrick in "Show HN: Huewords, a Word and Logic Puzzle"]]></title><description><![CDATA[
<p>Just spent two hours on this. Would happily spend the time again (and probably will soon!). Awesome work.</p>
]]></description><pubDate>Wed, 05 Jun 2024 05:40:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=40581709</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=40581709</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40581709</guid></item><item><title><![CDATA[New comment by lukemerrick in "New attention mechanisms that outperform standard multi-head attention"]]></title><description><![CDATA[
<p>Just skimmed so far and didn't see any reference to the Simplified Transformer block of <a href="https://arxiv.org/abs/2311.01906" rel="nofollow">https://arxiv.org/abs/2311.01906</a> (and it seems they also left out grouped query attention, too, as pointed out by another comment).<p>While lazy me wants them to explain how their approach compares to these approaches, it looks like their exposition is pretty clear (quite nice for a preprint!) and I guess I'll just have to actually read the paper for real to see for myself.<p>Given how well I've seen Simplified Transformer blocks work in my own playground experiments, I would not at all be surprised if other related tweaks work out well even on larger scale models. I wish some of the other commenters here had a bit more curiosity and/or empathy for these two authors who did a fine job coming up with and initially testing out some worthwhile ideas.</p>
]]></description><pubDate>Thu, 30 May 2024 15:16:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=40524740</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=40524740</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40524740</guid></item><item><title><![CDATA[Startup Rivos Says Apple Intimidates Workers Who ‘Dare to Leave’]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.bloomberg.com/news/articles/2023-09-23/startup-rivos-says-apple-intimidates-workers-who-dare-to-leave">https://www.bloomberg.com/news/articles/2023-09-23/startup-rivos-says-apple-intimidates-workers-who-dare-to-leave</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=37638627">https://news.ycombinator.com/item?id=37638627</a></p>
<p>Points: 32</p>
<p># Comments: 8</p>
]]></description><pubDate>Mon, 25 Sep 2023 01:07:08 +0000</pubDate><link>https://www.bloomberg.com/news/articles/2023-09-23/startup-rivos-says-apple-intimidates-workers-who-dare-to-leave</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=37638627</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37638627</guid></item><item><title><![CDATA[New comment by lukemerrick in "The Pile: An 800GB dataset of diverse text for language modeling (2020)"]]></title><description><![CDATA[
<p>Related to the idea of "no one trains on data they own, they shouldn't own the resulting model": since big public datasets like The Pile have CC-SA items in them, is anyone considering bringing the argument that model weights are derivative work that must be "shared alike"?</p>
]]></description><pubDate>Wed, 12 Jul 2023 01:58:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=36689613</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36689613</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36689613</guid></item><item><title><![CDATA[New comment by lukemerrick in "JupyterLab 4.0"]]></title><description><![CDATA[
<p>As you guessed, the history tracking is one of the killer features. Imagine it being super easy to edit the history of a REPL session (delete, reorder, merge, and edit contents of each command) and rerun... That's a notebook! Notebooks also allow for markdown input and rich HTML output (which is killer for plotting) making it possible to polish your REPL history into a document you'd actually want to share with a colleague to explain something like a data analysis workflow.<p>I actually started in notebooks and then learned to love the REPL as a simplified "scratchpad notebook." I'd say in many ways notebooks are an improvement that cater heavily to REPL-lovers, but that for some quick tasks, the extra complexity isn't always worth it.</p>
]]></description><pubDate>Fri, 16 Jun 2023 14:34:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=36357193</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36357193</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36357193</guid></item><item><title><![CDATA[File from Microsoft Xandr shows the many ways advertisers label people]]></title><description><![CDATA[
<p>Article URL: <a href="https://themarkup.org/privacy/2023/06/08/from-heavy-purchasers-of-pregnancy-tests-to-the-depression-prone-we-found-650000-ways-advertisers-label-you">https://themarkup.org/privacy/2023/06/08/from-heavy-purchasers-of-pregnancy-tests-to-the-depression-prone-we-found-650000-ways-advertisers-label-you</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=36267897">https://news.ycombinator.com/item?id=36267897</a></p>
<p>Points: 7</p>
<p># Comments: 2</p>
]]></description><pubDate>Sat, 10 Jun 2023 05:31:48 +0000</pubDate><link>https://themarkup.org/privacy/2023/06/08/from-heavy-purchasers-of-pregnancy-tests-to-the-depression-prone-we-found-650000-ways-advertisers-label-you</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36267897</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36267897</guid></item><item><title><![CDATA[New comment by lukemerrick in "Building a Lox Interpreter in Julia"]]></title><description><![CDATA[
<p>Thank you for the tip! Getting to implement a different language from Lox feels like a nice way to cut down on the tedium.</p>
]]></description><pubDate>Sun, 04 Jun 2023 07:47:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=36183822</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36183822</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36183822</guid></item><item><title><![CDATA[New comment by lukemerrick in "Building a Lox Interpreter in Julia"]]></title><description><![CDATA[
<p>Wow, the whole concept of a peephole optimizer is a bit mind blowing to me. I'm appreciating all the reasons to power through to writing a bytecode VM as the next step.<p>I'm not sure how far down the compiler I actually will enjoy going vs. exploring ideas around type systems, linters, etc. up near the AST level, but if I do venture down this advice will certainly come in handy!</p>
]]></description><pubDate>Sun, 04 Jun 2023 07:44:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=36183808</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36183808</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36183808</guid></item><item><title><![CDATA[New comment by lukemerrick in "Building a Lox Interpreter in Julia"]]></title><description><![CDATA[
<p>Thank you for the suggestions! I was actually just searching about MLIR today after reading some Julia language community discussions on the new Mojo language that uses MLIR.</p>
]]></description><pubDate>Sun, 04 Jun 2023 07:34:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=36183777</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36183777</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36183777</guid></item><item><title><![CDATA[New comment by lukemerrick in "Building a Lox Interpreter in Julia"]]></title><description><![CDATA[
<p>I actually played with Unityper.jl and SumTypes.jl, but my conclusion was that if I was going to depart from dispatch on Julia types in my code, I might as well just stick to an untyped tree, since either way I'd have to have a single `evaluate` function for interpreting any kind of node.<p>Reconsidering now, it seems that there might be benefits beyond type dispatch to having a typed syntax tree, so maybe I'll give that a shot as a next step!</p>
]]></description><pubDate>Sun, 04 Jun 2023 07:25:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=36183748</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36183748</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36183748</guid></item><item><title><![CDATA[New comment by lukemerrick in "Building a Lox Interpreter in Julia"]]></title><description><![CDATA[
<p>In general, if you keep the source code positions of every nontrivial token, and you keep the raw source code, then yeah you can print out those pretty specific point error messages regardless of whether you keep your trees lossless. Also, if you want to include filename in your messages (perhaps because unlike Lox your language supports imports), then you'll need more than just lossless trees to store the necessary information.<p>I'm not sure exactly how Rust and rust-analyzer keep track of the info necessary to their excellent error messages and diagnostics, but I wouldn't be surprised if pinpoint messages were not the primary motivation for rust-analyzer to do lossless parsing.</p>
]]></description><pubDate>Sat, 03 Jun 2023 16:53:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=36178230</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36178230</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36178230</guid></item><item><title><![CDATA[New comment by lukemerrick in "Building a Lox Interpreter in Julia"]]></title><description><![CDATA[
<p>Disclaimer: I wrote this blog post. If this were an "Ask HN" post, though, the question would be "What next after reading Crafting Interpreters?" I have only done the tree-walk interpreter half of the book, but I'm already excited to move beyond Lox, and I'm curious to hear what others have done in this situation.</p>
]]></description><pubDate>Fri, 02 Jun 2023 04:40:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=36161130</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36161130</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36161130</guid></item><item><title><![CDATA[Building a Lox Interpreter in Julia]]></title><description><![CDATA[
<p>Article URL: <a href="https://lukemerrick.com/posts/intro_to_julox.html">https://lukemerrick.com/posts/intro_to_julox.html</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=36161129">https://news.ycombinator.com/item?id=36161129</a></p>
<p>Points: 74</p>
<p># Comments: 24</p>
]]></description><pubDate>Fri, 02 Jun 2023 04:40:48 +0000</pubDate><link>https://lukemerrick.com/posts/intro_to_julox.html</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=36161129</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36161129</guid></item><item><title><![CDATA[New comment by lukemerrick in "Show HN: Yaksha Programming Language"]]></title><description><![CDATA[
<p>I'm late to the party, but I want to say thank you for sharing this. It's inspiring to look at how much you've built and (hopefully) enjoyed the process of building! I'm loving everything -- your site, your language design, your docs, your builtin libraries, your dev tools. Beyond impressive. People like you are the ones who make HN one of my best places on the internet.<p>For context on where I'm coming from, about two weeks ago I picked up Crafting Interpreters [1] for fun. I'm finding your clear-yet-concise Compiler internals [2] to be particularly compelling reading, and jumping back and forth between those "how this all works" docs and the live example of this language you <i>actually</i> built do a WASM-compiled tree-blowing-in-the-wind animation is just... just wow. So freaking cool!<p>I also enjoyed reading the comment thread that inspired you to start on Yaksha and seeing how this project has a wholesome start as inspiration-by-programming-hero. I hope you recognize that a few years later you've now ascended from inspiree to inspirer. I also hope you're still having tons of fun building out Yaksha!<p>[1] <a href="https://www.craftinginterpreters.com/" rel="nofollow">https://www.craftinginterpreters.com/</a><p>[2] <a href="https://yakshalang.github.io/documentation.html#compiler-internals" rel="nofollow">https://yakshalang.github.io/documentation.html#compiler-int...</a></p>
]]></description><pubDate>Fri, 24 Mar 2023 15:17:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=35290171</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=35290171</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35290171</guid></item><item><title><![CDATA[New comment by lukemerrick in "Optimizing utility-scale battery storage dispatch"]]></title><description><![CDATA[
<p>Disclaimer: I'm the author.<p>I was torn whether to share my own post, but I figured the HN crowd might include a few others who will also really geek out about this topic and appreciate it. It's mathematical optimization and forecasting used to guide giant batteries hooked up to the electrical grid, after all.<p>There is some accompanying code I got to share publicly, too, if you want to run this yourself [1]. While I'm at it, I'll also mention some papers for anyone who wants a true deep dive [2, 3].<p>[1] <a href="https://gist.github.com/lukemerrick/4e1f9921a19ec97f7b94990953c2e799" rel="nofollow">https://gist.github.com/lukemerrick/4e1f9921a19ec97f7b949909...</a><p>[2] Linear Programming for battery optimization -- <a href="https://www.osti.gov/servlets/purl/1244909" rel="nofollow">https://www.osti.gov/servlets/purl/1244909</a><p>[3] Mixed-Integer Linear Programming for battery optimization [PDF] -- <a href="https://www.sandia.gov/ess-ssl/wp-content/uploads/2018/08/2017_EESAT_Proceeding_Tong.pdf" rel="nofollow">https://www.sandia.gov/ess-ssl/wp-content/uploads/2018/08/20...</a></p>
]]></description><pubDate>Thu, 06 Oct 2022 22:28:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=33114950</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=33114950</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=33114950</guid></item><item><title><![CDATA[Optimizing utility-scale battery storage dispatch]]></title><description><![CDATA[
<p>Article URL: <a href="https://medium.com/@lukemerrick_/df823572b59e">https://medium.com/@lukemerrick_/df823572b59e</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=33114949">https://news.ycombinator.com/item?id=33114949</a></p>
<p>Points: 1</p>
<p># Comments: 1</p>
]]></description><pubDate>Thu, 06 Oct 2022 22:28:33 +0000</pubDate><link>https://medium.com/@lukemerrick_/df823572b59e</link><dc:creator>lukemerrick</dc:creator><comments>https://news.ycombinator.com/item?id=33114949</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=33114949</guid></item></channel></rss>