Christian, you effort is appreciable and yes, they fixed it for now. Let’s just keep this in mind:
‘Not actionable’. From this we can safely conclude that in a certain town in Texas, the inmates ru(i)n the institution.
‘Not actionable’. From this we can safely conclude that in a certain town in Texas, the inmates ru(i)n the institution.
No… if the INMATES ran that asylum then perhaps we might have some concensus… But as history has indicated time and time again, this particular asylum is run by an Iron Fisted ego maniac
2 Likes
I actually specifically mentioned this case being marked that way to Geoff in a very long email
I dont understand it BUT other related cases seem to indicate that they HAVE removed the string parsing
I guess those who still use the product will find out in future releases
I’ll point Hopper, or another disassembler, at this code again to test that claim since I am still using Xojo for client projects
Yeah, I see what you mean. How can a self-respecting software developer make such statement? ‘Not actionable’ spits in the face of all available evidence.
If Xojo Inc is a place where such brain-dead decisions can be made without consequences, I can only recommend to anyone who still uses Xojo to drop it as fast as they can. Looks like the Xojo team is capable of doing more of this kind…
2 Likes
The process they use needs improvement
Dunno if they do code reviews for check ins
Dunno if unit tests are required for code check ins whether its net new or a bug fix
Better processes should lead to better outcomes
Watched a show last night where the owner had a saying
6 P’s
Proper Planning Prevents Piss Poor Performance
1 Like
The English language is a treasure trove - love it!
There is a difference between what’s good for you (Customer) and good for the inc (vendor). Because what is good for you has not in all cases also to be good for the customer. In case of Xojo is good for the customer everyrthing what is good for getting new customers to make revenue. In case of the Customer it is good to get all the needs of stability, reliability and so and espeicially getting all bugs fixed which are inside of the framework.
In the optimum the vendor has a structure which allows to do both: building new features and fixing Bugs for existing customers. That is the system driven by many vendors like you can see, like C#, C++, Java and much much more. So existing users getting their needs of sustainability and stability fulfilled and for new customers there are many features for supporting newest technologies.
For small vendors this becomes automatically a problem while fixing all stuffs is really complex when in the same time building new features. In case of Xojo there is also a big Platform project behind: the Android project. Since there is no problem to directly compile for Android as binary like others are doing there would be the need of providing a rendering framework for it.
The other chance is a JVM Language, in case of Android it is named Dalvik VM instead of Java JVM. Dalvik of course has an own rendering engine and so there is no need to fulfill that.
A third way if kotlin multiplatform mobile. Using that you can compile directly to Android and run it there using the renderer of dalvik. Xojo decided after trying before another ways to go this way. Simply looking stuffs can be a big problem. So it is in this case. That is a problem which follows Xojo since they decided to go this way. Android is costing them until today years of development and - without a real success of a release.
This is fundamentally their problem. New features for the platforms combined with the need of everything else.So it is not simple to have both sides happy while that needs on both sides manpower. Since Xojo has only a hand full of developers there is a big problem to implement that stuffs. And also to be able to get that stuffs maintained.
The CEO decided that he wants to get as much as he can get new customers so new features are the hottest target. Simply. A decision. And that decision is the needed argument how to behave with bigger projects you business will rely on. For me a Don’t do. And that’s it.
2 Likes
Is there though in the end, if you really understand the interdependency of the two? Sure in the short term something may be more in the customer’s interest than the vendor’s. But if enough customers have their interests ignored it will hurt the vendor ultimately, and probably more than it would have to begin with in almost all cases.
This is playing out on Reddit right now. I’m not very active there but from what I can tell they have decided to charge up the wazoo for using their API all of a sudden when it has been 100% free. Some popular tool vendors are shutting down because it would cost them millions to keep operating. Some moderators are shutting down their subreddits in protest. In fact the site went down for awhile, so many subreddits shut down for 2 days. Others are shutting down until they undo these charges. Reddit is strong-arming moderators and claiming they are not.
Sound familiar – especially you former and soon-to-be-former Xojo 3rd party vendors?
Like the Green Ones, reddit is taking the position that “this, too, shall pass” and remaining firm in this unpopular decision, when they should IMO be pausing it and doing the kind of humble and respectful communicating they clearly weren’t, to begin with. They are not respecting their users and their ecosystem and it will cost them dearly. But they don’t seem to know that. Just like a certain someone we all know & love.
Catering to stockholders (or to a sole proprietor) over customers and ecosystem partners, is losing sight of where your bread is buttered.
2 Likes
You’d think watching the unfolding disaster that Twitter has become would be sufficient to warn others about rash and ill communicated changes
But … more money than brains ???
1 Like
Thinking the CEO or shareholders are the ONLY, or even the MOST important, stakeholder is usually a mistake
No customers = no business
1 Like
Clear words to it: I didn’t said that this is a good way of behaving. I am following only the logic of what I can see from the outside. We all have to accept that they have their thinking about that if or if not the decisions are good for the future of the product.
1 Like
Usually good for the customers = good for the company
Twitter & Reddit are examples of the reverse thinking in action
2 Likes
The problem is: you need to have the needed revenue to turn your company around. And at the end this is for the most products the ending: not enough customers. And that danger they wanted to prevent. And again: was that the right way? possibly not. Was that the only way? I don’t think so. Was it possible to make another strategy with a LTS Release Modell? Yes, for sure. Was that a good decision not to do it? Nope not at all.
But again: at the end they decide how and was and when and why. We decide only: to buy or not to buy.
Yes - users have little influence except with their wallets
They can beg, plead, whine, bitch, complain all they want
But in the end it comes down to “Do I pay them money or not ?”
And I know how many here answer that question
1 Like
I know at least one genius on this planet checking every day if he really looks like Steve Jobs or perhaps a tiny bit like Elon 
Peanuts, Green peanuts. Their way to give back to the community
Perhaps their future business model is about people paying to be allowed to post again on TOF?
Pesnuts reminds me to deutsche Bank and Mr. Schneider…hawg…niot nice what they have done. And I believe strongly that Xojo inc. has not the same financial background like Deutsche Bank has…freaky but true in a real not nice wise.
Do I get a blue verified bird avatar too ???
1 Like
no people like you and me are getting a warning notice!
1 Like
no, but a green bug.
I am on Mac OS 12.6.8 (Xojo 2019R1.1) and trying your code:
Declare Function NSClassFromString Lib "AppKit" ( className As CFStringRef ) As Ptr
Declare Function processInfo Lib "AppKit" Selector "processInfo" ( ClassRef As Ptr ) As Ptr
Dim myInfo As Ptr = processInfo( NSClassFromString( "NSProcessInfo" ) )
Declare Function operatingSystemVersion Lib "AppKit" Selector "operatingSystemVersion" ( NSProcessInfo As Ptr ) As OSVersionInfo
OSVersion = operatingSystemVersion( myInfo )
I get :
Major = 10
Minor = 16
Bug = 0
Using System.Gestal I get exactly the same thing… but 10.16 would have been Big Sur if it had been called MacOS 11…
So how does one get the correct OS version using 2019R1.1?
Thanks,
-karen