On 2021-10-19 15:44, Chris Angelico wrote:
... and needs to be updated to GTK3 if it's to survive. As the Red
Queen explained it, it takes all the running you can do just to stay
in the same place, and you have to go twice that fast to actually get
anywhere.
Yes, the constant churn puts smaller "organizations" at a major
disadvantage. I think we've reached a point where a lot of people look
at "mature" software as automatically being "bad", and I strongly object
to that world-view (when it makes sense). The rip everything down and
rebuild every few years world we're living in can be pretty exhausting
:)
IIRC, Lance had done a lot of work to get GTK2 up and running. I don't
know if he's got any thoughts on getting back onto a supported version
of GTK. Hopefully the fact that a lot of the code is generated will ease
/some/ of the effort. I've been going through a similar effort getting
the ObjectiveC/Cocoa binding a little closer to current use; thankfully
that's been a bit less terrible than I expected it to be.
One little note on something that I think is pretty incredible: a few
months ago I downloaded an ancient version of pike (0.4 something,
maybe) and compiled it on an arm64 system without having to make any
changes, and it worked.
Thoughts? Comments? Suggestions?
There are some fairly cool features in the latest Pike builds that, to
my knowledge, aren't well documented yet. Maybe someone - and I'm
fully aware that that probably means "I" - should put together an
example of a socket server with on-the-fly updates and asynchronicity
provided by continue functions.
I don't think there's much in the way of documentation of the Concurrent
and async stuff that's landed in 8.1. A tutorial of that (or some
subset) ala the annotations document I wrote would be really welcome,
even if it's not "publication ready"!
Bill
