Recent submissions

Comment · 1 year ago
A plugin can spawn arbitrary processes so if neovim is not started in a sandbox (container, namespace, firejail...) they can basically do whatever your user has the right to do.

Pretty big supply chain risks here.

Comment · 5 years ago
The devlog videos are great : https://github.com/eduard-permyakov/permafrost-engine#devlog

Thank you so much for making this in the open and documenting everything !

Comment · 5 years ago
Compiling it yourself from source is quite easy, you can find instruction here: https://www.sqlite.org/howtocompile.html

Here is an article from Julia Evans explaining it: https://jvns.ca/blog/2019/10/28/sqlite-is-really-easy-to-com...

Or if you are familiar with Docker, you can use a more recent Debian in a container and install sqlite inside it.

Comment · 5 years ago
The problem lies in baking entire distribution into an image.

Using distroless images or "FROM scratch" with statically compiled app reduces the risks.

You still have to watch for your app dependencies updates but that's less work than for an entire distribution.

Comment · 6 years ago
Comment · 6 years ago
I feel that learning from (bad) past choices to build a better solution is a good engineering practice ? Sure the initial db choice didn't scale but they learned from it and they seem to be happy with how they built their new db now
Comment · 6 years ago
Comment · 7 years ago
It appears to simply apply this CSS to the selected elements:

.___blur-blur { filter: blur(5px); }

Comment · 12 years ago
We have more precise data about global warming. Sensors are good at measuring temperature or sea rising, less at measuring divorce rates.
Comment · 12 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton