jaysylvester

5 ms·

1.
by jaysylvester 2y ago
Just wanted to thank everyone for helping citizen get its first 100 stars on Github. Looking forward to your feedback.
2.
by jaysylvester 2y ago
I used to fall into the trap of always wanting to build everything myself, which ironically led to me building a framework so I wouldn't have to do that over and over. So I agree totally. Every "framework" available when I st
3.
by jaysylvester 2y ago
I think the first request isn't all that bad. Something like: 1. Transpile .ts modules to .js on app startup (development mode only) 2. Import .js modules into citizen as it does today 3. Watch for updates to .ts files and transpile to
4.
by jaysylvester 2y ago
In reviewing the Adonis docs, I think the biggest difference between citizen and Adonis is convention over configuration. citizen expects you to put certain things in certain places so it can handle all the imports, execution, and flow cont
5.
by jaysylvester 2y ago
Guess I should've posted it on HN much sooner. I shared it on social media years ago, but it never got much traction (I have few followers).
6.
by jaysylvester 2y ago
Question: would you expect it (or want it) to use a runner or a transpiler? Or does it not matter?
7.
by jaysylvester 2y ago
I don't know what's out there that's similar to citizen, honestly. I didn't set out to create competition for existing frameworks; I just built the stuff I found useful for my own projects and think it's finally at
8.
by jaysylvester 2y ago
As you've noted, citizen is clearly written to handle pretty much everything within the application server itself, which stems from my own particular use cases. I suppose that's my anti-pitch: citizen caters to apps that can run c
9.
by jaysylvester 2y ago
The scenario you described is exactly how I host my sites now (Debian on DO). I've seen numerous engineers advocate for letting the app crash (or at least gracefully shutting it down), capturing the error, and restarting. Errors crash
10.
by jaysylvester 2y ago
Thanks! "Fun" and "comfortable" haven't applied to web dev for a long time in my opinion, and my preference is to keep it as simple and enjoyable as possible.
11.
by jaysylvester 2y ago
It mostly means keeping routing/rendering/etc. on the server rather than client. My preference has always been to let the server render the initial request in full (feed the client an entire HTML document) and then update on the c
12.
by jaysylvester 2y ago
At least I stopped deploying site updates via FTP.
13.
by jaysylvester 2y ago
No tests yet, that's been on my list since the beginning and I now have the incentive to work on them: https://github.com/jaysylvester/citizen/issues/24 I don't use TypeScript myself, but based on w
14.
by jaysylvester 2y ago
That's a fair observation. I only include it because the Node way of doing things seems to be "just let the process crash and restart it", and that's been a tough concept for me to accept. I'm particularly proud of
15.
by jaysylvester 2y ago
Thank you! I try to be thorough. Getting to be a bit much for a readme though, probably deserves its own site.
16.
Show HN: Citizen – A Node.js web app framework for fans of classic app servers(github.com)
82 points by jaysylvester 2y ago|30 comments