text stringlengths 0 1.22k |
|---|
[5533.94 --> 5534.38] You're screwed. |
[5534.50 --> 5535.20] It's not going to burn down. |
[5536.00 --> 5536.40] Okay. |
[5537.82 --> 5539.38] That sounds like a good game plan. |
[5539.74 --> 5539.90] No. |
[5539.98 --> 5540.80] It won't burn down. |
[5540.80 --> 5544.50] If it doesn't exist in three places, it doesn't exist. |
[5544.62 --> 5548.00] And one of those places has to be not geographically local. |
[5548.74 --> 5554.30] If we had a fiber store somewhere or fiber access to something externally, and it would |
[5554.30 --> 5558.62] take maybe two days to get a, even then, I mean, this is a whole different subject. |
[5558.72 --> 5562.38] We're talking about disaster recovery, which is such a deep topic. |
[5562.38 --> 5565.12] And one that I'm somewhat familiar with. |
[5565.48 --> 5566.28] I don't think it's feasible. |
[5566.28 --> 5570.06] We can go backstage on this, but it's super easy for you to just get that onto a cloud. |
[5570.18 --> 5572.00] And then you're just additive at that point. |
[5572.06 --> 5573.00] You're just adding new episodes. |
[5573.16 --> 5575.50] You don't ever have to do that 10 terabytes again. |
[5576.00 --> 5577.44] But you can pull it down whenever you want. |
[5578.50 --> 5579.92] So, look into it. |
[5579.96 --> 5580.84] We can backstage that. |
[5580.84 --> 5586.90] But let's wrap this one up as we've switched topics away from Apple hardware to why you |
[5586.90 --> 5587.72] need to be in the cloud. |
[5588.46 --> 5589.10] That's right. |
[5590.66 --> 5591.28] All right. |
[5591.46 --> 5594.52] Well, let us know what you think of this episode. |
[5594.70 --> 5599.18] Of course, next time Apple has an event, if y'all like this, we will continue to do this. |
[5599.28 --> 5601.32] We like to nerd out about these things and more. |
[5601.60 --> 5601.82] We do. |
[5601.92 --> 5602.88] Come nerd out with us. |
[5602.88 --> 5607.54] Not just about Apple stuff, but about all things software, open source, developer. |
[5607.54 --> 5609.30] You know, the kind of stuff that we talk about. |
[5609.30 --> 5610.90] ChangeLog.com slash community. |
[5611.84 --> 5615.92] If you're listening to this on the spotlight feed, which is ChangeLog.com slash spotlight, |
[5616.34 --> 5617.80] realize that we have a master feed. |
[5617.88 --> 5619.12] That's where you can get all of our shows. |
[5619.24 --> 5623.12] If you like this show, if you like any of our shows, you will probably like all of our |
[5623.12 --> 5623.38] shows. |
[5623.78 --> 5626.48] So definitely check out ChangeLog.com slash master. |
[5626.82 --> 5627.44] It's nice. |
[5627.50 --> 5632.08] You can remove all those ChangeLog subscriptions out of your podcast app and just put one in your |
[5632.08 --> 5633.84] podcast app and get all of our shows. |
[5634.50 --> 5635.98] I mean, that's almost too good to be true right there. |
[5635.98 --> 5637.50] So check that out. |
[5637.90 --> 5638.92] Closing thoughts, guys. |
[5639.46 --> 5641.04] One feed to rule them all. |
[5641.64 --> 5642.32] Nothing for me. |
[5642.48 --> 5643.38] That's my clothing thought. |
[5643.66 --> 5643.96] One feed. |
[5643.96 --> 5645.18] ChangeLog.com slash master. |
[5645.18 --> 5646.64] Thank you. |
• Microsoft's acquisition of GitHub |
• News broke on Friday, confirmed by Sunday, with a pending regulatory review |
• The deal is worth $7.5 billion, paid in stock |
• Potential implications for the open source community and software development |
• Questions about how this will change GitHub and its users |
• Nat Friedman to take over as CEO of GitHub |
• Microsoft's motivations behind acquiring GitHub |
• Initial reactions to Microsoft acquiring GitHub |
• Impact of change in leadership and ownership on GitHub's open source values |
• Community concerns about loss of independence and potential negative impact on developer ecosystem |
• Optimism vs. skepticism about Microsoft's intentions and ability to maintain GitHub's neutrality |
• Discussion of revenue and financial struggles at GitHub leading up to the sale |
• Consideration of potential changes to GitHub's business model, including IPO or ICO options |
• Microsoft's acquisition of GitHub and its potential impact on the platform |
• Community reaction to the news, including concerns about Microsoft's intentions and the ease of transitioning to alternative platforms like GitLab |
• Patience vs. mass exodus: whether developers should give Microsoft a chance to prove itself or immediately switch to other platforms |
• Nat Friedman's statement that GitHub will continue to operate independently with its own product philosophy |
• Potential changes at GitHub, including whether there will be dramatic changes or just small ones over time |
• Microsoft's acquisition of GitHub and its implications on the tech industry |
• Concerns over Microsoft's control of GitHub code and potential security risks |
• Comparison of Microsoft, Amazon, Google, and other companies as potential owners of GitHub |
• The potential impact of GitHub going public through IPO or ICO |
• Influence of venture capital investments (e.g. Google Ventures' investment in GitLab) |
• Reaction from the tech community and concerns over industry consolidation |
• Discussion of GitLab's reaction to GitHub being acquired by Microsoft |
• Analysis of DHH's tweets on the acquisition, including his criticism of venture capitalists |
• Speculation on GitHub's biggest loss leaders and potential reasons for the company's financial struggles |
• Basecamp's Jason Fried predicting the sale in 2014 and Jerod Santo following him on Twitter |
• Encouragement to be patient and give Microsoft a chance to make the acquisition work, despite initial concerns |
• Community reaction and opinions on the acquisition, including Michael Jackson's comments on Microsoft's control of the modern development stack |
**Adam Stacoviak:** \[00:17\] The best place to open is the question at the start of the weekend, which is on Friday we heard the news, "Will Microsoft buy GitHub?" and we went into the weekend kind of speculating whether that was actually true or false... Some pretty interesting parties reported this, so it seems like... |
**Jerod Santo:** The Verge... |
**Adam Stacoviak:** The Verge... I mean, these are outlets that don't tend to spread not true news yet. I don't wanna say fake news... |
**Jerod Santo:** Well, they were even reporting rumors, so... The Business Insider one on Friday afternoon was a report of people saying things that are going to happen, but there was no confirmation, so that one was very much rumor-ish. |
And then, like you said, the Bloomberg one hit... I mean, Bloomberg is a pretty big news source. And as The Verge hit... And these were on Sunday, right? These were either Saturday or Sunday. |
**Adam Stacoviak:** Bloomberg was on Sunday. Business Insider was the first to break it on Friday. This is like end-of-day Friday, too... Worst time for news, because like "Hey, I'm done. I'm gonna go do my weekend", but no, it was time for news. I think at like 4:30 I logged the "Will Microsoft buy GitHub?" and linked... |
**Jerod Santo:** And here it is... Yeah, Monday afternoon, and the deal is done. |
**Adam Stacoviak:** Yeah. |
**Jerod Santo:** Or at least pending regulatory review. The rumors were true. Whatever leaks were happening over the weekend were legit, and Microsoft has agreed to acquire GitHub for 7.5 billion dollars. |
**Adam Stacoviak:** I think the important thing there too is -- and I'm not sure how nuanced this is, but that's in stock, in Microsoft's stock. So that means it's not a cash deal, right? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.