The "XE" that is used in many of our Embarcadero products
"XE" is the new product version/badge for all new major Embarcadero product releases. The "X" signifies heterogeneous and "E" signifies Embarcadero. The "XE" badge signifies that a product is part of the Embarcadero family of heterogeneous application and database develop tools and identifies Embarcadero’s unique market advantage supporting heterogeneous database or platform connectivity and deployment out of the box.
For RAD Studio, Delphi, C++Builder, Delphi Prism and RadPHP (formerly known as Delphi for PHP) "XE" signifies the unique heterogeneous database and Datasnap and cloud deployment capabilities, and in future releases will include heterogeneous client (desktop and device) and server deployment to a variety of OS platforms and architectures.
"XE" designated products are also ToolCloud enabled or include ToolCloud capabilities to facilitate streamlined on-demand tool access and administration. "XE" also unifies the wide variety of differing version numbers and schemes among nearly twenty different Embarcadero products.
For example some products previously used year designations such as 2010 to signify the year they are released in and others used the year to designate the upcoming year a product will be released and yet others used a variety of differing decimal schemes such as v3 or v7.5.2 with some products incrementing the major version number annually and others incrementing the second decimal version annually.
Beginning with products released in the calendar year 2010 all Embarcadero XE feature qualifying products will be designated XE, subsequent major version releases designated as XE2, XE3, XE4 etc. To assist in support and identifying specific technical lineages, products will continue to include internal technical version numbers as they have in the past. For example Delphi 2010’s internal technical version number found in the about box was actually v14.0.XXXX and as such Delphi XE’s internal technical version number will retain the same scheme and is v15.0.XXXX.
Stay tuned to this and other Embarcadero employee blogs and our website for additional details about our "XE" products. Stay tuned to the RAD Studio XE sneak preview page for additional videos and product details about our upcoming releases of our developer tools.
If you want to contact me directly, need a non-disclosure briefing, have any questions or just want to say hi, you can reach me at:
- email: This email address is being protected from spambots. You need JavaScript enabled to view it.
- skype: davidi99
- phone: +1-831-431-5399
Thanks for all your support and interest. We will continue to everything possible to deserve your business now and in the future.
David Intersimone "David I"
Vice President, Developer Relations and Chief Evangelist
Embarcadero Technologies
Comments
-
Wednesday, 11 August 2010How does the Tool Cloud help the small developer who only needs Delphi or maybe C++ ?
-
Wednesday, 11 August 2010
@Fritz
"we don’t Know what is inside the product delphi XE"
You might have missed the link to the preview page with one video up and a couple more scheduled.
http://www.embarcadero.com/rad-studio-xe-preview -
Wednesday, 11 August 2010
> Fritz writes: Funny, now we know what is inside the "name". But we don’t Know what is inside the product delphi XE. I cant believe the strategy behind these is thinking on the customers.
These are preview videos and blogs. We will formally announce and launch the product soon. Then you will have complete information. -
Wednesday, 11 August 2010
Why people are so negative?
Embarcadero is not microsoft, but it works people who need to earn money to live.
There are many applications developed using Delphi.
What's new in office 97, or 2000, or xp, or 2003, or 2007, ... a ribbon?....
This is a business, and we're all in it.
Delphi is a great product, a great community.
Please let's give it a try.
Sorry 4 my english. -
Wednesday, 11 August 2010
One idea for new release: set new low price for product / or upgrade!
D7 was a standard for years. D2010 is first quality-enough release to be compared with d7. Studio XE is polished and enhanced version of d2010. Let make it standard! Set extreme low price for upgrade, set liberal price for new license! Spread this version as a base for whole new line of products - use quantity instead price for increasing revenue. Don't use increased bundling of product - make entry level turbo editions instead! Spread, spread, spread - now you have mature product with current features - make all your customers upgrade to it.
IMHO, new licenses can be achieved only by developing new platform features - like cross platform, x64, cloud, social, server.
Invest some money into internet related stuff - Indy/synapse libs and make some Internet components - google API, Facebook, flickr, oauth, json, XML an so on. It's not expensive to develop such VCL, but can be good selling points.
Datasnap is good tech but not advanced enough - rem objects dataAbstract is superior. No advanced security, only win server, no Mac/Linux clients or linux servers. Not very good for 3tier. You have compete with industry standard app servers with data snap. -
Wednesday, 11 August 2010
Next idea: develop new help system for studio.
Current Microsoft system is ugly - it's slow and not connected with wiki.
My suggestion: create open source language parsers for Delphi, c++, prism, php to extract metadata (classes, objects and other stuff to be documented) into XML document. Support several doc comment styles (javadoc, etc). Then make some sort of syncing XML with wiki to be sure for all properties to be documented. Then make offline browser for wiki with search, auto updates. Then integrate this browser into studio and let have stand-alone version.
Then make all this stuff open source and suitable for component developers. Let other parties to enhance it with support for new export targets in addition to wiki: chm, PDF, help, help2 and so on.
Make some QA metrics about documentation for components or projects - like in doc-o-matic.
And you can partner with rem objects - they have such system already, but it's not so advanced. -
Wednesday, 11 August 2010
We all love Delphi and If we can all find a middle ground between what EMB can deliver for now and what customers are demanding, with an agreement on how we ALL move foward, TOPGETHER, I think we will all succeed. Its like we are all married to Delphi and EMB are our in-laws.
-
Wednesday, 11 August 2010
Personally, I think the "XE"-naming scheme is one of the worst ideas ever.
Customers are already confused with all the bundles and licensing schemes that are available for Delphi, e.g. I meet a lot of people that think Delphi is not sold anymore as they only hear about RAD Studio. The XE-step will bring more confusion to customers as it changes yet another scheme people have gotten known to. Change is not always bad if there is a proper reason for doing so. I think to call Delphi "XE" now lacks proper reasoning as it does not help to draw more attention to the product. This is all my personal opinion, of course. -
Wednesday, 11 August 2010
I totally agree with Holger. the year-based scheme was way better than any number/xe-naming. By stating "I'm working with Delphi 2010" everyone (even those how don't know Delphi) knows I am "up to date" with my development tools (and maybe my development strategy). Why not combining the xe/year schema?
RAD Studio XE 2011
Delphi XE 2011
...
Oh you marketing guys don't know anything about a real programmers' life and his struggle and fight with management -
Wednesday, 11 August 2010
I look forward to the new version of Delphi. I hope indeed that it will be a good release. And I trust in you, the makers of Delphi (hoping that the management of Embarcadero does really support you).
Personally I don't like much these "soon", "in a few days". Speaking in this manner to our customers does not give them a great satisfaction. So I have to develop my patience ...
But thumbs up, guys go on!
Klaus -
Wednesday, 11 August 2010
Fran: In a big family there a brothers who play in the adult league with customers that are called Enterprises where Delphi has prooven to be a good approach on the server side.
From time to time these Enterprises switch their server OSes and usually this are bigger rollouts with the goal that all the servers are switched. They do not care if you can do or not even if the IT people understand there is CIO - and says - why not this server and why not now. Then they have name a certain supplier who is not is not in the position to bring a solution on 64bit - because there is a compliance rule that says - Software running on servers must bit 64bit compiled. And if you cannot ship you are not in the position to serve the strategic plattfrom - IT Managment solve this problem - this can mean beside nice words - in the background they seek another supplier. And in this league you must tell the customer about - availabilty of 64bit support of your supported tool.
The moment you come to a classical C/S App or Desktop App there is at moment nearly no issue with 64-bit in the market of Enteprise. There are issues with 64-bit dlls, IIS integration or comunicating with other processes. You have XP 32bit there.
It leaveas little bad taste. Thats all.
Desktop:
In some areas I never really understood - if a vendor like MS says - guys we want you to integrate via .net into Office - Embarcadero offers a .net Pascal and then complaining, we cannot simply recompile our apps - we fear loss of sales, because we are dependent on Add-In-Express that also ship something that works together with Prism - here it is time to break a lance for Embarcadero - Product vendors like MS have straight strict rules how to build addins to their apps and Embarcadero cannot compensate this kind of "freedom" permature.
They cannot offer more than an opportunity in case of an urgent compensation in the fashion it is requried but in your language.
They should not here blame Embarcadero for ones breaking these rules.
This very often goes wrong in the 64bit discussion. Other points are here where I say ... but there are priorities and dependencies.
@Holger: All Access XE is from a marketing point of view a lot better for Delphi - because accompanied by the DB products it makes Delph part something bigger where the is no discussion about ...
No one decides at low level in an Enterprise .. they decide --> Aha ok with on All Access XE licence I cover
a) My mainsteam DB, and a house made server with a toolset that fits from the overall picture.
b) Get per seat an IDE for .net and native (in the future more OSes) maybe for mobiles too.
c) Can handle ASP.net development or in other cases with PHP or Intraweb and most in one language.
d)...
This is what I call an offer. Enterprises have Archtiects, DBAs and developers ... the tools must come from a well known vendor. Thats the game.
All the movtivated guys with one D7 license never updated for 10 years having it installed for 10 people ... will not help us to move the product forward. It is always very simple in this world to find reasons against. I know a DB Tool that was built also with Delphi 2005 SVP2 and released. It is a matter of will and with a tiny number of people have rewritten a Toad clone integrating the best from other too in shortest period.
Embarcadero is very polite against its whole customers. On other plattfroms there is a lot more rough wind, where sales promises pruchasing departments heaven and straight send the developers and the user to hell, never having ever the intention to implement things.
Concerning this Embarcadero is really is very open and honest in the overall picture and they take into account that sometimes little rumor is on the way.
Toold Cloud: Believe it or not - licencing in some area already worth via leasing on a montly base. Since the whole tool area - similar to the case tools in the 90s are simply seen as indirect spend to thirdparties - they are under heavy pressure.
I think we will profit on long term from the XE ... maybe the wish to Embarcadero to consider Win Win possibiltites into direction of Linux on the serverside too in a reasonable period. -
Thursday, 12 August 2010
> Dennis writes: I totally agree with Holger. the year-based scheme was way better than any number/xe-naming. By stating "I’m working with Delphi 2010" everyone (even those how don’t know Delphi) knows I am "up to date" with my development tools (and maybe my development strategy). Why not combining the xe/year schema?
You can tell everyone that you are using Delphi 2011. You can see the build number, the compiler version number - and use those naming conventions too. "XE" is our company wide naming to identify those products that have the same attributes versus non-XE versions of products.
> Oh you marketing guys don’t know anything about a real programmers’ life and his struggle and fight with management
I am a developer. I have been since 1969. I also know what a real programmers' life and struggles are. If there is more I can do to help you, provide you with additional information - there are many ways to contact me. If I need to visit and meet with your management, I am happy to do this as well. -
Thursday, 12 August 2010
> Ray Andrews writes: How does the Tool Cloud help the small developer who only needs Delphi or maybe C++ ?
One part of Tool Cloud is the use of our on-demand versions of our products. This allows you to use any product without having to install it first. You can run it from our server, your server or from a USB memory stick. If you've installed 3rd party components and made other registry settings - the on demand version of Delphi will pick those up too.
Another benefit of Tool Cloud is that it allows you to manage all the versions of our products that you have on the server we give you. You can use the All-Access client to on-demand launch any version to deal with projects that may have been built with any number of current and previous versions.
One more (and there are more) benefit is that you can have your own local copy of our license server to manage all of the licenses you have for our products instead of using our server(s). You can continue to use our license/registration server as well. -
Thursday, 12 August 2010
David I. XE in the Oracle world was intended as ""works out of the box" for the developer but limited to 4GB in storage. So this term turned into "reduced feature set", propagated too by Oracle concerning the Windows Edition of the DB to "take away fear" from the being bloated image forced by Microsoft when they compared SQL Server to its main competitor. That's the "misunderstanding".
Coming back to priorities. It makes sense what is built in. Wish all here fun when trying to get a bigger company to buy you a Beyond Compare - I see at least 100s of reasons why developers will give up when trying to get something like this. This must come on board.
Embarcadero has understood that in the Delphi community there is a broad range of different people developing in different development process kinds from good old RAD over Software Kanban to Agile and is definitly hard working to keeping Delphi appropriate for us. If it turns out that a dynamic Pascal language on the JVM is an appropriate alternative for Enterprise developments then the Delphi XE can appear in these clothes too - this little strange idea but would allow to reuse the existing multi-tier profiling capabilites of a certain infrastructure. In this extreme scenario you can simply check it out from the toold cloud run it and proof that it works. Without an infrastructe like the toold cloud you have no chance. If we think over more realistic scenarios - I find a lot more. -
Friday, 13 August 2010
[...] Ahhh… olvidaba una cosa… quizás os esteis preguntando el por qué del nuevo nombre “XE”, “sufijo” con el que están marcando los ultimos productos de Embarcadero. La respuesta, la deja David Intersimone en una de las ultimas entradas de su blog: http://blogs.embarcadero.com/davidi/2010/08/11/40088/ [...]
-
Monday, 16 August 2010
Flotsam and Jetsam #5...
Flotsam and Jetsam #5... -
Tuesday, 6 August 2013
[...] you want to order it from German speaking countries.From this Delphi and RAD Studio version on, the XE is now part of the product name – indicating the new family of Heterogeneous products from [...]
-
Please login first in order for you to submit comments
- Page :
- 1
Funny, now we know what is inside the "name". But we don't Know what is inside the product delphi XE. I cant believe the strategy behint these is thinking on the customers