|
Just to satisfy my curiosity: what area of functionality/support do we talk about that breaks your path to Windows 8?
Cheers
Andi
PS: Do you know this proverb: "Attributing others with nicknames tells more about you than about the others..." 
|
|
|
|
|
No. I have found sme surviving videos, so I can show you.
Here you see the 3D engine[^] at work. And here we have a video about the GUI[^].
Both needed XNA, which was silently scrapped. Instead they wanted to haveus write some Win8 (cr)app, made for weak devices that don't support half of what was needed. Much less did I want to wate my time porting code once again.
Sent from my BatComputer via HAL 9000 and M5
|
|
|
|
|
So, how is Windows 8.1 treating you?
|
|
|
|
|
Not at all. Win 7 is still good for running old stuff, but I have already thrown out Visual studio and do my programming with C++ again.
Sent from my BatComputer via HAL 9000 and M5
|
|
|
|
|
I don't think any version of .NET has become obsolete. It has just got bigger with the newer versions.
Regards,
Rob Philpott.
|
|
|
|
|
There are obviously still People who use Versions 1.0 or 1.1. They have not seen much new stuff for almost 10 years and the clock is ticking for the support for those Versions to end. Or has it already?
And what about Windows Forms, WPF or Silverlight? One UI has been chasing the next. What great new things can we expect here? Probably just one more member in this Club: Metro, after the Mickeysofties have found the next great Thing.
Sorry, but the .Net Framework has become a museum and None of the exhibits has had the time to mature before it started to collect dust.
Sent from my BatComputer via HAL 9000 and M5
|
|
|
|
|
What is *your* product life cycle? How long do you support people who do not migrate to your latest version of the software? I wonder if you can afford to provide bugfixes on *old* versions...
Cheers
Andi
|
|
|
|
|
*My* lifecycle is a little different. I have been building libraries since the stone age. Libraries always insulated me from the OS (or frameworks), saved me a lot of time and with version control can also be easily be adapted to changes without breaking older code.
This worked great for all kinds of operating systems or languages, but not at all for Mickeysoft and .Net. After Vista they became more and more chaotic and kept introducing more and more changes just to sell their next great idea. I was working more and more to keep up with their random changes of direction than I was working on any projects. The end came when they decided to kill some things to 'help' us over to Windows 8. Rewriting major parts was just a Little too much, so I scrapped everything and I will not touch anything from Mickeysoft again until the new Lamborghini they owe me for this stands in front of my door. That probably means never.
So what do I do now? I dug out 10 year old stuff which (oh miracle!) still works as good as it always did and started to look for some good open source libraries. Someone further up called what he was doing instead of .Net 'multi platform C++'. Sounds good and it also feels good to be back in the scary unmanaged world again.
P.S: Any errors in capitalization also are Mickeysoft's fault. The spell checker in the browser refuses to let itself be deactivated, but also does not care that I'm currently not writing in my native language.
Sent from my BatComputer via HAL 9000 and M5
|
|
|
|
|
that's like justifying the question from my kids about taking a shower or cleaning their room. it's just going to get dirty again.
you want something inspirational??
|
|
|
|
|
Still, I don't need Mickeysoft to get myself dirty, mess up a room or otherwise make my life more exciting. And I assume you don't often say 'Take it or leave it' to the kids, right? 
Sent from my BatComputer via HAL 9000 and M5
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
