I'm looking forward to the research paper to address key questions. What resources (training, inference) did Google use and how do they compare to the competition? Was this mostly a machine learning problem with big data, or a big data problem with some machine learning? Is there a GitHub yet?
I can't bear to part with my S100 computers; Vector Graphics and Alpha Micro. I'll take them to my grave. My Alpha Micro colleagues feel the same way. IIRC, at the Atlantic City Computer Festival (August 1976?), I rode the elevator up with Carl Helmers, editor of Byte Magazine. He was excited by a meeting where the various hardware manufactures agreed on a moniker of S100. I also had a conversation with Steve Jobs at his cardtable booth. He claimed to have advanced orders for 600 Apple 1 boards. I thought that was bullshit because no one had that kind of volume. He confided that Apple would soon release an improved model, called Apple 2, that offered color, a completely unique offering. I asked if people really cared about color. Wasn't monochrome just as useful? He assured me people would snatch up there completed-system color computer. I often told this story to illustrate how Steve was so much more attuned to peoples wants than I was. But in 1984, he rolled out the first Macintosh, a monochrome computer -- so much for must-have color computers.
A BAD or a NEGATIVE review? Personally I don't have an issue with anyone (seller/buyer/competitor) who leaves a negative review provided it's accurate.
Amazon can stop fake reviews by putting real fear into the minds of sellers. If a seller is caught in a fake review scam, Amazon should force the seller to accept returns. Until then, I give Amazon two stars in their efforts to control fake reviews. I'm looking forward to Amazon rolling over the perps and exposing their cheating clients. Fake reviews are against the law in some jurisdictions.
All this means that Apple has committed a pricing blunder by under estimating competitor's pricing. They are unlikely to repeat this next time. Don't expect any pricing reductions any time soon.
When I was interviewed for an elite job at an elite company, I was dumbfounded to discover that their "elite" engineers didn't understand fundamental flaws in their solutions. When their top programmer tried to optimize my solution, I told him he just added a syntax error, not an optimization. The conversation got out of hand and was finally settled by referencing the ISO standard. Apparently, this guy had been giving a thumbs up to people who couldn't spot syntax error. My advice, take time to know the algorithm and the language really, really well.
In Mauritainia, where I did Peace Corps duty 10 years ago, people self identified themselves as slaves even though slavery was abolished twenty years before. Why? Because it was their culture and job. Being a slave gave them steady meals. The alternative was worse.
Here's my educated guess as to what's happening. I have absolutely no inside information. I've just taken publicly available tidbits and assembled them into a big picture. It may or may not be accurate. In short, Wpf and Silverlight will be present and supported for years. However, they are zombies having been smitten by changes in technologies.
There are two new relevant core technological changes that I'm expecting to hear at Build 2011 (née PDC 2011). First, Microsoft will promote a new UI called MoSH (MOdern SHell but more conceptually MObile SHell) based on IE's Trident render engine that will form the basis for a new initiative. Moving forward, it behooves everyone to build MoSH applications, definitely not Silverlight (web) and possibly not WPF (desktop). MoSH is implemented using HTML5 and thus constrained by HTML5 capabilities. WPF and Silverlight are still completely supported but they're future is cut off at the legs by their successor (MoSH). MoSH can be used with XAML but, significantly, will only support a subset of WPF's and Silverlight's XAML. Again, the constraining factor is HTML5 capabilities and Microsoft's abstractions of them. Thus the key question for Silverlight shops is “How much of Silverlight ISN'T abstracted from HTML5?” I expect both MoSH and WPF/Silverlight to support new device interfaces such as location, multi-touch, gyroscopes, Kinect, etc. I'm not sure if the support will come in the form of.Net 5, be built into MoSH, or as a separate cross-platform library. I believe MoSH for IE will be accompanied by a cross-platform version (Mozilla, Safari, maybe Chrome) in the form of a browser plugin. Marc Andreesen has predicted “The browser will become the OS”. I believe more correctly the control renderer will become the OS. MoSH will become the heart of IE apps, Windows 8 and Windows devices (Windows TV anyone?). The pundits will say Microsoft is becoming a control's vendor. Microsoft could write MoSH controls by C#, native code, or Javascript. This is another key question. Perhaps they'll use all three with Javascript being used for the plugins.
The second technological change is what Microsoft might be calling Native Code. Native Code is a set of technologies that enable software (applications and gadgets) and hardware (graphics) to perform at near native speed inside a container (browser). Most notably, Microsoft will supply tooling to build browser applications, principally with MoSH, without today's performance penalties. Currently browser based applications are limited by API availability (DOM), programming speed (Javascript), and often software rendering. This will all change. Internet Explorer 11(?) will expose a much richer API, possibly.Net 5.0, Visual Studio will enable Native Code development, and IE's Trident renderer will directly use hardware graphics.
Some issues I'm unclear on: * Will Microsoft port MoSH and Native Code to iOS and Android? I'm guessing that they intend to do so directly or through partnerships. * Will a single dll, possibly named.DLLX, run across all devices? If so, when is the code JITed? * Will Native Code force any syntax changes to.Net languages? I'm guessing Microsoft is working hard to limit the changes to attributes. * Is Native Code implemented using.Net sandboxing or with the aid of hardware as with Google's Native Client (NaCl)? This would make the difference as to whether C will be supported. * Do CPU processors need changes to optimally support Native Code? Remember, Windows 8 will run on ARM. ARM are the non-Intel processors that power most tablets. Do all existing processors and graphics chips support Native Code and MoSH? I'm particularly curious about the compatibility of legacy ARM processors.
What does Microsoft hope to gain by these changes? * Build an eco system based on HTML5 standards. The idea being that no competitor can block Microsoft’s tools because they’r
Think about long term. This won't be the first and last app you develop. Have confidence in your dev skills. Treat this as a learning experience. Make a good choice. Execute well. Learn from the choice so you can do even better next time.
Does this count under the French three strike rule? I bet it will. Nothing like a good threat to extract the upper hand in negotiations. I'll bet some mouthy minister takes up the threat to cut off Google's Internet access under the three strike rule. Nationalism, populism and greed will surely overpower any talk about citizen's benefits. The big loser is not Google, it's the citizens of France.
As the project leader for the open source French Verb Conjugation Rules Database project at SourceForge, I hope Microsoft considers the prior art contained within it. The database contains RegEx expressions for conjugating and infinitizing French verbs. The database is in Microsoft Access because it easily handles Unicode. Algorithms were written in.Net.
http://sourceforge.net/forum/forum.php?forum_id=49 0001
The world needs more open source versions of similar databases and linguistic algorithms. Language processing databases and software are ideal global open source projects. I would greatly value an open source project that documents syntax forms and algorithms for the world's languages. I have not found such a project.
Slashdot Mirror
I'm looking forward to the research paper to address key questions. What resources (training, inference) did Google use and how do they compare to the competition? Was this mostly a machine learning problem with big data, or a big data problem with some machine learning? Is there a GitHub yet?
I can't bear to part with my S100 computers; Vector Graphics and Alpha Micro. I'll take them to my grave. My Alpha Micro colleagues feel the same way. IIRC, at the Atlantic City Computer Festival (August 1976?), I rode the elevator up with Carl Helmers, editor of Byte Magazine. He was excited by a meeting where the various hardware manufactures agreed on a moniker of S100. I also had a conversation with Steve Jobs at his cardtable booth. He claimed to have advanced orders for 600 Apple 1 boards. I thought that was bullshit because no one had that kind of volume. He confided that Apple would soon release an improved model, called Apple 2, that offered color, a completely unique offering. I asked if people really cared about color. Wasn't monochrome just as useful? He assured me people would snatch up there completed-system color computer. I often told this story to illustrate how Steve was so much more attuned to peoples wants than I was. But in 1984, he rolled out the first Macintosh, a monochrome computer -- so much for must-have color computers.
Contact is the gold standard despite its Hollywood ending.
A BAD or a NEGATIVE review? Personally I don't have an issue with anyone (seller/buyer/competitor) who leaves a negative review provided it's accurate.
Amazon can stop fake reviews by putting real fear into the minds of sellers. If a seller is caught in a fake review scam, Amazon should force the seller to accept returns. Until then, I give Amazon two stars in their efforts to control fake reviews. I'm looking forward to Amazon rolling over the perps and exposing their cheating clients. Fake reviews are against the law in some jurisdictions.
All this means that Apple has committed a pricing blunder by under estimating competitor's pricing. They are unlikely to repeat this next time. Don't expect any pricing reductions any time soon.
Expose and block cheating by randomly delaying the announcements by milliseconds. Good news is they'll find the perps by threatening RICO.
Bad at explaining the issue? Are you sure you really know the issue yourself? Your explanation shows you do not.
He believed there was no issue in assigning an int to an unsigned in C. Not a quibble, right?
When I was interviewed for an elite job at an elite company, I was dumbfounded to discover that their "elite" engineers didn't understand fundamental flaws in their solutions. When their top programmer tried to optimize my solution, I told him he just added a syntax error, not an optimization. The conversation got out of hand and was finally settled by referencing the ISO standard. Apparently, this guy had been giving a thumbs up to people who couldn't spot syntax error. My advice, take time to know the algorithm and the language really, really well.
... but you get USB 2.0.
In Mauritainia, where I did Peace Corps duty 10 years ago, people self identified themselves as slaves even though slavery was abolished twenty years before. Why? Because it was their culture and job. Being a slave gave them steady meals. The alternative was worse.
Looking forward to seeing the gun camera videos filmed during the Mirage's strike on the convoy.
How come you never hear about successful traders getting arrested?
This software unblocks my use of Kinect. Microsoft has not released a gesture library. Looks like this will enable it's creation.
Here's my educated guess as to what's happening. I have absolutely no inside information. I've just taken publicly available tidbits and assembled them into a big picture. It may or may not be accurate. In short, Wpf and Silverlight will be present and supported for years. However, they are zombies having been smitten by changes in technologies.
There are two new relevant core technological changes that I'm expecting to hear at Build 2011 (née PDC 2011). First, Microsoft will promote a new UI called MoSH (MOdern SHell but more conceptually MObile SHell) based on IE's Trident render engine that will form the basis for a new initiative. Moving forward, it behooves everyone to build MoSH applications, definitely not Silverlight (web) and possibly not WPF (desktop). MoSH is implemented using HTML5 and thus constrained by HTML5 capabilities. WPF and Silverlight are still completely supported but they're future is cut off at the legs by their successor (MoSH). MoSH can be used with XAML but, significantly, will only support a subset of WPF's and Silverlight's XAML. Again, the constraining factor is HTML5 capabilities and Microsoft's abstractions of them. Thus the key question for Silverlight shops is “How much of Silverlight ISN'T abstracted from HTML5?” I expect both MoSH and WPF/Silverlight to support new device interfaces such as location, multi-touch, gyroscopes, Kinect, etc. I'm not sure if the support will come in the form of .Net 5, be built into MoSH, or as a separate cross-platform library. I believe MoSH for IE will be accompanied by a cross-platform version (Mozilla, Safari, maybe Chrome) in the form of a browser plugin. Marc Andreesen has predicted “The browser will become the OS”. I believe more correctly the control renderer will become the OS. MoSH will become the heart of IE apps, Windows 8 and Windows devices (Windows TV anyone?). The pundits will say Microsoft is becoming a control's vendor. Microsoft could write MoSH controls by C#, native code, or Javascript. This is another key question. Perhaps they'll use all three with Javascript being used for the plugins.
The second technological change is what Microsoft might be calling Native Code. Native Code is a set of technologies that enable software (applications and gadgets) and hardware (graphics) to perform at near native speed inside a container (browser). Most notably, Microsoft will supply tooling to build browser applications, principally with MoSH, without today's performance penalties. Currently browser based applications are limited by API availability (DOM), programming speed (Javascript), and often software rendering. This will all change. Internet Explorer 11(?) will expose a much richer API, possibly .Net 5.0, Visual Studio will enable Native Code development, and IE's Trident renderer will directly use hardware graphics.
Some issues I'm unclear on: .DLLX, run across all devices? If so, when is the code JITed? .Net languages? I'm guessing Microsoft is working hard to limit the changes to attributes. .Net sandboxing or with the aid of hardware as with Google's Native Client (NaCl)? This would make the difference as to whether C will be supported.
* Will Microsoft port MoSH and Native Code to iOS and Android? I'm guessing that they intend to do so directly or through partnerships.
* Will a single dll, possibly named
* Will Native Code force any syntax changes to
* Is Native Code implemented using
* Do CPU processors need changes to optimally support Native Code? Remember, Windows 8 will run on ARM. ARM are the non-Intel processors that power most tablets. Do all existing processors and graphics chips support Native Code and MoSH? I'm particularly curious about the compatibility of legacy ARM processors.
What does Microsoft hope to gain by these changes?
* Build an eco system based on HTML5 standards. The idea being that no competitor can block Microsoft’s tools because they’r
$1.375 billion or $990 million formatted.
Think about long term. This won't be the first and last app you develop. Have confidence in your dev skills. Treat this as a learning experience. Make a good choice. Execute well. Learn from the choice so you can do even better next time.
Does this count under the French three strike rule? I bet it will. Nothing like a good threat to extract the upper hand in negotiations. I'll bet some mouthy minister takes up the threat to cut off Google's Internet access under the three strike rule. Nationalism, populism and greed will surely overpower any talk about citizen's benefits. The big loser is not Google, it's the citizens of France.
As the project leader for the open source French Verb Conjugation Rules Database project at SourceForge, I hope Microsoft considers the prior art contained within it. The database contains RegEx expressions for conjugating and infinitizing French verbs. The database is in Microsoft Access because it easily handles Unicode. Algorithms were written in .Net.
http://sourceforge.net/forum/forum.php?forum_id=49 0001
The world needs more open source versions of similar databases and linguistic algorithms. Language processing databases and software are ideal global open source projects. I would greatly value an open source project that documents syntax forms and algorithms for the world's languages. I have not found such a project.