4 ms·

Running a server isn't demoing something cool in biology, coming up with something cool to demo in deep learning, or starting a blog. If these people are going

Running a server isn't demoing something cool in biology, coming up with something cool to demo in deep learning, or starting a blog. If these people are going to spend their time doing innovation in biology, hacking on deep learning, or writing about physics, they shouldn't be spending their time running a server or configuring IP.

dheera 9y ago
Why not? It's 2017, and it's super-easy to spin up a server and code something cool to demo something you did in any of these fields. Or spin up an MVP of a random product idea you have. Never tell anyone that "they should not be doing something" when they want to. That too stifles innovation. The idea is to create a low-friction path for people to do what they actually want to do. NAT is technological friction. Telling people that "they should not do something" is also friction. What about even just learning to write apps in your own time? I built dozens of demo websites while I was a student there. A few were slashdotted. Having IPv4 addresses and access to bandwidth from my bedroom was a massive blessing. The problem isn't configuring IPv6. The problem is without IPv4 you cannot easily make a server that is guaranteed accessible from anywhere in the world, by anybody. That's not a problem that most MIT students are in a position to solve or innovate in a short time. At least not without spending money for an AWS instance that frankly most undergrads don't have the money for. Innovating in making an HTML5 app to demo your cool bioinformatics project on the other hand is a weekend hackathon deal. And servers are basically free at MIT. You can just pick up and assemble them up off of reuse when labs throw away various parts. Plug them into your gigabit ethernet socket in your bedroom, get an IPv4 address, and you're up and running in less than an hour.
- thwarted 9y ago
  Why not? You're the one who said people should be spending their time doing innovation in biology, hacking on deep learning, and starting a blog, rather than learning how to configure and deal with networking. If anyone wants to do those things, they can do them now and not have to worry about installing and configuring servers and dealing with IP networking. Or they can work on innovating in networking. The fact is, however, that no one is going to say "if my server wasn't IPv6 only, then people would read my blog". They'll most likely be saying that because there's a lot of other content to consume on the Internet, and attention is limited. And if that is the case, they can get a $5 a month digital ocean instance, or one from any number of other providers, accessible over IPv4 and IPv6, and serve both protocols to entire Internet. Also, chances are, the audience for a physics student's blog is most likely at some university, which has a good chance of having a working IPv6 stack; especially now that MIT is going wholehog on IPv6.

dheera 9y ago

Why not? It's 2017, and it's super-easy to spin up a server and code something cool to demo something you did in any of these fields. Or spin up an MVP of a random product idea you have. Never tell anyone that "they should not be doing something" when they want to. That too stifles innovation. The idea is to create a low-friction path for people to do what they actually want to do. NAT is technological friction. Telling people that "they should not do something" is also friction. What about even just learning to write apps in your own time? I built dozens of demo websites while I was a student there. A few were slashdotted. Having IPv4 addresses and access to bandwidth from my bedroom was a massive blessing. The problem isn't configuring IPv6. The problem is without IPv4 you cannot easily make a server that is guaranteed accessible from anywhere in the world, by anybody. That's not a problem that most MIT students are in a position to solve or innovate in a short time. At least not without spending money for an AWS instance that frankly most undergrads don't have the money for. Innovating in making an HTML5 app to demo your cool bioinformatics project on the other hand is a weekend hackathon deal. And servers are basically free at MIT. You can just pick up and assemble them up off of reuse when labs throw away various parts. Plug them into your gigabit ethernet socket in your bedroom, get an IPv4 address, and you're up and running in less than an hour.

thwarted 9y ago
Why not? You're the one who said people should be spending their time doing innovation in biology, hacking on deep learning, and starting a blog, rather than learning how to configure and deal with networking. If anyone wants to do those things, they can do them now and not have to worry about installing and configuring servers and dealing with IP networking. Or they can work on innovating in networking. The fact is, however, that no one is going to say "if my server wasn't IPv6 only, then people would read my blog". They'll most likely be saying that because there's a lot of other content to consume on the Internet, and attention is limited. And if that is the case, they can get a $5 a month digital ocean instance, or one from any number of other providers, accessible over IPv4 and IPv6, and serve both protocols to entire Internet. Also, chances are, the audience for a physics student's blog is most likely at some university, which has a good chance of having a working IPv6 stack; especially now that MIT is going wholehog on IPv6.