Why I wouldn't recommend Svelte JS to a fellow CTO

This page summarizes the projects mentioned and recommended in the original post on /r/sveltejs

SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
  • MDsveX

    A markdown preprocessor for Svelte.

  • not sure about your use case. but you either import your markdown files and convert them to svelte components yourself (with remark => json => svelte) or take a preproc like https://github.com/pngwn/MDsveX

  • carbon-components-svelte

    Svelte implementation of the Carbon Design System

  • Defining scaleable code disciplines is often a good place to start for solving these issues - except for the library ones. The funny thing is that i often find myself not needing libraries when programming in Svelte, because the available tools are often enough to solve our problems. I do feel that the Svelte echosystem is lacking when it comes to component-libraries - the best one I've found so far is the one from IBM. We used this as our main source when developing our own component library.

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
  • Svelte

    Cybernetically enhanced web apps

  • 2-way data binding and unpredictable reactivity: In my experience unpredictable reactivity always happens from poorly laid out logic. The very nature of pure reactivity makes it very hard for our brains to follow complex resolving (see this thread), most of the time (if not always) there is a simpler way to do it. A spaghetti reactive logic will have as many expected outputs as the number of programmers looking at it. A typical illustration of this is over use of dual bindings, setting the same value in several different places (sometimes on different events) and expecting something very specific to happen.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Svelte 4 Released

    4 projects | news.ycombinator.com | 22 Jun 2023
  • Observations about Svelte

    2 projects | dev.to | 23 Aug 2022
  • Securing SvelteKit Apps with Keycloak

    2 projects | dev.to | 6 May 2024
  • Mario meets Pareto: multi-objective optimization of Mario Kart builds

    2 projects | news.ycombinator.com | 4 Apr 2024
  • How I Contributed to Open-Source While Learning Svelte

    3 projects | dev.to | 21 Jan 2024