RAD Studio 10.4 has a nice set of new features, now covered in several blog post and in the announcement webinar (the replay is available at https://www.youtube.com/watch?v=-rTLEXLVueQ).
The 10.4 release also addressed a large number of issues, including fixes for over 700 publicly reported issues on Quality Portal (QP). You can see a (partial) list of the fixed issues in the product documentation at: http://docwiki.embarcadero.com/RADStudio/Sydney/en/New_features_and_customer_reported_issues_fixed_in_RAD_Studio_10.4
The large number of issues resolved is also visible in the Created vs. Resolved chart (limited to bugs) on QP:
This is a continuously updated graph that you can see in one of the QP dashboards at https://quality.embarcadero.com/secure/Dashboard.jspa?selectPageId=13100
Finally, this is a breakdown of portion of the bug reports and new feature requests addressed in 10.4. The items are grouped by product area, with some of the categories overlapping (for example Compiler and Tools includes C++ and Delphi compiler issues, but also Linker issues) and issues possibly listed in more than one category:
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
Yes, it certainly appears from all the comments that 10.4 is a bit of a disaster. This perception is not helped by the silence from Embarcadero on any of this. Still I get a daily email telling me it is the best version ever and I should buy it (even though I have a subscription). I learned a while back not to install the ##.0 version, but to wait for ##.1 at least.
The 10.4 IDE is CONSTANTLY crashing. On search functions, on IDE popup menu selection etc! Very very unfortunate!Second: Code insight is not working at all! There is sometimes a quick message displayed like "calculating..." or so but nothing happens. This release is really very bad as it costs us many hours of valuable time. We cannot go back to 10.3 (which worked very well) as thousands of files have been "updated" to work with the new installations we made. PLEASE release a patch asap. Thanks!
Try shaneATstumpwareDOTCOM is my e-mail address.
The e-mails were 5+ months ago when I was trying to decide if I was going to renew by 2020 Rad Studio Enterprise subscription.
All the best,
I don't disagree with this list, but it is not "just the basics" it is a long term goal. CodeInsight, we are spending a huge effort rewriting. Seems in line with your expectations, but a large effort. 4K monitors support for the IDE, that's a significant rewrite of a lot of code would imply more bugs, not fewer bugs. We need to get there, but you are saying you only want stability but asking for significant features.Don't read this as a criticism, your list of fixes is very close to what we also want to do -- but I want to mention this is not simple and it is going to take time
> I have sent David Millington a couple of e-mails with concerns and NEVER get a reply about serious bug fixes
I'm sorry about that. Sometimes I can't answer. I can't reply that something will be fixed, if it isn't already, for example. I pass on customer feedback internally to help make decisions.
I searched my email for "aggie" but saw nothing - were they sent from an email address with a different name?
Hi Marco, I will believe this if it is released. But you should verify your beta programme. There is something going wrong systematicaly. I have the fear that marketing tells the road not the development team.
The last days I learned that you are using C# and .NET in the IDE. What?!? So, thats surely one problem why the IDE crashes all the day long. Too complex. Why not using Delphi/C++.Opening Tools/Options takes on my threadripper system 5 seconds to wait. For an options window (alle values should already be in memory).
I a have a complex form. It tooks always 25 seconds to open and 3-5 seconds for closing!
Creating actions in objectinspector. Almost every 2-3 calls my IDE crashes. This is not funny anymore. These and so many other problems exists since years and with each version marketing tells me the development workflow is better than ever. Bullshit. (Sorry)
Again. Make an Vanilla-Update for the IDE. No other stuff. Only the IDE.. We can talk about Bluetooth, REST, EMF and so many other cool stuff but the IDE/Compiler is the base, something each user needs in his daily work. make it work again in the the next 2-3 months..
* Remove that stupid X on the editor tabs
* Object inspector working (no phantom values any more)
* Structure Panel panel working (click means the focus gets the object under the mouse cursor and no random object)
* Breakpoints can be removed
* Local Watches can be removed
* CodeInsight for complex projects (currently this is for "cats programs", Sorry Matthias)
* Project manager with integrated Subversion (not this crop like currently) - Did you realy use "Save Under new filename"? Yes, can you compile such a project now? Can you check into subversion. If yes: Make the version public.
* Kill that IDE crashes
* Use the Delphi Parallel Lib for Get It.
* Fix all the small translations typos..
* Support 4k monitors
See the list above: Basics, just basics.
A Delphi Lover for more than 35 years.
We are forced to note that C ++ builder is no longer compatible. Android. Either Embarcadero does the necessary to restore the situation before August 1, or they announce the end of android support for C ++ builder.
Thanks for replying.
I understand business priorities but C++ Builder is leaving many users livelihood in the wind.
How are C++ programmers who have an Android footprint going to move forward come August 1st when Google no longer accepts their 32 bit Android apps?
The first Android I app I tried to develop / deploy with 10.3.3 crapped out on ANY EXCEPTION. I reported it after Thanksgiving, had it validated as a bug, and still no fix. I had an opportunity to do a few Clover apps (32 bit Android) and lost out.
I really think Embarcadero's top management needs to get out and visit with its users and give an honest assessment where their priorities are so that their users can adjust as needed (even if the decisions are hard ones).
And no, we don't look at you (or others) as a disgruntled user. I'm sure that if you complain there is a reason for it and we take it seriously. We cannot always act or act promptly, due to constraints we have as a business but we really hate loosing any customers (long time and loyal or new alike).
I can speak for the Delphi side of the tool, more than C++. But in general, I know the product (and the entire industry) has changed in its focus (and also its costs, from the early days). We are focused on improving on quality while keeping adding nice and interesting features.
Sorry, but you don't seem to be working on Embt products. Or You work in embt team. Quality control showing how long errors are removed. Average 800 days each. Taking money for c ++ builder is an unjust enrichment. "Unjust enrichment" - legal law definition. quality.embarcadero.com/.../Dashboard.jspa
First I give you credit for at least responding to the firing squad (I have sent David Millington a couple of e-mails with concerns and NEVER get a reply about serious bug fixes).
But I still get what I consider aggressive e-mails from the sales department since I have let my Rad Studio Enterprise subscription expire this past month (can't justify not getting anything for my money on a small company budget).
I began using Turbo Pascal in 1983 when it was first released to write my first shareware program Pc-Sweep. I switched over to c/c++ not to longer after that and used a product called Desmet C. When Turbo C++ was released in 1987/1988, I switched back to Borland.
For the first time in almost 37 years of using Borland/Codegear/Embarcadero, I am seriously thinking of looking elsewhere for a new way to create new products going forward.
I realize Embarcadero probably just looks at me as a disgruntled user, but I know many developers who have left Embarcadero over the years. I wish I could afford to lose loyal customers.
We are looking into releasing a patch relatively quickly (need to test its stability) to address some of the new issues found. For the debugger stopping, it looks like a workaround is to close/disable the Welcome page -- at least until a patch is available.
Thank you for the Quality push! The last few versions have been more aggressive on features and quality and it's appreciated. We'll never have a bug-free product, but it's nice to see issues being addressed.