What is the criteria for chosing a framework vs implementing using language fundamentals?<p>I don't care about one over another, but I would prefer if all examples followed the same approach. It would make the comparison more valuable.
Would have been even more interesting to split the code in different folders (maybe only keeping the global Makefile) as it would have demonstrated the level of boilerplate / config / dependencies needed for what is basically the "hello world" of the web.
Hey, the author here.<p>Agree, I wasn’t consistent with “a framework” vs “just language” approach. Ideally it should be 100% one or another.<p>My idea was to use the standard library as much as possible, but I didn’t eliminate the use of third party libraries entirely if it would allow async/concurrent processing.<p>It all started with Go vs Rust vs Zig as the main point of comparison. Then I added more languages I am familiar with.<p>By far, IMHO, Go is a clear winner in terms of being 100% with the standard library, fully concurrent and quite concise.<p>Sure, JS/TS implementations are also concise but it is different, not natively compiled technology.<p>The language's selection is purely my personal familiarity, so nothing wrong with Java, it’s just not my area.
this thread is going to be dozens of replies of people overly defensive of their language producing the whole gamut of "the code in LANGUAGE_X is not optimal, it should use SOME_TECHNOLOGY instead"
i am surprised at how many languages look more like some kind of yaml configuration file rather than actual program.<p>also of note is to notice how many languages lack good support in standard library and therefore require much more code to be needed.