At times, mczs still come handy for some merges...
And Smalltalkhub is good as a safe heaven for collecting packages that are otherwise scattered all around.
nothing that a real catalog/centralised package manager alla npm/apt-get/etc cannot do it.
using a package manager as a catalog feels to me like hammering a screw.
Is there a reason why Smalltalkhub would not stay working nicely?
because we do not have the strength/willing to maintain it.
and each day we are: farther from ���state of the art��� source management, and farther from state of the art javascript, etc. (which is the reason why sthub
Are we talking about using bigger boxes here? Or is it a deeper issue?
keeping up-to-date a system like sthub is a lot of work, and takes a lot of time.
personally, I prefer way more to spend my time in things that will have a real impact in the community (like having a modern vm) than lose it trying constantly to catch up with what others (with a lot more resources) already did.
each time I start a sub-project, my first question is: ���this stuff will have a multiplier effect in the community?��� and second question is ���do we have to doit from scratch, or can we take advantage of other projects?���. As a maintainer, and being conscious of our limitations, this are the driving forces I find positive to work.
(and of course, most times I do not start sub-projects at all, I just jump into a burning place and try to do my best to fix it��� not always very successfully :P)
so, coming back to less ���philosophical��� question:
1) do we need a state-of-the-art source code management? YES.
2) do we want to spend the few manpower we have on running into a worst solution of what is already around? I think no.
Esteban