It's still very costly to replace code. The hard part of migrations isn't usually the churning out of code.

Same, I love fixing bugs

Fishing licenses aren't actually free but at least they're cheap

Fishing equipment isn't free, and you will have recurring (though small) costs in hooks and line, at least.

Coffee, similarly

Maybe because the laws for giving away money are complicated? There’s tax and reporting burden

Seems like it could mean death for Columbia as a desirable college honestly

Probably not, they'll just pump up international student numbers to recoup and basically gut the domestic student experience. There's near infinite demand for American universities overseas even now.

I think you're wrong. I know several bright students that have decided to not go to the US now given the persecution and targeting of international students.

You can't expect the brightest minds to study in an authoritarian country.

Intl students are not mad. Who is going to pay the US intl student premium, to add the Columbia tag. Intl students are paying for very specific future life paths.

Really? That demand is rapidly dropping, for all kinds of terrifying reasons

No

> You do not have to pay this back.

There's a very big key difference from standard small business here

Do you all forget the web pre chrome? Google and Chrome forced browser vendors to do better by standards in the first place. Google’s stewardship forced browser vendors to compete like never before.

I don't remember Google doing that. What I remember from that time is a browser war happening between the power players in mobile with iOS, Android and Windows Phone.

I would attribute the improvement in browser standards support to the finalization of the HTML5 spec by the W3C in 2009, which led to browser vendors harmonizing their feature set. We still needed jQuery to ensure cross-browser support, and floats and polyfills to get sites to work on mobile. That ended when browsers harmonized ES2015 support and built in support for flexbox and grid.

> I don't remember Google doing that.

They didn't

> I would attribute the improvement in browser standards support to the finalization of the HTML5 spec by the W3C in 2009

I would attribute it to IE losing market share. It was always IE... and <the rest>.

> repositories that were once public but later made private

Or maybe the post needs a better title

I suppose they could sue themselves for accidentally making their own private data public.

Or the wronged parties were those who entrusted someone else not to put their data (e.g., closed software, NDA material, proprietary internal info shared with contractor, access control secrets) in a public repo.