transit-lang-cmp VS realworld

> The axum::debug_handler macro is invaluable to debug type errors (there's some with axum too), like for example, accidentally having a non-Send type slip in.

Heh, yeah. For my recent project where I explored implementing the same little app in a few different languages[0], I chose Axum for the rust version.

The whole "extractor" system was pretty magical, and when I had this exact issue (non-Send argument), the compiler error was totally useless. I did see the docs about adding this extra macro crate for error messages but it seemed like a bit of a red flag that the framework was going against the grain of the language. Still, on the whole, I did enjoy working with Axum.

[0] https://github.com/losvedir/transit-lang-cmp

This is great! Just pushed up a commit that uses it and updated the benchmarks[0]. I'm seeing a 1.6X - 2X improvement in overall performance. Not bad for a drop-in replacement. And since it's based on serde, I trust it, and I feel like trying out a different JSON library is within scope for me of not just "gaming the benchmarks", as this is actually something I'd now consider using at work.

It's not quite as high as I was seeing with `jiffy` (3,800 req/sec here vs 4,000+ with jiffy), but I'm not confident that was a totally fair comparison. `jiffy` doesn't integrate as nicely with Phoenix, so I was just calling `:jiffy.encode(...)` in the controller and then doing a `text(...)` response. I need to double-check if `json(...)` is doing more work here.

[0] https://github.com/losvedir/transit-lang-cmp/commit/140d693b...

Nowadays, I reached out for some benchmark results. Scala is slower than Java and Kotlin. Can you explain it? https://github.com/losvedir/transit-lang-cmp https://github.com/kostya/benchmarks

I had a chance to update the Go code (commit) to pre-allocate the arrays based on the known length before all the appends, and saw ~30% increase in performance, with top requests per second going from about 8,600 to 11,000.

I recently did a little project to compare several languages (https://github.com/losvedir/transit-lang-cmp) so I contributed to a bunch of those points!

In light of all this, it became exceedingly clear that someone else needed to step in and help. Why not me? Well, it can be me. And, after 3 months of development, I am happy to announce (again) dwayne/elm-conduit (demo), an open-source Elm SPA for RealWorld's Medium.com clone.

https://github.com/gothinkster/realworld

It's just for web app (a Todo app). Your GIS AND CLI ideas are interesting, I haven't seen anything similar to realworld for those.

View on GitHub

So what would be a better benchmark? Perhaps a "standard" "real world" app, like https://github.com/gothinkster/realworld

Or something simpler?

RealWorld example app is a full-stack application called "Conduit" that consists of a backend that serves JSON API and a frontend UI. There are numerous implementations for different languages and frameworks, but in this tutorial you will be using the Spring backend and the React frontend.

Github has millions of projects, some large fraction with more than 100 stars, so it doesn't seem like you are searching very hard. But more importantly, why "100 stars"? Stars are meaningless and arbitrary. Many developers use stars like bookmarks. I just did a quick search and noticed a project like realworld (just a demo for learning, 65 contributors) has have more stars than Bitcoin (900+ developers, perhaps you have heard of it?)

I feel you, context API sometimes overcomplicates everything. Let me introduce to you RealWorld. It is a great project that uses composition to make its structure scalable. It is actually a codebase that implements various fragments of a larger scale project such as Medium or Twitter. Check it out here: https://github.com/gothinkster/realworld. I hope this helps!