Lack of vite/webpack/... FE integration is a huge breaker.
How? It claims to support InertiaJS.
AdonisJS
41–50 of 69 posts
Re: AdonisJS
#42Earlier quoted context omitted.
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
Re: AdonisJS
#43No mention of Views? The one thing I'd love to understand and is missing vs. Rails/Laraval is an integrated solution of solving the View part of MVC I think? Looks like a really beautiful framework. EDIT: Nevermind, it's in the docs, just not on the main landing page so feels a little more secondary. TLDR they recommend you use Edge/Pug/Nunjucks, htmx, vite for css bundling. Nice! https://docs.adonisjs.com/guides/vie…
An official mention of Pug? Now, they got me listening. Maybe it's because it's (mostly) markup, but Pug is the only whitespace language that I really gel with. I wish it had more support across the board! Maybe it's the years of Emmet use that's got me biased. I remember getting excited about both of these before they each changed names.
I never saw the appeal of Pug, it's hideous and completely unreadable for me. I can't easily tell where code starts and ends
Re: AdonisJS
#44Anyone else see these types of announcement posts, and it's like they already have thousands of users? Where do y'all learn about these projects so early?
Right here on Hacker News, actually. https://news.ycombinator.com/item?id=16509058
Re: AdonisJS
#45Nah, if you want heavy backend, go with Go/Ktor/C#, not node. If you want light backend, use sth like Hono or H3. If you want to primarily produce html, use Remix or Next. Adonis/Redwood/Nest is something you will regret in few years because it will lock you down to "their" ways of doing things instead of something with replaceable components. Admitted, Adonis looks most sensible out of these 3. Redwood is poisoned w…
i mostly agree with your take, except that if you primarily want to produce html going with a server-side rendered approach might be simpler.
i'm building https://www.plainweb.dev/, which uses htmx + react style components for templating.
Re: AdonisJS
#46Nah, if you want heavy backend, go with Go/Ktor/C#, not node. If you want light backend, use sth like Hono or H3. If you want to primarily produce html, use Remix or Next. Adonis/Redwood/Nest is something you will regret in few years because it will lock you down to "their" ways of doing things instead of something with replaceable components. Admitted, Adonis looks most sensible out of these 3. Redwood is poisoned w…
i mostly agree with your take, except that if you primarily want to produce html going with a server-side rendered approach might be simpler. i'm building https://www.plainweb.dev/ , which uses htmx + react style components for templating.
Looks great! +1 for using JSX as a backend templating layer.
We played a bit with Kita too and its great
Re: AdonisJS
#47Earlier quoted context omitted.
Locking things in is not an issue if things are well built and well maintained. Having used Laravel, I'm amazed at their DX. First party libs all built by the same team, tools also built by the same team. Everything is congruent and just flows. Compare that to the wild west that is Javascript land. Multiple libraries that all do the same thing in different ways. Stuff being deprecated or completely changed. Sure, if…
PHP world is different. There's only Laravel and Symfony. You can't count on both surviving till atomic winter. As you say, js world is fickle and I wouldn't count on Adonis being here for a long time. Mix and match is more pragmatic in this setting.
Lol, Symfony was released in 2005 and Laravel in 2011. PHP is much older. They've been around for long time and will stick around for many winters.
Re: AdonisJS
#48Earlier quoted context omitted.
An official mention of Pug? Now, they got me listening. Maybe it's because it's (mostly) markup, but Pug is the only whitespace language that I really gel with. I wish it had more support across the board! Maybe it's the years of Emmet use that's got me biased. I remember getting excited about both of these before they each changed names.
I never saw the appeal of Pug, it's hideous and completely unreadable for me. I can't easily tell where code starts and ends
I absolutely understand. For me it's the _only_ exception to this feeling. Probably something to do with it not being a programming language, and my own preference for as little nested elements as possible, though I can imagine how anything close to div soup would be completely untenable.
Re: AdonisJS
#49Earlier quoted context omitted.
I looked at AdonisJS, but it has soo many things missing that I'd rather just go with Laravel or Rails. Both of those have been around for so long and have an amazing ecosystem (especially Laravel) and are battle tested. I've also just lost my trust in JS for any serious long term projects. Things work at first and then a year later all the underlying dependencies have changed and stuff stops working.
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.
Re: AdonisJS
#50I never understood why you need more than a simple expressjs server. After all nodejs works best if served directly after a load balancer. But before heavy duty application logic. Node is fast in accepting, forwarding and replying requests. Put your real work in small c# or golang apps.
Curious, why do you say Node.js works best served directly after a load balancer? Genuinely just wondering, never heard this before.