New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Your comparison of lines of code is unfair #27
Comments
You can click on the "pages" on the comparison area and they go directly to the correct code on GitHub. Seems the above snippet is from here: https://github.com/rgossiaux/svelte-headlessui/blob/v1.0.2/src/lib/utils/Render.svelte#L76 Seem the utils is referenced here on the main file: https://github.com/rgossiaux/svelte-headlessui/blob/v1.0.2/src/lib/components/listbox/Listbox.svelte#L81 |
I also suggest you change the title of this thread. It's not my intention to "lie" or post "frauds". I'm merely pointing out that there is an acute need for minimalism in today's frontend scene. |
Ok I will change the wording, but please agree that comparing tailwindcss homepage and yours is not a fair comparison. They don't have the same features at all! I'm merely pointing out that there is a toxic tendency to boast in today's frontend scene. Good job for all your work on this nevertheless, it's always good to see new ideas. |
I agree. I need to fix the narrative a bit. I guess the topic is more about mixing vs. separation of concerns rather than the lines of code on some places. And on places where the topic is LoC an accurate 1-on-1 comparison is needed, like Todo MVC for example. |
I improved the compare area a lot, please check: https://nuejs.org/compare/component.html The comparison is not about size anymore and the focus is on the coding style instead. FAQ on every page explains the details of each section. |
Seriously, who write this code written in your comparison page ?
Nobody would ever write this, whatever the framework.
Maybe that nuejs framework saves lines, but please provide acceptable code for a fair comparison!
The text was updated successfully, but these errors were encountered: