Ask HN: Help me pick a front-end framework
&gt; I&#x27;m thinking of building a text-annotation based app _alone in my spare time_. The core usage loop is about viewing and interacting with &quot;visual markup&quot; applied to a body of text. So lots of tooltips&#x2F;hoverbars I guess.<p>Can you elaborate a bit more on this part, please? Or show us a mockup... doesn&#x27;t have to be anything fancy, just like a pen and paper sketch or a simple Figma.<p>I&#x27;m asking because it kinda sounds like you&#x27;re wanting to do something like an online IDE or Google Docs, where you&#x27;re manipulating a body of text in the style of a rich text editor. If that&#x27;s the case, it&#x27;s possible the HTML DOM model isn&#x27;t quite the right fit for you... you may find it better to abstract over a Canvas or WebGL object instead of trying to shoehorn that experience into the raw DOM. That way you have full control over rendering, outside of the normal layout&#x2F;styling&#x2F;rendering loop. It might also make a good case for a single-page app (at least the majority of the editor itself would be, and the other stuff -- marketing, blog, etc. -- can be routed to individual pages).<p>In that case, it wouldn&#x27;t be so much a question of &quot;framework&quot; in the sense of React, Vue, etc., which traditionally work on the DOM. It might be more a question of &quot;engine&quot;, like whether to use something like PixiJS to manipulate the graphics layer vs rolling your own. State management can be done with something like Redux (even without React), or if you choose to use a frontend framework for the rest of it, you can maybe use their state solution with your rendering engine.<p>In addition to choosing a low-level graphics lib, you can also look at some existing rich text markup solutions. A CMS I used had a good blog post on this: <a href="https:&#x2F;&#x2F;www.datocms.com&#x2F;docs&#x2F;structured-text&#x2F;dast" rel="nofollow">https:&#x2F;&#x2F;www.datocms.com&#x2F;docs&#x2F;structured-text&#x2F;dast</a> (especially the parts of about &quot;abstract syntax trees&quot;), along with their open-source editor: <a href="https:&#x2F;&#x2F;github.com&#x2F;datocms&#x2F;structured-text" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;datocms&#x2F;structured-text</a><p>That&#x27;s one possible to way to deal with complex annotated text.<p>A more widespread one is the toast UI editor: <a href="https:&#x2F;&#x2F;ui.toast.com&#x2F;tui-editor" rel="nofollow">https:&#x2F;&#x2F;ui.toast.com&#x2F;tui-editor</a><p>I know you&#x27;re not just working in Markdown, but these give you an idea of what it&#x27;s like to work with complex text trees in JS.<p>Once you have the actual text editor part figured out, choosing the wrapper around it (again, just for marketing pages, etc.) is relatively trivial compared to the difficulty of your editor app. I really like Next.js myself (if you choose React), but I don&#x27;t think you could really go wrong with any of the major choices today... React&#x2F;Vue&#x2F;Svelte&#x2F;etc. And it looks to me like the complexity of your site wouldn&#x27;t really be around that anyway, but the editor portion.<p>Lastly: I don&#x27;t think ANY JS tool or package is going to be maintained in 10 years. Frankly, 2 years is a long time in the JS ecosystem :( I&#x27;m not defending this phenomenon, I hate it too, but that&#x27;s the reality of it. If long-term maintenance is a goal of yours, you might want to consider writing abstraction layers over third-party tools you use, so you can easily swap them out when future things come out (because they will). The web itself is changing too fast for libraries to keep up; instead, people just write new ones every few years. An example of this is the pathway from the Canvas to WebGL to workers to WASM (and how to juggle heavy computational vs rendering loops around)... a lot of the old Canvas-based renderers, which were super powerful in their time, are now too slow vs the modern alternatives. Nobody is going to port the old stuff over, they just make new libs. It&#x27;s likely that trend will continue in the JS world (that whatever you write today will be obsoleted by a new web API in a few years).<p>Lastly, as an aside, TypeScript is a superset of JS... if you find a JS project&#x2F;lib&#x2F;plugin that you want to use, there will often be types for it made by the community (<a href="https:&#x2F;&#x2F;github.com&#x2F;DefinitelyTyped&#x2F;DefinitelyTyped" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;DefinitelyTyped&#x2F;DefinitelyTyped</a>) , or you can write your own types for it. I don&#x27;t really have an opinion about TypeScript vs writing in some other language and compiling to JS, but it would probably be easier to find help (especially frontend) in the future if you stick with TypeScript instead of convoluting your stack with multiple languages. Sounds like most of your app will be clientside anyway with limited backend needs.<p>---------<p>Tech aside... have you considered partnering with a frontend dev for this? I know you said &quot;alone&quot;, but just having someone set up the basic skeleton of such an app with you for the first month or two could be super helpful. Or a UX person to help you with some of the interactions before you start serious coding. They don&#x27;t have to be with you the whole journey, but maybe they can help jumpstart your project so you can then work on adding features &amp; polish in your spare time, instead of figuring out basic architecture? Unless, of course, that&#x27;s the part you actually enjoy. In that case, don&#x27;t let anyone rob of you that :)<p>Have fun! Sounds like a cool project.