June 29, 2006
Nick and Delphi IDE bugs
In a recent post in his new Borland blog, Nick Hodges asks for the "The Top Ten Niggling, Irritating, and Downright Bad IDE Bugs List". Interesting approach in getting help from the community and in showing that progress is being made, at the same time. Hope this starts a trend, couple with frequent hot fixes to the products.
Suggestions have started to flow, ranging from memory leaks, to disappearing new items elements, and to blue dots on wrong lines. By the way, the disappearing effect takes place also on the Tools Palette: I'd really like a separate Component and New Items Palette pages, with context switching, but so that I can always get to that components list even when I'm writing code (but this is a featuyre request, so it doesn't count for Nick's Top Ten).
What I want to undeline, though, is that Nick's initiative has been very well received. John Herbster write: "One reason that they hired Nick may be that he comes with a support group of volunteer experts who can thoroughly discuss just about any topic from all sides." Thomas Miller writes: "Hats off to this initiative." And many others agree...
Nick has been active on other areas, despite he's one week old DevCo employee. In the 120 messages he recently wrote in the Borland newsgroup (you'll get a different list when you use that link, as newsgroups data changes over time), he answers to request on 64bit Delphi, low-cost editions, and more. Lot's of interesting posts, with Michael Swindell and John Kaster involved as well.
But this is by far the best exchange:
Bruce McGee:
I can only hope you do or say something that will be interpreted
(actual logic need not apply) as controversial by some vocal minority
in these groups. Seems unlikely, though.
Nick Hodges:
Oh yeah, that will never happen. ;-)
I think I'm starting to like this new guy. Now if I could only grab the roadmap from his desk and change it a little bit...
4 Comments
Nick and Delphi IDE bugs
Call me crazy, but I'm NOT impressed with the .NET 2.0 WinForms applications I've seen so far. They are extremely SLOW. Perhaps others would disagree. ASP.NET 2.0 web apps might be .NETs saving grace. IMHO, the whole .NET development experience is extremely painful. Big VB.NET projects in Visual Studio are like Chinese water torture! (unbelievably slow!) My gut feeling is that the DevCo roadmap for Delphi should fork. There should be a .NET team and a NATIVE compiler team. I do not think adding .NET 2.0 support is going to increase new BDS license sales. I think it will simply STOP some of the faithful from jumping ship to Visual Studio. The real growth opportunities for DevCo are in high performance NATIVE code IDEs amd compilers! (starting with Win64 and Linux) They need to EXPLOIT cross-platform NATIVE compilation. They should either resurrect CLX or reinvent it.Comment by Tom Wilk on June 30, 07:03
Nick and Delphi IDE bugs
I would like to see 1: Generics in the native Win32/64 compiler 2: A new cross platform VCL (Win/Linux). DevCo should use the LCL from the Lazarus project as basis or idea source.Comment by Peter on June 30, 22:18
Nick and Delphi IDE bugs
- Try to look at RealBasic, how the development once can compile into many platform (Linux, Windows, Mac OS). - And also reporting engine that support cross platform off course.Comment by Donny Wu on July 3, 08:11
Post Your Comment
Click here for posting your feedback to this blog.
There are currently 0 pending (unapproved) messages.



Nick and Delphi IDE bugs
Comment by Bruce McGee on June 29, 18:25