RsmFz

But I never maximize my web browsers, either

Looks correct now on Firefox on macOS (light mode, probably)

We have that here at Firezone. To deal with I/O we don't use Tokio inside the test boundary at all, just futures. So no I/O, no sleeping, etc. Thomas explained it here https://firezone-git-docs-blogsans-io-firezone.vercel.app/bl...

I haven't dealt with it directly on Firezone but I wrote one or two games this way for game jams years ago, and I keep wishing it would catch on. It was harder with the games because floating-point math doesn't like to be deterministic across platforms.

I think it's LiveView for the frontend-backend comms and Tailwind CSS for some of the frontend, not sure if that answers your question

-- (non-web) developer at Firezone

Well that's also true for Firezone :)

It's a tradeoff between in-process and out-of-process though. It's nice that Firezone Gateways don't have access to the service's memory space and can't crash the process, but it's also nice that an in-process Gateway equivalent doesn't need to loop through the network to reach its service.

Ah that's tough because Wireguard being UDP is a selling point for us at Firezone

Oh so that allows it to run in-process?

That's cool, I did that for an HTTP forwarding thing a while back.

Hm, is Wireguard getting blocked by middleboxes or something?

I live by but two rules, private keys stay on the storage device they're first saved to, and makeup stays with the first person to use it.

Firezone employee here. I believe we have an idea to let customers sign their keys so that they don't need to trust our portal not to rewrite keys. This is probably the same idea Tailscale hit on.

(I can't find this idea in the issue tracker and I don't think it's on the roadmap yet, but we've discussed it.)

Unfortunately there is a big convenience-security tradeoff, managing your own keys and certs is a lot of work.

> has signed a bill into law that will significantly curb the penalties companies could face for improperly collecting and using fingerprints and other biometric data from workers and consumers.

Darn. I would really like less biometrics.

I think the phrase is "zero-cost abstractions", meaning "Supposing you want bounds checks, you may as well use ours and not roll your own"

> You can't just write some code and then say it must be secure because Rust was involved

Did they say that?

That'll happen with permissive licenses

I don't remember any big insights except that I'm pretty bad at estimates.

Everything that feels like a "half-day" task took an entire day or two. I would look back on every feature and think, "No way was I working on that for X days straight?"

Basically nothing takes less than half a day.

I cranked out a Lua interpreter implemented in Rust in a week or two.

It only ran about 3x slower than PUC Lua... And never collected garbage either :P

Oh I built one of those with Rust and FLTK: https://six-five-six-four.com/git/reactor/annoying_journal

I figured if it works for software profiling it oughta work for people. And I set the interval to some Golden Ratio thing like 37 minutes, with the hopes that it wouldn't log the same times every day, but also wouldn't be purely random.