I’m sure it’s available but our company does not support them. We regard readability to be more important than compactness.
Though, with that said, Go developers seem to really like the 1 letter variables at times which drives me nuts since I don’t consider them to be more readable.
I’ve always favoured making code read like English (or as close to it as possible) esp when it came to variable names
Comments get outdated
Code doesnt so if the code is clear & understandable then it should help whoever has to touch it down the road
one letter variable names are, IMHO, the epitome of making no effort to make your code readable
Still no replies to the two DB Kit threads.
* Thou shall write code that is Readable by you and your peers now
and into the future
* Thou shall write code that is easily Maintainable by you and your peers
now and into the future
* Thou shall write code that is of course Executable as efficiently as
possible without violating * commandments 1 and 2
Amen
The only time I use 1 letter variables is for loop counters…
Then I use i,j,k depending on loop level.
I have been doing that for decades… I don’t remember where that came from… maybe FORTRAN from way back when I was in school?
-Karen
Xojo should do something like what the Delphi people are doing.
And prioritize feature development accordingly. In short after conducting surveys they should deliver!
Another DB Kit question. I wonder if Geoff will bother to reply?
not likely since they feel they already know what people want
I’d guess mostly by talking to a handful of MVP’s or reading the feature requests in Issues
Go does a similar survey twice a year. They publish the results and talk about what they’re doing to address the concerns.
Don’t hold your breath for Xojo to actually listen to customers. They’ve made it quite clear that we don’t know what we want and need and they’ll give us what they think we need.
…is it possible that the last Xojo Newsletter was in August 2023? This would be a 5 months ago. I do remember newsletters on a regular basis 2-3 month apart.
Remember I need X-Platform, have a short timeline assuming I retire (voluntarily or involuntarily) at 70, can’t spend too much money on it at this point, and have a mental block against reading code who’s syntax is derived from C or something similar.
Over the years I have used a number of difference languages but they did not fall off the C tree.
I have used a number of flavors of BASIC, mainframe/mincomputer FORTRAN, Pascal, Datatrive, and a proprietary language called VGL. Way back when some AppleScript, and in my early 8 bit home computer days a language called ACTION!
What they have in common (besides not being object oriented) is that for most of them the syntax is not that different from each other (though I have to admit I did not like the semicolons in Pascal)
But in the last about 25 years I have only used RB/Xojo.
All that makes moving to something else not practical.
Xojo has a long history of just ignoring users with the famouse now deleted quote “it is my company and nobody is going to tell me how to run it”
But at the same time, maybe they know that user input is important so they lie saying it is community-driven??? 
Come on… minutes after my remark i got a xojo newsletter… WTF!
they really should work more on their crappy newsletters with included marketing bullshit. This is what I see…
He replied!
Maybe Christian can get Xojo to fix this crap? I’m so glad I never bothered with Web 2.0. Freaking insane there was not an upgrade path other than a rewrites as peeps suggest.
25 years with Xojo also, albeit towards the end, I’d started picking up Objective-C as a means of understanding Apple’s API (I was gifted some source code when I asked for documentation on a part of the system and that’s all in C++).
You don’t have to do SwiftUI, I made a list of all the declarative UI languages I could find and most of them cover the big 4, Windows, Android, iOS and Mac.
https://ohanaware.com/blog/2023/10/Declarative-UI-is-the-future..html
I only mention 100 day of SwiftUI, because that’s one of the courses I took (I also read a book). I’m certain there’s something very similar for nearly all mainstream languages.
Not to toot my own horn, but to give you an example of how long it took, I’m just about ready to release my very first SwiftUI app, I started in mid-October.
I could have done it much sooner, if I’d done a 1:1 of the existing app, and not decide to do something new, and had I not done an entire web site overhaul. I also spent some of that time fighting my health, with only working a couple of hours a day for several days. Lastly, I’ve created at least half a dozen basic apps to learn certain things and to help me with some others. One of which is going to become part of a bigger project later in the year.
If you want to “move on”, I’m 100% confident you can do it, but you have to let go of all the reasons you give yourself to stay where you are.
Here’s the scary thing, it doesn’t tell you when you open a Web 1.0 project…
You only know when you try to run it and dozens and dozens and dozens of errors appear. I ended up with far more errors than my Web 1.0 app had lines of code.
And if you edit and save changes, you’re fucked. The older version of Xojo I was using couldn’t open the project anymore and I had to restore from a backup, and redo my changes.
Naw I have ones in Oct & Nov Dec & Jan
but its not like they say much
