Lots of abandonware that would not be available otherwise.
Lots and lots of medical, cultural content that should be patrimony of humany but that is currently held hostage by a few privileged who would like to live off it parasitically ad infinitum.
TFA is a total fallacy, there is not even a weak attempt at justifying the conclusion that the DMCA has had any sort of beneficial effects on technology, much less "catalyzing the interactive '2.0' web".
There is as much of a cause/effect relationship between the two as there is between the DMCA being enacted and my balls growing gray hairs the same year.
1 - CIO reads magazine articles equating "Ruby on Rails" and "multicore programming" in the same sentence,
then proceeds to plan new projects with a vision towards "massively distributed MVC, ROR, multicore Web 2.0 social applications",
(code word for slow ruby websites that seem developed by drunken monkeys).
2 - Follows advice regarding "Your ability to talk tech will go a long way to earning the respect of application development professionals."
Usually developers have close to zero tolerance for the inane utterances ("talking tech") of managerial staff,
or as it is call in technical terms, "bullsh!t".
3 - Reads articles that use dehumanizing terms to refer to technical staff ("resources"),
then proceeds to use them to form akward "complimentary" sentences:
"Bob, you are by far my most leveraged, hyper-synergic resource".
- Bonus: CIO fires the company's most experienced engineers, hires an all-Kazakhstani team,
which after six months of working without a formal design produces hundreds of slideshows
that are demoed to customers on MacOSX, extra points if shown on spanking new MacBook Airs.
The elephant in the room is that primitive, unsafe tools endlessly perpetuate these problems. Buffer over/under flows are not difficult problems to solve at language design level, but the common tools We currently use to create applications make diagnosing them and fixing them rocket science. C and C++ (and other lesser used languages) are notorious for being hostile to catching these problems at compile time or debugging them when they happen later. In most cases, the problem goes "unnoticed" affecting unrelated functions in the application downstream and incorrect behavior or crashes happen at a later time when they can no longer be traced back to the original cause.
Spamming would continue to occur despite any amount
of "shunning".
It just generates large amounts of revenue for the spammers.
The real solutions are to fix the major screw up SMTP is
and in the interim punish spammers with jail time
and expropriation to take away spamming's financial incentive.
"Social repudiation" of criminal behavior as a solution
is both pedantic and laughably innefective.
Project Gutenberg, with thousands of works, a project which toady would be illegal,
if the copyright mafia had existed 100 years ago in its current incarnation:
http://thepiratebay.org/torrent/4305494/11_000__Project_Gutenberg_ebooks_for_Sony_Reader_(.lrf)
http://thepiratebay.org/torrent/3467147/Project_Gutenberg_DVD_ISO
http://thepiratebay.org/torrent/3502346/Project_Gutenberg_Jul._06_DVD_-_17500_Ebooks.iso
Linux: .....
http://thepiratebay.org/torrent/4728577/Debian_GNU_Linux_5.0_%5Bx86-64%5D
http://thepiratebay.org/torrent/4726079/Damn_Small_Linux_-PhilCam-
http://thepiratebay.org/torrent/4717761/Mandriva-Linux-Free-Mini-2006-CD.i586
http://thepiratebay.org/torrent/4702548/Mandriva_Linux_One_2008_Spring_KDE_Int_CDROM_i586
http://thepiratebay.org/torrent/4677799/64_bit_Linux_Ultimate_Edition
http://thepiratebay.org/torrent/4669172/linux_for_aspire_one
BSDs:
http://thepiratebay.org/torrent/4697784/fRee_BSD_disc_2_
http://thepiratebay.org/torrent/4697784/fRee_BSD_disc_1_
http://thepiratebay.org/torrent/4296193/PC-BSD_1.5.1
Haiku:
http://thepiratebay.org/torrent/4244595/Haiku
http://thepiratebay.org/torrent/4451598/Haiku-OS_for_VMware
Here's folding at home:
http://thepiratebay.org/torrent/3775577/Folding_home
Lots of abandonware that would not be available otherwise.
Lots and lots of medical, cultural content that should be patrimony
of humany but that is currently held hostage by a few privileged
who would like to live off it parasitically ad infinitum.
1 - Copy your ex employer product
2 - Get sued into bankruptcy
3 - ????
4 - Profit ???
"Compiler", is that the new spelling for "Automated Buffer Overflow Generator" ?.
$ sudo apt-get purge vim && sudo apt-get install emacs
TFA is a total fallacy, there is not even a weak attempt at justifying the conclusion
that the DMCA has had any sort of beneficial effects on technology, much less
"catalyzing the interactive '2.0' web".
There is as much of a cause/effect relationship between the two as
there is between the DMCA being enacted and my balls growing gray hairs the same year.
Here's a link to the definition of Non sequitur: http://en.wikipedia.org/wiki/Non_sequitur_(logic)
Just your typical lame eyeball whoring by Wired, nothing to see move along.
Depends on one's metric. In terms of potential jobs C# is about par with C++, and well below Java.
Hotjobs, title search
Java: 577 jobs
http://hotjobs.yahoo.com/job-search?kwchanged=1&kw=Java&search_title_only=title&ui_kw_type=kwall
C++: 246 jobs
http://hotjobs.yahoo.com/job-search?kwchanged=1&kw=C%2B%2B&search_title_only=title&ui_kw_type=kwall
C#: 213 jobs
http://hotjobs.yahoo.com/job-search?kwchanged=1&kw=C%23&search_title_only=title&ui_kw_type=kwall
Monster, title search
Java: 2016 jobs
http://jobsearch.monster.com/Search.aspx?re=0&brd=1&jsnonreg=1&q=java&rad_units=miles&pg=1&vw=b&jto=1
C#: 889 jobs
http://jobsearch.monster.com/Search.aspx?re=0&brd=1&jsnonreg=1&q=C%23&rad_units=miles&pg=1&vw=b&jto=1
C++: 806 jobs
http://jobsearch.monster.com/Search.aspx?re=0&brd=1&jsnonreg=1&q=C%2B%2B&rad_units=miles&pg=1&vw=b&jto=1
Top three signs:
1 - CIO reads magazine articles equating "Ruby on Rails" and "multicore programming" in the same sentence,
then proceeds to plan new projects with a vision towards "massively distributed MVC, ROR, multicore Web 2.0 social applications",
(code word for slow ruby websites that seem developed by drunken monkeys).
2 - Follows advice regarding "Your ability to talk tech will go a long way to earning the respect of application development professionals."
Usually developers have close to zero tolerance for the inane utterances ("talking tech") of managerial staff,
or as it is call in technical terms, "bullsh!t".
3 - Reads articles that use dehumanizing terms to refer to technical staff ("resources"),
then proceeds to use them to form akward "complimentary" sentences:
"Bob, you are by far my most leveraged, hyper-synergic resource".
- Bonus: CIO fires the company's most experienced engineers, hires an all-Kazakhstani team,
which after six months of working without a formal design produces hundreds of slideshows
that are demoed to customers on MacOSX, extra points if shown on spanking new MacBook Airs.
The elephant in the room is that primitive, unsafe tools endlessly perpetuate these problems. Buffer over/under flows are not difficult problems to solve at language design level, but the common tools We currently use to create applications make diagnosing them and fixing them rocket science. C and C++ (and other lesser used languages) are notorious for being hostile to catching these problems at compile time or debugging them when they happen later. In most cases, the problem goes "unnoticed" affecting unrelated functions in the application downstream and incorrect behavior or crashes happen at a later time when they can no longer be traced back to the original cause.
For kicks check http://en.wikipedia.org/wiki/Buffer_overflow#Choice_of_programming_language
Google search on http://www.google.com/search?hl=en&q=%2Bbuffer+%2B%22overflow%7Coverrun%7Cunderrun%22&btnG=Search
Spamming would continue to occur despite any amount of "shunning". It just generates large amounts of revenue for the spammers. The real solutions are to fix the major screw up SMTP is and in the interim punish spammers with jail time and expropriation to take away spamming's financial incentive. "Social repudiation" of criminal behavior as a solution is both pedantic and laughably innefective.
That vulnerability is purely theoretical.