Hacker News Reader

Comment by horusthegame | Hacker News Reader

We've been down this road before. It's neat but not for long term maintenance, support or training as soon as HTMX loses its luster and the, then manager, has to concede the whole thing has to be re-written from scratch.

View on HN

I've gone down this road before and that's not what I would criticize.

Where things went south for me:

- hard to hire developers that know how to work with this or that are willing to learn

- very hard to debug performance issues

- version control gets weird, since migrations are not really meant for functions and procedures (although Pyrseas[0] helped a lot)

[0] https://pyrseas.readthedocs.io/en/latest/

Is it possible to capture changes in git somehow? If not what did you do?

I smell a startup opportunity.

I think using Postgres as a runtime would feel like a PaaS runtime not much different from other offerings in the market. But, for something self-hosted, it feels like super powers in the beginning.

I've used git as usual to evolve my SQL functions and procedures and my CI/CD pipeline used Pyrseas to sync code with database.

I am starting to believe that "system has to be rewritten from scratch in the future" is not nearly the dealbreaker people make it out to be. Especially if it didn't take that much work building the v0 version.

You should almost always rewrite the system in the future, that's just the nature of growth and systems evolution.

https://wiki.c2.com/?PlanToThrowOneAway

So like nearly every JavaScript framework that comes along?

Reply on news.ycombinator.com