Windows Vista will not use .Net

After all, .Net is taking some time to lift off. The following articles extracted from a good discussion on the borland newsgroups show us how the new Windows operative system ended up not relying on the .Net framework.

http://www.grimes.demon.co.uk/dotnet/vistaAndDotnet.htm

and ...this other ones covering the API and GUI.

http://blogs.msdn.com/greg_schechter/archive/2006/03/10/549310.aspx
http://www.edbott.com/weblog/?p=1272

Personally, I'm more interested on future native Win64 support. If Intraweb is able to catch up and improve its performance (which they did in version 8), then i will not have any other use for .Net (which i think is only useful for web apps for us Delphi developers) in the short term.

Letter from David I to the Brazilian Delphi Community.

A great post to a big community down south, that touches the topic of Delphi spinning into its own company.

Click here to read it.

Delphi 2006 Architect version Trial available!

Try the best Delphi ever. Click here to download the Delphi 2006 Architect Trial.

Transactional Data Modules on Delphi 2006

Tonight i was working on my project's middletier using DataSnap and i decided to add a new Transactional Data Module, perfect, i click on File / New / Other and select the MultiTier tab... ooops, it only says Remote DataModule!!!

Where is my Transactional Data Module!! Well, it seems that the Wizard didnt make it for the official Delphi 2006 release (as i said officially), BUT... after a quick "let me ask Mister Google" i found this good entry on Borland's Chris Bensen blog. Good stuff it is there, notice that you will have to enter "both" (Free) in the component factory section if you want to specify support for both Single and Apartment Threading Models, the option in the wizard only offers Single or Apartment.

Anyway it seems that Delphi 2006 supports them fully and there is no problem with it. (We already deployed our newly D2006 compiled modules).

Another way to do it is just to open your project with Delphi 7 and add the transactional data module, save, close and go back to D2006. (Hey, i still use the D7 help file :P)

Marco Cantu's eBook Delphi 2006 first draft

I mentioned before on the borland nontech newsgroups that Marco Cantu was planning to extend his Mastering Delphi 2005 book.

Well, here is the link to his initial Delphi 2006 ebook first draft. I can say that Marco's book is great, it is part of a good collection of Delphi .Net books on my office, which i will be waiting to increase with his next book, which i expect to be available when Delphi 2007/2008 comes out.

Enjoy the good reading.

2005 is gone, welcome 2006!

Well, personally and professionally 2005 was a great year for me, i spent my Christmas in my beautiful and warm country, the perfect way to close a good year.

But now, it is 2006, and what better way to start the year than with the BEST DELPHI EVER, yes sir, i am right now installing the Man, the Mighty One, the only Delphi not bashed so far in the non-technical borland newsgroups... Mr. Delphi 2006.

So far so good, i'm installing right now my standard components: JVCL 3.10, SUISkin and ExpressGrid.

If all these guys come up right, then we are ready to move, yup, i'm not thinking twice, i'm going all the way, i'm migrating from Delphi 7. It is worth it and the feedback so far has been A+.

So, people, the time is now, Delphi 3, 4, 5, 6 and 7 users, we have our safe spot is Delphi 2006.

Let the party begin.

Pst. It looks like i will have a lack of sleep this coming days. :)

Danny Thorpe message for the Delphi Community

Post taken from the delphi.non-technical newsgroups. I'm including the text in order to avoid confusions, if you want to see the real text, go to the google newsgroups, it should show up there.


"
Members of the Delphi Community,


As you've no doubt read in other threads in this newsgroup, I have left
Borland to seek new opportunities at Google.

This was not a sudden action. I have tried my best to ensure a smooth
transition for the Delphi team, starting with transition plan
discussions with Borland management more than nine months ago.

Delphi is built by a team, not by any individual. Far greater talent
than mine has come and gone from the team, and Delphi presses on. More
importantly, far greater talent remains in the team, some of it as yet
untapped.

As you may know, my philosphy is that teams should be built to
anticipate, tolerate, and support the comings and goings of individuals
on the team. Everyone will eventually leave the team - either by
choice, or by pine box. To ignore this is childish.

I have full confidence in the Delphi team to continue to deliver the
right stuff to keep Delphi current, innovative, and competitive for
years to come. Though there have been some difficult spots between
myself and Borland corporate management, the internal changes in
attitude and messaging in recent months from Borland corporate toward
Delphi have turned my faith in Borland supporting Delphi back toward
the positive. I'm sure that will only get better as Todd Neilsen
steps in as the new CEO.

I'm also pleased that in some small measure my departure is creating
opportunities for advancement within the Delphi team, and that Borland
management (Boz and Steve Todd) was very supportive of "redrawing the
map" under the guidance of Allen, Michael, Eli, and myself. Several
individuals on the team have been promoted in title and/or in pay as a
result of this change. Many of those have not seen promotion or pay
raises for as long as 5 years. Borland has also committed to opening up
several new positions in the Delphi group in Scotts Valley, which may
be filled with entry or mid level engineering talent. This alone is a
significant reversal of the "No new hires in Scotts Valley" edict
earlier this year by then-CEO Dale Fuller.

