react-jsonschema-form VS Kong

I've been very passionate about a project called react-jsonschema-form (github, editor). I personally hate writing forms, and love the idea of serializable components, schema, validation all in one. I've always wanted an alternative to this project that offered an alternative to react, and possibly the ability to render a schema form to static HTML (like ssg).

See their playground app for examples of creating schema driven forms in no time.

I've tried with https://github.com/rjsf-team/react-jsonschema-form ,but the performance is poor when dealing with deep nested form with many inputs.

For example, I had a requirement for my team recently to be able to build dynamic form UIs, based off a JSON schema. There are heaps of javscript frameworks for this task e.g. react-jsonschema-form, but nothing in nuget or Blazor is going to help there. So you'd have to write all the logic yourself.

React-json-schema form has plenty of tests, using... it looks like react-dom/test-utils

https://github.com/rjsf-team/react-jsonschema-form

YAML-LD (application/ld+yaml) round-trips to JSON-LD (application/ld+json) which round trips to RDF; so W3C Linked Data Signatures / W3C Verified Claims cryptographic signatures verify regardless of graph representation.

YAML-LD > 3.1 JSON vs YAML comparison: https://json-ld.github.io/yaml-ld/spec/#json-vs-yaml

React Json Schema Form: https://github.com/rjsf-team/react-jsonschema-form

The most popular package it is being used in currently is react-jsonschema-form, which currently has 11,876 stars on GitHub

When I used react I used react-jsonschema-form which was awesome. Instead of writing inputs and forms I wrote the shape of that form in schema (or better yet, had my server send the shape of the form from the endpoint so that the front end required no coding). Unfortunately the vue equivalents never got ported to vue3 (and seem abandoned), so I wrote my own. Now I write stuff like:

Kong: A cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway or API Middleware). Made available as an open-source project in 2015, its core functionality is written in Lua and it runs on the nginx web server.

OPeNsOuRcE. Good time to switch to Kong, better option anyways.

Sounds like you want an API gateway? What about Kong?

Unquestionably no, Kong is "OpenResty plus a management plane" and they're Apache 2: https://github.com/kong/kong#license

Kong (https://konghq.com) | Gateway Senior Engineer | REMOTE Europe | Full-time

The Kong Gateway is an API Management solution, which serves as a foundation for many other solutions by the company. The business model is open-core: an Open Source solution exists (https://github.com/kong/kong), and there's an Enterprise version with more features and dedicated support.

The tech stack is a modified Openresty with of Lua code on top. The ideal candidate would be someone who is already familiar with Kong. Alternatively, if you are familiar with Openresty or other API management solution, we also would love to talk with you.

I am personally interested in finding people to join me in the European Gateway Team. The role involves adding features, fixing bugs, and collaborating with other teams. Here's that position:

https://jobs.lever.co/kong/c1a2b204-45a8-4c19-9cd4-d9824a778...

We have many projects and many teams all around the world (current headcount is ~450), using other technologies like Node in the Kong Manager or Go in the Koko project, and we are constantly looking for people. Please visit our careers page to find out more!

https://konghq.com/careers/

Kong Gateway allows the complexity of service-tier APIs to be reduced to a collection of endpoints (or URIs) focused on meeting a collection of business needs and functionality. Often-duplicated components (like authentication, logging, and security) are handled by the gateway and can be removed from the service-tier design.

I am seeing different companies taking different approach. I am not sure anymore where each should be actually used. On top of that tech like Kong make me question whether API Gateway should be one thing for all. Some perspective into this would be really appreciated.