paholg

Most of that time was probably compiling dependencies. If you give it another go, I would recommend a shared sccache.

https://github.com/mozilla/sccache

It's a real risk. The British Indian Ocean Territory is going away, and by ICANN's rules, that means .io should as well.

When I worked at Amazon, I had to run a special Amazon Linux. But I could just install whatever I wanted. I used emacs with whatever plugins I wanted.

Big tech can be suprisingly not locked down!

Some of us would like our expensive hardware to work without hacked third party dongles.

So we can also fly? Sign me up!

You can build docker images with nix, in which case you can have every dependency be its own layer.

That is clearly not what these people are doing, though.

Futurelock is not about cancellation safety (cancellation is actually one solution to futurelock), though the related issues that are linked in that post are.

At an early stage startup, shipping a feature should not require "many meetings across product, legal, and engineering". Especially not one that can be mostly built in a day.

Ethernet doesn't support 240 W.

I am very happy that I can charge my phone and laptop from the same charger, and don't ever have to worry about whether the cable I'm using will be a fire hazard.

I think the real issue here is that two Android phones take photos with incompatible naming schemes.

I am sure that at some point someone thought the milliseconds should or should not be separated from the seconds and made that change without thinking through the consequences.

zoxide stores a rank for each directory based on how often you visit it, but you can manually adjust the scores.

Run `zoxide query -ls thing` to see the scores, and `zoxide add thing -s AMOUNT` to increase the score.

I don't think that's true. I have seen R4L folks reiterate time and again that C changes are allowed to break Rust code, and they will be the ones to fix it.

I think they were saying they want a format instead of PDF where the reader can change those things.

As you said, it's not static. You can update the content of pages.

You can also reorganize things and keep old links as 302s.

At a minimum, you should be aware of when you're breaking links and it should be a conscious decision.

Awesome! You and Carol rock!

Ah, good to know! Is that tooling public anywhere, or was it pretty tailor-made just for the Rust book?

That's what I meant by instructions on automated deployments. MdBook generates HTML, so you don't need anything fancy to host it.

This example shows a fairly short GitHub action to deploy to GitHub pages: https://github.com/rust-lang/mdBook/wiki/Automated-Deploymen...

Okay? I don't know what point you're making.

The difference is mostly a matter of perspective, isn't it?

In Rust, if I have

``` enum Foo { A(u32), B(u32), C(u32), } ```

Then the number of representable states is deduced my an "algebra of numbers", but the size is deduced by an "algebra of sets".

For example, the size of Foo is just 8 (4 bytes for u32, and 4 for the tag + alignment).

What you see as annoying, I see as a strength. You shouldn't break links; they don't only exist in your site. People will have them bookmarked or shared on the web.

There's nothing worse than finding a post online that seems like it will cover your exact issue, but the link is now a 404.

Have you looked into mdBook? I haven't used it myself, but I've enjoyed the documentation of many projects that do and it seems really nice once you get past the point where a single readme file works well.

They also have some nice instructions on automated deployments.

https://github.com/rust-lang/mdBook

I think a good example is all of the wonderful documentation that's been created with mdBook.

Heck, the Rust book was written with it, and they also made a print edition, so maybe markdown is enough even for that.

https://github.com/rust-lang/mdBook

Huh, interesting. I did primarily use FOSS and CLI applications. It's been a couple years, so I don't remember what exactly I used it for. I probably installed Docker Desktop via whatever method docker recommends, and I'm not sure about Firefox.

For alacrity, I remember it being annoying to integrate into Mac's launcher, but it otherwise worked.

Pretty much everything else was programming-related and just worked.

When I've had to use a Mac, I've used nix to good success. I'm actually surprised how well it worked; I was able to basically just use the same config I use on Linux, removing just the few Linux-specific packages.

You can avoid the kvm with a cheap USB switch and software.

https://github.com/haimgel/display-switch

In emacs, there's robe mode which I found to work very well. It keeps a Ruby process running with your code loaded in it.

I wonder why no one's written a Ruby LSP with this approach rather than relying on static analysis.

https://github.com/dgutov/robe

I worked on something different, but we integrated with Crowdstrike and such.

Maybe someone could do a study of like breaches in Fortune 500 companies that use an EDR vs. those that don't, but they probably all do at this point.

I used to work in this space, and I always had the nagging question of "is any of this stuff actually useful?"

It seems a hard question to answer, but are there any third party studies of the effectiveness of Crowdstrike et al. or are we all making our lives worse for some security theater?

I'm curious if the different SMS message would have mattered in practice.

I for one don't ever read those messages, and Android at least will usually copy the code for you making them even easier to ignore.

Minimum of "all the money you made doing this" plus a percentage of total revenue, IMO.