The only missing thing is a big sponsor. mozilla -> rust google -> go, kotlin ... n/a -> dlang

Yesterday I released version 0.7.17 of Serverino, my HTTP server written in D

Serverino is a small, fast, and dependency-free HTTP server implemented in D. A minimal app with serverino can handle on my laptop ~150k reqs/s and it uses just a few mb of ram.

https://github.com/trikko/serverino

Hi there. I'm the serverino's author.

Could you please explain better what's wrong with it?

It could be useful to improve newcomers experience.

How did you choose serverino over other frameworks?

Oh the issue isn't with serverino itself but with the lack of tooling-support for the language features that serverino makes heavy use of. And while serverino is open source, so one can ultimately view its source code, not having access to modern IDE type inspection adds a lot of unnecessary friction.

Still curious: How did you choose Serverino among the many servers?

Might seem silly, but the choice just came from looking at (https://code.dlang.org/search?q=websockets) and seeing that serverino is the only one maintained. vibe-d isn't listed there, I only learned about that later. Basically, serverino has good SEO.

Thanks, good to know. Also the fact that you searched directly on the site is a clue for me :)

How so, if I may ask?

Well, you might have searched for GitHub or got there from some page where serverino was mentioned (forum, ...) or maybe someone suggested it to you in the community. Once a program of mine was mentioned in a telegram channel and I started seeing a lot of stars on github and I didn't understand why.

Thanks man. Which os are you using?

Mostly using a macOS machine, and on some occasions Ubuntu Linux.

Are (abstract) unix sockets supported?

I'm trying to run a self-contained webserver executable without any external dependency. It starts but daemon <-> workers communication doesn't seem working (it is done via unix socket)

It works fine with bubblewrap or inside a scratch docker container.

aren't abstract sockets un-jailable unless using network namespaces?

or in the other direction, to truly prevent e.g. xorg socket from being accessed by a bubblejailed application, it should exclude --share-net, regardless if you bind the actual path to the socket (since abstract permeates beyond that)

Well, so should it work?

You're telling me there's another reason, then... Can't guess which one.

Hmmm...

they can be jailed by landlock, we don't have support in go-landlock tho afaik, @Gnoack

It's tracked in https://github.com/landlock-lsm/go-landlock/issues/35 - signals and abstract Unix sockets do unfortunately not interact well with the inherently multithreaded Go runtime. We are working on a fix in https://github.com/landlock-lsm/go-landlock/issues/36 but this needs to be on the kernel side and this is delaying this feature in Go, unfortunately. It is usable from (single threaded) C programs though.

Thanks!

I didn't explain myself well but load testing is not the point

I've just released it. Source on github: https://github.com/trikko/vasaro-web Try it : https://vasaro.art

Very intuitive. I haven't even watched the video before using it.

Thanks. Good to know!

I hope to see some vases created by someone with it :)

Just one thing, Is it possible to modify the vase "lip"?

I do not understand. What do you mean exactly?

this part: https://i.imgur.com/ab53RLa.png

ie, having the ability to make it less sharp,etc

I think I would left to postprocessing, just like infill.

It's quite easy to do with any modeler, I think.

Video: https://www.youtube.com/watch?v=RIVDdXV6D-A Source: https://github.com/trikko/BlobEditor

Waiting for a post entitled "unsuccesful one-person online businesses"

Next feature for website: organize plant by trap's type or insect they eat :)