81–90 of 249 posts
Quoted post unavailable.
Your question seemingly conflates these three things and adds unrelated elements.
To answer what you might be asking: TS is a nice language and Deno offers excellent tooling, Deno Deploy is easier to use than AWS and Fresh makes it easy to write web apps in a React-ish manner.
If you’re interested in something similar for the Node.JS ecosystem, check out Astro (https://astro.build).
Fresh’s Zero-JS island architecture approach was largely inspired by it.
Earlier quoted context omitted.
> 100ms added latency can cost you 7-8% in conversions i hear this metric (or something equally absurd) cited frequently and have never seen it to be true in my own experience. i guess if you have to load a product page with 100 images (or assets) and each has 100ms network latency, then it will add up to much more than that. but 100ms for a single interaction or network request (e.g. process payment POST) is not goi…
I think if frame it as, “each 100ms you shave off a critical consumer shopping checkout flow page increases conversions by X%” it starts to seem more defensible. Agreed that in the general case 100ms to full paint (with interactivity not far behind) is really good.
Just averaging out those numbers could result in engineering time being wasted chasing rapidly diminishing returns, if the site is already below one of those thresholds.
Am I the only one that think nowadays anything can be called "full stack"? For me "full stack" is something like Rails, Laravel, Django, etc. Or is it just being able to run code on the server enough to be "full stack"? I'm missing the translations system, the validations, the background jobs, the authentication system, authorization helpers, email sending, ORM or data access layer, testing framework, CSRF and relate…
I thought full stack means going all the way down to tuning the database, the kernel, building your own CI/CD, and performing your own deployment and scaling.
Am I the only one that think nowadays anything can be called "full stack"? For me "full stack" is something like Rails, Laravel, Django, etc. Or is it just being able to run code on the server enough to be "full stack"? I'm missing the translations system, the validations, the background jobs, the authentication system, authorization helpers, email sending, ORM or data access layer, testing framework, CSRF and relate…
> For me "full stack" is something like Rails, Laravel, Django, etc. Rails, Laravel, or Django are completely agnostic about the frontend side of the full stack though :-) Well, maybe Rails will have an opinion about Stimulus; but this fresh thing continues the journey after the response has reached the client.
My productivity with Rails 7 and Turbo has never been higher.
I really like the idea of Deno and Fresh's philosophy also resonates with me (I'm a Rails guy). I would like to see an integrated ORM (can be an existing one) and testing framework though, before I would consider it a "full-stack" web framework.
The JS ecosystem seems a lot more hesitant to bundle features into frameworks à la Rails/Laravel & friends, but Redwood.js sounds like what you're looking for. The ORM it uses is Prisma, which works really well on its own too. https://redwoodjs.com https://www.prisma.io
Am I the only one that think nowadays anything can be called "full stack"? For me "full stack" is something like Rails, Laravel, Django, etc. Or is it just being able to run code on the server enough to be "full stack"? I'm missing the translations system, the validations, the background jobs, the authentication system, authorization helpers, email sending, ORM or data access layer, testing framework, CSRF and relate…
Are deno packages usable from the node side of the ecosystem ? and vice versa ?
I really like the idea of Deno and Fresh's philosophy also resonates with me (I'm a Rails guy). I would like to see an integrated ORM (can be an existing one) and testing framework though, before I would consider it a "full-stack" web framework.
The JS ecosystem seems a lot more hesitant to bundle features into frameworks à la Rails/Laravel & friends, but Redwood.js sounds like what you're looking for. The ORM it uses is Prisma, which works really well on its own too. https://redwoodjs.com https://www.prisma.io
But yes, I guess if I would need to pick a more mature framework with JS, Redwood would be the way to go.
React is here to stay and will have jquery like longevity. Sure, performance wise, it isn't the best, but performance isn't an end all be all. What separates react from the rest of the group is the maturity of React Native. If Discord is betting on React Native, so too can it be used for a lion's share of applications out there. When you're a startup deciding between technologies, usually you're a 1-5 man shop. If yo…
Flutter is awesome for mobile dev. For web? Not so much.