Well I certainly see why no one takes this forum seriously. No, servers, personnel, or bandwidth don't go to zero or anywhere near zero.
Amazon will happily sell you a 10MB high-quality audio track for $0.89. That's likely about 1/100th the price-per-megabyte that they're charging with this bookstore. A $0.10 book would be pretty damn close to zero
They're an internet company. Their site can be viewed in China whether or not they employee people there. So yes, pull the employees out and refuse information requests like this. If the refusal causes China to block yahoo.com, too damn bad
OS X can run on AMD fine. The fact is Apple prevents OS X from running on unverified x86 hardware to lock customers into Apple hardware. You can be for or against that decision, but it has absolutely nothing to do with the GP's point that "Most of the complaints about Vista are in relation to drivers" and that OS X somehow skates those issues to such an extent that it's unable to run on anything but a single x86 manufacturer's hardware
As the parent points out this is ludicrous - especially if you count the iPhone, OS X supports a much broader range of CPUs than Microsoft. I don't doubt Microsoft has spent more time addressing driver compatibility than Apple has, but there are a number of other issues in play, such as Apple's willingness to break backwards compatibility for the sake of cleaner APIs and a saner OS, and their utilization of third-party components wherever possible - BSD tools/Mach/KHTML/DTrace/ZFS(soon)/etc. Microsoft has full-blown NIH syndrome, with the end result that they go out and build everything from scratch, with 90% of it being worse than open source solutions. They're getting crushed by their own proprietary codebase and enormous level of legacy support
The Netbeans 6 dev/beta releases have been quickly becoming the best Ruby/Rails IDE, bar none. Used to be Eclipse/RadRails for Windows/Linux, and Textmate for Mac. Netbeans has completely blown Eclipse out of the water for Ruby development as Aptana+RadRails has stagnated. Textmate isn't really an IDE to begin with, it's quite a unique and useful text editor. But the pace and quality of Netbeans Ruby support would be very tough to match, so even many hardcore Textmate Mac users have switched to Netbeans
Along with JRuby and Glassfish Rails, Netbeans is proving that Sun is dead serious about being the best Ruby game in town. They've got competitors in all three areas, but they are quickly becoming a major force in the Ruby community
We have evidence of an NSA-controlled room in the Folsom Street AT&T facilities in San Francisco. We have evidence that AT&T diverted copies of everyone's Internet traffic into that room. And we know that there's very sophisticated equipment in that room that is capable of doing real-time analysis analysis of the Internet traffic that is getting routed into there.
Yes but look at how well Apple pulls off these enormous transitions. They've gone from 68k -> PPC(w/ 68k emulation), from Classic Mac OS -> Rhapsody/OS X(with a completely new codebase from NeXT, but still a program to run "Classic" apps), from 32 bit -> 64 bit PPC, and now PPC -> Intel again with an emulation layer
Guess what though: * 68k emulation: gone * Classic Mac OS: gone * 32 bit PPC(as of Leopard): gone
And eventually PPC will be gone too. Apple has pulled off all these transitions without pissing off their users more than necessary but also without dragging behind huge reams of crufty old code. If MS did a ground-up rewrite of Windows as Apple did with Mac OS, they would likely end up with a much better OS than they have today. Apple would never have been able to get the old Mac OS codebase up to the quality they've got in OS X. They tried, with Copland, and failed miserably. The only real difference is Microsoft has the endless piles of money to just "git 'er done" no matter how poor the end result
And so now they're stuck with an awful unmaintainable mess of an operating system and not a whole lot of good options. I would suggest looking at what Apple did with continuing minor mostly-maintenance releases of the old OS(see: Mac OS 9) while pushing most of their effort into NeXT/Rhapsody/OS X, and easing users into the new OS over a slow transition period. New adopters are less likely to complain about usability and performance issues when they know it's a 1.0 and things will get better. OS X didn't start firing on all cylinders until maybe 10.2
Of course, Microsoft should have begun that process 5 years ago and used XP as the maintenance OS. Instead now they have a trainwreck release that they can't simply maintain - everyone hates it
There's nothing wrong with using tools that have been around for a while, and your choice of tools may be completely appropriate and optimal for the type of work you're doing. But the fact that you can accomplish meaningful work with the set of tools you use really means very little. A horse and buggy is a meaningful tool, as is a honda civic. But simply because your horse and buggy can bring you from point A to B, it doesn't follow that you should scoff at all the people telling you it's "so 100 years ago"
See also, the Blub Paradox. Almost everyone has experienced the paradox for themselves, but its a constant struggle to not continue committing it again and again
If you're still using RadRails/Aptana for Rails development, I'd very strongly recommend downloading the Netbeans 6 beta. The Netbeans people have come a long way for Ruby development over a very short period of time. There's still some hiccups in the app, but it shows a lot more promise than the Aptana everything-to-everyone crapfest (I used RadRails/Aptana for about 18 months)
Read through this extensive feature review and try not to drool - Ruby/Rails tooling is really starting to move forward
Eclipse + Java + CVS, woohoo. Welcome to three years ago. How about instead let's try: * Textmate / Netbeans * Ruby (Rails or Merb for web programming) * SVN or Git for source control
Their project list doesn't seem to have been updated in quite a while. Many of their recent papers seem more focused on how to scale and utilize the type of computing cluster they have than they relate to any sort of medical progress
I'm not dismissing the contributions to the study of computer science, but the stated goals of the project are:
The Folding@Home project ("FAH") is dedicated to understanding protein folding, the diseases which result from protein misfolding and aggregation, and novel computational ways to develop new drugs in general. Here, we briefly describe our goals, what we are doing, and some highlights so far.
We feel strongly that a distributed computing project must not just run calculations on millions of PC's, but d.c. projects must produce results, especially in the form of peer reviewed publications, public lectures, and other ways to disseminate the results from FAH to the greater scientific community. Below, we also detail our progress in these areas as well.
I doubt the cloture vote itself could be considered treason. I would be in favor of punishing anyone voting in favor of a grossly unconstitional bill like the MCA though. Sadly a number of blue-dog Democrats voted for that, and Chafee was the only Republican not to. Disbarring all 65 of those "yea" votes from ever serving in public office again would be appropriate
This Congress has been having cloture votes at twice the rate of any Congress in history. Please don't try to pretend this is standard operating procedure, especially after the months-long hissy fit the media went along with a couple years ago when the Democrats were getting half as many
After a resounding defeat in the last election signaling a widespread popular desire for change, the Senate Republicans have been threatening filibuster on any significant piece of legislation, most with broad public appeal. The Democrats primary failure is not taking the gloves off and forcing the GOP to actually filibuster the bills, rather than just signal the intention to do so
That was a proposed amendment to the Constitution that was never ratified - i.e. it is not US law. Do you have the slightest idea what you're talking about?
My guess as to the problem is the RIAA would tell Apple two things: 1) allowing "ripping" of ringtones from iTMS-bought songs would be illegal, Apple would have to charge 2) they would prefer not to allow any ripped ringtones
After #1, Apple themselves would be in a tough position because they would have to provide a tool that says "you can rip whatever ringtones you want, unless you bought the song from us." So yes I believe Apple ultimately cast the final vote on non-iTMS ringtone ripping, but their only other choice would have been essentially screwing over their own iTMS customers - not an enviable position to be in
Article summary quotes text that is then shot down a paragraph later as incorrect. Try this instead:
Ask Not For Whom the Ring Tones.
Writing about Apple's iTunes ringtones, John Gruber of the Daring Fireball cited Engadget, which reported that "the RIAA wanted to be able to distribute ringtones of its artists without having to pay them big money to do so (surprised?), and it won a decision last year before the Copyright Office saying that ringtones weren't 'derivative works,' meaning they didn't infringe on the copyright of the songwriter."
Engadget, known for shooting from the hip rather than the brain, didn't really understand whole story. From its report, Gruber concluded, "So if you have the right to play a song, you have the right to use it as a ringtone on your phone."
Gruber blamed a "complicated, confusing mess of a ringtone policy" on Apple, and suggested the company should have simply handed out tools to create ringtones from any users. Incidentally, that's apparently what Apple was going to do back in January.
Derk Nek of Epplegacks explained that--unfortunately--what the RIAA actually won in the case cited by Engadget was instead the right to collect money for ringtones without distributing those fees to the artists they represent. There was no establishing that ringtones are not protected intellectual property, so the RIAA will continue collecting royalty fees, because distributing songs or portions of songs requires mechanical rights. Playing a ringtone might also--in the mind of the RIAA and the letter of the law--require performing rights.
That's ~3 requests per second. I work with a single vertical application that handles roughly three times that at peak times.
You compared per-day vs. peak times, nice. At peak times the highest-traffic Rails app is about 20/second. Still not very many, well gee...its more than 99.9% of web sites will ever need to do, so complaining that Rails can't scale is a little silly
Can you describe some of your experiences scaling Rails? I'm currently serving up to 250,000 requests per-day with a handful of Rails apps, so I'm wondering where you hit the breaking point and had to switch to the crapfest that is PHP
There's no doubt that Ruby and Rails especially are much slower in execution time than comparable code written in PHP. That said, the PHP code would be 2-10x as verbose, take far longer to write, and be far less maintainable. With Rails you just throw more hardware at it and it will scale as far as you need to. If you're running up against real walls in Rails scaling, try Merb. If you're just a PHP n00b who wouldn't know decent OO-code if it punched you in the face, then by all means stick with the Personal Home Page language
Sounds similar to the experimental (human) treatment being practiced in China. There's been a lot of skepticism about why/how such a thing could work, but according to a lot of people who've gone through the treatment it does restore some amount of functionality
No, the event is a B-52 landing with unauthorized nukes.
According to the FAS, the last time a bomber was loaded with nuclear weapons was over 15 years ago. The last time a bomber flew with nuclear weapons was nearly 40 years ago. So it would appear GP was correct, and you are not
Maybe the BSD license should be altered to say code can be closed-sourced but not open-sourced without retaining the original BSD license(adding an additional license to the code would probably be fine). Seems like BSD's intent is to allow code to be used anywhere(including closed-source) without the viral effect, and its understandable that taking the code, modifying it, and applying a viral license to it would anger some developers
They're not throwing away their entire company. My guess is any company is making approximately zilch on BluRay/HD-DVD at this point. The studios don't have a lot to lose either way - if they pick the wrong horse, just switch later on. Why not take the 100 mil?
Slashdot Mirror
There is no gun pointed at Microsoft's head, they're fully on board with HD-optical DRM, though they may haggle over pointless specifics
Well I certainly see why no one takes this forum seriously. No, servers, personnel, or bandwidth don't go to zero or anywhere near zero.
Amazon will happily sell you a 10MB high-quality audio track for $0.89. That's likely about 1/100th the price-per-megabyte that they're charging with this bookstore. A $0.10 book would be pretty damn close to zero
They're an internet company. Their site can be viewed in China whether or not they employee people there. So yes, pull the employees out and refuse information requests like this. If the refusal causes China to block yahoo.com, too damn bad
OS X can run on AMD fine. The fact is Apple prevents OS X from running on unverified x86 hardware to lock customers into Apple hardware. You can be for or against that decision, but it has absolutely nothing to do with the GP's point that "Most of the complaints about Vista are in relation to drivers" and that OS X somehow skates those issues to such an extent that it's unable to run on anything but a single x86 manufacturer's hardware
As the parent points out this is ludicrous - especially if you count the iPhone, OS X supports a much broader range of CPUs than Microsoft. I don't doubt Microsoft has spent more time addressing driver compatibility than Apple has, but there are a number of other issues in play, such as Apple's willingness to break backwards compatibility for the sake of cleaner APIs and a saner OS, and their utilization of third-party components wherever possible - BSD tools/Mach/KHTML/DTrace/ZFS(soon)/etc. Microsoft has full-blown NIH syndrome, with the end result that they go out and build everything from scratch, with 90% of it being worse than open source solutions. They're getting crushed by their own proprietary codebase and enormous level of legacy support
The Netbeans 6 dev/beta releases have been quickly becoming the best Ruby/Rails IDE, bar none. Used to be Eclipse/RadRails for Windows/Linux, and Textmate for Mac. Netbeans has completely blown Eclipse out of the water for Ruby development as Aptana+RadRails has stagnated. Textmate isn't really an IDE to begin with, it's quite a unique and useful text editor. But the pace and quality of Netbeans Ruby support would be very tough to match, so even many hardcore Textmate Mac users have switched to Netbeans
Along with JRuby and Glassfish Rails, Netbeans is proving that Sun is dead serious about being the best Ruby game in town. They've got competitors in all three areas, but they are quickly becoming a major force in the Ruby community
Come on, far better was "Fry, I will always remember you. MEMORY ERASED"
I was never there for Chips & Dips, but wasn't there a time Slashdot existed before the current user scheme?
Yes but look at how well Apple pulls off these enormous transitions. They've gone from 68k -> PPC(w/ 68k emulation), from Classic Mac OS -> Rhapsody/OS X(with a completely new codebase from NeXT, but still a program to run "Classic" apps), from 32 bit -> 64 bit PPC, and now PPC -> Intel again with an emulation layer
Guess what though:
* 68k emulation: gone
* Classic Mac OS: gone
* 32 bit PPC(as of Leopard): gone
And eventually PPC will be gone too. Apple has pulled off all these transitions without pissing off their users more than necessary but also without dragging behind huge reams of crufty old code. If MS did a ground-up rewrite of Windows as Apple did with Mac OS, they would likely end up with a much better OS than they have today. Apple would never have been able to get the old Mac OS codebase up to the quality they've got in OS X. They tried, with Copland, and failed miserably. The only real difference is Microsoft has the endless piles of money to just "git 'er done" no matter how poor the end result
And so now they're stuck with an awful unmaintainable mess of an operating system and not a whole lot of good options. I would suggest looking at what Apple did with continuing minor mostly-maintenance releases of the old OS(see: Mac OS 9) while pushing most of their effort into NeXT/Rhapsody/OS X, and easing users into the new OS over a slow transition period. New adopters are less likely to complain about usability and performance issues when they know it's a 1.0 and things will get better. OS X didn't start firing on all cylinders until maybe 10.2
Of course, Microsoft should have begun that process 5 years ago and used XP as the maintenance OS. Instead now they have a trainwreck release that they can't simply maintain - everyone hates it
There's nothing wrong with using tools that have been around for a while, and your choice of tools may be completely appropriate and optimal for the type of work you're doing. But the fact that you can accomplish meaningful work with the set of tools you use really means very little. A horse and buggy is a meaningful tool, as is a honda civic. But simply because your horse and buggy can bring you from point A to B, it doesn't follow that you should scoff at all the people telling you it's "so 100 years ago"
See also, the Blub Paradox. Almost everyone has experienced the paradox for themselves, but its a constant struggle to not continue committing it again and again
If you're still using RadRails/Aptana for Rails development, I'd very strongly recommend downloading the Netbeans 6 beta. The Netbeans people have come a long way for Ruby development over a very short period of time. There's still some hiccups in the app, but it shows a lot more promise than the Aptana everything-to-everyone crapfest (I used RadRails/Aptana for about 18 months)
Read through this extensive feature review and try not to drool - Ruby/Rails tooling is really starting to move forward
Eclipse + Java + CVS, woohoo. Welcome to three years ago. How about instead let's try:
* Textmate / Netbeans
* Ruby (Rails or Merb for web programming)
* SVN or Git for source control
I'm not dismissing the contributions to the study of computer science, but the stated goals of the project are:
I doubt the cloture vote itself could be considered treason. I would be in favor of punishing anyone voting in favor of a grossly unconstitional bill like the MCA though. Sadly a number of blue-dog Democrats voted for that, and Chafee was the only Republican not to. Disbarring all 65 of those "yea" votes from ever serving in public office again would be appropriate
This Congress has been having cloture votes at twice the rate of any Congress in history. Please don't try to pretend this is standard operating procedure, especially after the months-long hissy fit the media went along with a couple years ago when the Democrats were getting half as many
After a resounding defeat in the last election signaling a widespread popular desire for change, the Senate Republicans have been threatening filibuster on any significant piece of legislation, most with broad public appeal. The Democrats primary failure is not taking the gloves off and forcing the GOP to actually filibuster the bills, rather than just signal the intention to do so
That was a proposed amendment to the Constitution that was never ratified - i.e. it is not US law. Do you have the slightest idea what you're talking about?
My guess as to the problem is the RIAA would tell Apple two things:
1) allowing "ripping" of ringtones from iTMS-bought songs would be illegal, Apple would have to charge
2) they would prefer not to allow any ripped ringtones
After #1, Apple themselves would be in a tough position because they would have to provide a tool that says "you can rip whatever ringtones you want, unless you bought the song from us." So yes I believe Apple ultimately cast the final vote on non-iTMS ringtone ripping, but their only other choice would have been essentially screwing over their own iTMS customers - not an enviable position to be in
My understanding is once something is in the public record, it doesn't matter how it got there. I think they're screwed
That's ~3 requests per second. I work with a single vertical application that handles roughly three times that at peak times.
You compared per-day vs. peak times, nice. At peak times the highest-traffic Rails app is about 20/second. Still not very many, well gee...its more than 99.9% of web sites will ever need to do, so complaining that Rails can't scale is a little silly
Can you describe some of your experiences scaling Rails? I'm currently serving up to 250,000 requests per-day with a handful of Rails apps, so I'm wondering where you hit the breaking point and had to switch to the crapfest that is PHP
There's no doubt that Ruby and Rails especially are much slower in execution time than comparable code written in PHP. That said, the PHP code would be 2-10x as verbose, take far longer to write, and be far less maintainable. With Rails you just throw more hardware at it and it will scale as far as you need to. If you're running up against real walls in Rails scaling, try Merb. If you're just a PHP n00b who wouldn't know decent OO-code if it punched you in the face, then by all means stick with the Personal Home Page language
Sounds similar to the experimental (human) treatment being practiced in China. There's been a lot of skepticism about why/how such a thing could work, but according to a lot of people who've gone through the treatment it does restore some amount of functionality
No, the event is a B-52 landing with unauthorized nukes.
According to the FAS, the last time a bomber was loaded with nuclear weapons was over 15 years ago. The last time a bomber flew with nuclear weapons was nearly 40 years ago. So it would appear GP was correct, and you are not
Maybe the BSD license should be altered to say code can be closed-sourced but not open-sourced without retaining the original BSD license(adding an additional license to the code would probably be fine). Seems like BSD's intent is to allow code to be used anywhere(including closed-source) without the viral effect, and its understandable that taking the code, modifying it, and applying a viral license to it would anger some developers
They're not throwing away their entire company. My guess is any company is making approximately zilch on BluRay/HD-DVD at this point. The studios don't have a lot to lose either way - if they pick the wrong horse, just switch later on. Why not take the 100 mil?