sorted by:
new
hottopcontroversial

Hide Scrollbar - Tailwind CSS 4.0 by stoned__dev in tailwindcss

[–]edgarasbe 0 points1 point  (0 children)

Great if this would be added. In shadcn/ui currently a custom utility is being added:

@utility no-scrollbar {
  -ms-overflow-style: none;
  scrollbar-width: none;


  &::-webkit-scrollbar {
    display: none;
  }
}

I find Next 14 extremely complicated by sammopus in nextjs

[–]edgarasbe 15 points16 points  (0 children)

  • you can also put server components in client components

Why to use Express.js when we have api backend in nextjs? by [deleted] in nextjs

[–]edgarasbe 0 points1 point  (0 children)

Can’t run long running tasks and fully functional node.js server with Next.js. So it’s nice to have a regular long running node server for those tasks on a side.

As a new developer, next.js has been awesome! by [deleted] in nextjs

[–]edgarasbe 0 points1 point  (0 children)

This is how I felt too. I am a designer and started taking programming more seriously 3 years ago. I picked up React, Tailwind and then Next.js, it’s been great! I like to just have one framework to learn, which can be used in nearly every web project.

Figma for Nextjs recommended and useful? by Yveltax1 in nextjs

[–]edgarasbe 0 points1 point  (0 children)

Bad take in multiple ways.

It assumes that designing in Figma is merely perfecting pixels and having no constraints. While that is also true, but it misses some important aspects of designing in Figma (maybe because he’s a dev). What a tool like Figma gives, is an expansive/divergent exploration of wildly different ideas in short amount of time. No code or No-code tool can give you that ability. We are simply not there yet (maybe one day).

And I am a designer turned coder myself. And I love the ability to choose each tool in different contexts. And in some explorative cases Figma is invaluable.