It maintains its own index of apps and the filesystem in process and it ends up being 5-9x faster than mdfind. App search is nearly instantaneous and file search across the entire home directory takes ~100-150ms.

I've focused on just replicating spotlight's functionality and don't plan to add more features like workflows or plugins since I personally don't have a use for them. This is really about just having a fast way to search apps and files that works well.

https://floodlight.vmg.dev/ https://github.com/vmg-dev/floodlight

Comments URL: https://news.ycombinator.com/item?id=49155188

Points: 1

# Comments: 0

Even the purported reason for these photos existing is sad, that they want to be able remember or relive the experience. Just get new experiences? That idea is much more uplifting to me.

Caveat, this obviously doesn't include once in a lifetime experiences that in my opinion it's justified to take photos of like marriage or things involving milestones of children etc.

A lot of people go “js is bad” reflexively and they are right for the wrong reasons. Its not because js (specifically v8) is slow. I have many websites and web based apps open and none fuck up my laptop as hard as claude code.

Put up the code and prove it. We already know exactly how fast golang is in comparison to nodejs on basic numeric computations, it's roughly 40 to 50% faster.

> they need a high powered game engine rendering loop

Don't believe the bs on twitter. Claude code source was leaked, there is no high powered game engine rendering loop.

> It needs to stream text to stdout

These apps are doing real work taking text that is streaming in and doing syntax highlighting, calculating diffs, and rendering markdown. If the work was split across threads they would not use anywhere close to as much power and there would not be a slow ui.

If you think this is actually nothing, prove it. Put the code up on github that shows taking a constant random stream of markdown, code, and diffs and displays it in the terminal can be done cheaply on a single thread.

The reason the computer gets hot and uses more power is because the cpu is getting close to 100% utilization.

It's also all cpu bound work. The majority of the stuff on your screen is being rendered by the gpu.

With js you get 1 thread at 100% utilization. Power usage and heat scale non-linearly with cpu utilization and 100% utilization on a single threaded js app means you will have ui lag. Other languages like golang would split work across 8 threads and have 8 threads at 20% utilization and this would result in less power usage. Claude Code would have been better off performance wise being an electron app because it would be offloading rendering to the browser and gpu.

Also, the architecture of Open Code is actually a lot better here than Claude Code. ClaudeCode does everything, including rendering in a single thread and it's all in js. OpenCode has a zig based tui renderer it offloads that work onto.

But I will also say these coding agent tuis do get unfairly maligned because they launch subprocesses and those subprocesses tend to be expensive. If you are using Rust analyzer with claude code, it's rust analyzer that's causing the majority of your problems.

This is actually non-trivial. There's an app I was working on where I wanted to have a local first mode that allowed people to use the app for free without an account and there was also a cloud hosted version that allowed for team collaboration, etc.

For this kind of thing to work chunks of the app essentially need to be written twice. So, not fun.

Rowing across an entire ocean is absolutely amazing.

You were able to turn around a codebase that was growing its bug count exponentially by changing an entire company's hiring practices?

I really don't believe in the "just don't be stupid" or "don't hire stupid people" approach to things. If it works, it only works at a small scale and once things become urgent enough, things fall apart.