I guess on one hand Microsoft needed to do this to keep MFC alive [like it
was even alive :( ], but they also killed several companies in the process.
I work on a private UI library similiar to CodeJock, BCGSoft, so I'm pretty
much killed by this MFC update as well.
This *sucks*... 10yrs of my life I'll never get back working on my GUI
library.
No word on what the dependencies will be, but from the sound of things, the
worse dependency will be GDI+.
This news is exactly why I hate programming :(.
Oh wait, I just read they are actually *USING* BCGSoft, not rewriting
anything. Still kind of retarded and still kills all 3rd party companies
(except BCGSoft I suppose).
"Somebody" <some...@cox.net> wrote in message
news:l9oZi.969$kl7...@newsfe21.lga...
Fair enough. RealPlayer was bigger then MediaPlayer for a while. Then
RealPlayer refused to add support for popular formats while MediaPlayer
happily added them. So buh-bye RealPlayer.
Honestly, I will continue to use my own GUI library for the time being even
though the BCG one and the CodeJock one have more "stuff" at this point in
time because:
1) I see the current BCG product as very buggy with no attention to detail
(nice GUIs require a lot of attention to detail). The Office team has
tremendous attention to detail when it comes to GUIs where as the Visual
Studio team has very *poor* attention to detail when it comes to GUIs.
2) GUIs, new controls, bug fixes, etc. require fast turn around. BCGSoft and
CodeJock as small companies have quick turn around. For example, both had
Ribbon controls before Office 2007 was even out. BCGSoft as a branch of MFC
code will have a 1 to 2 yr turn around and likely zero opportunity to
release bug fixes for the "MFC branch" (seeing as they don't release MFC
fixes between releases).
3) I hope this integration doesn't ruin MFC. The benefit of MFC was my app +
a few DLLs < 5MBs was all I needed. BCGSoft is a 20MB+ behemoth.
The *ONLY* way I see this working is if the BCG lib is NOT tightly
integrated into MFC and in a DLL off on its own. That way it doesn't bloat
the MFC DLLs, I don't need to use it if I don't want to and BCG can update
it more easily.
Wow. Now I'm in. I've already compiled and run our app under 2008 beta
on vista just to see what I'd be dealing with. But I wasn't ready to
commit till now. I do like that the compiler/runtime checks are so much
stricter. It took me an couple of hours to run and I'm figuring a day or
so more to get rid of all the warnings and runtime checks. I'm 2003,
skipped 2005. We gave up on 98 for this next release anyway.
I am glad MS is supporting native so well again...
Best, Dan.
That's the worst part of the news, really. Microsoft invented the ribbon
as a GUI metaphor, and now they're licensing some (apparently not very
good, from what I read in this group) thord-party implementation of it
to ship to their developer customers.
I really don't mind Microsoft driving the other guys out of business if
they do it by distributing *better* software, but they can't just
license a cut-down version of an existing 3rd-party product that is
demonstrably less good than the code they use themselves and claim to be
doing the users (us developers) any kind of service.
--
Cheers,
Daniel.
Yup. BCG is horrid. There are other 3rd party libs that are much better. I
think MS just got a deal with BCG that the other vendors were unwilling to
do (ie, give it to MS for pretty much free). You can easily find tons of
drawing bugs in the BCG lib. Drawing bugs are kind of a no-no in a GUI
library LMAO.
Microsoft *says* they are fixing performance & drawing bugs, but in the same
blog, they also say it "works great as is". So I wouldn't expect much.
I am not sure, but I think that the Windows GDI is nearly the same as IBM's
GDDM for their mainframes. Probably Microsoft's Rich Text Format is nearly
the same as IBM's Revisable Form Text.
Microsoft did not like the way that Sun owns and controls Java so Microsoft
designed the CLR and the C# langauge.
That's business.
"Somebody" <some...@cox.net> wrote in message
news:l9oZi.969$kl7...@newsfe21.lga...
> Microsoft did not like the way that Sun owns and controls Java so
> Microsoft designed the CLR and the C# langauge.
And Thank you Microsoft, because IMHO the quality of C# and .NET is superior
to that of Java.
Giovanni
Not really. They did it to renew revenue opportunities.
>
> And Thank you Microsoft, because IMHO the quality of C# and .NET is
> superior to that of Java.
>
Really? How come I've never had a java app take as long as VS2005 to
populate a directory list when opening a file?
> Really? How come I've never had a java app take as long as VS2005 to
> populate a directory list when opening a file?
I think that VS2005 is written mainly in C++, not in C#/.NET :)
This of course makes things worse :)
I don't like the performance of VS2005 at all, in fact I use the great VC6
and sometimes also VC7.1 (which seems to me faster than VS2005 kind of
resource-hog, but not as good as VC6, the best Microsoft IDE for Visual C++
in history!).
However, it seems that Microsoft paid more attention to performance in
VS2008, and exspecially also for next version. I hope (VS2008)+1 will be
top-quality like VC6 for C++ native programming!
Giovanni
So you're saying that if it had been up to you - you would have written the
compiler and linker using C# ....?!?
No! I'm saying that IMHO it is bad that a C++ native app is performing worse
than a Java app.
Giovanni
In fact, I replied to BobF, who wrote:
<quote>
GD: > And Thank you Microsoft, because IMHO the quality of C# and .NET is
GD: > superior to that of Java.
BF: Really? How come I've never had a java app take as long as VS2005 to
BF: populate a directory list when opening a file?
</quote>
Giovanni
Tom
"BobF" <rNfOrS...@charter.net> wrote in message
news:OJ6gueUJ...@TK2MSFTNGP02.phx.gbl...
Tom
"Giovanni Dicanio" <giovanni...@invalid.it> wrote in message
news:ugFQbKWJ...@TK2MSFTNGP04.phx.gbl...
A problem with Mono is that it is .NET 1.1 compatible, working on ver
2.0.
Later this month MS will be at ver 3.5. Where is the portability?
Bo Persson
Tom
"Bo Persson" <b...@gmb.dk> wrote in message
news:5ps3ruF...@mid.individual.net...
"Tom Serface" <tom.n...@camaswood.com> wrote in message
news:D0764981-D8B5-42B1...@microsoft.com...
Visual Studio just doesn't have very good performance. Its generally fine if
you have smaller projects, but once you start throwing multi-project
solutions with hundreds of files, it slows to a crawl. My project at work
takes about 1 minute to load and it is a fraction of the entire product.
Tom
"Somebody" <some...@cox.net> wrote in message
news:4Xa_i.1817$kl7...@newsfe21.lga...
Tom
"Sam Hobbs" <sam...@social.rr.com_change_social_to_socal> wrote in message
news:%23Gpyxja...@TK2MSFTNGP02.phx.gbl...
Tom, I just read on the VC blog that MS will be (or already has) released a
patch to address the performance issues. Haven't tried it yet though.
http://blogs.msdn.com/vcblog/archive/2007/11/12/performance-improvements-in-visual-c.aspx
Good find. I'm going to try it today
Good news! This hotfix appears to have solved the "slow opening" problem
when adding existing files to a project!!
Tom
"Somebody" <some...@cox.net> wrote in message
news:iYc_i.3427$jd3....@newsfe19.lga...
Given the numbers of applications and developers that use Java, I think that
it's safe to say that it has indeed been a "hit". Expecting the mindshare
of Java to continue to expand is unreasonable though because newer languages
come out that address the shortcomings of the language and runtime to
address the latest set of problems.
-Pete
How did the hotfix work out for you?
I work on a dual Xeon 3.2GHz box similar to yours and I've never had VS2005
stop responding like that....
Does the status bar say anything?
I'm full time on VS2008 RC1 so I'm just curious how the hotfix goes, so I
can pass it on to others that ask :)
Thanks!
Mark
--
Mark Salsbery
Microsoft MVP - Visual C++
"Tom Serface" <tom.n...@camaswood.com> wrote in message
news:B5D1F80D-F4CA-4CCA...@microsoft.com...
Tom
"Mark Salsbery [MVP]" <MarkSalsbery[MVP]@newsgroup.nospam> wrote in message
news:4AECF0A1-7EAE-4E0C...@microsoft.com...