Hi Adam, hi all, Adam Kennedy wrote: > There are absolutely problems with the current task system slowing > down development. > > I would love to work on the directory tree, but I can't bring myself > to face the work needed to make it work on the current task system. > > The new task model should improve all kinds of things, and it should > make that programming actually feasible for ordinary humans (because > I've designed it specifically so you don't need to know threads to use > threads). So I would HOPE that finally making background tasks easily > will bring some people back again. > > I don't HAVE to break everything. But however, I WANT to break > everything, because I don't want to be using Padre::Task2 forever. > > I'd rather replace the current Padre::Task with a next-gen Padre::Task > and choose to break all the existing code.
I agree with this approach. Breaking things means that they'll be fixed sooner rather than later. Keeping both systems running just means that we postpone the breakage in an unhelpful way. But I was going to add another, minor note to the discussion. I don't think the v1 Task system is all that bad to work with (don't know about Services). I believe it held out well enough for prototype code that started as a learning experiment. It already hides most of the *hard* issues with concurrency. Don't get me wrong, I'm not being fussy about my hacks being replaced. Quite the contrary, I like the new system and API much better. It's a clear improvement and I'm a fan of Adam's code and engineering in general. I just want to move things in the right light for those following along without looking too closely. It's not as bad a transition as some others we went through. I believe, for example, Config 2.0 was a much bigger deal, despite the internals of the concurrency system being possibly more complex*. Best regards, Steffen * or at least having more strange edge cases and workarounds for evil Wx+perl+threads problems _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
