I've implemented a number of very large projects using COM (one written using VB, the other using Delphi). The larger of the 2 had over 800 COM dlls, the smaller has 30 COM dlls and is being used around the world in multiple languages. So yes, I have. The only thing that would have been insane about these projects was thinking about doing them in C++. That would suck. Delphi and VB make it easy (Delphi being the more powerful of the 2).
I've also read this book, I thought it was more of a methodology book with a few examples than a how-to book. Of course some of my bias is because I think of a Component as a Delphi Component where is something you can drop on a form (like a text box or a timer). The authors view of a component is a class/object, reguardless of what it does. I find that bogus.
Frankly I think the book was mis-titled, it should have been: Component-Oriented Programming in.NET.
A good OLAP service. Something to compete with Microsoft Analysis Service, Hyperion, and Oracle.
Other than that: a full Exchange and Outlook alternative. This is parcially there, but is really a "sum of parts" implementation, not one cohesive unit.
Neither does the author. He is talking about application development. Application development is different that OS development.
And as far as application development goes, C++ is a bad choice.
Point one: Applications dont care about squeezing every bit of performance out of their code. Niether do you if you use STL, so why not use a language that is actually easy to use overall.
Most windowing libraries that I've seen for C++ have a 6 month learning curve. I learned VB in 2 weeks, Delphi in 3 weeks, and C# in 1 week (posted in order learned). In both languages I was creating Windows applications in an hour. I've been using C++ for years and still cant create a decent Windows application in under 2 weeks.
Point two: Applications care about features.
Point three: Applications care about getting it done. And the faster they better.
Most applications are written in VB, Delphi, or Java these days, and.NET will quickly overtake them. Welcome to the real world.
I've been wondering about that all night (heard about it at my Borland developers group meeting last night). Are they moving into consulting or just giving up all together?
They do have wonderful tool, no doubt there. It would be a bad omen if they are closing shop altogether.
Personally, I think a lot of the Delphi Component developer groups are moving to.NET right now. Kind of an adopt or die mentality. Luckely the next version of Delphi will come with a C# compiler.
What is left after that??!! True, Delphi kicks VB's ass in every possible catigory...but after you take out C++Builder and Kylix you are left with
1. Delphi -- Competes with VB
2. JBuilder -- ya, MS just loves Java!
3. Interbase -- already got SQL Server, Access and Fox Pro
4. People -- oh wait, they already hired all of them away.
Consider this, Borland is MS biggest competitor in the compiler market. MS would buy Borland and gut it. Once again, the superior technology (Borland) looses.
Most dont use TCP/IP, it is to bulky. UDP/IP is far more common. Nice an light with none of the packet checking that you don't need anyway. After all, if a packet gets corrupted (on TCP/IP you have to resend a bad packet) you dont care, you get half a moment of static and you move on.
Your migrating to an unproven platform pretty early on. If there is one consistent thing about all microsoft products, its that ver. 1 sucks!
Good luck, I'm sticking with native compiled code.
I think this an introductory price (have any of you ever payed extra to have the latest hardware -- I pre ordered the MonsterII for $200 when it came out). Most people in the Kylix newsgroups agree that Kylix will cost less later on. $999 for the enterprise edition, but other editions for less (like 100-200).
All I can think of on this is Dana Carvey's 'Cranky Old Man' skits. I can actually hear him say "Bahhh!, we didn't have any of this funny 'World wide web' stuff when I was a kid, all we had was tin cans strung together with barbed wire to keep the cows in. And if you tryed to move one of the cans the farmer would come out and blow your leg off with a shotgun!! And we LIKED IT!!!" Same basic consept.
OK, this is a junk post. I admit it. I just had to figure this thing out myself OK.
Now on topic, I also think it is a nice idea but I'm definately missing a practical use for the transparent windows (I guess I'll have to think about it for a few days), right off hand: they seem like a good way to get lost.
Now the idea of IDL is intreging, definately have to look into that more.
I will 3rd that. Delphi is a wonderful language. Top that off with the fact that it is being ported to Linux and you have the best of both worlds. A easy to read language with all the power of C++ in the desktop enviornment of your choice.
Slashdot Mirror
Now if we could just quantify the rest of the psudo-sciences!! e.g. Psycology, Sociology, and the like.
I've implemented a number of very large projects using COM (one written using VB, the other using Delphi). The larger of the 2 had over 800 COM dlls, the smaller has 30 COM dlls and is being used around the world in multiple languages. So yes, I have. The only thing that would have been insane about these projects was thinking about doing them in C++. That would suck. Delphi and VB make it easy (Delphi being the more powerful of the 2).
.NET.
I've also read this book, I thought it was more of a methodology book with a few examples than a how-to book. Of course some of my bias is because I think of a Component as a Delphi Component where is something you can drop on a form (like a text box or a timer). The authors view of a component is a class/object, reguardless of what it does. I find that bogus.
Frankly I think the book was mis-titled, it should have been: Component-Oriented Programming in
Other than that: a full Exchange and Outlook alternative. This is parcially there, but is really a "sum of parts" implementation, not one cohesive unit.
Neither does the author. He is talking about application development. Application development is different that OS development.
.NET will quickly overtake them. Welcome to the real world.
And as far as application development goes, C++ is a bad choice.
Point one: Applications dont care about squeezing every bit of performance out of their code. Niether do you if you use STL, so why not use a language that is actually easy to use overall.
Most windowing libraries that I've seen for C++ have a 6 month learning curve. I learned VB in 2 weeks, Delphi in 3 weeks, and C# in 1 week (posted in order learned). In both languages I was creating Windows applications in an hour. I've been using C++ for years and still cant create a decent Windows application in under 2 weeks.
Point two: Applications care about features.
Point three: Applications care about getting it done. And the faster they better.
Most applications are written in VB, Delphi, or Java these days, and
All mules are infertal because they are cross-breeds. So no, they cannot reproduce naturally.
Neal Stephenson is a good start in this section, you wouldn't even have to change isles in the book store.
I've been wondering about that all night (heard about it at my Borland developers group meeting last night). Are they moving into consulting or just giving up all together?
.NET right now. Kind of an adopt or die mentality. Luckely the next version of Delphi will come with a C# compiler.
They do have wonderful tool, no doubt there. It would be a bad omen if they are closing shop altogether.
Personally, I think a lot of the Delphi Component developer groups are moving to
What is left after that??!! True, Delphi kicks VB's ass in every possible catigory...but after you take out C++Builder and Kylix you are left with
1. Delphi -- Competes with VB
2. JBuilder -- ya, MS just loves Java!
3. Interbase -- already got SQL Server, Access and Fox Pro
4. People -- oh wait, they already hired all of them away.
Consider this, Borland is MS biggest competitor in the compiler market. MS would buy Borland and gut it. Once again, the superior technology (Borland) looses.
Most dont use TCP/IP, it is to bulky. UDP/IP is far more common. Nice an light with none of the packet checking that you don't need anyway. After all, if a packet gets corrupted (on TCP/IP you have to resend a bad packet) you dont care, you get half a moment of static and you move on.
Still the number 1 backup device for a lot of applications out there. Not everyone has 10 gig of data to save.
AAaahh ha ha ha haaaa!!!
Life has meaning again!!!!
This is a must have for just about any computer programming library
Your migrating to an unproven platform pretty early on. If there is one consistent thing about all microsoft products, its that ver. 1 sucks! Good luck, I'm sticking with native compiled code.
I think this an introductory price (have any of you ever payed extra to have the latest hardware -- I pre ordered the MonsterII for $200 when it came out). Most people in the Kylix newsgroups agree that Kylix will cost less later on. $999 for the enterprise edition, but other editions for less (like 100-200).
hmmmmmmmmmm. So nice. Almost makes me wish I knew the language (Dutch, not delphi). Tot ziens.
All I can think of on this is Dana Carvey's 'Cranky Old Man' skits. I can actually hear him say "Bahhh!, we didn't have any of this funny 'World wide web' stuff when I was a kid, all we had was tin cans strung together with barbed wire to keep the cows in. And if you tryed to move one of the cans the farmer would come out and blow your leg off with a shotgun!! And we LIKED IT!!!" Same basic consept.
If it is C++ without that MFC gorilla standing on its sholders I'll go for it. (or did I just describe Borland C++ Builder?)
OK, this is a junk post. I admit it. I just had to figure this thing out myself OK.
Now on topic, I also think it is a nice idea but I'm definately missing a practical use for the transparent windows (I guess I'll have to think about it for a few days), right off hand: they seem like a good way to get lost.
Now the idea of IDL is intreging, definately have to look into that more.
I will 3rd that. Delphi is a wonderful language. Top that off with the fact that it is being ported to Linux and you have the best of both worlds. A easy to read language with all the power of C++ in the desktop enviornment of your choice.