Easy: recognizing bird calls on my phone.
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.
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’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.
The explanation given to you makes it sound like ==
was deliberately designed to be a more convenient version of ===
, but what actually happened was that ==
used to be the only equality operator in JavaScript, which meant that if you didn’t want it’s auto-coercing behavior then you needed to go out of your way to add additional type checks yourself. Because this was obviously a tremendously inconvenient state of affairs, the ===
operator was introduced later so that you could test for equality without having to worry about JavaScript doing something clever underneath the hood that you weren’t expecting.
Every one had already been launched.