HNHacker News
TopNewBestAskShowJobs

kjuulh

512 karma · joined March 22, 2021

submissionscomments
kjuulh··on OpenTelemetry collector: What it is, when you need it, and when you don't
I had a brief look at greptime db. And I'd like to give a little bit of feedback on your funnel. It is clear that your product marketing is targeting business folks rather than developers. That 3 minute vid on the frontpage was next to useless for me. Also very clearly AI.

Having stats is nice but i am not choosing your product because of stats. I actually think greptimedb is exactly what I am looking for, I.e. a humio / falcon logscale alternative. But I had to do some digging to actually infer that.

Your material doesn't highlight what sets you apart from the competition. If you want to target developers which you might not. I dont know.

I want to debug issues using freetext search, i want to be able to aggregate stats i care about on demand.

kjuulh··on YouTube addresses lower view counts which seem to be caused by ad blockers
YouTube even has a feature now that if you skip, it will skip over sections that other people skip to. Which in practice does the same thing as sponsorblock, except that you have to press skip ;)
kjuulh··on React is winning by default and slowing innovation
There is always a "better" thing. I do think that it is fine to have a bit of stability in the frontend space. Should react stay the default for the future, probably not, but it is fine if it stays that way for a while.

React is a good enough choice for a lot of problems, heck, going without a framework is often a good enough choice, we don't always have to choose the "best" option, because what we value might not actually be that important, over other important metrics. Signals might have performance, elm elegance and purity, etc, etc. But for 95% problems, and teams React is just fine.

A bonus is that I can come back to my project in a year, and not have to rewrite it because everything changed since then.

In Danish we say

> Stop mens legen er god

Stop, while you're still going strong (ish). React is plenty equipped to solve a lot of problems, it doesn't need to solve all of them.

kjuulh··on Dotfiles feel too personal to share
Chezmoi has been a blessing to use. It is one of the only tools I've used that had been able to survive me neclecting it for months and then getting back to it. I'd love a more interactive diff when my dotfiles have driften too much. But otherwise it is perfect for my needs.
kjuulh··on Woman takes 10x dose of turmeric, gets hospitalized for liver damage
I was working at a small farm-shop at some point, we sold smoothies of turmeric and ginger, we had to label it clearly, and restrict sale for pregnant woman, young kids and the elderly because large doses can be dangerous. As far as I recall both are a natural blood thinner.

Edit: in europe

kjuulh··on Next month, saved passwords will no longer be in Microsoft’s Authenticator app
I felt the same when implementing OpenID connect flows according to spec. It uses the browser in creative ways ;) Especially the device flow, absolutely insane complexity for what it is.
kjuulh··on I Switched from Flutter and Rust to Rust and Egui
I actually wanted to ask you about this at our last meetup (Rust Aarhus), so nice to see it on hackernews. It did seem you switched away from flutter. ;)

How is shipping egui apps vs flutter. I'd imagine that especially shipping a rust integration with Flutter might be a bit of a pain

kjuulh··on Hyprland Premium
It is weird, this is their main website: https://hypr.land/

Which has a demo. This website seems to only be for the account / payments.

kjuulh··on Hyprland Premium
I've got absolutely no problem with them taking donations / having a premium option. But it is very difficult to comment on when there is no indication what the premium experience brings.
kjuulh··on Rust compiler performance
You can rent bigger runners from github. They're still not as fast as third party ones, but it takes 5 minutes to set up and is still pay as you go. I just see a lot of people use the default ones, which are very small.
kjuulh··on Rust compiler performance
Could Rust be faster, yes. But honestly, for our use-case shipping; tools, services, libraries and what have you in production, it is plenty fast. That said, Rust definitely falls off a cliff once you get to a very large workspace (I'd say plus 100k lines of code it begins to snowball), but you can design yourself out of that, unless you build truly massive apps.

Incremental builds doesn't disrupt my feedback loop much, only when paired with building for multiple targets at once. I.e. Leptos where a wasm and native build is run. Incremental builds do however, eat up a lot of space, a comical amount even. I had a 28GB target/ folder yesterday from working a few hours on a leptos app.

One recommendation is to definitely upgrade your CI workers, Rust definitely benefits from larger workers than the default GitHub actions runners as an example.

Compilling a fairly simple app, though including DuckDB which needs to be compiled, took 28 minutes on default runners. but on a 32x machine, we're down to around 3 minutes. Which is fast enough that it doesn't disrupt our feedback loop.

kjuulh··on GCP Outage
Downdetector shows they've got issues as well, but it can be fairly unreliable, as people don't know which service is behind their apps.

I at least have no issues on their services across a few regions, and their console works fine.

kjuulh··on GCP Outage
I wonder what the damage ($) for having a good portion of the internet down for an hour or two ;)
kjuulh··on GCP Outage
This feels very much like when facebook, locked themselves out of their datacenters. ;)

