Looks great! +1 for using JSX as a backend templating layer.

We played a bit with Kita too and its great

Heck. 3yrs is quite long. Ill drop anything that doesn't allow me to ship daily

You must be its creator (Harminder Virk) because this is the type of responses (much worse ones, to be accurate) you were used to provide for anyone who asks you about something.

That was sarcasm on your original comment that you have edited 3 times.

Anyways, don't take it seriously and have fun

If you check my Github profile, you will see I still have on my list of starred repositories several of yours. I also still have at least 2 articles on my blog related to AdonisJs. I hope you understand what I mean.

We came 10yrs ago

Hell yes. Maintaining this framework for 10years and only recently we have started getting attention because of all this Laravel vs JS drama!

Fair criticism of the JS ecosystem. Things are always changing.

Btw, its hard to compare two ecosystems with a checklist. For example, Rails doesn't have inbuilt support for Auth, Authorization or Model factories and you rely on community solutions for those.

Similarly AdonisJS is missing some core integrations like queues and you have to rely on community solutions

Yes, this is why I think Laravel is superior to Rails in terms of out of the box functionalities, but I digress.

In the short term, it's fine to use community solutions, but over time, Adonis should bring those things in-house. They also need to find a proper way to monetize the framework so that the core team has the incentive to stick around for a few years to build something truly great. I think this has been the biggest issue with JS world, very few people can and will stick to working on something for long periods of time to make it really good.

The Laravel team figured out the monetization by building out pro-level tools in their ecosystem that people are willing to pay for.

Too much misinformation

- Locks you to their own Validator. Nope, Run npm install Zod and you have it working

- Their own Response/Request classes. Isn't it same with Fastify, Express and other frameworks?

- Annotations, Aren't they part of JavaScript?

That's why I don't recommend Fastify or Express. Remix and Hono use standard Req/Res

Annotations are not part of Js, they are part of Ts and are a concession to OOP people coming from other languages. It's a personal opinion but I don't like them and I enjoy this opinion is not uncommon because only few libs are riddled with them.

Yeah being subjetive is fine. We all have tastes and preferences and that's why there are so many frameworks and ecosystems.

Going to nitpick a little here

Hono docs language says, they wrap the standard Request object that you can access via HonoRequest.raw https://github.com/honojs/hono/blob/main/src/request.ts#L26

Annotations/Decorators are in stage3 of JavaScript. But I agree they are not super common in JS world except TS heavy libs or frameworks. Btw we aren't big fan of them and use them sparsely in models and commands only

ORM, Auth, Session and templates are first party packages and maintained by the core team.