1. At some point, the app will be covered with tonloads of ads to the point of impossibility to use
2. The core functionality will be hid behind sign-up/sign-in walls. The email addresses will be collected and then spammed to the brim
3. To add an insult to the injury, the app features will be gradually crippled unless you switch to a "Pro" plan. But you will not be able to do that efficiently as a user because you will be constantly attacked, bombarded and poisoned by ad banners and popups everywhere
4. Then, the app will start to upsell other offerings (of course, with modal banners!)
Those are cynical observations but they are 99% precise. I wish you good luck if you are among 1% elite.
I'm a bootstrapped software developer myself, so I can't decide if I should admire this or flag this as spam. But you're probably right, we're getting a "pricing" page very soon.
The main issues with other libraries is that they're either:
(a) ugly (b) difficult to use (i.e. having to do things imperatively) (c) not flexible enough
Apache ECharts solve these 3 problems. It's pretty by default, it allows us to mount/calculate the declarative spec for the graphs in the back-end and then only send the desired spec to the front-end so it can render, and it's also extremely flexible to the point we can support everything that traditional BI tools can do.
We've never had to extend the lib to do anything new, everything we need is already there.
Glad to see this great piece of work on top of HN.
* Echarts is about the only dependency in our project that I can upgrade - and be sure it never breaks anything. It is so well-thought in that regard. Upgrading for 3.x to 5.x? Sure! "npm update" and everything just keeps working smoothly. That is so refreshing to see these days. Unbelievable.
* It's both SSR-friendly and SPA-friendly. Being mostly vanilla-js, works seamlessly with both react/vue/apline AND with old-school rails/asp.net/php/whatever. Our app is pretty classic SSR (https://www.jitbit.com/) and I can construct my chart's JSON object on a server using some linq-queries and provide that to echarts.
* ...OR I can give it a reactive object from vue-based SPA. Dun matter, it just works.
* whenever we have to add some workarounds (like, showing hovering labels on a pie chart with a bold percentages or something) - I never have to dig into their sources. Almost anything has already been figured out. Easily googlable and "LLM-able".
AWS is $220 (us-east, r6a.2xlarge instance, 1yr reserved)
For context: last month they banned Cursor and all other forks from using C++, C# Dev Kit, Python and other extensions. Guess this was preparation for this move.