Early this year, Raymond Chen blogged about Why 16-bit DOS and Windows are still with us.
I found this an intersting read, if for no other reason than I’m currently involved in a 16-bit project.
- Podcast RSS:
Early this year, Raymond Chen blogged about Why 16-bit DOS and Windows are still with us.
I found this an intersting read, if for no other reason than I’m currently involved in a 16-bit project.
Cool! A Delphi 1.0 app! That rocks!
You should give Delphi 8 for .Net a look. Full support for the .Net framework with that great Object Pascal Language.
Yeah Delphi 8 .net is really cool, just downloaded the demo this week. I have used D4 a couple of years ago (And I liked it). Did not use Delphi (For different reasons) for years now. Guess what? I found my way very fast, even in the real .net enviroment. I am sure I will get me copy real soon
I’ve always liked Delphi, but it’s one of those things…many employers have never heard about it and those that have haven’t wanted to break out of their VB/SQL Server frame of mind.
The funny thing about this particular 16-bit app is that when it was first installed (with only a couple people knowing it was a delphi app), one of the IT guys looked at it and said: “Wow…a Delphi app.” Those damn speed buttons gave it away.
Michael –
Hey, thanks for the reply.
Yep, those speed buttons are everywhere.
Just to do a little marketing — remember that you’ll be able to migrate the 16-bit app to 32-bit fairly easily (depending on how much of the Win31 API you’ve used, etc…..)
Then, if the time every comes, that /same code base/ can be migrated to .Net.
Just some food for thought.
Joerie — you rock. Glad you liked Delphi in the .Net world.
Nick
Nick,
The 16-bit app is pretty straight-forward — no Win16 API calls, although like I said in another post, I did have to hack printers.pas to accept a filename.