|
Now don’t get me wrong. C++11 is fantastic! I am in just about 100% agreement with all of the changes that have been made. C++ has definitely become much easier to use and it has even become more powerful. There is one thing it didn’t become though—and this is the most important—more simple. It seems that many of the seasoned developers have forgotten why we stopped using C++ and moved on to Java, C# and other modern languages. But there is still some value in learning C++.
|
|
|
|
|
I love C++. Yeah, C++11 made it a lot better than what it was for sure. C# has some simplicity. I keep going back to C++ for gui work simply because WPF is just too insane. It requires a lot of "do it your damnself" rather than offering some simplistic stuff like (enable tab closing, no multiline tabbing, drag and drop previewing), etc. No C# book I have shows how to do sockets properly. I have yet to find decent documentation on C# sockets, especially with non-blocking event sockets.
I love programming, even if I have to deal with pointers. C++ offers a lot of gui frameworks like Qt, wxWidgets, etc. I prefer Qt, because win32, MFC, etc. just doesn't offer simplicity when designing gui applications in C++. I can easily have a nice gui program in way less time than I would in win32 and MFC. Microsoft's documentation is just piss poor on win32. COM is just horrible in C++ unlike in C#. That's another good thing about C# is COM development.
My only gripe about C++ is Microsoft's slow arse at adding features of C++11. It is so far behind it ain't funny. GCC, Clang, etc. are almost done with the implementation of C++. Microsoft doesn't offer continuous updates of their C++ compiler for C++11. You have to wait for the next major release of Visual Studio to find more features. I can almost use all of C++11 when I'm developing a C++ application in Linux. I wouldn't be able to port it to Windows for use.
This is how I see the Windows platform. If you are going to develop for it use C#. Don't even bother with C++. If you want C++ development switch to Linux.
|
|
|
|
|
xComaWhitex wrote: No C# book I have shows how to do sockets properly. I have yet to find decent documentation on C# sockets, especially with non-blocking event sockets. I found the help and MSDN to be more than adequate, if you understand the basics of socket communications.
We have a TCP/IP socket-based tracing tool we developed for debugging our distributed application. It requires several complex classes, including threading and pool support, in our C++ applications. I replicated all of the functionality in C# in less than a day.
Software Zen: delete this;
|
|
|
|
|
xComaWhitex wrote: C# has some simplicity. I
my app complicated enough, i don't need any further complexity to delete(thisshit)
xComaWhitex wrote: <layer> I keep going back to C++ for gui work simply because WPF is just too insane
yea think WPF sucks sh*t but why not just use Winform?
xComaWhitex wrote: My only gripe about C++ is Microsoft's slow arse at adding features of C++11
I started my career doing MFC/WIN32/C++ - but I wish C++ just die and everything just .NET/C# so I can only focus on real application logic/capability
xComaWhitex wrote: If you want C++ development switch to Linux.
I don't switch to another platform because it's cool or that I want to do C++
(I would if it *PAYS*)
xComaWhitex wrote: That's another good thing about C# is COM development.
Gosh, they used to say "COM is Love". WTF just hype ... all this complexity to for just a god damn procedure call? I remember one whole book just on DCOM while I can wire down any sh*t with C# in binary format with existing library or build new one for RPC in two days.
All in all, I wish C++ is dead and whole world just do one single language C# and one single API - .NET
dev
|
|
|
|
|
Thanks. Good stuff. Unfortunatley cannot vote.
|
|
|
|