I took a crack at implementing this in Go. For anyone curious I settled for algorithm 2 as I can just use a map as the base set structure.

https://github.com/tristanisham/f0

What about the Go try/catch claim? There is no try/catch in Go. Returning errors and values is closer to Rust and Zig than D and C++.

Go has panics. You can unwind them, and recover from them. Using these for control flow is heavily discouraged and therefore it's rarely ever an issue, but they are a type of exception handling, or at least very close to that.

Also worth noting is that while they are discouraged, the very same Go devs who discouraged this pattern chose to use it in the standard library for basic things.

Rust has panics too, which also unwind, and you can also recover from them; they are also a type of exception handling. Unless the project was compiled with panic=abort, in which case they don't unwind at all and you can't recover from them; the existence of the panic=abort option means one cannot reliably use them for control flow, which makes it harder to abuse. But even then, you still have to make sure your code is "panic safe" when writing library code (usually through clever use of RAII guards, instead of expecting the code flow to always reach the end of a function).

I’ve made the exact same website for myself. It’s just a little PHP static webapp but I can write reviews for posts and it’s got a simple SQLite/PHP ^8 backend.

https://artsie.red/

I could have used something like Safari’s reading list, but that wouldn’t scale to all of my devices. And I don’t like the idea of putting control of those links into a service I can’t delete.

This site literally solves one problem perfectly and beyond the occasional functionality upgrades (auto-fetching post metadata, a refresh button, and a little CMS behind authentication) it’s super light and useful for me!

Just was in the National Irish Museum - Archeology yesterday and saw these stones for myself! These are such impressive structures, at least 5 feet high with writing so deeply engraved it’s still legible today (a specialist’s eye is still required).

If you’re interested in trying Zig out and want an easy way to update/use multiple versions I’ve been working on a Zig Version Manager for the past few weeks.

It works on Windows, Mac, Linux, a smattering of BSD’s and Plan 9. Arm and x86.

https://github.com/tristanisham/zvm

On Windows one can use https://scoop.sh too. There's a "zig" package for numbered releases, and a "zig-dev" package for nightly.

There is also `pip install ziglang`

With nix you can use https://github.com/Cloudef/nix-zig-stdenv see the versions.nix

I had to do a lot of manual transcription in Journalism school. Using a tool like Descript saved HOURS of my life. Generally it was 80% accurate, but going over an two-hour-long recording again at 3x speed while reading over the transcript, fixing errors from memory or pausing took a five hour job down to 30-40 minutes. Either way, somebody is going to have to listen to the recording. This just removes a layer of grunt work.

Golang has https://pkg.go.dev. Rust has https://docs.rs

Golang entire standard library is documented. Plus with how the language is designed docs don’t need to change with new versions. Just with new functions.

More importantly, golang has https://go.dev/ref/spec — most of the time I wished for better TypeScript documentation it's about syntax (though I did need to go read the default bundled libraries a couple times for details, that's rarer).

My spam horror show started after responding to a text similar to these. It was poised as a woman trying to connect with her daughter. I responded, and since then have had a deluge of spam and crap messages.

Please clap

This comment section reads like an ad for Flex.