Censorship sucks and I can’t believe we let an entire country get away with it and still did business with them the whole time.
It is not clear to me that the country would be less censored now and the people there better off if we had refused to do business with them.
(Just to be clear, I am not saying that we handled China as well as we could have over the last few decades, but hindsight is 20-20.)
A Linuxponential curve!
Unless the C++ code was doing something wrong there’s literally no way you can write pure Python that’s 10x faster than it. Something else is going on there.
Completely agreed, but it can be surprising just how often C++ really is written that inefficiently; I have had multiple successes in my career of rewriting C++ code in Python and making it faster in the process, but never because Python is inherently faster than C++.
Genuine question: does anyone actually use Vala for anything? I think that the idea of a language whose OOP system is native GObjects is a nifty one, but I have seen no evidence that it has caught on in any significant way.
Sure, but if you are not regularly expressing code that has the potential of summoning elder gods that will swallow your soul into a dimension of ceaseless screaming then are you really living?
I don’t always use regular expressions, but when I do, I use it to parse XML,
Something that definitely separates me from some of my less experienced coworkers is that, when I sit down and start to implement a plan I came up with in my head, if it turns out that things start exploding in complexity then I reevaluate my plan and see if I can find a simpler approach. By contrast, my less experienced coworkers buckle down and do whatever it takes to follow through on their plan, as if it has now become a test of their programming skills. This makes life not only more difficult for them but also for everyone who has to read their code later because their code is so hard to follow.
I try to push back against this when I can, but I do not have the time and energy to be constantly fighting against this tendency so I have to pick my battles. Part of the problem is that often when the code comes to me in a merge request it is essentially too late because it would have to be essentially completely rewritten with a different design in order to make it simpler. Worse, the “less experienced” coworker is often someone who is both about a decade older than me and has also been on the project longer than me, so even though I technically at this point have seniority over them in the hierarchy I find it really awkward to actually exercise this power. In practice what has happened is that they have been confined to working on a corner of the project where they can still do a lot of good without others having to understand the code that they produce. It helps that, as critical as I am being of this coworker, they are a huge believer in testing, so I am actually very confident that the code they are producing has the correct behavior, even when I cannot follow the details of how it works that well.
Every one had already been launched.
Easy: recognizing bird calls on my phone.
I disagree; I think that we do care about it being popular enough that it incentivizes software and hardware vendors to support it rather than ignoring it.
Sometimes this can help, but lately I’ve been running into the opposite problem where people have been following this advice to such a degree that one cannot ever figure out what is going on without having to constantly jump around to find the actual code involved in doing something.
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.
Because it looks like that functionality uses special compiler functionality only available on GCC and clang?
“This isn’t us encouraging you to gamble-it is us asking you to think about how bad you would feel years from now if you learned that you could have made a ton of money if you had only placed a bet right now! It’s completely different!”
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 feel like the modern name for it would be just “Script”.