To start my long answer, this is one of the best feedback I could have for someone believing in the project and proposing it internally: thank you!
While I know documentation and tutorials are what’s missing the most, and my whole campaign is about making them happen, I’d like to answer to all of your (their) questions, keeping in mind all the great hints you gave me already.
“How are we supposed to manage State? — there is no tool for that!”
You can use plain objects and remember to update after changes,
or simply use any state management library you can find on npm,
including those they are using right now.
“This is not scaleable! — that are not components. Because COMPONENTS are what makes your app scaleable!”
You can make components as a no-brainer.
There are various examples against any framework they want here.
“Is this available on NPM?”
Yes.
“How are we supposed to organize our source-files without [ name something ].”
There is a project, called create-viperhtml-app which gives you
the most basic structure and automation to create PWAs with SSR capabilities out of the box. It’s structured for you too.
“What about our build-tools we so eagerly installed and configured?”
Build-tools should be used to solve problems, not configured before having some 😂
“It is not backed by a known company… can that be STABLE?”
I’m not a known company myself but I’ve worked as full time employee at NOKIA, Facebook, and Twitter.
I’ve created libraries used in every browser of this planet, and on top of that,
my hyperHTML/viperHTML/HyperHTMLElement projects have 100% of code coverage, and that’s for every target browser, including IE9.
They should probably rather ask themselves how they are measuring the stability of their projects, when React has 600 opened issues while I keep my issues close to zero because there are none, and there are tests demonstrating such fact.
Currently, my projects are the only targeting 100% of test code coverage plus, like you’ve said, these are small and fully based on platform standards,
including runtime and tested feature detections that won’t lie in the wild.
So, what’s again their definition of STABLE? They should review it, IMO.
“MVC…? Seems like a bad idea to me… FACEBOOK does not use it also…”
hyperHTML has exact same React model, but it’s flexible enough to be adapted to any model you want.
You can create components as MVV, you can create MVC, you can create M only too and compose views a part.
Of course, you need to know what you are doing, and what these acronyms mean in the first place. Not sure I can solve hype around acronyms though.
“And what about our damn-f***ing [ BUZZWORDS HERE, PLEASE ]?”
They should solve problems instead of / before creating new for themselves.
