I had the same problem with Dell a few years back (2001, 2002?): I installed a second hard drive, moved my Windows install to it and put Linux on my primary hard drive (the second hard drive was slower - someone gave it to me). I couldn't get the Windows NVIDIA GeForce driver to work after this. I called Dell support, and they said I wasn't supported.
Turns out they have a good reason for this. I reinstalled Windows on my original hard drive, and the NVidia driver suddenly worked. Still don't know why that happened (didn't look too deeply - Linux is still fast enough on the slower hard drive, and NVIDIA driver works in Linux properly).
As much as I don't like these policies, the computer companies DO have a reason for saying they don't support you with another OS installed. The same thing would happen if you moved from Win2K to WinXP. It's not a Linux bias, but a "we didn't sell you it" bias.
That sounds like Georgia Tech. My schooling there was about half CS-foundation work (math, OS fundamentals, CS theory (which is also math)), while the other half was about software engineering. The whole point was that you take the fundamentals and apply them in real-world situations. You can't teach good software engineering without the students understanding the CS fundamentals. Likewise, you can't have just the CS fundamentals because then there are very few jobs. The two pieces complement each other. It's worked out great for me - there's a lot of software engineering work I need to do to get the project done, but without understanding the fundamentals of CS, I wouldn't be able to do half of what's needed on my current project.
So Microsoft should be sued for forcing users to download IE7 saying it is a "critical security update".
No. Sad as it is, IE7 WAS a critical security update to IE6. Of course, to be totally accurate, they should have forced the users to download Opera, Firefox, or some other browser as a critical security update to IE6 instead.
FTA: Furthermore, in my experience, AJAX-enabled web applications are no more functionally complex than standard web applications.... Gmail is less complex than Outlook Web Access.
Gmail and OWA both use AJAX. Heck, Microsoft created the XMLHTTPRequest object. Comparing Gmail to OWA to prove this point just doesn't make sense.
To further complicate things, there is a severity and priority attached to every bug. Severity is a measure of the impact the bug has on the customer/end-product. It can range from 1 (Bug crashes system) to 4 (Just a typo). Priority is a measure of the importance of the bug. It ranges from 0 (Bug blocks team from doing any further work, must fix now), to 3 (Trivial bug, fix if there is time). (I don't know why the ranges don't match, BTW, seems silly to me)
This sounds similar the ClearQuest database we use where I work. A bug has High, Medium, or Low priority, usually assigned by the technical managers (i.e. those who know how the system should work for our customers, but also have to report to upper-management on the status of the product). Bugs marked as "High" are worked off before Medium and Low bugs. Then there's the Severity rating (we have 5), such as Bug Crashes system, there are work arounds, the bug's a typo, etc. This is determined by the person who found the bug.
It allows for finer-grain of rating a bug: what do the system engineers and technical managers think about the bug, and what do the software developers, testers, etc. think about the bug. If you have good communications, then it works really well and the critical bugs get worked off making both the software developers & testers as well as the technical managers happy (and thereby upper management assuming it doesn't set the product back a few months).
If you notice, Bugzilla even has a Severity and Priority field. It seems that this system of two different types of "priorities" works well for many different types of people.
Graphics card manufacturers are blatantly flouting the law which says that a person is privy to every secret embodied in every article they rightfully own, by simple virtue of the fact of ownership, even if that article be a graphics card and the secret be how to program it. Both ATI and nVidia licence their drivers on egregious and legally unenforcible terms which ride roughshod over the user's common law property rights. They get away with this by having the upper hand to begin with.
This is blatantly wrong. Think about Coca-Cola. I own a 2-liter of it, but I do not have the right to every secret about what's in the 2-liter. The formula is a trade secret. Of course, I'm still allowed to try to figure out the formula for Coca-Cola using the product, but it's very hard. Same goes for hardware. These things are card Trade Secrets. Trade Secrets are very legal.
Because *I* was talking about Linux (there is no swap partition with Windows). I must have used swsusp last time I set up my system, as without enought swap (actually 1.5G swap for 768M of RAM), I couldn't suspend to disk. Hibernate is just another word for it (been using it at work, unfortunately and got stuck in my head).
It depends on what you want to use. If you don't care about Hibernate mode, then you probably wouldn't need any swap (or much). However, if you want to use that mode, you need to have at least the same amount of swap space as memory. I've tried it with less, and it wouldn't even attempt to go to sleep (for obvious reasons - swap is used to store what's currently in RAM when going into hibernate mode).
There's exceptions, of course - the boy scouts at least used to require faith in a monotheistic religion, for example - but it's best to stay away from it unless you want your ass sued.
It doesn't even have to be monotheistic. There were Hindus in my troop. It's belief in that there is some higher power that is required.
The lack of cameras on all Blackberries (is a God-send!) is due to the restrictions placed on cameras in senstive areas. If one Blackberry had a camera they may all be banned from those locations (rumor has it there may be one coming though, I hope not).
Thank you! Now if only the companies making PDA + phone devices (or even just phones) would listen. Where I work, no cameras are allowed inside, period. It's company policy. I wouldn't be surprised if many companies have the same policy. This policy prevents me from buying something like the Treo 700p to replace my PalmOS device and cell phone - the place I'm going to want that PDA much of the time is at work.
One of these days, the device makers will wake up and realize that not everyone wants a camera.
I found the patent that EpicRealm holds. It was filed in 1999. EpicRealm patent
Basically, the patent is about the web server receiving a request, and handing the request off to a page server. The page server finishes the request and responds to the client while the web server continues to handle other requests.
This sounds very similar to many web applications in use today (J2EE, ASP.net, etc.). There are usually a few processes running with J2EE (the one I'm most familiar with). One handles the HTTP requests and then hands it off to another process to dynamically create the web page. The second processes send the generated page back to the HTTP processes, which sends it to the client. In the meantime, the HTTP process could have been handling other HTTP requests.
As a UK citizen, I'm unfamiliar with US law - how long does a US patent last? I assumed it was 5 years, considering this patent was filed in 1991 (if I read correctly) it must be at least 15 years monopoly - something that seams completely unfair to the progression of business...
The main reason for making it so long is that people and companies typically file the patent while R&D is still going on. It can take 5-10 years (or more) after the patent is filed for the product to come to market. This is especially true with drugs in the United States, as the process with the FDA takes an extremely long time.
And those auto-generated comments are always useless.
But look at what the parent said: So our code has hundreds of methods called things like getFoo() and setFoo() with comments like "this returns the value of foo" or " this sets the value of foo".
These comments are just as useless as autogenerated comments, so why not use them?
The company I work for has a "standard" that says "every method you write must have a comment". So our code has hundreds of methods called things like getFoo() and setFoo() with comments like "this returns the value of foo" or " this sets the value of foo".
By the time you've written all these useless comments, you're too tired to write a single useful comment that explains how the code works.
There are programs out there for auto-commenting get/set methods. Heck, there are programs that'll create basic get/set methods from your class variables and comment the functions at the same time.
In any case, code is always obvious when you've writing it. So it's hard to know what comment would be needed to make it clear to someone who wasn't familiar with it. Maybe comments should always be written by someone other than the author of the code?
Instead, write your code, comment as you think it should be, and then send it out via e-mail for review. If you don't have enough comments, you'll get e-mail back saying "this needs comments here, here, and here". It works well. Usually, you don't have to change anything, but every once in a while, you miss a comment or something you think is obvious is not obvious to others.
No where do the links call this a "standard". RSS is a standard. These are add-ons (extensions) to the RSS standard. Now, I have no love for Microsoft, but I'd say we should give them a little credit for releasing their own extensions and licensing them under a Creative Commons License that essentially lets anyone impelment these extensions.
This is only due many people reading slashdot from work. I'm forced to use Windows at work (though most of the development team would love to use Linux).
It's not a really bad PDF. I opened it up in xpdf (in Firefox, at that), and it looks great. I'm using Mandrake 2005LE, so I don't know if they have some particular settings that make it look good or it's just your configuration.
Slashdot Mirror
I had the same problem with Dell a few years back (2001, 2002?): I installed a second hard drive, moved my Windows install to it and put Linux on my primary hard drive (the second hard drive was slower - someone gave it to me). I couldn't get the Windows NVIDIA GeForce driver to work after this. I called Dell support, and they said I wasn't supported.
Turns out they have a good reason for this. I reinstalled Windows on my original hard drive, and the NVidia driver suddenly worked. Still don't know why that happened (didn't look too deeply - Linux is still fast enough on the slower hard drive, and NVIDIA driver works in Linux properly).
As much as I don't like these policies, the computer companies DO have a reason for saying they don't support you with another OS installed. The same thing would happen if you moved from Win2K to WinXP. It's not a Linux bias, but a "we didn't sell you it" bias.
That sounds like Georgia Tech. My schooling there was about half CS-foundation work (math, OS fundamentals, CS theory (which is also math)), while the other half was about software engineering. The whole point was that you take the fundamentals and apply them in real-world situations. You can't teach good software engineering without the students understanding the CS fundamentals. Likewise, you can't have just the CS fundamentals because then there are very few jobs. The two pieces complement each other. It's worked out great for me - there's a lot of software engineering work I need to do to get the project done, but without understanding the fundamentals of CS, I wouldn't be able to do half of what's needed on my current project.
FTA: Furthermore, in my experience, AJAX-enabled web applications are no more functionally complex than standard web applications. ... Gmail is less complex than Outlook Web Access.
Gmail and OWA both use AJAX. Heck, Microsoft created the XMLHTTPRequest object. Comparing Gmail to OWA to prove this point just doesn't make sense.
At least that's what I've seen in my limited experience.
I noticed that earlier today. I also noticed that someone's starting to tag them with "itsnotatrap" on many of the later articles.
Quite an amusing way to beta-test the feature.
It allows for finer-grain of rating a bug: what do the system engineers and technical managers think about the bug, and what do the software developers, testers, etc. think about the bug. If you have good communications, then it works really well and the critical bugs get worked off making both the software developers & testers as well as the technical managers happy (and thereby upper management assuming it doesn't set the product back a few months).
If you notice, Bugzilla even has a Severity and Priority field. It seems that this system of two different types of "priorities" works well for many different types of people.
Because *I* was talking about Linux (there is no swap partition with Windows). I must have used swsusp last time I set up my system, as without enought swap (actually 1.5G swap for 768M of RAM), I couldn't suspend to disk. Hibernate is just another word for it (been using it at work, unfortunately and got stuck in my head).
It depends on what you want to use. If you don't care about Hibernate mode, then you probably wouldn't need any swap (or much). However, if you want to use that mode, you need to have at least the same amount of swap space as memory. I've tried it with less, and it wouldn't even attempt to go to sleep (for obvious reasons - swap is used to store what's currently in RAM when going into hibernate mode).
Make that six users now.
One of these days, the device makers will wake up and realize that not everyone wants a camera.
I found the patent that EpicRealm holds. It was filed in 1999.
EpicRealm patent
Basically, the patent is about the web server receiving a request, and handing the request off to a page server. The page server finishes the request and responds to the client while the web server continues to handle other requests.
This sounds very similar to many web applications in use today (J2EE, ASP.net, etc.). There are usually a few processes running with J2EE (the one I'm most familiar with). One handles the HTTP requests and then hands it off to another process to dynamically create the web page. The second processes send the generated page back to the HTTP processes, which sends it to the client. In the meantime, the HTTP process could have been handling other HTTP requests.
OK, that's a cool feature. I just tried it, and I think it's going to be one of the more-used features for me. thanks!
The launch has been scrubbed for Wednesday as well, because of a power outage in Maryland at the New Horizons control center
u tolaunch/)
(see http://www.floridatoday.com/floridatoday/blogs/pl
The main reason for making it so long is that people and companies typically file the patent while R&D is still going on. It can take 5-10 years (or more) after the patent is filed for the product to come to market. This is especially true with drugs in the United States, as the process with the FDA takes an extremely long time.
So our code has hundreds of methods called things like getFoo() and setFoo() with comments like "this returns the value of foo" or " this sets the value of foo".
These comments are just as useless as autogenerated comments, so why not use them?
No where do the links call this a "standard". RSS is a standard. These are add-ons (extensions) to the RSS standard. Now, I have no love for Microsoft, but I'd say we should give them a little credit for releasing their own extensions and licensing them under a Creative Commons License that essentially lets anyone impelment these extensions.
Google Video is plugin-free? I just took a look at it, and it uses Macromedia Flash. That's a plugin last time I checked.
The dinosaurs died
This is only due many people reading slashdot from work. I'm forced to use Windows at work (though most of the development team would love to use Linux).
It's not a really bad PDF. I opened it up in xpdf (in Firefox, at that), and it looks great. I'm using Mandrake 2005LE, so I don't know if they have some particular settings that make it look good or it's just your configuration.