Indeed, there is quite a lot of data against (Biblical/young-earth) creationism.
Everything from "humans' chromosome 2 is a fusion of two other chromosomes, and we see those two other chromosomes still present in chimpanzees and gorillas and bonobos", which argues for common descent, to "when zircon crystals form, they accept radioactive uranium but violently reject the lead that it decays to, and modern zircon crystals have lead-uranium ratios indicating that they formed billions of years ago", arguing for an old age of the universe. And many, many, many, many other pieces of evidence.
Chromosomal similarity argues for solid engineering principles just as much as it does common decent. Do you have any data to suggest that the almighty did not take a working chromosome 2 (made in their own image, perhaps), and reuse it in these other animals you reference?
> Do you have any data to suggest that the almighty did not take a working chromosome 2 (made in their own image, perhaps), and reuse it in these other animals you reference?
Why would an almighty god leave markers in our Chromosome 2 that look like they are from chromosomes 2a/2b in other apes?
It's not just that there's a huge genetic similarities between the chromosomes. Which there are! Chromosome 2 also has an extra, deactivated centromere, which was used in the copying of the previous chromosome 2b, before the fusion. And, remember that chromosomes typically have telomeres at their ends to keep them from fraying apart. In a fusion event you'd expect some telomeres from the end of the ingredient chromosomes to end up in the middle of the resulting fused chromosome. And this is what we see.
Of course God could have created our chromosome in such a way that it looks very much like the fusion of 2 chromosomes from our shared ancestor with chimpanzees, down to the addition of an extra centromere and telomere region. But why would he?
But, I've also got to say, man, please don't be surprised if I don't respond much. I have no offense intended towards you, but from my perspective, arguing with a young earth creationist is about as productive as arguing with a flat earther. There are about 6 orders of magnitude of difference in age between an Earth that's about 6k years old and 4 billion, and those differences should be readily apparent all over the natural world. And they are! We see an incredible wealth of evidence for an old universe.
But... well, horse and water and all that. I can't expect to change your mind any more than I'd expect to change a flat-earther's mind.
I get that you don’t understand why a creator might do things they way they might have done. I don’t either. But surely you admit your own lack of understanding is not a scientific proof point?
If I said “I don’t understand why the big bang happened”, would that be evidence it didn’t?
Ok. Not really sure what you’re getting at here tbh. But I assume you have read some paper that said that this tree had some isotope of some material, and you’ve taken that to mean the earth is older than 6,000 years?
No, you have data that you’ve interpreted to mean that the trees are older than 6,000 years old. What is that data, and why have you interpreted it in that way?
It's not faith when a bunch of different people all did the homework and came up with the same answers. Especially when they're all part of a system that rewards new discoveries, and they did the homework in very different ways.
There are mountains (both literal and metaphorical) of evidence for an old earth. The only evidence for a young earth is a book which contradicts its own creation story in the first two chapters.
At least they’re forward about it - I’ve lost count of how many bike accessories claimed to be USB C, but they only charge when connected to their specialized cable that converts from USB A to C.
Double-sided USB-C connections require a handshake before sending voltage. USB-A ports can have the 5v line active at all times. Cheap USB C gadgets often don't make the handshake, they just use it as a 5V input, necessitating an A to C cable.
I think you're overstating this. The "handshake" is purely 2 simple resistors correctly installed. The problem is a lot of folks do it wrong for various reasons, most likely never testing with anything more than type a to type c cables.
If you add 5.1kΩ pulldown resistors on the CC lines for USB-C, you can get the standard 5V without a handshake although current may be limited by some chargers without negotiation.
One of the many deficiencies of usb-c (who knows what power your cable supports, charger supports, if you accessory will charge, of it will connect at all)
There is no handshake, all that's needed are two 5.1 kΩ pulldown resistors. By omitting them the manufacturer saved all of about 0.1c and made their device incompatible with compliant usb-c chargers.
I am not sure that their goal (<200mb ram) is really related to their approach (using a built in rendering engine for the same exact source material) at all.
One could (and I would) argue that they achieved that despite their web-tech-based UIs, not because of. At least those of us who were around for the days when most apps were still native, do notice and get bothered by the input lag, for instance.
Slack is, in fact, one of the worst offenders. It is so incredibly sluggish. And it doesn't need to be, when I compare it to the speed (and memory consumption) of Pidgin with the Slack plugin.
Async comm in web apps often keeps them responsive when the native app experience is: spinner... spinner... spinner... spinner... lock up the window and you can't move it... spinner... spinner... spinner... "should i reboot the whole machine first thing or should i try killing the app with task manager and starting again?"
Their killer feature, being able to share a link with anyone at the company and instantly collaborate (live!), is made far easier on the web platform vs native. “The input lag” frankly does not matter in the big picture, imo.
Interesting, at first pass I’d say the source availability has little to do with the topic at hand. But on second thought it might be rather significant. No company would finance making 2x identical cross platform apps, but if you have a pool of OS folks who are free to contribute at their leisure, the calculus changes a bit.
But isn't the whole point of linked article is that author doesn't like regular apps because it lacks control over UI and functionality compared to Web apps?
Being open-source is kinda even better in that regard.
Yes, they do. OGs remember that Facebook circa 2012 had navigation take like 5-10 seconds.
Ben Horowitz recalled asking Zuck what his engineer onboarding process was when the latter complained to him about how it took them very long to make changes to code. He basically didn't have any.
If it's true that nobody is getting promoted for improving web app performance, that seems like an opportunity. Build an org that rewards web app performance gains, and (in theory) enjoy more users and more money.
Can you point to any good plots or schemes they’ve pulled off in the past? We’re starting our sixth year with this guy at the helm and so far it’s nothing but a cavalcade of stupid.
He simply wanted a quick strike, not a war. He thought Iran would capitulate and not take any actions after the strike.
His thinking did not even change. Just read this 2021 article about preventing Trump from starting a war with Iran: https://www.newyorker.com/news/letter-from-bidens-washington... Trump is predictable. What he thought in 2021 was similar to what he thought in February 2026.
> Trump did not want a war, the chairman believed, but he kept pushing for a missile strike in response to various provocations against U.S. interests in the region. Milley, by statute the senior military adviser to the President, was worried that Trump might set in motion a full-scale conflict that was not justified. Trump had a circle of Iran hawks around him and was close with the Israeli Prime Minister, Benjamin Netanyahu, who was also urging the Administration to act against Iran after it was clear that Trump had lost the election. “If you do this, you’re gonna have a fucking war,” Milley would say.
First response: It doesn't matter if I use copilot right now. It matters if I will ever use copilot in the future. Opting-out is future-focused. What if I said "no, I don't use copilot, so I don't need to opt out", then a year from now start using copilot, completely forgetting about this whole debacle? That's the evil of opt-out. My inaction only benefits them, never me.
Second response: Maybe? I press the little button to auto-generate commit titles and messages that showed up in my Github Desktop. Does that count?
I'm asking sincerely. I don't "use Copilot" as in using it in VS Code or while writing code, so I'm honestly not sure if I am.
Do we get a choice? I did not ever explicitly enable it yet GitHub's web UI by default uses copilot to autofill my web-based edit commit messages. It also shows up on the home screen by default now.
I'm pretty sure if you use the site you're using GitHub Copilot in some way, so your question becomes irrelevant.
Or that it is somehow less “scary”?
reply