8,465 karma · joined November 4, 2017
It's never the compiler until it's the compiler. Just didn't expect it during some simple fun coding at home. :)
Obviously you should have enough technical knowledge to do a rough sanity check on the reply, as there's still a chance you get stupid shit out of it, but mostly it's really efficient for getting started with some tooling or programming language you're not familiar with. You can perfectly do without, it just takes longer. Plus You're not dependent on it to keep your stuff running once it's set up.
So they might have saved all that time, but what's gonna be the impact of incorrect reimplementation? What does that software do?
But still, you could do the same for stun, turn, sdp. Disallow local host.
But that's not the case. We're not all cosmopolitans traveling the world all the time. For anyone living in a timezone where 00:00 happens when most people are asleep, there'd only be one word for tomorrow, as it'd be synonymous for "after date change" and "after the next sleep cycle". There would be no other word, because there is no need for that. Except in circles where coordinating meetings with people across the globe happens on a regular basis. But we already got that figured out by explicitly naming the time zone or using UTC.
The vast majority of people don't have to deal with this, so having the date change at night is just more convenient, as it completely avoids this ambiguity in day to day life.
But obviously as a nerd you get hung up on that one aspect and go "but imagine we had only one timezone, we could just say 13:00 and there'd be no ambiguity, no chance for a misunderstanding, it would be so much more efficient and coherent!"
> The argument against abolishing time zones always seems to assume that humanity would be incapable of adapting to a time zone free world.
Again, you need to take a step back and try to look at this from the average person's pov, not as a scientist trying to find the optimal solution for a problem 99% of people don't have. And "people would be able to adapt to this" Is a pretty weak argument. You could probably also change the clock itself so that there's 63 seconds in a minute, 59 minutes in an hour, and 195 hours in a day. I'm sure people could adapt to this. Doesn't make it a good argument.
On the other hand, just imagine the sheer chaos this switchover would cause worldwide, for what, marginal gains in convenience for a miniscule amount of people.
It reminds me of "that guy" who constantly wants to refactor half the codebase because something would look a little cleaner then, and if you let them, they'll end up refactoring the same part of the code over and over again every six months because they had another idea how to make it even more streamlined and elegant. And then someone else comes in wanting to implement a simple feature, but is greeted with an incomprehensible construct, while the refactoring-guy is repeatedly and excitedly reassuring them that it's "really simple and intuitive once you get the hang of it".
Also, I've run into a deadlock issue a while ago with mariadb. Skimmed their bug tracker and there are a couple similar reports, some remaining open, other getting fixes like "well I changed stuff around and I think it might solve the issue". An emerging pattern was that they think there might be a locking issue, but they're not sure, and any deadlock they can reproduce under rr (or whatever that recording debugger is called) is, according to them an issue with rr itself and a false positive. It gave me serious "we're just yoloing it" vibes. I understand it's not a trivial code base and they're probably understaffed, and I still prefer it over MySQL merely because of who owns that project but still, it left a weird impression.
I know it's moving slower and in a lot of ways it's inferior to mysql, but at the same time that would make it even better to have some contributions like this.
I did that too in the very beginning but soon realized that you need subtle, non-intrusive rules that make your day ever so slightly more comfortable but don't get in your way if you do something unexpected.
The problem is that HA gives you a million possibilities while Google and apple don't, and most techies just fall for it and start over engineering the shit out of it only to annoy the rest of their family to no end and then getting rid of everything again.
And yes, not using that tech is not a better approach then, but not worse either. But better in the way that Intel doesn't need to build convoluted shit into their cpus that might actually worsen security through exploits.
Case in point: TeleMessage. Supposedly E2E-Encrypted message archival turns out to be a plain text database on some servers. Surprised Pikachu face.
Another guess would be because that's where the enter key/send button is, so you can kinda see the message as coming from there...