Following the beta testing period and some blog post pre-announcing some of the key features (see also my blog), yesterday Embarcadero officially released RAD Studio 10.4 Sydney, which includes Delphi 10.4.
There are many new features in the product. For Delphi developers the key are:
There is way more in the product, this is just my personal take of the top 3 areas we worked on. Extensive bug fixing is another key element of 10.4, with one of the highest number of public reported bug fixed in a release. And the return of a very nice classic Delphi Greek helmet logo!
Learn more about RAD Studio 10.4 and download your 30 day free trial from our website
Reduce development time and get to market faster with RAD Studio, Delphi, or C++Builder. Design. Code. Compile. Deploy.
Start Free Trial
Free Delphi Community Edition
Free C++Builder Community Edition
"1) Delphi 10.4 Sydney changed the colors of the forms"You can see your color on design mode by active GlassFrame property of the form.
All products, especially software, are not tested well enough. It seems the problem is getting worse each year. There is a rush to meet deadlines, which are usually extended anyway. Who wants to buys something that does not work as promised ? Users shouldn’t need to wait for updates for something to work correctly.
Not just picking on Embarcadero, but all products. The customer should not be the main source of QA. Customers are trying to get their products completed on a time schedule too, for their customers. Using a product that is not working as it is supposed to, negatively affects not just the use and reputation of their products, but those of your clients too.
Quality matters. Would you want (or your family) to drive a car, use a tool, or sadly even get on a plane that has not been properly tested ? Sadly we are seeing the results of the disregard for quality built products. If it doesn’t work in many scenarios – don’t release it. From the many comments, there are many customers that desire and need a quality product. They would probably be willing to help the company achieve it by assisting in finding bugs in a pre-release version. QA by choice, not by using a new version – expecting (and hoping) it will work.
‘Do unto others as you would have done to you’ applies to products too. Build the quality of software that you would like to use.
as somebody suggested on quality.embarcadero page
<uses-sdk android:minSdkVersion="%minSdkVersion%" android:targetSdkVersion="28" />
which sits in your project directory
of course, 3mi help more than support team!
I had the same problem hrere!. You found the solution for this?
Happens to me every time as well. Switching back to embedded designer gets rid of the AVs, but get AVs all the time when using the designer in undocked mode (i.e. Embedded designer unchecked).
My 2 cents worth is that this version is released too soon. Buggy and a lot of GetIt components are not ready yet! We were made happy with premature baby, causing us all sorts of problems. Instead of being able to concentrate on developing we are bug tracing!
What you are asking for was accomplished by 10.3.1, 10.3.2, 10.3.3.
The remaining patches are solved by the new ability for auto-updates in the IDE. There's nothing more to do here.
Take a look at the number of releases surrounding 10.3: https://github.com/ideasawakened/DelphiKB/wiki/Delphi-Master-Release-List
When dealing with software, when do you ever have a solid bug free stable version? And they just added the ability to automatically and easily patch if some bugs are fixed.
Marco, if you find many issues here (the wrong place) it is only a "signal". If you have some influence in the developing process, you should be aware that developers don't need a "moving unstable target released every few months", but a solid - bug free - stable version; that can be automatically and easily patched if some bugs are fixed or small features added.
If you publish some patches (and you'll probably do it soon), please use a "cumulative patch" strategy (older patches are included in the last), in order to make it easier to align the product to the lastpatched version (this should also be done on older releases e.g.10.3.2)
A pure subscription model definitely sounds attractive -- depending on how attractive the initial cost is, of course ;) Please consider also a Windows only option. I'm sure there are many developers (apart from myself) who are only interested in Windows desktop apps. "Apps" on the phone are great, but not the be-all-and-end-all for every situation. Nothing comes close to Delphi/C++ Builder when it comes to building Windows desktop apps -- never has. VCL is still where it's at for me :) Anyway, thanks for your time, Marco. Onward and upward!
Yes, sorry. I see your point. We are not convinced a low cost edition is really useful, compared to a free option with some limits. But we might reconsider. And also we keep considering a pure subscription -- with my lower initial cost. Thanks for the feedback and suggestions.
Marco, you've misunderstood me entirely if you think I'm personally complaining because the Community Edition 10.4 release may lag several months behind the paid versions. I'm not. The 10.3.3 release is a very, very good release. In another thread Sarina stated that people are abusing the licence conditions of the Community Edition (and I've no doubt that is true), which is why I suggested a cut-down paid-for starter Edition (Windows only) might be a better way of getting people into the RAD Studio ecosystem, rather than having a free version that lags behind the paid-for versions (especially when we don't know what the lag is or whether the free version will even continue to be made available -- i.e. Idera did not disclose the status upon the release of 10.4). To dare suggest such a thing I was reported as a spammer and was forced to defend myself. A very strange practice, indeed.
You say with regard to the lag that "this is what many companies do". Obviously not Microsoft with Visual Studio, so perhaps you can let me know what other company producing developer tools works this way? Note once again that I'm not suggesting it's a bad practice, just that you've introduced the concept to the thread, and I'm curious to know what other comparable companies work this way, because TBH it's not something I regularly come across.
My point is this. I think it's fair to state that market share for RAD Studio is not as high as anyone would like. And I don't believe it's because the product is no good. Quite the opposite -- it's an amazing product! But what message do you send when you encourage people to try the software for free, but when they hit the website they find out they're going to get an old version? I know, and you know, that 10.3.3 is a great version and not "old" by any stretch of the imagination -- but do you think a prospective new user "intuitively" knows that?
Just some food for thought.