is this the answer to your original question? If not it is probably a good summary of this thread.
Funny, I had the same thought while reading. āThank you for your service and have a great dayā.
-
And there are more observations: alphabetical listing of the names would be more common in this case or is there a hidden ranking?
-
āMartin T.ā is interesting, because the full name is on the homepage. But MVPs are probably not important to the Inc. either, why spending the time to spell out names correctly?
-
Seems like it was spit out in order to actually convey a different message.
2 Likes
They have no incentive. But I wouldnāt blame the MVPs for that. It is Xojoās business to define who does what and what are the interfaces (APIs).
There are MVPs who do their best to keep the Xojo ecosystem alive. Alas, other MVPs turned into mercenaries for Xojo Inc.
The Xojo Director of Marketingās call for āreach out to us or the MVPs if you encounter issues with Xojoā is pure BS, dishonest and cynical.
They simply ignore any input that does not fit their own goals and intentions.
Fool me once, donāt fool me twice.
1 Like
another observation: long time ago (maybe somebody could find it out) Xojo announced a new addon-creation-process. Developers should be enabled to create addons for Xojo within Xojo without the need of external IDE/compilers. Never heard anything since then.
Having said this: Aināt it funny you are not allowed on TOF to speak about other IDEs/Compilers but you need them to create addons?
Can anybody prove me wrong in my conclusion?
1 Like
wow 8 yearsā¦ and still nothing in sightā¦ how long did duke nukem take for its successor? smells like a new vaporware awardā¦
we are developingā¦
So they started to develop and stopped somewhen?
Or did they postponed everyting because of API2 or Android or whatever?
Or was everything a simple lie to keep us Devs buying their licenses? (and MVPs addons?)
P.S. just checked: Duke Nukem Forever, announced 1997, released 2011ā¦ well then I expect this addon-feature in 2029, but i doubt xojo is still alive until thenā¦
1 Like
You arenāt wrong, I feel really sorry but there is no way in this reality that you are wrong. I know somebodyās reality whereā¦
I guess so seven years after Android release.
Would pretty much be my guess.
In the real world it is no question: everything around was postponed even Web 2.0 back changes. After renaming events for API 2.0 (look on messagebox which was before msg box and later renamed again to msg box but not so in Web 2.0 where it is still message box). There are so heavy stuffs insideā¦ The same Language but different names for the same functionalityā¦
So I beliebt that there is one Problem which causes all of this phenomenas: a too small Development Team. And that they can not compensate. Changes like they have done are dangerous. Too dangerous for Pro developers.
In my eyes that is also the reason why they changed their Customer target from professional Developers to citizen Developers / beginners.
What triggers me the most is this kind of invonsistency paired with the big amount of Bugs and showstoppers and with the Behavior of the inc. But maybe thatās why I am working with Java. Because there I have the code consistency over long periods (saying this I can still compile the most of the 2005 written Swing Applications or I have to do even really small changes) and where I have granted periods for Support, Maintenance and Security Updates foreseeable until 2031 with Java 21. It is exactly this what drove me crazy.
Wylie they do that amount of changes the time a programmer has to realize that changes is nearly 0. While can really think about to compile commercial sold Software at the end with a 6 years old Compiler (Xojo 2019R3.2) while the project is based on API 1 or on Web 1.0. The Deprecation process is coming out of the Blum without any warning. The only chance a user has then: using it as Long as it compiles on modern Systems.
But to speak truths: our Brute force Tests with Web 1.0 showed us: we would have to change to a newer Platform. And yes, that was promised by Geoff Perlman that Xojo Web 1.0 Projects can be converted to Web 2.0 Projects so that the Code will run on that Platform.
The Result all of us know: in the beginning half of the functionality was missed, until now there is much stuff which is impossible to convert and conversion of big apps can lead to a rewrite.
So exactly that Behavior is showing that Xojo really has no connection anymore to their Customers. Sad.
1 Like
Which is exactly how I feel.
3 Likes
Guess whatā¦there are many pople feeling like this. A really long time Xojo could hold the people to pay the maintenance fee. There was a leak in the market for a tool like this with simple drag and drop Designers for GUI and they provided native interfaces. That said I have to comply that they are not really butā¦
People had their Cool Aid and loved the platform. Youāll still find pople doing exactly that. With too many upcoming alternatives even the last professional User may wake up one day and realize: okay, full of Bugs, problems, workarounds, I need something else with less Bugs, less workarounds and so on. That leads to customers leaving Xojo and stopping maintenance.
People which are waking up will of coarse start to have this problems. While they are not listening to the Cool Aid. They are starting to realize that it is not really working. For example not to have Threads. In times where Java starts even to virtualize Threads so that you can save resources without by self taking care of it. Minimum functionality is not provided by Xojo. That is - as far as I can see - old stuff.
1 Like
You gotta remember that I started when it was a Mac only dev tool, and there were very few alternative options.
That of course has changed now and there are many options for developing Mac applications, I stuck with Xojo for so long, because I donāt want to learn another tool/language.
However Iām now forced to learn again, either I redo all my work to carry on paying this guy for a tool that offers me nothing better than what I can produce with an old copy, or I learn a new language (to me) that allows me to use another tool, which actually brings benefits to the apps I sell to customers.
Last week, I rewrote a small helper, it went from being 17MB 14MB, to 168k. Iām still testing it to make sure it really works as I need it to do so, but Iām going to start moving more of my stuff into tāother tool/language.
Edit: I said 17mb, which is wrong, each architecture slice is 7, so itās 14mb.
3 Likes
you triggered meā¦ single exe binariesā¦ discussion of 2008/2009? 
1 Like
No feedback can be gathered from developers who do not express themselves. As soon as they do, they are ignored (the loathed vocal minority).
Remains the foul marketing stunt āPM usā. No evidence provided to the community, no base to discuss or elaborate on a topic.
1 Like
Little helpers I am realizing with Python and the rest with java except firmware there I use c,c++ and Rust. All is possible.
2 Likes
what tool did you use?
Xcode
3 Likes