Trolling 101
-
That describes it perfectly. It is also useful for making flowcharts. Wait, flowcharts? What are those?
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
-
Thanks for supplying that analogy, because it's perfect! The sole little problem with it is that you said Microsoft put a box in place of the wrench and put the wrench in the box. No, they didn't. They put the box next to the wrench and left it up to you if you want to put the wrench in it.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
Nonetheless his credentials, he have something right, if you work on computers, the only thing that remains constant is the change, and if you work on computers, you're expected to keep moving on to the next "big thing"; there are, of course, maintenance of legacy systems (here, for example, every time i look for a job i find that Cobol programmers are still needed), but one of the reasons why i choosed this carrer is because is always and constantly changing.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
Dave Kreskowiak wrote:
No, they didn't. They put the box next to the wrench and left it up to you if you want to put the wrench in it
Nope. They keep moving stuff. It doesn't matter how or why they moved it. All that matters is that it was moved.
I've been writing code for Windows for about 20 years now. I know how Microsoft works and how the technology advances. They keep introducing new technologies. There is nothing Microsoft does that forces you to use them right now. Sure, very old stuff gets deprecated, like the VB6 community that refuses to die. But there is NOTHING at all forcing you to write Metro/Modern apps right now.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
I've been writing code for Windows for about 20 years now. I know how Microsoft works and how the technology advances. They keep introducing new technologies. There is nothing Microsoft does that forces you to use them right now. Sure, very old stuff gets deprecated, like the VB6 community that refuses to die. But there is NOTHING at all forcing you to write Metro/Modern apps right now.
A guide to posting questions on CodeProject[^]
Dave KreskowiakDave Kreskowiak wrote:
They keep introducing new technologies.
I didn't say anything about "new" stuff. What I said was that they moved existing stuff. Additionally you seem to be talking about the APIs and not the user interface.
Dave Kreskowiak wrote:
I've been writing code for Windows for about 20 years now. I know how Microsoft works and how the technology advances.
And I first wrote code for windows using Windows 3.1 and I used Windows 286. And I wrote code for PCDOS before that.
-
Dave Kreskowiak wrote:
They keep introducing new technologies.
I didn't say anything about "new" stuff. What I said was that they moved existing stuff. Additionally you seem to be talking about the APIs and not the user interface.
Dave Kreskowiak wrote:
I've been writing code for Windows for about 20 years now. I know how Microsoft works and how the technology advances.
And I first wrote code for windows using Windows 3.1 and I used Windows 286. And I wrote code for PCDOS before that.
jschell wrote:
What I said was that they moved existing stuff.
Who hasn't moved UI stuff around?? There comes a time when it just doesn't make sense to have something where it is now or the argument that made the decision was valid then but not any more. Change happens. It's a fact of life. Why bitch about it?
jschell wrote:
And I first wrote code for windows using Windows 3.1 and I used Windows 286. And I wrote code for PCDOS before that.
You're not the only one to go back that far.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
jschell wrote:
What I said was that they moved existing stuff.
Who hasn't moved UI stuff around?? There comes a time when it just doesn't make sense to have something where it is now or the argument that made the decision was valid then but not any more. Change happens. It's a fact of life. Why bitch about it?
jschell wrote:
And I first wrote code for windows using Windows 3.1 and I used Windows 286. And I wrote code for PCDOS before that.
You're not the only one to go back that far.
A guide to posting questions on CodeProject[^]
Dave KreskowiakDave Kreskowiak wrote:
Change happens. It's a fact of life. Why bitch about it?
Or why claim that it is better?
Dave Kreskowiak wrote:
You're not the only one to go back that far.
Yet you are the one that first posted it which suggested that you thought it was relevant.
-
Dave Kreskowiak wrote:
Change happens. It's a fact of life. Why bitch about it?
Or why claim that it is better?
Dave Kreskowiak wrote:
You're not the only one to go back that far.
Yet you are the one that first posted it which suggested that you thought it was relevant.
Yeah, I brought it up because I've been through over 20 years of Microsoft's changes and not once was there any pressure to drop what you're doing and go learn "the new thing". You get to it in your own time. What WILL put the pressure on you to move to new technology are customers, not Microsoft.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
He's a software consumer, not a software producer. For him it's just a menu change whereas for those of us who produce software it's learning XAML or a new database access framework or a new set of UI standards - where half the time we are working with incomplete frameworks so we have to write work arounds until version X fixes the problem - etc. If it was my job to understand that given a new UI I simply have to recognize that button 'A' is now located under submenu 'B' I wouldn't have much to complain about either. I'd use my spare time to write troll articles for ZDNet.
-
Learning is integral part of programming. If learning becomes cumbersome, perhaps its time to start thinking about retirement.
-
Yeah, I brought it up because I've been through over 20 years of Microsoft's changes and not once was there any pressure to drop what you're doing and go learn "the new thing". You get to it in your own time. What WILL put the pressure on you to move to new technology are customers, not Microsoft.
A guide to posting questions on CodeProject[^]
Dave KreskowiakDave Kreskowiak wrote:
Yeah, I brought it up because I've been through over 20 years of Microsoft's change
And thus it is certainly reasonable when I also point out that I have been through exactly the same changes as you. Thus your experience in that regard is no more relevant than mine.
Dave Kreskowiak wrote:
and not once was there any pressure to drop what you're doing and go learn "the new thing". You get to it in your own time.
Pretty sure Microsoft no longer supports Windows 3.1. So there is certainly some indirect pressure to move off of that OS.
Dave Kreskowiak wrote:
What WILL put the pressure on you to move to new technology are customers, not Microsoft.
Which has absolutely nothing to do with the quality of the Windows software nor the design of the user interface. Good or bad. So I have no idea what that has to do with this sub-thread.