Why every new release some language instructions change?

  1. 7 days ago

    With each new release (or almost) I have to change my code. Because even if the old features are still compatible, soon they won't be.
    This complicates my work. Especially if I developed components, I know for a fact that among some versions my customers will no longer be able to use them.

  2. Norman P

    Nov 6 Pre-Release Testers, Xojo Pro great-white-software.com/blog

    uh ... its new and shiny !

  3. Beatrix W

    Nov 6 Pre-Release Testers, Third Party Store Europe (Germany)

    This is called life: everything changes.

  4. Markus W

    Nov 6 #JeSuisHuman New Zealand, Auc...

    With some changes you have to wonder if they have been introduced to force users to upgrade …

  5. Sascha S

    Nov 6 Pre-Release Testers, Xojo Pro Germany, Lower Saxonary
    Edited 7 days ago

    @Markus W With some changes you have to wonder if they have been introduced to force users to upgrade …

    And others are a very welcome change (Exceptions, DateTime, ... f.e.) ;)

  6. Norman P

    Nov 6 Pre-Release Testers, Xojo Pro great-white-software.com/blog

    exceptions as a general purpose error handling mechanism are much slower
    thats deliberate
    they are meant to have almost no impact on normal code flows but are slow when you end up hitting them a lot
    I wrote about this

  7. Kem T

    Nov 6 Pre-Release Testers, Xojo Pro, XDC Speakers Connecticut

    What specifically?

  8. Norman P

    Nov 6 Pre-Release Testers, Xojo Pro great-white-software.com/blog

    @Kem T What specifically?

    no idea who you are targetting with that question ?

  9. Kem T

    Nov 6 Pre-Release Testers, Xojo Pro, XDC Speakers Connecticut

    Wondering what changed specifically for @GabrieleMarchionni that requires a change in code.

  10. Norman P

    Nov 6 Pre-Release Testers, Xojo Pro great-white-software.com/blog
    Edited 7 days ago

    Lord knows but there do seem to be new bugs in old code with R2
    Feedback has a bunch listed
    And the forums have several discussion - some relating to things like URLConnection which isnt new but the bugs are
    like https://forum.xojo.com/56833-2019r2-sslsocket-problem

  11. Michel B

    Nov 6 Pre-Release Testers, Xojo Pro RubberViews.com

    Let us be mercenary: these new changes will require upgrades to your components, and an occasion to grab some dough ;)

  12. Dave S

    Nov 6 San Diego, California USA

    Change is inevitable... but changes just for change sake is stupidity

  13. Norman P

    Nov 6 Pre-Release Testers, Xojo Pro great-white-software.com/blog

    @Michel B Let us be mercenary: these new changes will require upgrades to your components, and an occasion to grab some dough ;)

    update - not necessarily "upgrade"
    in many cases the only thing that changed in Xojo was the name
    they even said as much

    Many deprecated APIs still share their implementation with the API they replace. A good example is RecordSet.MoveNext and RowSet.MoveToNextRow

    from https://blog.xojo.com/2019/10/29/your-path-forward-with-api-2-0/

  14. 6 days ago
    Edited 6 days ago

    I started using Xojo 11 years ago. I bought the first license of RealBasic in 2008, then update to Xojo in 2013. And then I bought other updates over the years. I'm not talking about only this latest update to 2019r2, but in general.

    Take a look here at all the deprecated things over time http://docs.xojo.com/Resources:Deprecations
    Can you imagine how many times we had to rewrite the code?

    I don't understand in this release some simple things, for example:

    • Why "var" and no longer "dim"?
    • TextFiled, why "value" and no longer "text"?
    • Array, why "LastRowIndex" and no longer "Ubound"?
    • etc.

    And I don't understand why after lots of updates and yet:

    • There isn't simple and quick bookmark management like Visual Studio.
    • You can't change the code in debug running, but you have to stop, change and restart.
    • The main toolbar takes up a lot of space and has very few features.

    Dunno...

  15. Dave S

    Nov 7 San Diego, California USA

    @GabrieleMarchionni I don't understand in this release some simple things, for example:

    You are not alone here.... and there are literally HUNDREDS (ok, a few dozen) changes like that that do nothing to add benefit or productivity.... as a matter of fact.. .most reduce it.

  16. Kem T

    Nov 7 Pre-Release Testers, Xojo Pro, XDC Speakers Connecticut

    But these do not force you to change code. You don't have to rewrite a single line for any of those examples.

  17. Dave S

    Nov 7 San Diego, California USA

    @Kem T But these do not force you to change code. You don't have to rewrite a single line for any of those examples.

    Which would be fine if you could turn off the deluge of unnecessary "deprecation" errors.... [WITHOUT having to turn off ALL messages]

  18. Kem T

    Nov 7 Pre-Release Testers, Xojo Pro, XDC Speakers Connecticut

    "Deprecated" is misleading, I think we all agree with that. Those calls are not going away, probably ever. But you are still not *forced* to change code because of them.

  19. Dale A

    Nov 7 San Diego, California, USA

    Who really believes that "You don't have to rewrite a single line..." is a positive reason for moving to 2019r2? As far as I can see it, there is only one reason to move to 2019r2 and that is if you really, really need API2. Of course, later versions may introduce new features or bug fixes.

  20. Karen A

    Nov 7 Pre-Release Testers

    The biggest issue now (and it has never before been this extreme) is the problem with backwards compatibility all the change for the sake of 'consistency' introduced.

    At this time they do not really add significant new functionality/capabilities but take away something that is important to many.

    -Karen

  21. Newer ›

or Sign Up to reply!