Sounds scary! I wonder how one deals with license issues should the company go belly up.
If there is no licensing server it ends up at that day. So you may not be able to generate new licenses for xojo anymore. End of HardDrive is then end of Xojo. That’s the problem nobody can solve. And the risk which climbs at the moment. They should have published what will go on if they will be in that situation. Or speaking about plannings for that case. For companies relying on their product this IS a real argument. But they do not care about that. Cause it is for them no problem. Following the thinkning: if we die what do we care about our customers?
No, you can download a license key and activate offline.
Yes sir, you can. When your harddrive dies the deactivting m,ay not work properly. And your license ends. We have done tests about this and there are several issues about this. It is not a guarantee that it will work over the time. And that means: it is not endless and many will run into exactly this problems.
Ok, may my short Offline-test did not show all of this. Thats bad, of course…
I’m not sure what you mean by this. If you download your key and keep that key file around, you will be able to use it offline. The file is not system-specific.
You really couldn’t though. If you wanted to start using the new dictionary, you had to start using auto. It wasn’t entirely all or nothing, but close to it. API2 has some of this as well though with the new controls. You can mix old and new controls on a window, but you really shouldn’t, especially if you need to iterate over contents because an old window won’t see the new controls, and a new window won’t see old controls.
I do think the new controls part of API2 are wholly unnecessary. I can’t recall any problem they solved. But the language stuff is much more optional than the new framework ever was.
They should have the decency of at least open source and publish the code. If not, once they are gone a crack will just appear on the comunity.
That was Feb 2022, just after I left.
ALWAYS download your license files
Then you can install the license and it will work even if a license server cannot be reached
Oh it definitely works
It had to because there ARE places where Xojo was used where there was 0 internet connectivity so a license HAD to be able to work totally offline
I disagree - obviously
If you buy a diesel car and then expect to put your old gasoline in it yes you will have issues
You could use the new dictionary and auto and at least convert between auto & variant
Yeah this hasn’t worked at all for me
Considering the ONLY language item that has been added is VAR I’m not sure what you’re referring to
Nearly EVERYTHING else is just modules with extension methods - all “framework”
String, Integer, etc is all extensions - no magic there
Not language
True, I was conflating the framework and the language itself in this case. API2 is entirely framework stuff. Which also demonstrates the confusion. We have the framework, the new framework, and the new new framework.
and ppl are still havin’ discussion with me about open source… and toolchains…
open source would be the right way if something would be happened. At the end I am using open source technologies when using Java, intrlliJ, Netbeans. For me it is the normal. And yes, I am paying for the all products pack for my company. No question. But I could choose IntelliJ Idea CE and develop with an open souce toolchain. XoJo has none of this stuffs. But that could help them in development. But people would not pay that much anymore. Maybe more people would use it. Maybe not. Nobody knows.
That’s the only way to protect yourself when companies get greedy.
I do not understand “open source” for “commerical” products…. for niche special interest where you have a set group of people working on it sure. But putting something in the wild, where you have no idea if the people mucking with the code have a clue … no thanks
usually the product is the main fork of the open source and then any proposed additions are SERIOUSLY strictly vetted before being added
Other forks may adopt other patches etc but the official main distro doesnt
Red Hat does that (or did that)
And part of the commercial products offerings may be things NOT released to open source
And / or services
See, I am paying for Jetbrains even if I would not have to pay using their open Source Software. I am paying Supporters for JavaFX even if I don’t have to. Why? While Software has to be developed and maintained. But if this companies would die the Software is still available. XoJo is the example how it is really dangerous.
I have also some code open sourced, mostly Java Libs. I have Customers paying for special functionality and for support. That’s okay and normal. That would not be a model for Xojo while nobody would be interrested to pay. But it is a working model.
If Jetbrains would not give their IDE open source I would probably use Eclipse instead or Netbeans. I don’t want a lock in for some Hardware or Software vendors which are catching me like this. When Borland sold TurboPascal and Delphi all TurboPascal users where without new licenses and maintenance contracting. That was not a good situation at all. And there was no alternative for TurboPascal. That was the next problem. This was the first time I lost all sourcecode and could not reuse it really cause I needed to change.
If there would be an alternative for Xojo and - at least - a cli compiler which is paid for example - I would not say anything. But in this situation I would never recommend to use it.
This is different when using Apple Software like XCode and Swift / Swift UI. That stuff is apple related. But Swift is open source with it’s llvm compiler use. So would say: acceptable. And it is on you if you want to make your code public. There are many stuffs I would never give to the public. But also ones I give to the public. Why not.
If an App is not commercial why should it not be open source? I mean if there is no income with it it can be open source and maybe you’ll find developers working with you on the project.
I make my living from an open source commercial product.