Development Overload
-
Microsoft is killing me with all this new development technology. Have you seen the next generation, Visual Basic or c#. They have: LINQ (it's basically SQL for your generic's) LINQ stands for Language INtegrated Query and in a nutshell, it makes query and set operations, like SQL statements first class citizens in .NET languages like C# and VB. XLinq XLinq is XML code embedded in your program. (And a lot more)
Dim contact As XElement = <contact> <name><%= myName %></name> </contact>As if that wern't enough now we have WinFX And the Presentation Framework to deal with (As well as the tools that go along with those). But let us not forget that VS 2005 just came out... UGH... Does anyone other then me find this the least bit overwhelmed by aall this new stuff coming out AT THE SAME TIME? What do we learn next? :confused: --- Sometimes I miss the simpler DOS days of Borland Turbo Pascal (Heh, but not for to long). Matthew HazlettMatthew Hazlett wrote:
Does anyone other then me find this the least bit overwhelmed by aall this new stuff coming out AT THE SAME TIME?
Yes. I'm sure all of this new technology would add greatly to productivity if it would actually stabilize long enough for someone to become proficient with it. But, hell, the very minute you've learned the latest and greatest technology, another one comes along. Oh, for the good ol' days... when ever that was... "If anything, the West is awash in an epidemic of self-hate crimes." "a civilization that feels guilty for everything it is and does will lack the energy and conviction to defend itself"
-
Microsoft is killing me with all this new development technology. Have you seen the next generation, Visual Basic or c#. They have: LINQ (it's basically SQL for your generic's) LINQ stands for Language INtegrated Query and in a nutshell, it makes query and set operations, like SQL statements first class citizens in .NET languages like C# and VB. XLinq XLinq is XML code embedded in your program. (And a lot more)
Dim contact As XElement = <contact> <name><%= myName %></name> </contact>As if that wern't enough now we have WinFX And the Presentation Framework to deal with (As well as the tools that go along with those). But let us not forget that VS 2005 just came out... UGH... Does anyone other then me find this the least bit overwhelmed by aall this new stuff coming out AT THE SAME TIME? What do we learn next? :confused: --- Sometimes I miss the simpler DOS days of Borland Turbo Pascal (Heh, but not for to long). Matthew HazlettNo, not all. I just got to update VisualAssist for my trusty VC6.
Some of us walk the memory lane, others plummet into a rabbit hole
boost your code || Fold With Us! || sighist -
Microsoft is killing me with all this new development technology. Have you seen the next generation, Visual Basic or c#. They have: LINQ (it's basically SQL for your generic's) LINQ stands for Language INtegrated Query and in a nutshell, it makes query and set operations, like SQL statements first class citizens in .NET languages like C# and VB. XLinq XLinq is XML code embedded in your program. (And a lot more)
Dim contact As XElement = <contact> <name><%= myName %></name> </contact>As if that wern't enough now we have WinFX And the Presentation Framework to deal with (As well as the tools that go along with those). But let us not forget that VS 2005 just came out... UGH... Does anyone other then me find this the least bit overwhelmed by aall this new stuff coming out AT THE SAME TIME? What do we learn next? :confused: --- Sometimes I miss the simpler DOS days of Borland Turbo Pascal (Heh, but not for to long). Matthew HazlettI think it's kinda interesting to have so much variety. Lots of exciting stuff to learn. It gives us developers a chance at making more money too :-) Regards, Nish
My blog : Nish’s thoughts on MFC, C++/CLI and .NET
-
Microsoft is killing me with all this new development technology. Have you seen the next generation, Visual Basic or c#. They have: LINQ (it's basically SQL for your generic's) LINQ stands for Language INtegrated Query and in a nutshell, it makes query and set operations, like SQL statements first class citizens in .NET languages like C# and VB. XLinq XLinq is XML code embedded in your program. (And a lot more)
Dim contact As XElement = <contact> <name><%= myName %></name> </contact>As if that wern't enough now we have WinFX And the Presentation Framework to deal with (As well as the tools that go along with those). But let us not forget that VS 2005 just came out... UGH... Does anyone other then me find this the least bit overwhelmed by aall this new stuff coming out AT THE SAME TIME? What do we learn next? :confused: --- Sometimes I miss the simpler DOS days of Borland Turbo Pascal (Heh, but not for to long). Matthew HazlettMatthew Hazlett wrote:
Does anyone other then me find this the least bit overwhelmed by aall this new stuff coming out AT THE SAME TIME?
Very much so.
"The words of God are not like the oak leaf which dies and falls to the earth, but like the pine tree which stays green forever." - Native American Proverb
-
fat_boy wrote:
Look at COM, what a waste of time that was.
Damn, we agree on something. COM was the reason I moved to .Net. Anything had to be better than that insanity. "If anything, the West is awash in an epidemic of self-hate crimes." "a civilization that feels guilty for everything it is and does will lack the energy and conviction to defend itself"
-
fat_boy wrote:
but did it really offer the end user any benefit?
Without COM, then the integration of the various MS Office applications would have been a lot less smooth. Without it I wouldn't have been able to integrate some of my telephony products with various third-party applications or expose a rich object model to my customers to build on top of. Michael CP Blog [^] Development Blog [^]
-
fat_boy wrote:
but did it really offer the end user any benefit?
Without COM, then the integration of the various MS Office applications would have been a lot less smooth. Without it I wouldn't have been able to integrate some of my telephony products with various third-party applications or expose a rich object model to my customers to build on top of. Michael CP Blog [^] Development Blog [^]
-
we used to use another technology for that, i forget what it is called at the moment Nunc est bibendum
fat_boy wrote:
we used to use another technology for that, i forget what it is called at the moment
Well COM was the culmination of the work Microsoft did with DDE (Dynamic Data Exchange), Object Linking and Embedding (OLE) and with a little bit of the VBX controls thrown in for good measure. All these technologies made by apps better in the past. Of course, COM gets a bad name because of the associated IE Active X problems. COM was also a bitch to write until ATL came along too. But I still loved it. Michael CP Blog [^] Development Blog [^]
-
Microsoft is killing me with all this new development technology. Have you seen the next generation, Visual Basic or c#. They have: LINQ (it's basically SQL for your generic's) LINQ stands for Language INtegrated Query and in a nutshell, it makes query and set operations, like SQL statements first class citizens in .NET languages like C# and VB. XLinq XLinq is XML code embedded in your program. (And a lot more)
Dim contact As XElement = <contact> <name><%= myName %></name> </contact>As if that wern't enough now we have WinFX And the Presentation Framework to deal with (As well as the tools that go along with those). But let us not forget that VS 2005 just came out... UGH... Does anyone other then me find this the least bit overwhelmed by aall this new stuff coming out AT THE SAME TIME? What do we learn next? :confused: --- Sometimes I miss the simpler DOS days of Borland Turbo Pascal (Heh, but not for to long). Matthew Hazlett -
fat_boy wrote:
we used to use another technology for that, i forget what it is called at the moment
Well COM was the culmination of the work Microsoft did with DDE (Dynamic Data Exchange), Object Linking and Embedding (OLE) and with a little bit of the VBX controls thrown in for good measure. All these technologies made by apps better in the past. Of course, COM gets a bad name because of the associated IE Active X problems. COM was also a bitch to write until ATL came along too. But I still loved it. Michael CP Blog [^] Development Blog [^]
Yeah OLE, that was the one. We used to use it to manipulate Word from a VB app. Load a template, put an address in it from a jet DB etc. I did some pre ATL COM once, and, for an in proc server, could I see no benefit over using a straight dll. And before you say, 'dll hell', that only happens when a crappy instal writes an old dll to the system, and in reality, I have only experienced dll hell once, and for that reason. DCOM though is more impressive, but, as you say .NET has really made the whole thing redundant. Nunc est bibendum