This is brilliantly done. You have a bright future ahead.
A few suggestions:
1. You could add anonymous(but verified) tutor ratings.
This will enable children to find better tutors while tutors are encouraged to perform better to increase their ratings.
2. I think it's more user-friendly if you open internal pages within the same tab (e.g. the open section opened a new tab).
3. Also, I could think of many revenue models.
Example: Commission on tuition fees (better to do once you're established), Premium accounts for tutors to host learning materials, On-Demand tuition classes, private sessions, etc.
This is a cool project somebee. Interested to explore more.
On benchmarking:
I went through the same concerns and ended up building a little benchmarking tool for a simple reactive UI library I'm working on. It's not super user-friendly yet but doing a good job of profiling tasks.
You can write custom benchmarks by clearly separating pre-setup work than relying on ready-made benchmarks (a bit of a pain initially, but helps a lot to fine-tune at unit-level going forward).
It uses Chrome DevTools Protocol(CDP) through Puppeteer and allows to analyze execution durations separately (Scripting, Layout, Paint, etc). Plus, it saves raw JSON profiling data, so you could import & examine it visually on DevTools Performance Tab's Timeline.
1. _ kind of hide itself & give more prominence to the rest of the code (logic)
2. If we pick a long name like CalDOM, it becomes a PITA when it repeats so many times.
3. Not to be conflicted with jQuery by using $
Yeah, Lit is cool & futuristic. However, it's built for ES2019. It requires some effort to make it compatible with previous browsers: https://lit.dev/docs/tools/requirements/
In my opinion, this is the future. Especially, Native Web Components will take over in this decade. CalDOM's long-term plan is to seamlessly merge with native web components when it's widely supported.
Exactly, and state changes are batched behind requestAnimationFrame :)
Also, there's .react(new_state), which is synchronous.
If one prefer not to use Proxies (old browsers, etc), it can be disabled via .react( state, { ..., watched: false } ) and then can call just .react() manually after state changes. Which is also batched(async).
I honestly don’t know where this will lead. Probably all of this is just for nothing. The world has enough UI libraries already. Duh!.
I decided to make my own mini jQuery years ago because I wanted a lightweight library. Also, I wanted to stay close to the native DOM API & vanilla JavaScript. Looking back, it paid really well. Then React & Vue JS happened.
In my opinion, the reactive UI approach bought a huge productivity improvement from the perspective of the developer. Also, it enabled a lot of beginner developers to navigate the programming landscape more easily.
However, this shift also moved people away from the core stuff that’s happening under the hood. As a result, sometimes we have to struggle a lot to find solutions within the library’s limits, which are sometimes hilariously dead simple & performant to implement with native APIs.
CalDOM tries to solve this by being 100% interoperable with the native DOM. I hope this will be helpful for developers with similar requirements.
Introducing CalDOM, an agnostic, reactive & minimalist (3kb) JavaScript UI library with direct access to native DOM.
Instead of pulling you into a library-specific magical world, CalDOM let you fully access the DOM directly while keeping the reactivity. A 2-in-1 virtual-DOM & no-virtual-DOM approach if you will.
So you could take full advantage of native APIs & mix it with other libraries to gain superior performance & flexibility in the development process.
CalDOM does not require any dependency or tooling. It does not introduce any new syntax. Just pure JS.
This is the first time I’m publishing something like this. This was a simple jQuery alternative I made myself years ago & kept on improving it slowly. Worked really hard during the last few months to add reactivity and get it to this level.
Please check it out & let me know what you think, the good, bad & your suggestions to improve it.
This is brilliantly done. You have a bright future ahead.
A few suggestions:
1. You could add anonymous(but verified) tutor ratings. This will enable children to find better tutors while tutors are encouraged to perform better to increase their ratings.
2. I think it's more user-friendly if you open internal pages within the same tab (e.g. the open section opened a new tab).
3. Also, I could think of many revenue models. Example: Commission on tuition fees (better to do once you're established), Premium accounts for tutors to host learning materials, On-Demand tuition classes, private sessions, etc.
Again, really well done. I wish you all the best!
Cheers!