js-framework-benchmark
js-framework-benchmark copied to clipboard
krausest
Archive inactive frameworks
According to the deprecation policy I'd like to archive some inactive frameworks. Archived frameworks will appear in the history section in the README with a link to the last result table they were included it. The cleanup allows adding new implementations while keeping the benchmark duration bearable.
I'm informing the contributors in this issue. Please let me know if there are good reasons to keep the implementation.
The following candidates appear to have litte activity in the last year. Is it OK to archive them?
- [ ] vuerx-jsx @ryansolid
- [ ] ko-jsx @ryansolid
- [ ] mobx-jsx @ryansolid
- [x] uhydro @Krutsch: done
- [x] domdiff @WebReflection (I know feels like groundhog day, but maybe it turns out differently a year later): done
- [x] neverland @WebReflection: done
- [x] lighterhtml @WebReflection: done
- [x] heresy @WebReflection: done
- [x] hullo @arturkulig done
- [x] resonatejs @CodeMonkeyAlpha: done
- [x] etch (repo is readonly): done
- ~~s2 @gr0uch~~
- ~~redom @pakastin~~
- [x] endorphin @sergeche: done
- [x] sifrr @aadityataparia: done
- [x] 1more @Freak613: done
- ~~doohtml @hman61~~
- [x] sledgehammer (repo is readonly): done
- [x] domvm: done
- [x] fullweb-helpers (repo is readonly): done
- [x] fullweb-template (repo is readonly): done
(legend: checked = will be archived, strike through = will be kept) Non-keyed will follow...
you can also archive domvm, both keyed and non-keyed. i dont actively maintain it and dont really plan to. ivi does what domvm set out to do, but does it better (much faster, smaller, typed, etc.)
no time or motivation these days to maintain libs that i dont consider to be best-in-class.
RE:DOM is actively used in all my projects and others as well, it's just so minimalistic there's not constant need to push updates. I'd still hope you would keep it, i'm going to update at least the packaging/building part soon.
Hi Stefan,
Hope you are well. Yes feel free to remove resonatejs if it is creating unnecessary work / noise. I have made a number of updates to it but haven’t published them, and frankly don’t have the time at the moment as it would require work on the documentation. It was designed specifically for one project / team. I wasn’t really under the illusion anyone but me and a few friends would be using it commercially.
It was nice to see that it stacked up reasonably well against other complete frameworks.
Thanks
Terra
From: Stefan Krause @.> Sent: Sunday, October 15, 2023 9:07 PM To: krausest/js-framework-benchmark @.> Cc: CodeMonkeyAlpha @.>; Mention @.> Subject: [krausest/js-framework-benchmark] Archive inactive frameworks (Issue #1421)
According to the deprecation policy https://github.com/krausest/js-framework-benchmark/blob/master/README.md#history I'd like to archive some inactive frameworks. Archived frameworks will appear in the history section in the README with a link to the last result table they were included it. The cleanup allows adding new implementations while keeping the benchmark duration bearable.
I'm informing the contributors in this issue. Please let me know if there are good reasons to keep the implementation.
The following candidates appear to have litte activity in the last year. Is it OK to archive them?
- [ ] vuerx-jsx @ryansolid https://github.com/ryansolid
- [ ] ko-jsx @ryansolid https://github.com/ryansolid
- [ ] mobx-jsx @ryansolid https://github.com/ryansolid
- [ ] uhydro @Krutsch https://github.com/Krutsch
- [ ] domdiff @WebReflection https://github.com/WebReflection (I know feels like groundhog day, but maybe it turns out differently a year later)
- [ ] neverland @WebReflection https://github.com/WebReflection
- [ ] lighterhtml @WebReflection https://github.com/WebReflection
- [ ] heresy @WebReflection https://github.com/WebReflection
- [ ] hullo @arturkulig https://github.com/arturkulig
- [ ] resonatejs @CodeMonkeyAlpha https://github.com/CodeMonkeyAlpha .
- [ ] etch (repo is readonly)
- [ ] s2 @gr0uch https://github.com/gr0uch
- [ ] redom @pakastin https://github.com/pakastin
- [ ] endorphin @sergeche https://github.com/sergeche
- [ ] sifrr @aadityataparia https://github.com/aadityataparia
- [ ] 1more @Freak613 https://github.com/Freak613
- [ ] doohtml @hman61 https://github.com/hman61
- [ ] sledgehammer (repo is readonly)
Non-keyed will follow...
— Reply to this email directly, view it on GitHub https://github.com/krausest/js-framework-benchmark/issues/1421 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3WKTGAERV4D3NGO63HTWTX7Q66HAVCNFSM6AAAAAA6BHKBYSVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2DIMBTHA4TEMQ . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AE3WKTAZOGUAB5PNOOOPJBDX7Q66HA5CNFSM6AAAAAA6BHKBYSWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHHHX5OBI.gif Message ID: @.*** @.***> >
You can archive endorphin framework, working on a new version right now (maybe with different name), will add it via PR
Please DON'T remove doohtml or doohtml-dom, I'm planning a minor update in the next 2 weeks.
- Henrik
On Sun, Oct 15, 2023 at 1:06 PM Stefan Krause @.***> wrote:
According to the deprecation policy https://github.com/krausest/js-framework-benchmark/blob/master/README.md#history I'd like to archive some inactive frameworks. Archived frameworks will appear in the history section in the README with a link to the last result table they were included it. The cleanup allows adding new implementations while keeping the benchmark duration bearable.
I'm informing the contributors in this issue. Please let me know if there are good reasons to keep the implementation.
The following candidates appear to have litte activity in the last year. Is it OK to archive them?
- vuerx-jsx @ryansolid https://github.com/ryansolid
- ko-jsx @ryansolid https://github.com/ryansolid
- mobx-jsx @ryansolid https://github.com/ryansolid
- uhydro @Krutsch https://github.com/Krutsch
- domdiff @WebReflection https://github.com/WebReflection (I know feels like groundhog day, but maybe it turns out differently a year later)
- neverland @WebReflection https://github.com/WebReflection
- lighterhtml @WebReflection https://github.com/WebReflection
- heresy @WebReflection https://github.com/WebReflection
- hullo @arturkulig https://github.com/arturkulig
- resonatejs @CodeMonkeyAlpha https://github.com/CodeMonkeyAlpha.
- etch (repo is readonly)
- s2 @gr0uch https://github.com/gr0uch
- redom @pakastin https://github.com/pakastin
- endorphin @sergeche https://github.com/sergeche
- sifrr @aadityataparia https://github.com/aadityataparia
- 1more @Freak613 https://github.com/Freak613
- doohtml @hman61 https://github.com/hman61
- sledgehammer (repo is readonly)
Non-keyed will follow...
— Reply to this email directly, view it on GitHub https://github.com/krausest/js-framework-benchmark/issues/1421, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUCUQKFYP5MZQ5EV2Q26VDX7Q66FAVCNFSM6AAAAAA6BHKBYSVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2DIMBTHA4TEMQ . You are receiving this because you were mentioned.Message ID: @.***>
s2 is being actively maintained and used in production. i may have forgot to link back to the repo from here.
I’m OK if you remove the libraries you’ve mentioned as I’m not working much on these 👍
Ping @arturkulig: Can we archive hullo?
Yes, that's what I understood was about to happen previously.
Last ping for @ryansolid to stop me from removing ko-jsx, vuerx-jsx, mobx-jsx.
can vuerx-jsx (no-virtual-dom POC) maybe stay till we (hopefully soon) can replace it with https://github.com/vuejs/core-vapor (official no-virtual-dom in the making) ?
