I actually did what this article suggests in college. It didn't go well grade wise. However, I had money and time to study and learn about things I wanted to learn. I found that my path often was interwoven with the path of the class, but that the perspective was different and sometimes professors are only grading on perspective--specifically their own. The biggest dividing line is, I suspect, that college does not, at this point teach one how to think. How to think and good grades are not necessarily the same thing at all. I was busy learning how to think, and deciding what could be relegated to "It's in a book, I can find it if I need it" vs "I should memorize this because it will be useful in life for me later".

With all the domain buying out and weirdness, it is my fervent hope people seriously begin reconsidering what it means to have a domain name and to implement other structures to serve out names as opposed to the now, obviously bought and sold, DNS.

I'm not sure "useful content" should be the only metric. Think of all the things you learn in school that you think are useless until later.

The concept of this looks neat, although I am not sure I understand all the use cases yet.

It is a nonprofit version of regular food delivery or grocery delivery ... app !

Uh, that's not how any of that works. Rather, that's how it worked for the article writer.

I understand the basic issues involved here. Both countries are doing very odd things when it comes to information and privacy. However, I feel like making this a "country issue" is really not exactly the right horse to ride on. Rather, I think it should be stated due to the security policies of these governments, we are banning them as information safeholds at this time or something of the sort. Then, the issue is LESS the country, and more the governmental informational policies.

But the problem isn’t storing information in these countries in this case. It’s how these are known to coerce nationals with ties to the homeland into spying for them.

Very neat link. It is true that if you cannot create it, you are simply borrowing someone else's idea and treating it like your own.

> if you cannot create it, you are simply borrowing someone else's idea and treating it like your own.

With the understanding, of course, that this isn't necessarily a bad thing! Understanding is certainly useful, but if it works, then it works, regardless of who built it. Reimplementing, say, a standard library will make you a better programmer, but if just including libraries to do the heavy lifting produces a working system, then that has value too. There are only so many hour in the day; there's value in knowing when to just hand-wave the giants whose shoulders you stand on.

.. at least until the abstraction "leaks".

I believe all abstracts leak at least a little. It all comes down to trade-offs between what risks you want to take.

The timing of this event is curious. Hasn't this been an issue since almost the inception of web browsers?