This is my first post, so hello ;)
I'm got jelaous that all cool applications on gemini, so I'm thinking about changing my gemini server from agate to gmid and make something interesting.
And I've a few questions:
Is gmid good idea or you are recommedning something else?
Im torn between FastCGI and good ol' CGI, FastCGI seems to have little support in Gemini. Does your server support FastCGI?
Even if your server support FastCGI, do you think it is good idea? Maybe it is not wort to sacriface support for more gemini serveris for uncertain performance gains.
2 years ago · 👍 krixano
also @aelspire good for you. Gemini is a fun place to play and experiment. Its big enough that you will constantly be surprised by what you find, but small enough (the protocol itself, the overall size of gemini-space, the complexity of clients) that there is lots of room to make something intersting that doesn't exist · 2 years ago
Thank for replies. I was pondering if using FastCGI will make any visible performance gain. If @acidus says it will not, I'm gonna trust them ;). Indeed CGI seems sufficient for any Gemini-scale application and FastCGI gains seems uncertain. And there is problem with managing something like thread-pool, which doesn't exist in CGI, so app using CGI will be much simpler to write. · 2 years ago
I use GMID and for me is excellent but I do not code so I can't say anything about CGI, FastCGI or SlowGCI... 🤷♂️ · 2 years ago
Agreed with @mfoo2. The main thing FastCGI gets you is avoiding the overhead and latency of spinning up and tearing down a process per incoming request. I run some fairly high traffic services all which use plain CGI. When I profiled them, the "creating a process/tearing down the process" part was not significant. Also, plain CGI has a bunch of advantages in terms of how simply development, testing, and deployment is. Considering starting with CGI and changing if needed · 2 years ago
why not start with CGI then switch when your Gemini application gets a thousand hits a day :) · 2 years ago