Oh, maybe... because of the 2008 recession, which was caused by the financial crisis meltdown?
The crisis which became widely public in late summer/early fall of 2008, while he was still in the process of actually getting elected?
He didn't actually take office until 2009...
This has been a standard part of the republican playbook since the 80's... Either run up massive debt and ignore fiscal responsibilities just before leaving office, so that when democrats are elected, it "appears" as if it was all their fault, and then they have to spend time recovering...
So - they don't plan on using public cloud and combining with perhaps more than one vendor and/or using publically hosted websites? (i.e. Github, etc.)
If they stick with one or two vendors, then private connections are possible, but this seems to be quite a step backwards in todays network-neutral, cloud, SaaS & managed web services connected world...
Um - you realize the almost ALL of RIM's stuff is in Java. There are some smaller integration peices to interop with Exchange - but the BULK of their platform is Java-based...
The earliest was when I worked for a VAR back in 91/92 building custom systems for CAD/CAM use.
Our clients would pay for the absolute latest and greatest CPU's, at a time when most others managed to get by on 286's, they HAD to have 486 chips.
So, we tried out a different motherboard than we had used previously, I carefully grounded myself and seated the rather expensive 486 CPU... Built the rest of the system and turned on the power.
The room went black. The breaker had blown. Crapping my pants knowing my boss was going to kill me. RTFM - I had inserted the chip 180-degrees, this was before we had those nice missing pin 'hints'. Re-seated the CPU and turned the power on again.... vrooom - worked fine, even passed a 3-day burn-in test.
Phwew.
Next up - the story of how my crapberr..., uh I mean Blackberry fell in the toilet...
Ok - here's the rub. C# and the CLI specifications are not only ECMA standards - but they are now ISO standards. Just like C++ and the STL... Just like C...
What many of you don't realize is that if companies hold patents on mechanisms related to software development programming languages, compilers, parsers, lexers, interpreters, verifyers, runtimes, etc... this is not going to stop them from SUING ANY INFRINGING IMPLEMENTATION...
What is potentially vulnerable? Everything:
GCC
Python
Ruby
Perl/Parrot
Mono
Java
.NET
REXX
JavaScript
Basically, until some company decides to litigate NO ONE KNOWS which software may be infringing.
Patents are exactly like an arms race featuring nuclear weapons - everyone has to have 'em - but once the missiles begin to leave the silo's, there will be hell to pay...
Oh, maybe... because of the 2008 recession, which was caused by the financial crisis meltdown? The crisis which became widely public in late summer/early fall of 2008, while he was still in the process of actually getting elected? He didn't actually take office until 2009... This has been a standard part of the republican playbook since the 80's... Either run up massive debt and ignore fiscal responsibilities just before leaving office, so that when democrats are elected, it "appears" as if it was all their fault, and then they have to spend time recovering...
So - they don't plan on using public cloud and combining with perhaps more than one vendor and/or using publically hosted websites? (i.e. Github, etc.) If they stick with one or two vendors, then private connections are possible, but this seems to be quite a step backwards in todays network-neutral, cloud, SaaS & managed web services connected world...
Um - you realize the almost ALL of RIM's stuff is in Java. There are some smaller integration peices to interop with Exchange - but the BULK of their platform is Java-based...
The earliest was when I worked for a VAR back in 91/92 building custom systems for CAD/CAM use. Our clients would pay for the absolute latest and greatest CPU's, at a time when most others managed to get by on 286's, they HAD to have 486 chips. So, we tried out a different motherboard than we had used previously, I carefully grounded myself and seated the rather expensive 486 CPU... Built the rest of the system and turned on the power. The room went black. The breaker had blown. Crapping my pants knowing my boss was going to kill me. RTFM - I had inserted the chip 180-degrees, this was before we had those nice missing pin 'hints'. Re-seated the CPU and turned the power on again.... vrooom - worked fine, even passed a 3-day burn-in test. Phwew. Next up - the story of how my crapberr..., uh I mean Blackberry fell in the toilet...
Ok - here's the rub. C# and the CLI specifications are not only ECMA standards - but they are now ISO standards. Just like C++ and the STL... Just like C...
What many of you don't realize is that if companies hold patents on mechanisms related to software development programming languages, compilers, parsers, lexers, interpreters, verifyers, runtimes, etc... this is not going to stop them from SUING ANY INFRINGING IMPLEMENTATION...
What is potentially vulnerable? Everything:
Basically, until some company decides to litigate NO ONE KNOWS which software may be infringing.
Patents are exactly like an arms race featuring nuclear weapons - everyone has to have 'em - but once the missiles begin to leave the silo's, there will be hell to pay...