Well, if you search for Xojo speed optimization in google, the second result is a thread that explains about how compiler optimization sometimes strips a entire loop, talks about pragmas and even has a performance comparisson for Normal vs Pragmas vs Pragmas + Agressive compilation…
So, data is available for anyone to find it
The Xojo documentation isn’t great but what does have good documentation these days.
I just Googled “xojo speed up code” and found at least one Xojo forum posting + what looks like posts on Facebook & Twitter. It’s not hard to find.
Forum is not documenting at all it is user based content and not to use from security view.
Not really sure what you are saying here?
Are you saying that you cannot use information in the forum to lookup the commands in the official documentation to see what they do?
Whataboutism doesnt solve or address the issue
Lots of things could use better docs
I’ve submitted a feature request for them to add this to the LR
Not following to Iso 62304 cause the source of information can not be secured and the correctness of the information can not be verified also the author cannot be validated. So it is only usable after documented testing what makes it really complicated cause I dont want to rely on forum threads tro write test plans for that people telling there.
Another thing: Java, c++, Lazarus, C and c# are optimized with the described operation on my machine under 9 ms. Xojo reaches on 50 ms. That makes it: SLOW as HELL. And to provide a system like this without control if nil and without boundary control is anyhow not acceptable. This checkings Java, C++, C# and Lazarus are doing in Release mode at all. So it would be comparable to the 58 seconds, only to inform you about the stupidity you are building up when writing pro Xojo without looking behind the scenes. It may be so that I am not the best in many things but two things I can do really good: mathematics and logics. So think about it: with all controlling left on 58 seconds for Xojo, 13 ms for Java. Switching all the controls off around 59ms with Xojo, 9 ms in optimized compiling. With aggressive Compiler settings in xojo: Application is not running. That’s a result I would say. Okay, maybe because I am working under Linux and you not. Okay. But what I can see here is: XOJO is SLOW and is NOT programmed and documented PROFESSIONALLY. You can say about what you want. But when you are stepping on the parquet to dance it is not on the others, which shoes you are wearing and how good you can moove. So loosing the battle is nothing the others can change.
And small Hint on this place: B4J optimized comes up to 11 ms. I made also GUI Tests but that you really don’t want to know cause you may write then that I don’t know what I am testing. Exactly this kind of whataboutism you tried to do to me and there is again a small hint: do this only if it is not shooting in your feets when arguing.
So, why are you writing here and lamenting that no one give you an answer in this FORUM thread? 
THAT is shooting in your feets when arguing.
Ivan as far as I know language is directive and nothing else.
I can not use the Forum as the Documentation is one Slice of it.
That it is complex to get this informations for example for somebody which does even not know that Xojo could be faster is the other. That this Switches also can be fundamental for malfunctions of an App is also known. But it is not really deeply documented. The fact that other compilers are documenting this really detailled should show you that there is the need for documentation if you in the same moment want to say: this compiler is on the same professional level. And that is what xojo is doing so why you think I am writing here?
The source of the information would have been the documentation. The forum would have just helped you to look there.
I cannot comment on all of the languages but I’m pretty sure you don’t get Xojo style checking with C & C++ out the box.
So I’m stupid now?
Well I compiled your example in Java and Xojo earlier today on my Mac and Xojo was actually faster. Go figure!
Noi cause that is not in that form there; I was reading the articles written and I was reading documentation. I HAD this discussion with the FDA so I guess: what ever you try to argue in this case it is out of reality cause I am writing Software under authorities and there is the game not like yours where you byself can make the rules.
Try Clion and do the errors the xojo mechanism wants toi prevent you from and you will see that your errors will be catched and thats it. I don’t know why you want to argue if you even don’t know what you are speaking about.
What a dream. Xojo faster. Wo have done it in out testing institute on M1, X86 Mac and on X86 Linux systems. How can it be faster with Xojo. Nice try. I guess now you lost your contact to reality. So tell me please the config and show me the screenshots as I was doing also to show that xojo was faster. My Code was in Xojo measuring seconds as you said it was faster: while it is 0 when it is in milliseconds speed. So: somehow you where not reading what I was writing later or you try to get me with a lame argument. Thatś not possible like you say it.
By the way: it is on all computers except xojo fanboy computers. Can you see something?
And when he DID ask there no one responded to him with that
I gave it to him in a discord chat and was surprised he hadnt known it yet
So I also went seeking whats IN the xojo documentaiton under various titles
Its there IF you know what to look for - but its not on the pages that DO talk about optimizing etc
Thats what I’ve asked be added to their documentation so anyone can find it
and that’s also where it should be and where it has to be that anybody can find it. That is the practical example for misunderstanding the needs of documentation following software standards. That’s why Compiler directives are described by oracle for Java in a real big chapter. And yes it is doing really much stuff out of the box.
A friendly reminder that IGNORE works REALLY well
As @npalardy wrote, I have siomilar devices outside I have to support. And I will do that in the honor I have to do that. So I will not get to the point. I am not against the company. I am not against you. But what I am not accepting is the fact that people like you try to forbid me to speak. Yes, you have the freedom of Speak. So what is your real world name? I was writing mine. You not. Why?
With the attitude he has its no real surprise that nobody helped him.
Sorry that you believe that you can treat so. When I was acting before month I was complaining about the disruptive changing to Web 2.0 and ending support for 1.0 because there where more than 100 showstopping errors inside from our point of view. Speed was never the problem. Problems where ending of support, not correcting of errors, not working vompilefor Mac from windows and Linux, not working features, complete structural changing of web so that in the first versions it was impossible to rewrite completely and in later versions because of internal framework errors. Sorry for that cause you as a xojo fan believe world follows you. But for your information I was not there to get help I was there for changing it’s structural problems. When and if I need help I can and I will ask but I will never act as fanboy of. Whenever you believe that I tried to get help from xojo forum there is a hint: it was never the case. The errors inside xojo have nothing to do with the programming or the programmer but with xojo itself. When and oh you think that you have the right to do like you do: not my Problem. And with your attitude I would say that you really not know who I am and what I am. So please: I will not speaking about you and you hesitate to answer me would be perfect coexistence. Other than xojo forum we don’t want people to be banned here. Therefore you should go the civil way and leave it.
Are you sure your Java code is ok? It shows a negative result, and you are subtracting endtime from start time, whereas with Xojo you are using the opposite subtraction.
EDIT: Just read that getnano() in Java is reading the nanoseconds of the second. So your Java code must be terribly wrong IMHO: Once both timestamps exists in different seconds, it will fail. And the subtraction is indeed reversed.
Please redo the tests with a working time measurement code.
Negative result comes from wrong placement of variables in subtraction but makes no difference in tesult
It is not terrible wrong cause it is giving the correct time. Repeating of the code brings the same result, counting microseconds from 1970 brings the same result so what?
If you would calculate you would know that 10-3 is 7 and 3-10 is -7 so there is no difference except the -
The getNano() method of Instant class is used to return the number of nanoseconds later in the time-line represented in this instant, from the start of the second. The nanosecond-of-second value which measures the total number of nanoseconds from the second value returned by getEpochSecond().
Both times gernsno is related to the time now like you see in the code so it is related as the exact nanosecond relative to time now.
And for sure without pragmatic xojo needs 58 seconds and with pragmatic 59 microseconds what is acceptable but not fast. It is slower than the java code and also slower as c++ or Lazarus. This is fact at all. With optimizing I get to 25 microseconds with b4j what is double zime fast than xojo. There is no discussion around.