![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Warcraft: Orcs and Humans, fam.
Warcraft: Orcs and Humans, fam.
Which costs extra, of course
Sponsored product recommendations cannot be loaded without an internet connection. Please configure a wireless/ethernet adapter and connect to the internet to continue.
Flummoxed!
I mean do you think Fortnite has anywhere near the same level of ability to disseminate information or surveil people as TikTok does?
And actually it makes a material difference that ByteDance is based in Beijing, as opposed to just having Chinese investors. Those social platforms, movie studios, etc., being headquartered in the US is exactly what makes it different. Can Chinese firms apply financial pressure to compel them to act against the interests of US citizens? Yes, of course, and they do.
But that’s categorically different than being legally obligated to comply with the CCP, which ByteDance is.
TikTok is a massively powerful tool of influence and intelligence, in the hands of an adversary that is well understood to proactively meddle with democratic elections.
Yes, obviously the CCP will unabashedly pursue other interference vectors. That should be viewed as more reason to curtail TikTok, not less.
I admire your optimism. I don’t share it, but I admire it.
But they tried so hard…
Worked for me just now. What did it say when you did it?
Me too! I thought it was gonna be fake, or if not, they’d have fixed it already or something, but NOPE! Still works exactly as described.
Ah, you’ve never worked somewhere where people regularly rebase and force-push to master. Lucky :)
I have no issue with rebasing on a local branch that no other repository knows about yet. I think that’s great. As soon as the code leaves local though, things proceed at least to “exercise caution.” If the branch is actively shared (like master, or a release branch if that’s a thing, or a branch where people are collaborating), IMO rebasing is more of a footgun than it’s worth.
You can mitigate that with good processes and well-informed engineers, but that’s kinda true of all sorts of dubious ideas.
You can get in some pretty serious messes, though. Any workflow that involves force-pushing or rebasing has the potential for data loss… Either in a literally destructive way, or in a “Seriously my keys must be somewhere but I have no idea where” kind of way.
When most people talk about rebase (for example) being reversible, what they’re usually saying is “you can always reverse the operation in the reflog.” Well yes, but the reflog is local, so if Alice messes something up with her rebase-force-push and realizes she destroyed some of Bob’s changes, Alice can’t recover Bob’s changes from her machine-- She needs to collaborate with Bob to recover them.
I gotta say, I was with you for most of this thread, but looking through old commits is definitely something that I do on a regular basis… Like not even just because of problems, but because that’s part of how I figure out what’s going on.
The whole reason I keep my git history clean and my commit messages thoughtful is so that future-me (or future-someone-else) will have an easier time walking through it later, because that happens all the time.
I’ll still almost always choose merge instead of rebase, but not because I don’t care about the git history-- quite the opposite, it’s really important to me in a very practical way.
Yeah, tbh the “no timezones” approach comes with its own basket of problems that isn’t necessarily better than the “with timezones” basket. The system needed to find a balance between being useful locally, but intelligible across regions. Especially challenging before ubiquitous telecommunications
Imagine having to rethink the social norms around time every time you travel or meet someone from far away. They say “Oh I work a 9-to-5 office job” and then you need to figure out where they live to understand what that means. Or a doctor writes a book where they recommend that you get to bed by 2:00PM every night, and then you need to figure out how to translate that to a time that makes sense for you.
We’d invent and use informal timezones anyway, and then we’d be writing Javascript functions to translate “real” times to “colloquial” times, and that’s pretty close to just storing datetimes in UTC then translating them to a relevant timezone ad hoc, which is what we’re already doing.
That’s what my rational programmer brain says. My emotional programmer brain is exactly this meme.
I knew what this was going to be before I clicked.
Paywall.
Yeah great point. Or similar cases in the past, even.
Plus just the general sentiment that you’re not businessing right if you don’t something something AI.
Hundreds of dollars were on the line in this case! HUNDREDS!
“Completely new”
Okay, then don’t train it on anything at all and let’s see how it turns out.