HN user

leleat

57 karma

My personal blog: https://neverready.app/blog/ My GitHub profile: https://github.com/leleat

Posts0
Comments7
View on HN
No posts found.
Deno Desktop 1 month ago

Shared CEF runtime across apps. Every app currently bundles its own CEF copy. A managed shared runtime would drop binary sizes to a few MB per app. On the roadmap.

This[0] sounds interesting. I am not familiar with CEF, so I wonder how the versioning works. When different apps require different versions of CEF, do we just essentially end up with the electron model where every app bundles their own browser (just slightly less bad). Or is there still an advantage to a "shared runtime" in that case?

[0] https://docs.deno.com/runtime/desktop/comparison/

0ThreadHN
.gitignore Isn't the only way to ignore files in Git 1 month ago

There is also

  git update-index --[no]-skip-worktree
for files that are already tracked. This can be useful for some local experimentation... it's just a bit annoying to use because it's not really surfaced anywhere by git (kinda). You need to remember that you set it; otherwise other operations like checkouts may be blocked.
0ThreadHN
Ask HN: What are you working on? (February 2026) 5 months ago

https://github.com/Leleat/git-forge

From the README: "[git-forge is a] simple CLI tool for basic interactions with issues and pull requests across GitHub, GitLab, Gitea, and Forgejo".

Right now, I am looking into better testing. Currently, I do testing by mocking the forge APIs and then running git-forge against them with TypeScript. But not everything is testable that way. The TUI is pretty much untested. So I now want to port at least the tests to Rust (I am probably gonna leave the mock API in TS) and need to look into how to tests TUIs, which is a bit of a challenge since not only is Rust my first "systems programming language", I am also not knowledgable in Terminal/TUIs...

0ThreadHN
KDE is now my favorite desktop 10 months ago

The problem is that the extension experience can be really bad. There is no extension API; instead Extensions have (almost) full access to GNOME Shell's code.

This makes them incredibly powerful and flexible... but also fragile. Extensions can crash GNOME Shell/mutter. On Wayland that means your entire session goes down with GNOME Shell. Extensions can interfere with each other, and if you are an extension developer, you may need to update (or at least check) your extension every 6 months (GNOMEs release cycle).

0ThreadHN