I would just need to get one that manages to produce non-blurry analog video (had GTX260, the video was blurry on higher resolutions, returned the card).
You should have kept the card. In my experience, regardless of it being an nVidia, ATI, or any other card, blurry VGA display is almost always caused by a crappy VGA cable.
I hate to sound like I'm feeding the troll, but...
Microsoft doesn't even make the xbox 360: that's Felextronics. Microsoft doesn't even make the DVD drives in the xbox 360: that's LG, Toshiba, BenQ and LiteOn. If you want to blame somebody for scratched discs then blame the correct manufacturers - or yourself for moving the console while it's spinning the disc!
Microsoft is a crappy software company. When it comes to hardware they're just Badge Engineers - even the Kinect is PrimeSense technology!
Speaker-dependant speech recognition software can do reasonably well, given enough training as you have mentioned. Speaker-independent speech recognition software, on the other hand, is still very much in its infancy.
One of the telcos in our country, Telstra, has rolled out a service that I'd like to opt-out of... voicemail to SMS. If you miss a call, instead of a voicemail being recorded for you to listen to later on, a computer answers the call and gives the speaker 10 seconds to state their business with the results being SMSd to you (in text format). The quality of speech-to-text in this deployment is so often random gibberish, requiring you to call the person back to find out why they called in the first place. At least the caller's phone number is included.
but how is THAT going to save money? the only way eliminating bugs saves money is to fire developers. i'm betting these guys are salaried like the rest of us so their time is already paid for.
Yes, the developers' salaries are already paid for. But their time is also already allocated to developing new features.
The more time "wasted" having to stop to fix bugs and then get back into the zone of creating, the more project schedules will slip. Delaying feature launches can have a negative impact on a company, particularly if those features are being developed under SLA/contract with a major customer - sometimes millions need to be refunded. There's your cost.
One thing I've not yet seen mentioned here - quite often fixing a bug also requires fixing data that's been mangled by it. Sure, you could fix a couple of lines of C#/SQL/favourite language and the bug is fixed... but you've still got hours/days of time getting the mangled data right again. Having a proper test suite helps you to catch bugs before they get out the door and cause data carnage. Even if you only write regression tests, at least you won't be repeating data fixes. Doing the same thing in front of customers time and again wears thin after a while.
I just repeated the experiment on both my iPhone 3GS and my fiancée's iPhone 4.
My mother was born on 9-Nov-1930 and if I store that birth date for her contact entry she doesn't appear in the calendar. Change the year to 1931 or 1932 and she still doesn't appear. Change the year to 1933 or later and she does.
This issue is known to Apple... do I need to link a Google query for you as well?
I am sure you can give us an example where the iOS time routines don't work as advertised.
Here's a well-travelled and documented bug, which still hasn't been fixed: try editing a Contact entry to add a birth date for someone 77 years (I think) or older - good luck finding it in the calendar!
The three outcomes I've seen for this include:
Contact appears in the birthday calendar, but with the wrong birth date.
The correct birth date appears in the birthday calendar, but with some other contact's name against it (wtf?).
Neither the contact nor their birth date appear in the birthday calendar at all.
Apple's date and time code needs review and TFA just demonstrates another example.
If your company wants to deploy VDI they'll figure out the connectivity requirements soon enough.
You're right, though - any kind of network or server outage has people twiddling their thumbs while you're still paying them. Not ideal.
The main complaints I see about VDI, aside from connectivity issues, is that it "isn't fast enough" to play video and games. Big deal. The majority of corporates are supposed to be working in Office-like apps typing documents, editing spreadsheets or pulling together slideshows - no video requirement there. Big bosses don't want you to access YouTube or whatever other time-wasting video sites you like to inhabit.
The minority of people actually needing physical desktops (for things such as network sniffers and maintenance) won't be on VDI.
But we are talking about a computer game and game characters didn't really have very realistic faces back in the day, Since TRON takes place inside a computer, then that kind of facial graphic is exactly what I would expect to see.
In the original Tron, actors' faces were the only exposed part (the rest was "suit"), so they were actually the only realistic part inside the computer in the film. I don't think the makers of Tron: Legacy have an excuse for pulling another Polar Express.
The algorithms that we use today for speech recognition, for natural language translation, for chess playing, for logistics planning, have evolved remarkably in the past decade.
I for one am yet to see any major improvements in speech recognition in the last ten years. It seems that it plateaued around 1995-2000 and hasn't had any decent improvements since.
Meanwhile, speech recognition has seen an increase in deployments in things such as:
voice-driven menu systems... "I'm sorry, did you say 'put me through to an terminator'?", and
speech-to-text voicemail... Telstra in Australia is a classic for this, with voicemail SMS's being nearly incomprehensible in conjunction with changing peoples' names such as "Royce" into something completely different such as "Melissa". wtf?
Speech recognition still has a long way to go me thinks.
You won't have any problems with.NET apps though - even those which directly access system DLLs. So as long as most of your software is built with.NET on Windows, you might be just fine.
Can I sell you a clue?
Please?
You only have to step very slightly outside of the core.NET namespaces (system.*) before.NET has problems being portable between Windows 7, Vista, and XP. Even System.Net.* behaves slightly differently on each of those platforms.
As already mentioned above, the multimeter in the picture is reading 2.164 megaohms which is quite a high resistance and would make no difference at all to the operation of the Kindle.
It seems that the blog owner has realised their mistake and replaced their blog entry with the content of another, but not before it made it's way into Google Cache
For those interesting in seeing the high-resolution "Oopsie" image, it is here.
According to previous advice from Microsoft (which they issued when Google announced the Google Chrome Frame Plugin for IE), browser plugins are additional security risks which should be avoided.
Which, I might point out, didn't stop them from silently installing the "Microsoft.NET Framework Assistant" add-on in the Firefox browser so Firefox users would be vulnerable to attack ^h^h^h...^h^h^h able to install ClickOnce applications hosted on the web.
There's nothing stopping anyone from writing a similar plugin for Firefox that uses the H.264 codec in ffmpeg, for example. Then you have the same functionality for Firefox in Linux (and probably OSX).
Commercial is different though, with FOSS I and (everyone else should for that matter), expect that there are no backdoors and it does exactly what it says it does.
That is supposed to be one of the biggest "selling points" of FOSS.
This is not the first time that the NSA has partnered with Microsoft during Windows development. In 2007, the agency confirmed that it had a hand in Windows Vista as part of an initiative to ensure that the operating system was secure from attack and would work with other government software. Before that, the NSA provided guidance on how best to secure Windows XP and Windows 2000.
Oh, my sides! I guess that was an epic FAIL for the NSA then? (Either that, or Windows might actually have been more vulnerable to attack without their help.)
I also tried to explian that "hacking" was modifying a piece of hardware to do what it wasn't designed for (my favorite all time hack was the O2 scrubbers on the Apollo 13 mission, that was some excellent thinking)
Your example doesn't quite fit the definition. Whilst that was excellent thinking for the Apollo 13 mission it was essentially making a scrubber out of... a scrubber. The stupidity that led to the problem in the first place was that instead of using one type of scrubber throughout, the CM scrubbers were square and the LEM scrubbers were round - truly a square-peg-in-a-round-hole problem.
Slashdot Mirror
I would just need to get one that manages to produce non-blurry analog video (had GTX260, the video was blurry on higher resolutions, returned the card).
You should have kept the card. In my experience, regardless of it being an nVidia, ATI, or any other card, blurry VGA display is almost always caused by a crappy VGA cable.
The grandparent article is titled "Star Trek anyone? US sets out to build photon-based optical networks."
Shouldn't they be building bio-neural networks then?
No one is saying or has ever said that higher temperatures and levels of CO2 are bad for life in general.
Did you miss the environmentalists trumpeting the demise of thousands of species due to global warming?
As you can tell from the name, the "ErgoSlider Plus+" is something completely different and totally new.
Think I'll wait until the ErgoSlider Plus# is released.
I hate to sound like I'm feeding the troll, but...
Microsoft doesn't even make the xbox 360: that's Felextronics. Microsoft doesn't even make the DVD drives in the xbox 360: that's LG, Toshiba, BenQ and LiteOn. If you want to blame somebody for scratched discs then blame the correct manufacturers - or yourself for moving the console while it's spinning the disc!
Microsoft is a crappy software company. When it comes to hardware they're just Badge Engineers - even the Kinect is PrimeSense technology!
I've reported a few people who for instance, claim to be able to predict the future.
Damn, they should have seen that coming!
Speaker-dependant speech recognition software can do reasonably well, given enough training as you have mentioned. Speaker-independent speech recognition software, on the other hand, is still very much in its infancy.
One of the telcos in our country, Telstra, has rolled out a service that I'd like to opt-out of... voicemail to SMS. If you miss a call, instead of a voicemail being recorded for you to listen to later on, a computer answers the call and gives the speaker 10 seconds to state their business with the results being SMSd to you (in text format). The quality of speech-to-text in this deployment is so often random gibberish, requiring you to call the person back to find out why they called in the first place. At least the caller's phone number is included.
Voice recognition software is now quite a capable means of entering information into a computer system.
guffaw.
Still, where do I get two of these bots from so I can use the T3 lanes on the way to work in the morning?
but how is THAT going to save money? the only way eliminating bugs saves money is to fire developers. i'm betting these guys are salaried like the rest of us so their time is already paid for.
Yes, the developers' salaries are already paid for. But their time is also already allocated to developing new features.
The more time "wasted" having to stop to fix bugs and then get back into the zone of creating, the more project schedules will slip. Delaying feature launches can have a negative impact on a company, particularly if those features are being developed under SLA/contract with a major customer - sometimes millions need to be refunded. There's your cost.
One thing I've not yet seen mentioned here - quite often fixing a bug also requires fixing data that's been mangled by it. Sure, you could fix a couple of lines of C#/SQL/favourite language and the bug is fixed... but you've still got hours/days of time getting the mangled data right again. Having a proper test suite helps you to catch bugs before they get out the door and cause data carnage. Even if you only write regression tests, at least you won't be repeating data fixes. Doing the same thing in front of customers time and again wears thin after a while.
That was my first thought, too, but in FlashForward it was crows dying.
I just repeated the experiment on both my iPhone 3GS and my fiancée's iPhone 4.
My mother was born on 9-Nov-1930 and if I store that birth date for her contact entry she doesn't appear in the calendar. Change the year to 1931 or 1932 and she still doesn't appear. Change the year to 1933 or later and she does.
This issue is known to Apple... do I need to link a Google query for you as well?
I am sure you can give us an example where the iOS time routines don't work as advertised.
Here's a well-travelled and documented bug, which still hasn't been fixed: try editing a Contact entry to add a birth date for someone 77 years (I think) or older - good luck finding it in the calendar!
The three outcomes I've seen for this include:
Apple's date and time code needs review and TFA just demonstrates another example.
If your company wants to deploy VDI they'll figure out the connectivity requirements soon enough.
You're right, though - any kind of network or server outage has people twiddling their thumbs while you're still paying them. Not ideal.
The main complaints I see about VDI, aside from connectivity issues, is that it "isn't fast enough" to play video and games. Big deal. The majority of corporates are supposed to be working in Office-like apps typing documents, editing spreadsheets or pulling together slideshows - no video requirement there. Big bosses don't want you to access YouTube or whatever other time-wasting video sites you like to inhabit.
The minority of people actually needing physical desktops (for things such as network sniffers and maintenance) won't be on VDI.
But we are talking about a computer game and game characters didn't really have very realistic faces back in the day, Since TRON takes place inside a computer, then that kind of facial graphic is exactly what I would expect to see.
In the original Tron, actors' faces were the only exposed part (the rest was "suit"), so they were actually the only realistic part inside the computer in the film. I don't think the makers of Tron: Legacy have an excuse for pulling another Polar Express.
The algorithms that we use today for speech recognition, for natural language translation, for chess playing, for logistics planning, have evolved remarkably in the past decade.
I for one am yet to see any major improvements in speech recognition in the last ten years. It seems that it plateaued around 1995-2000 and hasn't had any decent improvements since.
Meanwhile, speech recognition has seen an increase in deployments in things such as:
Speech recognition still has a long way to go me thinks.
You won't have any problems with .NET apps though - even those which directly access system DLLs. So as long as most of your software is built with .NET on Windows, you might be just fine.
Can I sell you a clue?
Please?
You only have to step very slightly outside of the core .NET namespaces (system.*) before .NET has problems being portable between Windows 7, Vista, and XP. Even System.Net.* behaves slightly differently on each of those platforms.
As already mentioned above, the multimeter in the picture is reading 2.164 megaohms which is quite a high resistance and would make no difference at all to the operation of the Kindle.
It seems that the blog owner has realised their mistake and replaced their blog entry with the content of another, but not before it made it's way into Google Cache
For those interesting in seeing the high-resolution "Oopsie" image, it is here.
I'm a little confused on how giving more people access to the data helps to ameliorate the supposed privacy invasion?
Hear! Hear! This from TFA:
"We’re not asking for names or addresses. We want to see the nature of the data they have," he added.
Um, excuse me? What business is it of yours? They've already told you what types of data have been sniffed. Why do you need to see it?
According to previous advice from Microsoft (which they issued when Google announced the Google Chrome Frame Plugin for IE), browser plugins are additional security risks which should be avoided.
Which, I might point out, didn't stop them from silently installing the "Microsoft .NET Framework Assistant" add-on in the Firefox browser so Firefox users would be vulnerable to attack ^h^h^h...^h^h^h able to install ClickOnce applications hosted on the web.
There's nothing stopping anyone from writing a similar plugin for Firefox that uses the H.264 codec in ffmpeg, for example. Then you have the same functionality for Firefox in Linux (and probably OSX).
Commercial is different though, with FOSS I and (everyone else should for that matter), expect that there are no backdoors and it does exactly what it says it does.
That is supposed to be one of the biggest "selling points" of FOSS.
Yes, that is supposed to be one of the selling points (in relation to Many Eyes), however, lest we forget... http://cyberinsecure.com/adware-back-door-in-firefox-language-pack/
This particular issue wasn't in the core app, though, it found it's way in via a language pack. It just demonstrates that FOSS isn't immune.
(#) Copyright (c) 1983 The Regents of the University of California. All rights reserved.
Also from that link...
This is not the first time that the NSA has partnered with Microsoft during Windows development. In 2007, the agency confirmed that it had a hand in Windows Vista as part of an initiative to ensure that the operating system was secure from attack and would work with other government software. Before that, the NSA provided guidance on how best to secure Windows XP and Windows 2000.
Oh, my sides! I guess that was an epic FAIL for the NSA then? (Either that, or Windows might actually have been more vulnerable to attack without their help.)
While WikiLeaks is a current and exciting topic, the clothianidin/EPA leak has nothing to do with WikiLeaks.
Thank you!
Somebody probably got confused because TFA is titled, "Wik-Bee Leaks: EPA Document Shows It Knowingly Allowed Pesticide That Kills Honey Bees"
I also tried to explian that "hacking" was modifying a piece of hardware to do what it wasn't designed for (my favorite all time hack was the O2 scrubbers on the Apollo 13 mission, that was some excellent thinking)
Your example doesn't quite fit the definition. Whilst that was excellent thinking for the Apollo 13 mission it was essentially making a scrubber out of... a scrubber. The stupidity that led to the problem in the first place was that instead of using one type of scrubber throughout, the CM scrubbers were square and the LEM scrubbers were round - truly a square-peg-in-a-round-hole problem.