Repeating my other reply verbatim yet again as you keep copying and pasting the same exact comment:

First, to be clear, this isn’t so much “press” as a blog entry. Second, there are only so many mentions of “rust cultists” and “my rust” I can read in a blog before losing interest.

Repeating my other reply verbatim as you just did the same:

First, to be clear, this isn’t so much “press” as a blog entry. Second, there are only so many mentions of “rust cultists” and “my rust” I can read in a blog before losing interest.

First, to be clear, this isn’t so much “press” as a blog entry. Second, there are only so many mentions of “rust cultists” and “my rust” I can read in a blog before losing interest.

Yes, and that is my point: unless you wearing a seat belt somehow made the accident more likely to happen, it really doesn’t seem like manslaughter applies here.

According to this page, you could attempt to argue “lack of causation” if there was no connection between you not wearing a seat belt and your passenger getting killed.

I think you meant to say:

I knew it, no comments yet, everyone’s a sheep

Choosing to have a child later on generally has fewer negative consequences than unchoosing a child you have already had.

Have you really not heard of it? It is a new architecture that is a bit better than x64_64.

Every one had already been launched.

Easy: recognizing bird calls on my phone.

Because some of us are bitter at the trees for generating so much pollen at this time of year and want revenge.

Spotted the INTERCAL programmer.

Yeah, I miss living in Australia where you didn’t have your own waiter but on the other hand that meant that it wasn’t rude to flag down any of the wait staff if you need anything rather than being restricted to having to go through a single person.

Ah, yes, the good old git off --my lawn command.

Yes. My rule of thumb is that generally rebasing is the better approach, in part because if your commit history is relatively clean then it is easier to merge in changes one commit at a time than all at once. However, sometimes so much has changed that replaying your commits puts you in the position of having to solve so many problems that it is more trouble than it is worth, in which case you should feel no qualms about aborting the rebase (git rebase --abort) and using a merge instead.

The way I structure my commits, it is usually (but not always) easier and more reliable for me to replay my commits one at a time on top of the main branch and see how each relatively small change needs to be adapted in isolation–running the full test suite at each step to verify that my changes were correct–than to be presented with a slew of changes all at once that result from marrying all of my changes with all of the changes made to the main branch at once. So I generally start by attempting a rebase and fall back to a merge if that ends up creating more problems than it solves.

I’ve only met one other person that knew who/what Dvorak was/is, and also reportedly used that keyboard layout.

I experimented with it in University–I actually got a screwdriver and pried up and rearranged all of the keys on my keyboard within a week or so of starting–but after graduating I noticed that I was still slower at typing on Dvorak than I was on QWERTY so I gave up and changed back.

I’m not the one you asked, but what I like isn’t really about PHP itself, but the fact that I can get dirt cheap hosting with PHP and MySQL.

Oh, wow, I looked a little into this and hosting really is dirt cheap! That is a benefit that I genuinely was not expecting.

Either way, it’s an awesome language, happily been using it for decades now

Mind taking a moment to share why you like it? I am not very familiar with it.

A truly fantastic update for our times!