Yes, replaced few rich and reasonably complex UI components in admin interface that were previously developed in Adobe Flash (developed in the times when html wasn't as expressive for more visual/interactive UIs). The end users did not notice any difference.
The language is pure joy to work with. No issues with "deeply nested components", just use a function to render a "component", add data needed for the rendering as a function parameter, handle the events emitted from the "component" in the update-function.
Ignore the vacation, hobbies and meditation nonsense mentioned here. You need to attack the core of your problems.
You need to delegate, but before that, I think you need to think through your company's structure and have a clear separation of roles and responsibilities. You are saying you are the ceo but also do engineering in a ~20 person mostly dev-oriented team, that all might point to badly defined roles/responsibilities.
There are classically 5 roles in every company (some companies might have less, some more) -
1. the visionary (the person who has the crazy ideas and looks more into the future)
2. the integrator (CEO)
3. head of operations (the product/service you are developing and/or running)
4. head of admin/finance
5. head of sales/marketing
Each of those roles should be filled with one person. That person is also the single one to be responsible for performing in that role in that area. All the other roles should not micromanage the other role's responsibility areas. The role of the ceo is to work on the company systems and see that all of the "heads" are ticking ok (kpi-s are met, tasks have been done, etc) and communication is in place. Smaller companies can also assign multiple roles to a single person.
If that kind of structure is in place, it is much easier to delegate.
No. Basic bookkeeping. Equity = Assets - Liabilities. Assets can be "cash in a bank account", tangible stuff you buy to your company, intangible things (product you are building, ip, patents, etc). The "below 2500" rule kicks in as a safeguard when your equity (assets-liabilities) have dropped below 2500, to avoid approaching 0 "soon".
1. There is EveryPay https://every-pay.com/ . You need to open an account in the LHV bank first before receiving payments. (disclaimer: me and our dev team built their tech platform)
2. All the EU data laws apply.
3. I guess it depends on how you specify it in your contracts, you could do the disputes/arbitration wherever you want. There is an overview of dispute options here: https://www.eesti.ee/en/entrepreneur/legal-aid/resolution-of... . For example, if you have a customer not paying their invoices that are below 6400 euro you could file an a request in E-toimik/E-file (a paperless court system) and the collection is automatic. You could also sue people "online" there. (disclaimer again, I lead the software architecture/development work on the E-file project.)
The language is pure joy to work with. No issues with "deeply nested components", just use a function to render a "component", add data needed for the rendering as a function parameter, handle the events emitted from the "component" in the update-function.