It used to be legal in Texas to kill someone because they "needed kill'in'. These guys clearly fit in that category.
I remember when 386/486 were still being sent up in space when current PC processors were many times faster. (still are?) They were tested, protected, and proven. Ask yourself this. Do you buy the newest process off Newegg (or whatever) and send it into space hoping it doesn't fail at a price of $500 million or in Curiosity's case $2.5 billion? Umm, hell no.
We've begun to move away from MySQL offical release also. Although we went with Percona rather than MariaDB.
I have the Linksys E3000 WiFi router and have not had any quality issues. Part of this may be because I refused to install the push-based firmware that caused issues for a lot of people.
I did notice a lot of features being dropped from the Linksys line once they became Cisco branded. One of the biggest examples was removing CLI from some of the higher-end Linksys switches. Of course, this was to prevent a loss of sales for Cisco's enterprise lineup. The result was that a lot of SMBs went with Netgear and D-Link.
I have the E3000 also. The one thing I don't like about it is it runs very hot. I have to tilt it up on it's side to keep it cool. If I don't, I notice that my WiFi connections act flaky sometimes.
I used the base firmware for a long while, but finally switched to DD-WRT about a year and a half ago.
Cisco is used to fleecing companies just like Oracle does. Buying into consumer market will never get you those types of margins. (don't even bring up Apple, that fad is already on the down swing)
Even in the Enterprise world, there are good options opposite Cisco these days. I've replacement most of my Cisco equipment with Juniper and have been quite happy with them and in some cases far happier than I was with Cisco.
The Slashdot title says $4.5M, but the article it links to says $2.8M
For example, sound and light from the device could be disabled when entering a movie theater, or communications with other devices could be disabled in a science laboratory.
Umm. Already do with with the Tasker app.
Samsung can claim that the jury did not understand the testimony...
Actually, I think they did understand until Mr. Hogan derailed them by telling them his little story. My guess is the other jurors took Mr. Hogan as an expert in patent law which is obviously is not. They followed his lead right off the proverbial cliff.
The funny thing is, Mr. Hogan declared that it wasn't prior art because it didn't run on that processor. If that logic is used, wouldn't that imply the same thing about Samsung and Apple? Apple's software isn't prior art to Samsung's because Samsung's software definitely isn't going to run on an iPhone.
It also looks like a T-Mobile store. Maybe T-Mobile should sue both Apple and Samsung since T-Mobile stores looked like that before Apple opened any stores..
You want to see a catastrophe? Look at sound in Linux. Pulse was created to fix the sound problems, except for the fact that Pulse is terrible too. It presents a whole new set of problems and limitations.
The X doesn't deliver a very good experience either. I'm really hoping Wayland is the answer. It can't get here soon enough.
For me it was both.
Form factor of an eReader, power of an iPad, and half the price of an iPad.
I got a 16GB. I would have definitely bought a 32GB if it were available. I don't quite understand why they even produced an 8GB if it doesn't have an SD slot and doesn't have G4. If you drop a movie or two on it, you have no room left for your music, pictures, and other apps / data.
This thing would have been golden with an SD slot.
I was actually very interested in a XPS 13 Ultrabook. It had good reviews, a decent price and Linux would work on it. My only problem was that it supported a max for 4GB of memory. If it had at least supported 8GBs, I would probably own one right now.
The issue is people trying to shoe-horn what should be SQL into NoSQL. NoSQL has it's uses, but so many people don't understand why SQL fits better than NoSQL in most situations. There is a reason SQL has been around for a VERY long time and most technologies are still implemented in SQL and not NoSQL.
Whether it's people just wanting to use the cool new technology and finding out later that what they could do in SQL is just not feasibly possible in NoSQL. Then you and your project are in a serious pickle.
SQL has strengths that make it hard to move away from. If you are going to move away from SQL, then you probably already know NoSQL's pluses, but do you know NoSQL's limitations? Not only that, but do you know where your project will end up? If not, you better think long and hard about moving to NoSQL because down the road, that feature or functionality you need may be damn hard to implement using NoSQL.
There are been a lot of projects that started with NoSQL and are now SQL based.
iGoogle. Having all of your RSS feeds, your email feed, calendar, TODO list among a few other things. It is very useful and effective in what it does.
There are several websites that post interesting items, but not enough to visit them every day. The RSS feed makes it were you don't have too. Combining it all with stuff you do use every day (email, calendar, todo list) makes iGoogle extremely useful.
What I find is most people have tools at their finger tips that they have no idea how useful that tool actually is and therefore don't end up using it.
iGoogle is useful, but like Google+ most people have no idea how to actually use it. (at least half-intelligent people are actually figuring out how to use Google+, that just doesn't seem to be the case for iGoogle)
That ignorance is a loss for us all.