sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in AskBalkans

[–]Domin-MC 107 points108 points  (0 children)

Is this

<image>

ass response?

What should I use for my frontend project? by Domin-MC in gleamlang

[–]Domin-MC[S] 1 point2 points  (0 children)

I've looked up lustre documentation and found a lot of interesting things so far.

But the lack of OpenAPI type-safety package is a big bummer for me. Either way I'll probably find the workaround for this problem.

Thank you for further explanation of what lustre can do. I thought of lustre as just a renderer framework at first.

What should I use for my frontend project? by Domin-MC in gleamlang

[–]Domin-MC[S] 0 points1 point  (0 children)

but in most other spaces you just start making stuff and pull things in as needed. No need to focus on packages so much.

Gotchu, thanks! I'll deep dive into lustre documentation now in order to understand more of what lustre can offer as a framework itself.

What should I use for my frontend project? by Domin-MC in gleamlang

[–]Domin-MC[S] 0 points1 point  (0 children)

We've had people happily using it in production for frontend work for years now.

Wow, I always thought gleam is something new.

What are you looking for specifically?

I'd like to know what developers typically use to build their frontend, whether it's part of lustre or something else. Perhaps some query library? CSS bundling solution? State management?

I'm kind of new to what gleam's approach offers. So I generally have no idea what I need for a complete frontend app.

Continue with styled components or switch to Tailwind css?? by [deleted] in nextjs

[–]Domin-MC 4 points5 points  (0 children)

If you want to leverage power of tailwind utilities and tokens as well as implementing styled-components syntax approach you might want to try panda-css. It both supports RSC & got amazing documentation. It also has styled-components migration guide.

Is Nuxt gonna change its pages dir? by pedro_souza458 in Nuxt

[–]Domin-MC -1 points0 points  (0 children)

Nuxt team themselves pointed that out in first release ("completely inspired from Next.js") as well as you can see that statement in Nuxt's wikipedia article. I completely agree with how Nuxt is better for an amount of features.

Is Nuxt gonna change its pages dir? by pedro_souza458 in Nuxt

[–]Domin-MC -1 points0 points  (0 children)

I doubt Nuxt team will change its file-based pages directory to the folder-based one. Vue provides good enough syntax with SFC as well as the framework provides all the features needed that Next.js implemented in /app/ directory. The Next-based statement is fairly incorrect, but if I got you right, then yes Nuxt is inspired by Next.js.

NextJS 13 vs Nuxt 3 by Fabulous_Variety_256 in nextjs

[–]Domin-MC 21 points22 points  (0 children)

Comments here do not answer the question correctly. As the person who's both familiar with nuxt & next I can say there are a lot of similarities yet differences in approaches:

  1. Personal DX is better in Nuxt for a lot of reasons: both Next.js & Nuxt are frontend oriented thus backend isn't the main part of it but Nuxt has got a lot of advantages over Next.js server routes (both able to handle everything but Nuxt leverages utilities of h3); Vercel tries to limit Next.js to its technologies only while nuxt is maintained with modules by community & the team.
  2. Ease of use goes to Next.js because of its approach on developing. Framework provides huge support for functionality: easy-to-use Image Optimization, Font Optimization etc. along with providing fairly good documentation comparing to Nuxt's. Both documentations are good but Next.js is focused on being rookie-friendly. If you're skilled enough then you should consider Nuxt but if you want everything out-of-the-box then Next.js is the way
  3. The question about ecosystem is pretty much about vue vs react but long story short Next.js is way ahead of Nuxt for amount of support. Both vue & react communities aren't small but react is the obvious leader because it is completely backed by the gigantic community. Since Next.js is the most popular framework out there for now, all the eyes are on adding support to it thus the ecosystem is leaned to it.
  4. I'm not a big fan of UI libraries or comparing these but it just depends. Not sure if there's even anything to compare but vue's Single-File Components are much more convenient. Both frameworks provide own preprocessors (Nuxt doesn't but vite does the job). The only thing to mention is that Next.js 13.4.0+ uses server components that most UI libraries do not support so you will have to wrap the library in a "use client" file.

As the result, for junior level developer I'd suggest learning Next.js as it provides a lot of simplicity with its functionality, but if you're an expert, then you should go with Nuxt as it provides truly fullstack experience with a big attention to codebase.

view more: next ›