Smart, but not necessarily intuitive...
Umm. Before I start with what this post is all about. There was another development on the Google/Motorola situation that make this even more interesting. And I really can't help but bring these points out. That interesting development was that Microsoft won a motion to move the last patent suit (aside from one under investigation that will likely be moved as well once the investigation is complete) to the court jurisdiction of their choosing.
Apparently it is common practice to try and get IP suits tried in specific jurisdictions as each locale has a different mindset in general on intellectual property. And I guess Motorola knew this and started launching suits in every state under the sun. This ultimately is what it seems lead to the courts permitting this last case to be moved. The judge recognized that all of the other cases were already moved to Washington (I believe that was the place at least) and Motorola had no reason to be pursuing the suit in the state it was in, which was apparently not even a state in which the company operated.
Anyway this is interesting because if Microsoft wins these suits (and having them moved to their court of choice makes this more likely according to various reading material on the topic) Motorola may be banned from selling Android devices in the US. Which means Google will be under the same restriction when they acquire Motorola. I wonder if Google will call the whole thing off now and state that it fell apart during due diligence, of course that might be bad as well, as it would basically be equivalent to saying "Yup! We really did want the hardware business as well" which might tick off their partners more.
So, the smart but unintuitive element! Writing code in WPF/Silverlight that runs in a separate thread is a little bit of a nuisance. Increases number of lines of code by quite a bit per occurrence. But the discovery today is that it might be worth it. Started writing a little application on the side that was integrating with NHibernate, and when I was loading everything on the main thread, it would take close to a minute for the application to complete creating of the SessionFactory, but when I offloaded it to another thread, the process completes in seconds. Yes, I absolutely expected a dedicated thread to be faster, but this was several fold faster. It leads me to believe that the main thread in WPF/Silverlight might be throttled. Either that or there is a ridiculous amount of overhead going on in that thread. Either way, man that was quite the difference.
Apparently it is common practice to try and get IP suits tried in specific jurisdictions as each locale has a different mindset in general on intellectual property. And I guess Motorola knew this and started launching suits in every state under the sun. This ultimately is what it seems lead to the courts permitting this last case to be moved. The judge recognized that all of the other cases were already moved to Washington (I believe that was the place at least) and Motorola had no reason to be pursuing the suit in the state it was in, which was apparently not even a state in which the company operated.
Anyway this is interesting because if Microsoft wins these suits (and having them moved to their court of choice makes this more likely according to various reading material on the topic) Motorola may be banned from selling Android devices in the US. Which means Google will be under the same restriction when they acquire Motorola. I wonder if Google will call the whole thing off now and state that it fell apart during due diligence, of course that might be bad as well, as it would basically be equivalent to saying "Yup! We really did want the hardware business as well" which might tick off their partners more.
So, the smart but unintuitive element! Writing code in WPF/Silverlight that runs in a separate thread is a little bit of a nuisance. Increases number of lines of code by quite a bit per occurrence. But the discovery today is that it might be worth it. Started writing a little application on the side that was integrating with NHibernate, and when I was loading everything on the main thread, it would take close to a minute for the application to complete creating of the SessionFactory, but when I offloaded it to another thread, the process completes in seconds. Yes, I absolutely expected a dedicated thread to be faster, but this was several fold faster. It leads me to believe that the main thread in WPF/Silverlight might be throttled. Either that or there is a ridiculous amount of overhead going on in that thread. Either way, man that was quite the difference.
Comments
Post a Comment