I find it hard to believe that, as currently .Net calls the API's. Could you show me an example that shows this situation?Quote:
Originally Posted by Krzemo
packetvb
Printable View
I find it hard to believe that, as currently .Net calls the API's. Could you show me an example that shows this situation?Quote:
Originally Posted by Krzemo
packetvb
I think if ms doesnt want to support us as developers wanting to use vb
let them, ill switch my platform to somthing else linux and mac are looking for developers and with better conditions:
1. ill have less competion in my product class, with higher prices
2. nothing like embedded vb-conditions like winsock recv bug are nice reminders that our software cant be better than its operating system
3.open source and in apples case discounts towards dev systems
4.free tools
5.linux and apple need developers, in macs case this quarter ended i think i reads 3 folds higher than last years. im sure linux is used about that much more
6.example if i wanted to test my software on media center edition, i could one buy a whole new system, or buy a major hardware part and the software from a online retailer, i think that is funny
if im going to learn a new language its going to be somthing else and im not paying the bill gates tax to continue supporting his stock .net does sound like a improvement to go to just a bad move, its not like processors are getting slower, vb is fine the way it is for every one looking to do somthing basic
microsoft might not leave vb but we can leave microsoft to making their own pdf editors and software, bugs
Maybe you should have learned C++ instead of VB ? If you're going to switch OSes then you're going to have to now... :D
Come on, VB was only intended to be a learning language/rapid prototyping tool right from the off. In the modern day of object oriented languages VB6 really doesn't have anywhere left to hide.
Darwen.
I've come across a few claims which have asserted this. Last year I had an interview where they told me that they'd rewritten one of their apps. in C# from C++ and it was faster. I think the situation here is that the design of C# or other managed languages is such that you may more easily be able to express certain designs and that you get the performance boost because of this rather than because of a line-by-line comparison.Quote:
Originally Posted by packetvb
For example there is a case study on Eiffel Software's site, where one of their customers rewrote an app. from C to Eiffel and found that it was 10 times faster.
http://www.eiffel.com/executives/cas...xa/study1.html
Eiffel also uses a "managed" environment but in its case it gets compiled down to C. This means you will get at least comparable performance to C. Nonetheless in this case they got a 10 times boost, so this must be due to the OO design, resulting in more efficient code organisation, e.g., generics and multiple inheritance.
It dosen't matter b'cos we all know we have to upgrade to .net.
That's Microsoft Programmer
Since when is it an "upgrade"? And from what? Looks like a whole new ball of wax altogether.Quote:
Originally Posted by Soft_Brains
I can't speak for anyone else, but my system, and all my programs including development environments are still working just as before, and will continue to do so as long as I choose. No company can magically cause my system to cease functioning until I use their product. While it may be true that I'll need to cater to the chosen platform of the average consumer, it's also true that backwards compatability keeps things from radically changing over night. In any case, neither .net nor windows is written in .net. This means m$ must use another language to write them, like C++. There's a lesson in there...
For a long time now, I have been disgruntled by m$'s money grabbing dictator type philosophy.
I have for some time now been developing applications primarily in asp. I have to say I was pleasantly surprised by .net web-matrix (which is free). It cuts the time by more than half that it takes to develop a distributed database application. Although it is a little confusing to begin with.
Regards
I think that it's possible more .NET apps will be written with the advent of XP-64 bit and 64-bit processors.
.NET will automatically take advantage of 64-bit processors without the need for a recompile, whereas C++ will not.
And there are commercial .NET applications out there. Albeit not very good ones, but they do exist.
Here's one for subtitling :
http://www.fileboost.net/directory/m...84/review.html
A lot of .NET BCL is written in .NET - you can even decompile it using Loetz Roeder's disassembler.Quote:
In any case, neither .net nor windows is written in .net.
Presently Windows doesn't have any .NET code in it, but Longhorn will change this situation.
Darwen.
i also heard that there is no scop in vb.net every one looking in to java
The question is answered with the Delphi 8 release: Delphi continues to support both Win 32 and .NET platform, and intends do to so in the future.Quote:
Originally Posted by sukarso
It is more likely that Microsoft will abandon VB.NET in the future, since there is no more a big difference between C# and VB.NET, like it was between VC++ and VB6.
Actually M$ has stated that they have no intension of abandoning VB at all. Personally I almost wish they would.Quote:
Originally Posted by ergas
They are just not releasing any more service packs for VB. SP6 is now the last available for VB6.Quote:
Originally Posted by Pinky98
But the rest will stil be there for a while (or until us old farts who still use it die :cry: )
Speaking of SP6. I downloaded it last year, but I haven't gotten around to installing it. Is it really required ?
Personally, I think you should always have a trick in your baggage...You should not be very dependent on one specific technology you are coding-in in today's dynamic world. Its ever-changing and it's very tough to predict the future since everyone is trying to bring in some new idea, new concepts and who knows tomorrow coding could become so simple that even the clients start making applications with tools...
Talking of tools - I would expand on one of my own beliefs - the coding is becoming easier day-after-day. People find learning the new technologies much easier to produce production code than they used to when the whole software business started. .Net has become so simple to code in - you know what your client wants and bang! you have it coded it right away. And that abstraction is only going to improve.
What I feel is - what matters is what you code about and not what you code in. And that would mean that I am pointing towards domain of expertise rather than technology. Technology sure helps you earn better and open up the market for you but a blend of the domain specialization is something that is going to help you even though tomorrow the technology you used to work in ceases to exist! It just depends upon your choice of what domain you chose to specialize and this is what I personally think is very, very important in today's work environment. Regards All!
//Btw, nice thread with some very good/excellent posts ...nice learning. :thumb:
Urm... are we atlking VB the language? Because the language is still alive and kicking in the form of VB .NET, but yes M$ don't even want to know about VB6 any more.Quote:
Originally Posted by GremlinSA