Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
Lots of reasons; logon utility for enterprise-wide systems, input applications such as system-wide shortcut keys, search indexer, connection manager, image cache manager, continous on-line backup, and on and on and on.
Just open task-manager and look at all those many processes and those few applications.
Suppose, i have a database, the database of companies. This database was made from few other databases. Now, i have a lot of companies with almost the same names and the same addresses. I'm sure that the "similar" companies are the same, in spite of fact that they differ each other few signs in the name and have different ID's.
The general question is: how to create a wizard which can help user to analyze database, to suggest for user which companies are probably the same? How to merge companies ID's and remove wrong inputs?
I'm sure that, i can't merge ID's without help from user.
I'm trying to write algorithm which can:
1) compare the array of strings,
2) find a string with the longest similarity (biggest substring), to use it as a model,
3) define a similarity (in percentage) to the rest of strings, based on model.
The suggested Gestalt correlation gives the following correlation figures without considering any additonal information. Note that it would give similar results if the "typo" was somewhere in the middle of the text.
Basically, agree, but by somewhat different reasons.
Yes, VB.NET is similar in features compared to C# but always goes behind. Microsoft just does not take VB.NET as seriously as the flagship of C#. Other problems are more serious: VB.NET would be a pretty bad investment. First, C# and C++/CLI go through strict standardization under ECMA and then under ISO, but it never happens to VB.NET. I cannot believe it might ever happen in future.
There is one more reason, the social one. The fact is: many developers considering themselves at least "professional" do not take anything named similar to "VB" as "real". The historical reasons just do not matter (VB earned bad reputation with both quality and popularity with poor developers, and whatever else), this is the real attitude of real people. This is not for the flame wars or something like that. I'm trying not to express my own attitude; this is just a "medical fact", fact of nature.
In fact, if you try to find an answer of some technical question in .NET, best answers are usually in C#, and much more finding on most difficult topics will appear in C#. So, a serious VB.NET developer should also understand at least some C#.
By the way C++/CLI is a powerful thing which should be taken into consideration. I can see some drawbacks in it (I used to discuss on CodeProject pages). For example, I saw Microsoft article where they explained that it has its special optimized instead of general-purpose .NET optimizer used with other compilers. Mixed mode and value (stack) semantic for reference type are unique to this language (not counting IL).
I've been doing this for a LONG LONG time. I really don't need the history lesson on why VB has the reputation it does.
Also, Microsoft DOES take VB.NET seriously and it shows as the feature sets between C# and VB.NET have been merging quite a bit and continues to [ut considerable resources into adding features concurrently into both languages. And with .NET 4.5, VB.NET will get a feature you can't have in C# yet. I'll let you squirm on what that is for a while while I go try to remember what it was!
All I was refering to in this thread was that VB.NET doesn't support pointers, which makes image processing quite a bit easier.
May be I'm wrong, but I feel you are overreacting about "history lesson", saying as if it's something bad. What's wrong with lessons? As you probably know this history better then I do (mainly because I never allowed myself to play with the idea of accepting the opportunity to work with VB), you can always tell us something more interesting and useful than I could. And correct me if I'm wrong. I've noticed a long time ago that reading your posts can be really useful; as that can give a chance to learn something, and I'm trying not to miss a lesson, even if I think I know things the best way — but I always can be mistaken, like probably all of us. Perhaps it's good to remember that if I reply to your post, it does not mean that I always address personally to you. Everyone can read our conversation.
Thank you for interesting discussion. Will talk to you later.
I hope we are good. And we are doing basically the same thing on this site for this community. As to the criticism and possible negative estimates or votes, they are normal, absolutely unavoidable in any truly creative environment, as well as our mistakes, and they can be and should be handled in productive and constructive ways.
No, we're good. If I was pissed at you, I'd just ignore you.
As to the criticism and possible negative estimates or votes, they are normal,
absolutely unavoidable in any truly creative environment, as well as our
mistakes, and they can be and should be handled in productive and constructive