I have been reading all the signals from Microsoft (free upgrade, last version, free for life) as them moving to: a subscription model, a hardware tie in model, or both. While I recognize I could be wrong, this has lead me to telling people to cling to their Windows 7 licenses. Get them before they are gone. Just in case!
How many drones will be lost to dogs?
That is a great idea! Where can I get an anti-drone dog?
It won't be delivered by a drone, right?
Please mod parent up!
- 1: Always run changes by your existing customers.
- 2: Always look around and see if there is a "case study" for what you are considering.
That is great, however there is a whole set of employers that hire by the project. I personally attempt to avoid this (trying to provide stability for my family), however there is a certain appeal in always being focused on building something new. In this situation, having someone trying to make sure there is a next project to move to, would be nice.
Java has been open source for some time.
People still have trouble with the owner monetizing it.
.NET has just now been open sourced.
People should jump from Java to C#, because now the
I am confused, did I miss something?
The real last step is getting the WinRT APIs and environments up to snuff so they can be seamlessly used alongside Win32 applications on the desktop.
You mean like this?
I am no fan of Windows 8, however it biggest problem is its face not its core or its capabilities. Compared to a few years ago (when the: common, random, and jarring full screen interruption was a blue screen of death), this is the world upside down.
While I freely admit that most of my programming has been in other areas. In every project I do it seems the day comes when boss says, what we need here is a visual. Where: when I click on it here..., when I drag it their..., when I spin it... What you have to understand (and many here do) is that you screen/window/view is laid out in a coordinate system. So you cannot escape it! You quickly need: geometry, trigonometry, vectors, and if your doing any 3D calculus.
Did anyone in Star Trek ever wear a watch?
I cannot believe I am on Slashdot right now.
There have been compatibilitiy problems irking consumers ever since Vista x86_64 hit the market.
What? I never ran Vista x64, but I did run Windows 7 and do run Windows 8 in 64-bit. The only compatibility problems I've ever seen are with 16-bit programs...
The early 64bit days on windows where rough. Why? Programs that thought they knew where their 32bit dependencies would always be. Microsoft recompiled Windows (with some real effort) for 64bit meaning things like the Windows directory went from being 32bit to 64bit. 32bit versions supplied for backwards compatibility were provided under a new parallel structure (with different names) known as WoW64 (Windows on Windows). If you built your software with the proper: relative paths, environment variable, and registry references things just worked. If you had hard-coded paths or chose the wrong references, your software broke.