Not being familiar with BeeWare, my first thought when reading the title was "oh no, another project shutting down?" - because without the "exciting" before it (which was probably removed to avoid appearing "spammy"), "News for the Future" sounds kind of ominous...
Great news. BeeWare is one those projects I've been following for years, hoping that it would get just a bit more 'done' so that I could really start using it.
Hopefully this allows BeeWare to become "the" python toolkit for mobile. We've been talking about this sort of thing for more than a decade at this point, and it's a shame that the big boys of the ecosystem (FAANG etc) have basically contributed nothing - choosing to go all in on JS tools instead.
I think this says more about how hard it is to make Python performant for this than JavaScript.
Additionally, don't discount that both of the mobile OS vendors maintain their own JS engines that are directly accessible on their platforms, which makes integration faster and easier to build bindings around.
As someone with an interest in (but very little direct experience with) beekeeping, I'm curious what such a suite of tools would look like. All of the beekeepers in my area are very low tech.
It depends on what scale they're targeting. Quick search show about a dozen options. It looks like most of them are about documenting hive characteristics and schedules (how old the queen is, when to treat the hive, mite counts, etc). I haven't really looked into them since I'm low tech about it too, and only have a handful of hives.
I thought maybe this was an open source version that I could check out for free and maybe even get involved with. I was disappointed it wasn't about it at all. I wonder why/how they picked that name.
Did you actually read the underlying resource[1] or am I missing something? It just requires for-profit or government organisations (with over 200 employees!) to purchase a commercial license.
Seems more than reasonable tbh. I can see the "government organisation" being tricky though.
I've not read the resource either, but it sounds like (from only reading your and GP comment) Anaconda moved something from free-as-in-freedom to free-as-in-beer-as-long-as-non-commercial.
The free license has been severely curtailed. There are many organisations with >=200 employees which might have <=5 developers. In addition, while the client remains open source, the repository (which is almost as important for a package manager) is where the payments are enforced, and also unlike most code repositories, prohibits mirroring[1]
