juicypt

Working on a small SQL-based streaming ETL tool.

It reads from a replication stream and allows you to trim/enrich the replicated data by running SQL queries from the database, then writing the result out to another database (also using a custom SQL query, so it's easy to do upserts or joining with other data on the destination database).

It's working really well, and I'm just sprucing up logging and documentation a bit before making the source code public on github. The idea is for it to be a much simpler alternative to things like Debezium for small to medium sized projects.

Currently supports postgres for input, and postgres and clickhouse for output with more databases coming down the road.

I think there's a reasonable middle ground here. I would think it's fine for them to keep their algorithms closed-source, but be required to opensource the minimum amount of firmware to allow access to all of the hardware: bootloader, CPU, storage, memory, display, and sensors.

No need to reveal any trade secrets at all. The above stuff is not the secret sauce that makes people buy their watches anyway: they use some of the most basic hardware in the market at their price point.

It seems to me that they're not unsurprised, and so they're actually surprised.

That's really weird, since he did implement a calculator that uses a dialect of APL: https://aplwiki.com/wiki/Ivy

The parent comment could be the beginning of an interesting discussion on cold war dynamics. Wouldn't you rather engage with that and gain something from the discussion, than take a cheap shot at the author for a quick giggle?

Interesting! I couldn't find a link to github (or something else) on your website though. Is there a way to get the source to do some tests?

At my company we rent a couple of dedicated Ryzen 9 5950X boxes from Hetzner to host our Gitlab CI runners, for a bit over $100/month each.

These rip through our pipelines so much faster (and cheaper) than any managed CI offering we've tried, that we didn't even bother doing proper benchmarking.

I would assume 7900X or 7950X would be even better :D

This is tangential to the discussion, but are there any laptops that won't heat up your legs/groin when used on your lap?

I remember owning an Asus UL30VT [1] 10 or 15 years ago, and I could have it on my lap for hours without feeling any heat regardless of the CPU load. It was a bit crappy in other ways, but a joy to use on the go!

It seems like nowadays all manufacturers try to keep the components cool, but don't care much about the external chassis temperature. Even laptops that use ultra low voltage CPUs usually go for fanless setups instead of trying to improve external temperatures.

[1] https://www.notebookcheck.net/Asus-UL30VT.27130.0.html

I'm not sure about ToolJet, but I know it's possible to use external auth systems with AppSmith.

It supports at least Firebase and Supabase. I think self-hosting Supabase + AppSmith could be a good combo for quickly hashing out prototypes or internal company apps.

That looks pretty cool, I'll have to check it out :)

Man, given all the comments suggesting frameworks that will require you to do html/css/js it seems like no one has really read your post.

For your use case I would look at AppSmith (https://github.com/appsmithorg/appsmith) or ToolJet (https://github.com/ToolJet/ToolJet).

These are full-stack low-code frameworks, but it's easy to use them to do just the frontend and connect to a backend API you implement yourself separately.

Edit: forgot to mention that these support drag&drop for building user interfaces :)

Yes. The latch might not be strong enough to handle the centrifugal force when driving hard, or vibrations, etc.

You don't need to go out to the track once per tweak of course. You could very well do a few laps to test out the whole system once in a while.

Here's an interesting effort in creating an Ocaml for the BEAM VM: https://github.com/AbstractMachinesLab/caramel

It's still pretty new though, so I don't know how well it works just yet.

Actually webpack has the url-loader which allows embedding binary data as base64 data URLs in your CSS bundle. If used judiciously it can even be a good thing too.

EDIT: I mentioned webpack since the thread is about react, but you can do the same thing manually by putting the base64-encoded data in a data URL on a CSS file.

An interesting framework that I saw here on HN a couple of days ago is Tailwind UI (https://tailwindui.com/). It's not out just yet but looks very promising.

Other than that I would recommend Bulma (https://bulma.io/). It's like bootstrap but with a different philosophy on how CSS should be implemented. Also, it doesn't include any javascript. I think that was a good decision on their part as you won't have to fight the default behaviors on their components if you want to do something slightly different.