I was not snatched away from Borland, and I am not leaving Borland for
lack of money. I sought out Google, and I'll be making at Google
exactly what I made at Borland, which is nicely comfortable but not
excessive. There were other suitors (including the obvious one) but,
quite frankly, Google outmaneuvered them.

Could Borland have bought me back? No, because I didn't leave for
money. Why, then? Opportunity. I'm going to Google to pursue ideas
and opportunities that are simply beyond Borland. I love Delphi, I
know it inside out, but there's a lot more in me than just Delphi.

After 15 exciting years doing a wide variety of things at Borland, it's
time for me to do something /completely/ different.

This is not goodbye. This is just changing channels.

-Danny Thorpe
Engineer, Google.
"

Thanks Danny, your legacy on our amazing development tool will never be forgotten. May the force be with you in your new ventures.


Nos vemos pronto.

Danny Thorpe left Borland.

In my opinion one of the smartest guys i have the honor to met, it was on a great developer's three day conference in Toronto where i got the pleasure to listen and share some time with the guy behind the latest improvements on the Delphi compiler.

After 15 years (some people say 20 :P) of working with Borland he is leaving for a new great adventure in Google, helping on the development of lots of new things related to FireFox. Before leaving, he gave the Delphi community a last gift, by helping to provide one of the strongest Delphi versions ever. Delphi 2006.

Borland, the Delphi team and the Delphi community for sure will miss him, i'm happy to know that for a couple of months now, new people is already taking his place. New minds working on the progress of the language, environment, etc that we love so much. In my opinion, the future looks very bright, we have a roadmap, we have a strong Delphi version and we have the chance of fresh ideas coming into Delphi.

Thanks Danny, you are 'Da Man. Enjoy your new venture and keep in touch with the community.

Long nights of development...

Lately i have being a bit unplug from my blogging duties.

The reason, a big personal project i'm trying to pull out. Just for fun, let me extend a bit into it.

It is developed in WIN32 using DataSnap, Indy, the Quantum Express Grid and JVL/JVCL. No other component is allowed :) (well, i need some sound recording, so, im looking for some replacement to the MMTOOLS, if you guys know of any, please let me know).

My Datasnap modules on this occassion sit on Transactional Data Modules on MTS, using Free threading. My previous experiences with it have return amazing performance advantages of using connection and object pooling in coordination with a good load balancing and redundancy techniques thanx to the DataSnap built in load balancer.

Initially i tried to use a very good ntier framework called KbMw, but the learning curve and my short time to bring this project alive stopped me from doing it (once it is up and running i will try to port the project to it).

The Quantum Grid is just amazing, i haven't even scratch the surface of these components and i'm already shocked with the possibilities, if you guys have the budget, go and get them. They support VCL.Net and i'm waiting to see its Express bars working on VCL.Net too.

I still haven't decided what is going to be the web technology i will implement for the web front. ASP.Net? playing safe with nice ISAPI Dll's? or a cool combination of ISAPI DLL's and Ajax?

I need to implement some interfaces between different systems, and DCOM is not an option due to security restrictions among the products, my initial thoughts went to SOAP but recently i've being reading about REST and i think i will give it a shot. I want to thank Marco Cantú on his blog for bringing some light to the topic.

I have to go for now, but, i will go deep into my experiences with all these later on.

Delphi 2006 Tour - Toronto

Well, i was supposed to post this a bit earlier, so people can find this information useful, but i am extremly busy at work.

Today, November 15th, Borland Canada will be showing the new features and enhancements of Borland Delphi 2006. An amazing event conducted by Mighty Michael Li.

For more information please visit the Toronto Delphi Users Group.

Hope to see you all there.

DataSnap... as good as it gets.

Well, for the last 2 years since i started using DataSnap, i can't stop feeling amazed of how good it is. I know that you guys may say that now its all about .Net Remoting and BDP, but, ladies and gents, DataSnap is extremly versatile and easy to use, and definitly a proven way of implementing VERY effective multi tier systems.

These days i've being using lots of nested datasets in mix with the Quantum Grid, you can't imagine the THOUSANDS of lines of code i'm saving myself everyday with these lethal combination.

I mean it, for the same amount of database operations, we have at work complete hard drives of code in Java. Write this down, it is until you work with a language not as versatile and powerful as Delphi when you realize HOW MUCH YOU LOVE IT.

I must admit that i really like the way KbMw does things, but DataSnap is so integrated into all the Delphi stuff that the idea of migrating all the code to KbMw is something for the long term.

Borland has not stopped the support on DataSnap although i must admit is extremly stable and mature, it is not their main concern, but i feel that its adoption is growing instead of going away, specially on WIN32 systems. I hope we can get some minors enhancements and a firm fix to the multi-procesor issues experienced with socket connections, cause i cant wait to set our systems on some nice MultiCore Opteron processors.

Good night, cya all later.