Open Hywan opened 6 years ago
First, I think we can deprecate all libraries that have no composer.json
file because it means they are not use by anyone in the PHP world basically. I explain why:
hoa/log
: We can't fight monolog, that is the king in this area. Also, no revolution to expect or to bring in this domain (for PHP I mean),hoa/memory
: This was an attempt for something, but it's not finished, safe to drop,hoa/model
: When Hoa tried to be a complete framework toolbox, never correctly designed, other libraries do a better job, this is not our confort zone anyway,hoa/notification
: Never finished. One day, maybe, but not today, not in a close future,hoa/prototype
: Should already be deprecated. It was a joke that PHP could has a prototype model just like Javascript.Second, I would like to deprecate libraries addressing a dead technology, like:
hoa/xmlrpc
: We all agree that XML-RPC is dead. People mostly use SOAP in the industry (its competitor), or JSON-RPC, or BSON, or ProtoBuf, or Message Pack, or…Third, libraries I'm not sure if it is relevant to keep:
hoa/worker
: This library is cool but nobody continues to use PHP for workers, am I wrong?hoa/tree
: This library is incomplete regarding features people would like to have, it is so basic right now that it is not interesting,hoa/translate
: The Gettext backend is great, but I'm not sure we will support more industrial standards in a close future + ext/intl
is far more rich and is almost native now,hoa/irc
: PHP is not async, so having a good IRC library to do bots & co. is difficult. I'm not sure. Also, there is no real IRC library for PHP after a quick search on Packagist. Maybe we have a card to play,hoa/cache
: I never needed it yet. Am I the only one?no composer => drop : OK
:+1: drop no-composer
hoa/worker
: has an interesting way to run different job and communicate with it.
Even if in the today world, message broker as rabbitMQ are preferred to schedule job. It can be still interesting in specific use case.These can be deprecated too? :
hoa/serialize
is nice, more like a joke, but I agree yes, we should deprecate it,hoa/xyl
must not be deprecated until W3 (Hoa's website) and hack books are using it. The plan for hack books is to replace them by Kitab. Once this is done, then we can move W3 to another template engine than XYL. But yes, I woud like to see XYL deprecated.I've updated the first comment with a new column to the table: “Agreed to deprecate”, just to keep track of the discussion.
hoa/heap ?
No, it's a new library, which explains the low number of downloads and stars.
Hello,
agreed if everyone here. ❓ hoa/worker: As it looks used by @grummfy and still in way of time maybe keep it for now. We will see for next evolution after ❓ hoa/tree: Can drop ❓ hoa/translate: Can drop ❓ hoa/irc: It's used by Marvirc what about this tool ? Do we remove it also ? ❓ hoa/cache: Can drop
What about
hoa/database: ? For me we can mark it as deprecated also
Precision: I don't use hoa/worker, I just say I do worker in php and use stuff like this in several jobs. I have no specific point about keeping it or not.
database can be drop for me
I would like to keep hoa/database
because some projects use it.
It's true that hoa/database
are bit simplistic but I'm fine to keep it, it has the advantage to be really light with a minimum overhead of Php native functions.
OK, let's deprecated :-).
hoa/cache
README.md
,hoa/log
README.md
,hoa/memory
README.md
,hoa/model
README.md
,hoa/notification
README.md
,hoa/prototype
README.md
,hoa/serialize
README.md
,hoa/translate
README.md
,hoa/tree
README.md
,hoa/xmlrpc
README.md
,Website has been updated accordingly, https://hoa-project.net/.
Thanks!
@vonglasow Could you update the mirrors please?
@shulard Should write a blog post about that?
@Hywan yes for sure.
Mirrors on Gitlab are archived, On Pikacloud, this functionality doesn't exist. I can only make it private or delete it. What would you prefer ?
@Hywan, yep I try to write that article before the end of the week 😉.
@vonglasow I think deletion is fine. @shulard :+1:!
All deprecated libraries are now deleted from the mirror pikacloud
I've created the article here : hoaproject/Blog#20.
Hello fellow Hoackers,
As discussed yesterday during the Hoa Virtual Meeting, and since several days now, we would like to deprecate some libraries that are either (i) un-used/unpopular, (ii) not relevant anymore because they refer to dead technologies. The goal is to reduce the maintenance, the effort of documentation, testing etc.
To decide what libraries to deprecate, we need data. Here they are:
composer.json
hoa/acl
hoa/bench
hoa/cache
hoa/cli
hoa/compiler
hoa/consistency
hoa/console
hoa/core
hoa/database
hoa/devtools
hoa/dispatcher
hoa/dns
hoa/event
hoa/eventsource
hoa/exception
hoa/fastcgi
hoa/file
hoa/graph
hoa/heap
hoa/http
hoa/irc
hoa/iterator
hoa/json
hoa/kitab
hoa/locale
hoa/log
hoa/mail
hoa/math
hoa/memory
hoa/mime
hoa/model
hoa/notification
hoa/option
hoa/praspel
hoa/promise
hoa/protocol
hoa/prototype
hoa/realdom
hoa/regex
hoa/registry
hoa/router
hoa/ruler
hoa/serialize
hoa/session
hoa/socket
hoa/stream
hoa/string
hoa/stringbuffer
hoa/test
hoa/translate
hoa/tree
hoa/ustring
hoa/view
hoa/visitor
hoa/websocket
hoa/worker
hoa/xml
hoa/xmlrpc
hoa/xyl
hoa/zformat
hoa/zombie
My next comment will propose some libraries to deprecate, and why.