But the biggest piece of advice is to never guess about where things are slow. Measure them and then fix the slow parts. Don't change a thing until you've benchmarked it.
PHP security doesn't suck any worse than ASP or Perl
Have you even heard of "taint-mode" in Perl? It's a built security mode to make sure no user supplied data can ever make it's way into sensitive areas (system calls, filenames, etc) without have been "untainted" first. I'd say that's a pretty big difference in the security of the languages.
I have FC5 running on my laptop and use it as my development server for almost all of my work. All developers at my $job do something similar. We use SVN to manage the code and QA servers to test it on "real" hardware.
If you can't run you're server's OS as your primary OS, what's wrong with dual booting?
Why would it go to the RIAA? That's not how radio, clubs, restaurants, etc work now, so why would should P2P be any different. They use PRO's which monitor all kinds of outlets and make sure that the money is even distributed correctly to independent artists and labeled. You don't have to be affiliated with the RIAA, just a PRO. There are 3 big ones in the US, so you just pick one.
Actually PROs are in charge of all the complicated distribution issues. They already do it and it's already pretty complicated with restaurants, radio stations, clubs, etc. Artists (or song writer's) receive the bulk of these fees since it's not about recordings, but about the actual songs.
The task would be momumental, but could fit into their existing framework. PROs don't give money based on album sales, but based on how frequently songs are played. They don't perform exact counts but do a lot of survey work and extrapolation. With the digital realm, downloads and and sharing could be tracked (people wouldn't try so hard to make them difficult to track if they knew it wasn't illegal) exactly and artists compensated for their work from the fees collected from ISPs which are then passed on to users.
Even if this fee were mandatory (which it's not) it's no different than the 'fee' you pay when you go to a restaurant that plays music. Regardless of whether you listen or not, the restaurant still has to pay a fee to a PRO (Performance Rights Organization) and they pass the bill onto you.
To me it makes sense that the laws that govern the distribution of music through the air waves be similar to the laws that govern music through the ethernet.
Re:Who Uses Perl Anymore?
on
Pro Perl Debugging
·
· Score: 2, Informative
Tell me, what major sites have been build using Ruby?
Slashdot Mirror
Scalable Internet Architectures by Theo Schlossnagle http://www.amazon.com/Scalable-Internet-Architectu res-Developers-Library/dp/067232699X.
Great tutorial at OSCON about it too.
But the biggest piece of advice is to never guess about where things are slow. Measure them and then fix the slow parts. Don't change a thing until you've benchmarked it.
Have you even heard of "taint-mode" in Perl? It's a built security mode to make sure no user supplied data can ever make it's way into sensitive areas (system calls, filenames, etc) without have been "untainted" first. I'd say that's a pretty big difference in the security of the languages.
I have FC5 running on my laptop and use it as my development server for almost all of my work. All developers at my $job do something similar. We use SVN to manage the code and QA servers to test it on "real" hardware.
If you can't run you're server's OS as your primary OS, what's wrong with dual booting?
Why would it go to the RIAA? That's not how radio, clubs, restaurants, etc work now, so why would should P2P be any different. They use PRO's which monitor all kinds of outlets and make sure that the money is even distributed correctly to independent artists and labeled. You don't have to be affiliated with the RIAA, just a PRO. There are 3 big ones in the US, so you just pick one.
Actually PROs are in charge of all the complicated distribution issues. They already do it and it's already pretty complicated with restaurants, radio stations, clubs, etc. Artists (or song writer's) receive the bulk of these fees since it's not about recordings, but about the actual songs.
The task would be momumental, but could fit into their existing framework. PROs don't give money based on album sales, but based on how frequently songs are played. They don't perform exact counts but do a lot of survey work and extrapolation. With the digital realm, downloads and and sharing could be tracked (people wouldn't try so hard to make them difficult to track if they knew it wasn't illegal) exactly and artists compensated for their work from the fees collected from ISPs which are then passed on to users.
Even if this fee were mandatory (which it's not) it's no different than the 'fee' you pay when you go to a restaurant that plays music. Regardless of whether you listen or not, the restaurant still has to pay a fee to a PRO (Performance Rights Organization) and they pass the bill onto you.
To me it makes sense that the laws that govern the distribution of music through the air waves be similar to the laws that govern music through the ethernet.
Tell me, what major sites have been build using Ruby?
I can list several very high volume sites/applications that use Perl.