Replying again to say: that actually makes sense. You should have said that upfront! Suddenly being locked out of critical software is definitely a risk worth considering

Why?

He had an interview with Google and they asked him to invert a binary tree, which is essentially taking a tree of data and swapping the positions of all sibling nodes.

While most people agreed it was a pretty pointless question to ask at an interview, mxcl had a full “don’t you know who I am” shit fit on social media.

If anyone hasn’t made the connection, mxcl is the infamous Google interview binary tree guy

I googled “how to migrate from esxi to proxmox” last week. I must be psychic.

It depends on your intent. If you’re doing it to keep history clean and linear in the long term, it’s a huge waste of time as it gets splatted into a single squashed merge commit. It also makes it difficult for reviewers to rereview your changes as GitHub/Lab can’t calculate the diff because you keep moving the goalposts with force pushes.

If you’re doing it for cleanliness on your local branch then I guess that’s fine, but I find it anti-social in a multi participant repo.

Agreed. I’ve been trying to explain to someone recently why rebasing and force pushing their feature branch has no benefit when we use a squash commit strategy for merging to main.

Again, tools are not blame, but when combined with a lack of understanding and accumulated “git dogma”, it can be quite disheartening.

Same. I mostly use sourcetree to do quick self-reviews and to discard lines or hunks before a commit.

But I’ve also grown very weary of having to dig people out of git messes they’ve made with sourcetree and the likes.

Visual clients aren’t to blame for that, but they contribute. So many times I’ve asked “and what git commands did that run?” only to receive a dumb stare as a reply.

I think it’s exactly that. They are targeted at bootstrapping projects and prototyping and are, frankly, very good at that job.

Not sure on your use case, but I’ve been using Hetzner for a while and it does what it says on the tin.

Files have formats. Anything “hidden” here is destroyed by conversion to a different font format before redistribution.

There is no way of controlling this from the authors side without some sort of DRM.

Isn’t this easily bypassed by modifying the “hidden” part

You win

It creates an ssh tunnel and then sends the file over http, so … literally no advantage to using this over ssh/scp.

Worse in every way, actually.

I see, not as far as I’m aware. Cool idea though, the hass UI can be a bit limiting sometimes. I’d love to see a workflow view of different automations (automation management in Hass is pretty poor IMO)

I think you want something like Hass configurator?

In my previous house, the v1 prototype was wired straight to the boiler as there was no previous thermostat. In the current house, the v2 is wired to the Honeywell, so one can override the other as they are in parallel.

It was pretty finnicky stuff and I had to scour the internet for decade old wiring guides, but I like that sort of thing so it was good fun.

Every solution is a good solution if it makes your life easy and you have fun installing it!

My setup is a bit different but I had a lot of fun putting it together. I have a D1 mini with a switch hat wired into the boiler.

The D1 runs a tiny web server that lets me turn the heating on and off. Then I have a bunch of ZigBee thermostats around the house that provide a fuzzy average temperature.

Then I have a custom dash in hass that displays pretty much what a hive would display.

Whole setup cost about $20 and has been running nonstop for over 5 years!

The show and tell page is exactly that, show and tell; not a scientific or balanced comparison.

The original challenge only compared JDK solution in this way. Further down there is a link to another repo that does that same across many languages, and uses the same M1 MacBook Pro to run the tests.

To answer your question about environmental and hardware factors - from the repo:

Results are determined by running the program on a Hetzner Cloud CCX33 instance (8 dedicated vCPU, 32 GB RAM). The time program is used for measuring execution times, i.e. end-to-end times are measured.