And here is why I think twice before spending time to report feature requests to QP


And here is why I think twice before spending time to report feature requests to QP

And even bugs/unexpected behavior are regularly being sweeped under the carpet reclassified as new feature.

46 out of those 84 resolved/closed have the resolution "wont fix" or "works as expected".

This is not intended to be a flame but just pointing out the lack of emphasis on new features (at least those being reported in QP)

FYI: Marco Cantù David Millington Horácio Filho

Comments

  1. According to the QP team, how can a "New Feature" work as expected?

    ReplyDelete
  2. Well, that should quell all those complaints that Embarcadero is not "Open" to suggestions.

    ReplyDelete
  3. John Kouraklis From quickly looking through some of those reports it looks like they typically follow the pattern "please add/implement y because I cannot do x" where x was then possible with a different approach (also known as XY problem - see https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem)

    ReplyDelete
  4. Stefan Glienke I see. In that case I think it would be better to mark the issue as "Won't fix"

    ReplyDelete
  5. Migrate to Java instead. ;-) The language is awesome, the development tools are top notch and the available 3rd party tools, libraries and frameworks are out of this world! Makes me feel like the Delphi 4-7 days!!

    ReplyDelete
  6. there was a time when Jedi were great... it was a more civilized time.

    ReplyDelete
  7. Graeme Geldenhuys I know you wrote smiley there, but I still have to ask. Migrate to Java, you are joking, right?

    ReplyDelete
  8. Dalija Prasnikar Java IDEs have a whole lot more code editing and debugging features, their failing point is IME that they are allow unmitigatedly sluggish.

    ReplyDelete
  9. Eric Grange I know. If I count features and usability (besides few minor complaints) Android Studio (IntelliJ based) is the best IDE I currently work with (others are Delphi and Xcode).

    But it can be so unbelievably slow at times. Xcode and Delphi run circles around it.

    ReplyDelete
  10. Dalija Prasnikar: I have only really used Eclipse, and I find it runs just as fast as any other native application. The same can be said for any Java based applications I use. Also from a cold start (just after a reboot), Eclipse starts up about 10-15 seconds faster than Delphi IDE. And the features in the Eclipse IDE is absolutely mind boggling - code generation, refactoring, plugin system, deep code analysis etc.

    The days of Java being slow is long gone. Recently I implemented and compared a software 3D raycaster (game rendering engine) between GCC, Delphi and Java. Being a software raycaster, there is no GPU involved. The code was near identical in all implementations - just the language syntax that really differed. Java outperformed both GCC and Delphi executables by having the highest average frame-rate while the demo was running. I know its a small sample, but it shows what a great job the Java compiler and JIT does with near identical written software, and how well it optimises the source code.

    The Java JIT is amazing these days - optimising the binary on-the-fly to the latest features of the CPU the binary is running on. So you get fantastic forward and backwards compatibility too - without needing to recompile and optimise your application per CPU target.

    The Java language features are also pretty amazing, and tons of new features introduced with every release (something you don't really see with Delphi any more - where there are very small increments).

    I used to work with Java, then switched permanently to Object Pascal around Delphi 7. About a year ago I returned to Java. Things in and around Java have changed so much (for the better). The community around java is massive and very helpful too. I'm really loving it.

    ReplyDelete
  11. Graeme Geldenhuys IDE features are more than fine, but speed is extremely inconsistent, when it works it works, when it doesn't you end up twiddling your thumbs for 15 minutes wondering whether you should kill it and start again (which may take another 15 minutes) or it will be over soon enough.

    And Java is such a blah language you can't even properly hate it.

    ReplyDelete
  12. I thought I was the only who had suffered Android Studio. Tuned to be the slowest as possible, I guess

    I like Visual Studio (and Visual Studio Code) IDEs. Delphi is fine too, but it carries around several "legacy" features like refactoring engine which is demanding some "love" from Emba :)

    ReplyDelete

Post a Comment