* https://www.datacenterdynamics.com/en/news/facebook-blames-m...

kjuulh··on GCP Outage
Something must be preventing them updating the status page at this point. Of course they could still deem it not enough, but just from my limited tests, docker, buf, etc (it may not be GCP that is down, but it is quite the coincidence). are outright down. I'd wager that this is much more widespread.
kjuulh··on Modern C++ – RAII
I am by no means a C++ expert, a noob rather. It might be possible to make this generic, but it seems quite easy to forget a small detail here, and then be kneecapped because you forgot one of the overloads. So that in very few amount of edge cases your abstraction isn't actually cleaned up.

Better than nothing, and might be the most preferred way of doing things in C++, but it does seem dangerous to me. ;)

kjuulh··on Databricks and Neon
Mainly in relation to notify/listen and advisory locks. Most of our code bases use advisory lock based migration tools. It would be a large lift moving to an alternative or building a migration scheduler out of process
kjuulh··on Databricks acquires Neon
That is why I was hopeful for Neon unlike a lot of the other ones. Yugabyte however isn't just postgres.
kjuulh··on Databricks acquires Neon
Congratulations to the Neon team.

To be honest this is a little sad for me. I'd hoped that Neon would be able to fill the vacuum left by CockroachDB going "business source"

Being bought by DataBricks makes Neon far less interesting to me. I simply don't trust such a large organisation that has previously had issues acquiring companies, to really care about what is pretty much the most important infrastructure I've got.

There certainly is enough demand for a more "modern" postgresql, but pretty much all of the direct alternatives are straying far from its roots. Whether it be pricing, compatibility, source available etc.

Back when I was looking at alternatives to postgres these were considered:

1. AWS RDS: We were already on AWS RDS, but it is expensive, and has scaling and operations issues

2. AWS Aurora: The one that ended up being recommended, solved some operations issues, but came with other niche downsides. Pretty much the same downsides as other wire compatible postgresql alternatives

3. CockroachDB: Was very interesting, wire compatible, but had deeper compatibility issues, was open source at the time, it didn't fit with our tooling

4. Neon: Was considered to be too immature at the time, but certainly interesting, looked to be able to solve most of our challenges, maybe except for some of the operations problems with postgresql, I didn't look deeper into it at the time

5. Yugabyte: interesting technology, had some of the same compatibility issues, but less that the others, as they're also using the query engine from postgresql as far as I can tell.

There are also various self hosting utilities for PostgreSQL I looked at, specifically CloudPG, but we didn't have the resources to maintain a stateful deployment of kubernetes and postgres ourselves. It would fulfill most of our requirements, but with extra maintenance burden, both for Kubernetes and PostgreSQL.

Hosting PostgreSQL by itself, didn't have mature enough replication and operations features by itself at that point. It is steadily maturing, but as we'd got many databases manual upgrades and patches would be very time consuming, as PostgreSQL has some not so nice upgrade quirks. You basically have to unload and reload all data during major upgrades. Unless you use extensions and other services to circumvent this issue.

kjuulh··on Rust on the Ferris Sweep
I feel the pain, I had so much trouble setting up QMK to my handwired keyboard. I had to give up on VIA and VIAL and just config my keys in text.

It basically took the same amount of time 3d printing my case, soldering it (Dactyl Manuform) etc. As it did configuring it. Massive pain, and quite unclear documentation on how to actually set up a handwired keyboard. Next time will be smoother, and I probably should document what I did ;) I honestly, felt like a rookie programmer over again, good fun, but super challenging.

kjuulh··on I'll think twice before using GitHub Actions again
Exactly. When comparing dagger with a lot of the other formats for ci, it may seem more logical. Ive spent so much time debugging github actions, waiting 10 minutes for testing a full pipeline after a change etc. Over an over again. Dagger has a weird DSL in the programming languages as well but at least it is actual code that I can write for loops around or give parameters and reuse. The instead of a groovy file for Jenkins ;)
kjuulh··on I'll think twice before using GitHub Actions again
It is a perfectly valid crtitisim dagger is not a full build system that dictates what your artifacts look like. Unlike maybe something like bazel or nix. I think of dagger as a sort of interface that now allows me to test and package my build and ci into smaller logical bits and rely on the community for parts of it as well.

In the end you do end up slinging apt install commands for example, but you can test those parts in isolation. Does my ci actually scan this kind of vulnerability, install postgres driver, when I build a rust binary is it musl and working on scratch images.

In some sense dagger feels a little but like a programmatic wrapper on top of docker, because that is actually quite close to what it is.

You can also use it for other things because in my mind it is the easiest way of orchestrating containers. For example running renovate over a list of repositories, spawning adhoc llm containers (pre ollama), etc. Lots of nice uses outside of ci as well even if it is the major selling point

kjuulh··on I'll think twice before using GitHub Actions again
I am biased because I built the rust SDK for dagger. But I think it is a real step forward for CI. Is it perfect? Nope. But it allows fixing a lot of the shortcomings the author has.

