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.
Except for out-of-the-box integration with Remote Workplace
Alright, Microsoft Remote Web Workplace provides a convenient web interface (through a proprietary IE plug-in) to connect to RDP through a proxy. As long as IT supports Android and iOS, they will provide a way to RDP using one of the available third party clients. So how is this the must have, separating SurfaceRT from the established players?
let Metro apps run in a window on the desktop + add back windows 7 start menu. With only 1 control plan is realty all they need to do.
You can get the first two for $8 right now. I just did this for my parents who said, "Learning something new at this point just isn't a good idea."
Bye, bye, Ms. Karma Pie!
Hmm, interestingly 3.11 x 2 = 6.22, I never noticed that before.
7 + 1.1 = 8.
Do not throw out well engineered software, maintain it.
the problem is untangling the business logic and reproducing it without error
Hold the phone. I thought we were discussing upgrading. Too many of these comments assume an "upgrade" necessarily means replacing the old software with something completely different. I believe this is a bad assumption! The poster specifically mentions IE 6, which is only eleven years old. So we are well into the era of MVC programming where the code talking to IE6 is the View. Therefore in order to upgrade it for newer browsers, you should not be touching the business logic. I full recognize that you may have inherited a pile of spaghetti logic without any comments (as I did three years ago), in which case I wish you luck in your replacement endeavors (after getting some radical new requirements, I am just now getting close). I also realize that "updating for new browsers" could mean adding missing closing tags to replacing an ActiveX plug-in with AJAX components. However, in a great many cases we are working with the Controller's and Model's APIs and not touching the business logic (nor moving heaven and earth).
Businesses need to view both computers and software as a durable good. You maintain durable goods until they either catastrophically fail or are so outstripped by newer technology that a new one actually saves you money or makes you more money.