71–80 of 249 posts
Earlier quoted context omitted.
What does this free open source web framework have to do with a proprietary web service provider?
Quoted post unavailable.
> But client-side rendering is expensive; the framework often will ship hundreds of kilobytes of client-side JavaScript to users on each request. These JS bundles often do little more than rendering static content that could just as well have been served as plain HTML. server-side rendering for each request in V8 might be more expensive to host than client side rendering in V8? for a properly-chunked app, hopefully m…
Earlier quoted context omitted.
What does this free open source web framework have to do with a proprietary web service provider?
Quoted post unavailable.
They are legitimately asking how the comparison works. You are comparing a web framework and a Cloud Serverless runtime, which is a bit odd. Maybe you didn't have context on Fresh/Deno, but that doesn't mean they are "threatened by the mere question."
I don't agree with the downvote brigading you're receiving but when someone poses a question like this in neutral language, reacting in this way certainly isn't going to help the situation.
Maybe I am getting all wrong, but this sounds like PHP.
Maybe I am getting all wrong, but this sounds like PHP.
Earlier quoted context omitted.
Node/JS solutions typically don't come "batteries included." "Fullstack" means different things depending on the ecosystem and for Node devs it means "hey there's a solution for the front-end and back-end." Totally understand about Django, Laravel etc. but typically if I'm building in Node/JS I'm pulling all of that extra stuff in from npm piecing it together myself.
Yeah, I do the same. Most of what I do is Next.js + a good bunch of npm packages to get the "full stack". But I wouldn't call Next.js full stack because it can do SSR, or even API routes. But again, that's just me confused about what is "full stack".
There term has definitely become more amorphous and ambiguous. I spent a few years mostly working with physical hardware, networking, virtualization, scripting deploys for DBs and OSs, and handling the DNS alongside some business oriented C#. Then I moved over to working with AWS and Azure.
Now I primarily work with Node, Golang and Python.
With modern tooling and a team that supports it, I've found myself mostly working on services, APIs and React front-ends. Even with Next.js, it's hard to know where the line on what "full stack" is.
It's sort of come to encompass the frontend and backend of an application, less so the architecture of it. Mentally, however, I still lump it all together when I think of what qualifies for "full stack", as I personally think the term represents an understanding of how everything works together, which definitely helps when troubleshooting the source of a problem.
Earlier quoted context omitted.
> server-side rendering for each request in V8 might be more expensive to host than client side rendering in V8? Expensive not in money terms, but in user experience. Also: if you are doing e-commerce, 100ms added latency can cost you 7-8% in conversions. Spending 5% more on hosting to do SSR just makes economic sense.
> 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…
Agreed that in the general case 100ms to full paint (with interactivity not far behind) is really good.
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…
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.
Earlier quoted context omitted.
I think that particular metric (or one very like it) was originally about… Amazon.com. So, y’know, maybe a slightly different ballgame.
maybe there was more nuance to that statement, but i never bought it at face value, even then.