twovests

twovests OP wrote

But aren't there like, legal requirements jstpst has to meet? Like GDPR and stuff like that?

I don't suspect y'all of anything crummy, but if it's not a concern for us and if we've been running with dozens (hundreds?) of users for so long, I guess I'll be fine too.

3

twovests OP wrote

Oh I love these "weird JS behavior" talks and they're probably the reason I felt "Hmmm" in the first place about JS. (And the dependency issues you mentioned)

So while Javascript doesn't exactly make it hard to write good code, it makes it extremely easy to write incredibly awful code

This is an impactful takeaway

2

twovests OP wrote

For reference, this is a Jan 2019 Ycombinator post describing a go-to stack: https://news.ycombinator.com/item?id=18829557

TLDR:

  • Frontend: React with TypeScript
  • Backend: Django (Python) or Rails (Ruby)
  • Databases: Postgres
  • Serve using: Nginx, with cookies for authentication
  • Tooling: Use VS Code for Javascript, and something called json-server in npm for a quick REST API

(I understand REST is sort of a language describing APIs that can be imported into various web frameworks?)

This sounds like what I have in mind, but I know a lot of people have strong opinions and I like to hear them.

2