What is your current Delphi Version?
I just have to test the new poll feature. So silly that Google limited to five options, and doesn’t do multiple choice either. But hey, it’s a start!
What is your current Delphi Version?
Published
I rant, therefore I am.
I am living in the past, my friend.
XE2. But not voting, as I think there’s a big difference between XE/XE2 and >=XE3 where it became a new product direction away from Win/VCL.
Good point, Vin Colgin. I wanted a choice for every version, but Google restricted me to five, and it was kinda hard to decide how to divide them. It also annoys me that you can’t set a poll to be anonymous, or do a multiple choice poll, or lock results.
Lars Fosdal There are other tools to create meaningful polls ya know (like https://support.google.com/docs/answer/87809?hl=en). The choices in this one are making little to no sense.
D2010 and XE6, technically, all my projects can be upgraded to XE6 with very minimum work, but we don’t do it because that time can be spent elsewhere especially since it’s not mandatory to upgrade
Stefan Glienke – I know… I still wanted to try out the new poll mechanism.
…and besides, you left out D8!!!
First rule of D8: We don’t talk about D8 😛
You shouldn’t have grouped 2005-2007 with 2009-2010, these are just too different and many people stuck with 2007 because of Unicode. But I realize that it’s difficult with only 5 choices.
Can you believe we still have an app here written in TP5.5? we’re in the process of migrating it to XE5. I’m also doing some projects in XE7
TP 5.5 was awesome! It took me about 6 months to “get” OOP by first hand use, but when the light finally switched on, holy moly what a change!
The only thing that really came close to that, was Generics. They also are a paradigm shift.
Daniela Osterhagen
Stuck in D2007 here, but Unicode is not the reason. It’s simple inertia, with a really large app.
Lars Fosdal
I disagree. OOP was huge, of course, but so was the introduction of Delphi with exception handling. Left a lot of folks with their mouths open, and made Windows, at last, a low hurdle.
Exception handling was nice, but it didn’t change how I wrote my code – it merely added extra safeguards.
Lars Fosdal Visual forms design and event-based design were a big change, though.
Hey Google allow nested subpolls, hehe
Hmm. Note to self. Poll is not anonymous.
Bill Meyer – True. I was actually disappointed in D1, as I had written quite a bit of code with TPW 1 and 1.5 – but – I got over it 🙂
Voted XE6, which we use for the current development version of our software. Older versions of our software are all made with XE3.
We’re trying to track the new releases more frequently, though we have a lot of third party dependencies so it’s not easy. Takes my coworker a week or so just to download, compile and sort out the immediate issues for all our dependencies, and then there’s testing for regressions.
I have XE7 (use it for mobile now (android) but my main program I still use XE6 as I am waiting on instrument lab to be made available to XE7 🙂
Lars Fosdal I did not do a lot with D1, though I did build a tool for a major HDD manufacturer to use in analyzing the yield in the head plating operations. D2 kept me busy for years, though, with video server design. Then D5, briefly, and finally D7.
haha, All this talk of lore makes me think of the good days of TurboVision and DOS/Character based graphics. I remember we used to fiddle with the character definitions in the VGA controller to produce “graphically” characters out of the unused high ASCII characters…
http://en.wikipedia.org/wiki/Text_mode#User-defined_characters
Which leads me to a story, I used to do POS programming for Hollywood Video (nation video store chain). We had a problem with screen burn-in, so “one night” (literally) a co-worker and I made a small TSR that would come to life and present a small bee, made out of a three redefined characters (two for the wings, one for the body). This bee would randomly “eat” the characters on the screen and eventually blank them all out within about 5 minutes. It’s was super cool and a fun project. This was in the good ole days, about 4 developers and only about 30 stores, so that night we rolled it out. The next morning, we came into work where the owner of the company was frantically fielding calls from the store-managers about a VIRUS in their computer that was eating the screen!! Needless to say, they put controls in place to prevent programmers from randomly rolling out software to the stores at night.
talking about the good old days, my first programming was on a ZX81, with 16k (!) memory add on 🙂
Brian Hamilton
I’m sorry!
I still use D3 too believe it or not.
Voted for the one I use day to day, not the newest I have a licence for.
Me too. Waiting for the service pack before upgrading as usual.
What is your current Delphi Version?: It is XE7 but I have to use XE5 because our projects are relying on some 3rd party components that are not available yet for XE7.
Maybe you can add this to the poll as an additional option 🙂
Fred Ahrens – Unfortunately, Google+’s new poll is pretty braindead.
Lars Fosdal Hey last week you couldn’t even make a poll, sheesh 😛
Asbjørn Heid – Sure you could. Make post, add comments for each option, lock for comments and ask people to +1 comments that they would vote for. Multiple choice only, but still, 500 possible choices 😛
Lars Fosdal IMPOSSIBRU! 😛
Fred Ahrens
Inertia. A fact of life. Not so long ago, I was trapped in D6 because of a few non-visual components whose publishers had expired. Finally wrapped them in a DLL and moved on.
Bill Meyer This DLL wrapping sounds like a good idea.
Fred Ahrens In my case, it was the only available option. The component implemented an encryption algorithm, and may have had errors. At least, my tests with another component gave incompatible results. We had no source–in fact, I was unable to determine whether we were licensed.
At any event, with nothing but an interface, the DLL was the only path which was compatible with data in the field.