"A year in the Life of Delphi" webinar with Nick Hodges
Somebody asked about Delphi 2009 Feature Matrix. Here is the link.
Comments
-
Tuesday, 16 December 2008I certainly would have taken part had I known about it. If you are going to announce that a major product development is slipping by a year (64 bit) then it's surely better PR to manage the announcement more slickly than this.
Presumably you have your reasons for doing this and I'd love to hear them. -
Tuesday, 16 December 2008
Is there an updated road-map (a recording of the webinar isn't available)?
-
Tuesday, 16 December 2008
Erm, was this event ever announced anwhere? Sounds like it could have been THE big thing if only anyone had known about it... I thought of myself as following the various CodeGear outlets pretty closely but I never saw anything about this anywhere...
How many people were there in attendance (and how did they know about it)? -
Tuesday, 16 December 2008
i got an email about it although i wasn't in a position to be able to view it. The notice was pretty short
-
Tuesday, 16 December 2008
Just curious was there any mention of Mac OSX as being one of the possible native targets of cross compilation?
I assume this is what they are attempting to do, that is, allow development of a native application for multiple platforms from a single code base.
Is so that would make Delphi a pretty cool tool and unique (well other than Qt and RealBASIC). Now hopefully they target native GUI and not an emulated GUI.
With Prism/Cocoa# and this, they could be a single vendor allowing cross platform development in native code or .NET
Wow, things sure have changed course now that Enterprise idiots are no longer in charge
However, sorries to all you 64-bit developers, gonna have to wait. -
Tuesday, 16 December 2008
Delphi needs investment at databinding.
I can't find a proper way to architecture my DB applications with using object oriented approach and unit testing tools without losing rad capabilities. Delphi even assumes Datamodules will be one instance in application, you should do hack for that.
Datasnap is DB centric remoting approach. Remoting should not be the top priority in n-tier support. I want to work with abstract data, i want to work with my own bussines objects which can be tied to table fields. I don't want to put my all bussines logic into database table structure, this is a primitive method. I want to write codes for my bussines workflow while using RAD capabilities in delphi.
Those can be the major resoans for me to migrate to .Net if i will...
There are lots of things being happened in .Net. Like Linq, Entity framework. -
Tuesday, 16 December 2008
Cross platform using native code?
but if i am not mistaken reading from Nick Hodges's blog, the coss platform mentioned is thru Delphi Prism (using mono/net)!!!
Somebody please confirm whether we are going to get mono/net or native binary! -
Wednesday, 17 December 2008
A lot of events (PDC 2008, RAD 2009, CodeRage III,...) ... but still no roadmap ?!
C'mon, after several promises made by Nick & others regarding the roadmap I think it is time to better put it on the table ... All the SEC regulations & co could not be anymore put in front ... so please just let us know were we are "going" ....
CG/EB should be more aggressive when promoting their tools ...
Just look at MS that is already public-beta their Win 7, VS 2010 and .NET 4.0 ... It is not really needed to follow their path, but PLEASE make all your progress more TRANSPARENT to us. So lets have that ROADMAP published and STICK to it (too many changes in last couple of years !) since ISV using CG tools have their own business plans that may be totally disrupted by your continuous "adjustements" and delays (ex: x64).
In previous x64 related blogs & co ... it was mentioned that everything went smooth and Commodore will be released in the mid of 2009 (finally) ..
But suddenly we found out that CG is interested more on "cross-compilation" ... (remember that long debate with Simon/CrossKylix ?) so as a BONUS we will get another 1 year of delay (does this means the x64 work will be "freezed" in between ?!) .....
Don't get me wrong, I really love RAD (2009) and the new Prism ... but I'll like to see more cross-pollination (language/features compatibility) between these two into the future and to also see x64 and cross-compilation.
Conclusion: realease "THE ROADMAP" & "STICK TO IT" ! -
Wednesday, 17 December 2008
Delphi 2009 works. You just need to fix all the damn bugs.
-
Wednesday, 17 December 2008
I'm shooting this from the hip after just reading this post (and missing the webinar, no post event recording nor roadmap etc...). I will try and stay calm and rational....
No. No. No. As a couple of previous comments have touched on, 64 bit IS IN the roadmap and when the Embaracadero deal was going through we were assured that existing roadmaps would be honoured and followed through.
The prominance of 64 bit was (and MUST be ?!) undeniable. The code name of the release was Commodore, with much play made of the Commodore 64 link etc...
Commodore itself was back tracking on 64 bit i.e. Even if the next Delphi release included 64 bit, that itself was the result of broken "promises" (roadmap changes).
My company is one of those very ISV's (virtually a Micro ISV), that El Cy mentions and we are furious at this. There is no other printable word for it. I would love to scream and shout about this, throw the toys out of the pram. I feel absolutely incensed. Our product has been in need of 64bit for the last 18 months or more (the time period over which a 64 bit Delphi has been promosed, delayed, promised delayed). In turn we have promised partners and customers the features they need in order to keep investing in us.
Thanks Borland, CodeGear and now Embaracadero, you have just screwed us over yet again. Our whole strategy for the next year will now have to be reworked and product plans revised.
If we could afford it, a 6 to 12 month C# rewrite would be my favoured direction now. As it happens that is not out of the question. We already had a partner meeting scheduled for Thursday where we are due to discuss closer ties with their product. Our partners new products are in a C# framework, their old products are still lingering in Delphi 5. Guess which direction they have been pushing us to adopt for the last 12 months or more ?
We will survive this, but it will be inspite of anything Embaracadero do and not because of it. -
Wednesday, 17 December 2008
Noooooo, we need 64 bit compiler. You are really going to force us to abandon Delphi.
-
Wednesday, 17 December 2008
I believe most of you are seriously misreading this (though having missed the event myself I couldn't be sure). 64bit has not been dropped from the Commodore release nor has its priority been decreased at all.
The way I read this was that the Commodore release date itself has been postponed because they had essentially underestimated the effort required to produce the cross-compilation backend which in itself is a prerequisite for a 64bit-enabled Delphi release (unless they intended to either drop 32bit or make the 64bit compiler an entirely separate product). So I don't think there will be any Delphi release in 2009 at all, especially not one without 64bit-support.
It always seemed a bit unlikely to me that the roadmap had Commodore a mere half a year behind Tiburon... -
Wednesday, 17 December 2008
The main point is that announcements like this need to be made carefully. This is a classic PR mess-up.
-
Wednesday, 17 December 2008
We're in the same boat as Paul T - we've been waiting patiently for a 64-bit Delphi for a long time now and were promised it on the roadmap. Now according to this post they've moved the goalposts, which blows to say the least.
Some people have said on newsgroups that 64-bit is not important, well it certainly is to use because of expanding memory requirements. -
Thursday, 18 December 2008
Absolutely Alan. We are at the 3GB limit with memory usage and don't want to change the architecture to use AWE. Our target markets are now including the retail sector, which for us moves the memory bar way higher, far higher than we can accomodate with 3GB. We have already re-architected to a degree and if 64bit is delayed further we will have to do a certain amount more of that. The result will still not be what we want.
-
Thursday, 18 December 2008
"Some people have said on newsgroups that 64-bit is not important". The same who said "Localization is not important", "Unicode is not important", "templates are not important", "remoting is not important", "a working IDE is not important", etc. etc.
Oh well, everything depends on what kind of software ones writes - and which kind of customers CodeGears wants to target.
64-bit does not mean only a larger address space available, it means more registers available, increased speed in large number calculations (with native 64 bit integers BCD becomes a less appealing options for calculations up to 20 digits), and if one is going to write software that integrates with the system (i.e. shell extensions or the like) he needs a 64 bit compiler. Some software may do without - other can't.
CodeGear just needs to choose what kind of customers they want to keep. -
Thursday, 18 December 2008
>> cross-compilation backend which in itself is a prerequisite for a 64bit-enabled Delphi release
Where was this quoted or documented? And when one mentions cross compilation does this mean targeting native code on other platforms? -
Thursday, 18 December 2008
@Jeff: Nick made a statement similar to that in my interview with him in Episode 2 of the podcast:
http://www.delphi.org/2008/08/episode-2-nick-hodges/
I don't remember the exact quote. -
Thursday, 18 December 2008
Wow, soon these Qt folks get Mac OSX Cocoa and 64-bit and all native code. I am jealous
-
Please login first in order for you to submit comments
What was the thinking behind publicising this Webinar only after it finished, and describing it in the past tense?