Engineered Addictions
658 by echollama | 408 comments on Hacker News.
Sunday, June 29, 2025
Saturday, June 28, 2025
Friday, June 27, 2025
Show HN: I'm an airline pilot – I built interactive graphs/globes of my flights
Show HN: I'm an airline pilot – I built interactive graphs/globes of my flights
674 by jamesharding | 118 comments on Hacker News.
Hey HN! Pilots everywhere are required to keep a logbook of all their flying hours, aircraft, airports, and so on. Since I track everything digitally (some people still just use paper logbooks!), I put together some data visualizations and a few 3D globes to show my flying history. This globe is probably my favourite so far: https://ift.tt/H9NjFzf If you’ve got ideas for other graphs or ways to show this kind of data, I’d love to hear them!
674 by jamesharding | 118 comments on Hacker News.
Hey HN! Pilots everywhere are required to keep a logbook of all their flying hours, aircraft, airports, and so on. Since I track everything digitally (some people still just use paper logbooks!), I put together some data visualizations and a few 3D globes to show my flying history. This globe is probably my favourite so far: https://ift.tt/H9NjFzf If you’ve got ideas for other graphs or ways to show this kind of data, I’d love to hear them!
Thursday, June 26, 2025
Wednesday, June 25, 2025
Tuesday, June 24, 2025
Monday, June 23, 2025
Sunday, June 22, 2025
Saturday, June 21, 2025
Thursday, June 19, 2025
Wednesday, June 18, 2025
Tuesday, June 17, 2025
Saturday, June 14, 2025
Friday, June 13, 2025
Thursday, June 12, 2025
Wednesday, June 11, 2025
Tuesday, June 10, 2025
Monday, June 9, 2025
Tell HN: Help restore the tax deduction for software dev in the US (Section 174)
Tell HN: Help restore the tax deduction for software dev in the US (Section 174)
754 by dang | 310 comments on Hacker News.
Companies building software in the US were hit hard a few years ago when the tax code stopped allowing deduction of software dev expenses. Now they have to be amortized over several years. HN has had many discussions about this, including The time bomb in the tax code that's fueling mass tech layoffs - https://ift.tt/Oz5hkRx - (927 comments) a few days ago. Other threads are listed at https://ift.tt/4rmkyWZ . There's currently a major effort to get this change reversed. One of the people working on it is YC's Luther Lowe ( https://ift.tt/vK6qJCo ). Luther has been organizing YC alumni to urge lawmakers to support this reversal. I asked him if we could do that on Hacker News too. He said yes—hence this thread :) If you're a US taxpayer and if you agree that software dev expenses should be deductible like they used to be, please sign this letter to the relevant committee members: https://ift.tt/rYM62ac... . (If you're not a US person, please don't sign the letter, since lawmakers will only listen to feedback from taxpayers and we don't want to dilute the signal.) I'm sure not everyone here agrees with us—HN is a big community, there's no total agreement on anything—but this issue has as close to a community consensus as HN gets, so I think it makes sense to add our voices too. Luther will be around to answer questions and hopefully HN can contribute to getting this done!
754 by dang | 310 comments on Hacker News.
Companies building software in the US were hit hard a few years ago when the tax code stopped allowing deduction of software dev expenses. Now they have to be amortized over several years. HN has had many discussions about this, including The time bomb in the tax code that's fueling mass tech layoffs - https://ift.tt/Oz5hkRx - (927 comments) a few days ago. Other threads are listed at https://ift.tt/4rmkyWZ . There's currently a major effort to get this change reversed. One of the people working on it is YC's Luther Lowe ( https://ift.tt/vK6qJCo ). Luther has been organizing YC alumni to urge lawmakers to support this reversal. I asked him if we could do that on Hacker News too. He said yes—hence this thread :) If you're a US taxpayer and if you agree that software dev expenses should be deductible like they used to be, please sign this letter to the relevant committee members: https://ift.tt/rYM62ac... . (If you're not a US person, please don't sign the letter, since lawmakers will only listen to feedback from taxpayers and we don't want to dilute the signal.) I'm sure not everyone here agrees with us—HN is a big community, there's no total agreement on anything—but this issue has as close to a community consensus as HN gets, so I think it makes sense to add our voices too. Luther will be around to answer questions and hopefully HN can contribute to getting this done!
Sunday, June 8, 2025
Saturday, June 7, 2025
Friday, June 6, 2025
Thursday, June 5, 2025
Tuesday, June 3, 2025
Monday, June 2, 2025
Show HN: I rewrote my Mac Electron app in Rust
Show HN: I rewrote my Mac Electron app in Rust
591 by katrinarodri | 442 comments on Hacker News.
A year ago, my co-founder launched Desktop Docs here on HN. It's a Mac app we built with Electron that uses CLIP embeddings to search photos and videos locally with natural language. We got positive feedback from HN and our first paying customers, but the app was almost 1GB and clunky to use. TLDR; rebuilding in Rust was the right move. So we rewrote the app with Rust and Tauri and here are the results: - App size is 83% smaller: 1GB → 172MB - DMG Installer is 70% smaller: 232MB → 69.5MB - Indexing files is faster: A 38-minute video now indexes in ~3 minutes instead of 10-14 minutes - Overall more stability (old app used to randomly crash) The original version worked, but it didn't perform well when you tried indexing thousands of images or large videos. We lost a lot of time struggling to optimize Electron’s main-renderer process communication and ended up with a complex worker system to process large batches of media files. For months we wrestled with indecision about continuing to optimize the Electron app vs. starting a full rebuild in Swift or Rust. The main thing holding us back was that we hadn’t coded in Swift in almost 10 years and we didn’t know Rust very well. What finally broke us was when users complained the app crashed their video calls just running in background. I guess that’s what happens when you ship an app with Chromium that takes up 200mb before any application code. Today the app still uses CLIP for embeddings and Redis for vector storage and search, except Rust now handles the image and video processing pipeline and all the file I/O to let users browse their entire machine, not just indexed files. For the UI, we decided to rebuild it from scratch instead of porting over the old UI. This turned out well because it resulted in a cleaner, simpler UI after living with the complexity of the old version. The trickiest part of the migration was learning Rust. LLMs definitely help, but the Rust/Tauri community just isn’t as mature compared to Electron. Bundling Redis into the app was a permissioning nightmare, but I think our solution with Rust handles this better than what we had with Electron. All in, the rebuild took about two months and still needs some more work to be at total parity with its Electron version, but the core functionality of indexing and searching files is way more performant than before and that made it worth the time. Sometimes you gotta throw away working code to build the right thing. AMA about Rust/Tauri migration, Redis bundling nightmares, how CLIP embeddings work for local semantic search, or why Electron isn't always the answer.
591 by katrinarodri | 442 comments on Hacker News.
A year ago, my co-founder launched Desktop Docs here on HN. It's a Mac app we built with Electron that uses CLIP embeddings to search photos and videos locally with natural language. We got positive feedback from HN and our first paying customers, but the app was almost 1GB and clunky to use. TLDR; rebuilding in Rust was the right move. So we rewrote the app with Rust and Tauri and here are the results: - App size is 83% smaller: 1GB → 172MB - DMG Installer is 70% smaller: 232MB → 69.5MB - Indexing files is faster: A 38-minute video now indexes in ~3 minutes instead of 10-14 minutes - Overall more stability (old app used to randomly crash) The original version worked, but it didn't perform well when you tried indexing thousands of images or large videos. We lost a lot of time struggling to optimize Electron’s main-renderer process communication and ended up with a complex worker system to process large batches of media files. For months we wrestled with indecision about continuing to optimize the Electron app vs. starting a full rebuild in Swift or Rust. The main thing holding us back was that we hadn’t coded in Swift in almost 10 years and we didn’t know Rust very well. What finally broke us was when users complained the app crashed their video calls just running in background. I guess that’s what happens when you ship an app with Chromium that takes up 200mb before any application code. Today the app still uses CLIP for embeddings and Redis for vector storage and search, except Rust now handles the image and video processing pipeline and all the file I/O to let users browse their entire machine, not just indexed files. For the UI, we decided to rebuild it from scratch instead of porting over the old UI. This turned out well because it resulted in a cleaner, simpler UI after living with the complexity of the old version. The trickiest part of the migration was learning Rust. LLMs definitely help, but the Rust/Tauri community just isn’t as mature compared to Electron. Bundling Redis into the app was a permissioning nightmare, but I think our solution with Rust handles this better than what we had with Electron. All in, the rebuild took about two months and still needs some more work to be at total parity with its Electron version, but the core functionality of indexing and searching files is way more performant than before and that made it worth the time. Sometimes you gotta throw away working code to build the right thing. AMA about Rust/Tauri migration, Redis bundling nightmares, how CLIP embeddings work for local semantic search, or why Electron isn't always the answer.
Subscribe to:
Posts (Atom)