That would be my view, as well. I don't think there is enough demand to
warrant specifically targeting Spring Boot, and I don't think the webapp
itself would benefit from adopting Spring Boot internally.
I'd also expect that a framework like Spring Boot that sits on top of
JavaEE would be able to make use of libraries that support JavaEE (like
guacamole-common) without requiring that those libraries implement
specific support for Spring Boot.
- Mike
On 2/29/24 12:29, Ivanmarcus wrote:
Nick ,et al.
Agree with your comments around support and maintenance of previous
versions of Guacamole. There seems little point to me in backporting
and, as you say, it would create quite a lot more work - most likely to
the detriment of future improvements and features.
Probably obvious that the same could be said of 1.x and 2.x branches,
although I have to confess I prefer 2.x Python to 3.x and sometimes wish
for days of yore :)
WRT Spring Boot; I had to look it up, from what I can tell it appears to
offer some simplification/ease of use advantage for some people, but to
the detriment of diversity? I do speak as someone who won't use snap,
and looks at flatpaks with suspicion, but I also very much agree with
you that fundamentally Guacamole should be - as much as is *reasonably*
possible - supported and able to be installed on widely diverse platforms.
Obviously this does not preclude a Spring Boot release, indeed that
would seem a positive thing, but at this point it's unclear to me
whether it's got a wide enough following to warrant spending a lot of
time on it?
On 26/02/24 11:37, Nick Couchman wrote:
...
I'm all for making it easier to use and develop, but I'm very cautious
and
usually opposed to moves that lock a certain project (Guacamole) into
something else and make it more difficult for people to run in
environments
that don't match exactly what I happen to be doing.
Mike, James, Carl, Luke - interested to hear your thoughts...
-Nick