Pros:

- pipeline as code, write it as golang, python, typescript or a mix of thr above.

- Really fast once cached

- Use your languages library for code sharing, versioning and testing

- Runs everywhere local, ci etc. Easy to change from github actions to something else.

Cons:

- Slow on the first run. Lots of pulling of docker images

- The DSL and modules can feel foreign initially.

- Modules are definitely a framework, I prefer just building having a binary I can ship (which is why the rust SDK doesnt support modules yet).

- Doesn't handle large mono repos well, it relies heavily on caching and currently runs on a single node. It can work if you don't have 100 of services especially if the builder is a large machine.

Just the fact that you can actually write ci pipelines that can be tested, packaged, versioned etc. Allows us to ship our pipelines as products which is quite nice and something we've come to rely on heavily

kjuulh··on Delta: A syntax-highlighting pager for Git, diff, grep, and blame output
I've been using a mix of delta and difftastic both are amazing. Difftastic especially for tree-sitter AST syntaxes, it is a bit slower, but AST aware diff is so nice.

Delta looks clean, and is super fast

kjuulh··on The IPv6 Transition
I'd like to use ipv6, if only to avoid having to pay for an ipv4 address for some private vpcs (with public address for reasons). I remember having issues with fly.io as well, because they're ipv6 by default if I remember correctly.

Currently Denmark has worse support than I expected:

> Liste over danske udbydere (List of Danish providers)

> Internetudbydere på listen: 41 (ISPs on the list)

> Internetudbydere med fuld IPv6-understøttelse: 17 (41%) (ISPs with full IPv6)

> Internetudbydere med delvis IPv6-understøttelse: 10 (24%) (ISPs with partial IPv6)

> Internetudbydere uden IPv6-understøttelse: 14 (34%) (ISPs with no IPv6)

source: https://ipv6-adresse.dk/

kjuulh··on NixOS is a good server OS, except when it isn't
Nickel lang is such an effort. Id say the syntax is a mix of json and lua and aims for a non-touring complete program. It is still a bit early but it looks promising
kjuulh··on Rainfrog – a database management TUI for Postgres
I've been using both.

Charm/bubbletea toolstack, is very much focused on an ELM style architecture, I.e. message passing and deriving UI from state. You can still do immediate type UI if that is what you prefer, but it won't fit with any of the standard components. Bubbletea is a framework more or less, so even if you know Go, it will require you to learn how to build to its strengths.

Ratatui is by default not very opinionated about how to handle state and updates, which requires some development from you, or using a third party library to get an opinionated architecture around it. Ratatui is more of a collection of libraries, out of the box, it expects a certain interface for components, but it is up to you how you want to compose them together. Whether that is immediate-, stateful-, react-, or ELM style. Stateful is the default for all their examples.

Charms way of doing terminal UI is very much based around strings, which can sometimes give issues with spacing, as components can be fiddly to be constrained within a certain space.

Ratatui creates UI on top of a matrix of bytes, which makes it more difficult to do easy things, but allows you to more easily build complex uis.

Generally I prefer Ratatui, as you can really build robust and fast uis on top of it. It does take a bit more work to get started though. I am also biased by Rust tho.

kjuulh··on Ask HN: Going low-level – what to learn next?
If you want something on the more application side, I.e. utilization of low-level techniques, I can highly recommend looking into game engine development, even if you aren't interested in games per say.

I've recently enjoyed Game Engine Architecture, mostly because there is an interesting mix using low level techniques to solve problems a normal application wouldn't be required to fix.

Game development in general is case for tuning yourself to when you should utilize high level programming techniques, and when required dropping into low level optimization to solve local problems.

kjuulh··on Show HN: Neosync – Open-Source Data Anonymization for Postgres and MySQL
Sadly not, it is very much tied to our workflows and as such wouldnt provide much value for anyone else other than a reference. Nevertheless I thought I'd share our approach to anonymization / pseudoanomyzation as I haven't really seen that done elsewhere.
kjuulh··on Show HN: Neosync – Open-Source Data Anonymization for Postgres and MySQL
I just published our approach to pseudo anonymization and sort of anonymization.

We'd built a tool which can traverse data extract the pii data and put back a token into the data. Before one of our allowed systems would read the data we'd swap in the actual data or an anonymized version if we didn't permission to use it anymore. So we sort of get the best of both worlds we can use the actual data of our customers because we require it, but can safely use data for analytics and retain a lot of the statistical variance of our data.

Crazy complex project to work on given our limited resources but very fulfilling in the end.

It should be mentioned that I don't mention the difference between anonymization and pseudo anonymization in the article mostly because I didn't know it was really a thing. I just implemented a solution given or requirements

https://tech.lunar.app/blog/data-anonymization-at-scale

← PreviousPage 3 of 6Next →