Stack is super simple, for the blog in general I'm using caddy to serve my markdown files, using the built in templating functionality to turn them into html.
For the sequencer page, it's basically a self-contained html page. The js/css is written in separate files to make it a bit easier to edit, but they are then just included in the main file without any kind of minification or obfuscation so it should be quite easy to look at the source. Feel free to read and remix it for your own purposes!
There will be some limit to this approach, but for this use case I really like the idea of dependency less HTML files. As long as the main browser APIs I'm using remain, it should keep on working.
I put together the core, but also often pasted the whole thing into Claude web, asking it to make an artifact and then playing with it on my phone while commuting, if it was good I'd use it as inspiration later.
Ooh! I've been semi-aware that there's been things going on in the iPad space, but didn't know that there was so much. ZOA seems like an interesting take on a sequencer so will try to dig a bit deeper into how it works.
Don't have an iPad though, part of wanting to play with hardware is getting away from all the daily screens (not that I'm always managing to do that), but I'm imagining there's some ideas you can get from videos about them too. But looking up some of the things above they do look quite cool... And would definitely be cheaper than Eurorack.
Haha, now I feel like I need to contain myself to current rabbit holes before it goes to far, but thanks a lot for sharing! :D
Not sure about the ones mentioned in the article, but for the kind I'm used to (i.e Bäsk) in Sweden it's a given.
In our family it's generally been a tradition to go out in the night of August 24th each year to pick some wormwood, and then infuse some plain alcohol with it to have for the coming months. We generally don't leave it in as long recipes call for though, 24h instead of multiple days so the taste is a bit milder.
Its the day when all farmers should be done harvesting and autumn officially begins according to "Bondepraktikan" [1], which says to be done by St Bartholomews day.
Like many old traditions the reasons have for many become lost to time, and now it's an accepted fact that that's the magical night to get some wormwood.
Yeah, it's always so cool looking. The device is using a CRT vector display, so instead of the CRT drawing each pixel row line by line, each shape on the screen is drawn one by one as small line segments.
Curves are also possible, but you'd have to formulate the vector shape for it, which is harder than for straight lines.
It also looks even cooler in person, as the refresh rate is also really good due to the CRTs, if there's an old arcade close with Asteroids or similar early vector games I'd really recommend going to see it.
Never had the chance to use Quickwit at a $DAYJOB (yet?), but I really appreciate the fact that it scales down quite well too. Currently running it on my homelab, after a number of small annoyances using Loki in a single-node cluster, and it's been working very well with very reasonable resource usage.
I also decide to use Tantivy (the rust library powering/written by Quickwit) for my own bookmarking search tool by embedding it in Elixir, and the API and docs have been quite pleasant to work with. Hats of to the team, looking forward to what's coming next!
You might want to have a look at SigNoz [1] as well. We have also published some perf benchmark wrt Elastic & Loki [2] and have some cool features like logs pipeline for manipulating logs before ingestion
Just got started this year so it's only got two posts so far. One on logging and the other on config languages.
I'd like to spend a bit more time writing but still need to build it into a habit.
I think there's nothing currently that combines both logging and metrics into one easy package and visualizes it, but it's also something I would love to have.
Vector[1] would work as the agent, being able to collect both logs and metrics. But the issue would then be storing it. I'm assuming the Elastic Stack might now be able to do both, but it's just to heavy to deal with in a small setup.
A couple of months ago I took a brief look at that when setting up logging for my own homelab (https://pv.wtf/posts/logging-and-the-homelab). Mostly looking at the memory usage to fit it on my synology. Quickwit[2] and Log-Store[3] both come with built in web interfaces that reduce the need for grafana, but neither of them do metrics.
Side note: it should be possible to tweak some config parameters to optimize the memory usage or cpu usage of quickwit. Ask us on the discord server next time :)
Yeah, I was a little bit surprised it was so close. And I've been using tantivy (the library which powers quickwit afaik) in another side project where it used comparatively less.
Might jump in there then as an excuse to fiddle a bit more with the homelab soon then :)
Nickel was among the other languages that popped up in my search, but I sadly didn't have enough time to deep dive in.
I'm also on the verge of experimenting with switching out the HCL to something else for my homelab setup. It currently uses terraform and nomad, and it's fine, but I always have a feeling there should be something more ergonomic.
Now, I use vim mode in Sublime, so I have already "seen the light" so to say. But that situation is probably one I'd actually be able to solve faster with multiple cursors.
What I'd do is this: Put the cursor on one of the calls, then use ctrl-d to put a new cursor at all the matches. Then use ctrl-right-arrow to move by word until the second comma, combine that with shift to select the argument and edit all of them with visual feedback to my heart's content.
In reality, depending on the complexity of the text, after creating all the cursors, I'd probably use the vim movements to get them to where I need though.
I think they extended it fairly recently, I also live in Neukölln and fell outside of the delivery area before Christmas at least. But I did a quick check after reading the article, and now everything seems to be working.
Stack is super simple, for the blog in general I'm using caddy to serve my markdown files, using the built in templating functionality to turn them into html.
For the sequencer page, it's basically a self-contained html page. The js/css is written in separate files to make it a bit easier to edit, but they are then just included in the main file without any kind of minification or obfuscation so it should be quite easy to look at the source. Feel free to read and remix it for your own purposes!
There will be some limit to this approach, but for this use case I really like the idea of dependency less HTML files. As long as the main browser APIs I'm using remain, it should keep on working.
I put together the core, but also often pasted the whole thing into Claude web, asking it to make an artifact and then playing with it on my phone while commuting, if it was good I'd use it as inspiration later.