Live data from Hacker News

Fresh is a new full stack web framework for Deno

deno.com

21–30 of 249 posts

Re: Fresh is a new full stack web framework for Deno

#21
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 related security protections, logging, error handling framework, etc, etc, etc.

To me that's a "full stack" framework. If just running code on the backend and on the frontend is enough, then I can make a bash script a full stack framework, right?

Re: Fresh is a new full stack web framework for Deno

#23
post #18

Earlier quoted context omitted.

Yes, this is something I want to add in the future. We're just not quite there yet. My current plan is: 1. first class styling plugins 2. synchronized island state 3. built in data persistence

Amazing. If I can make a wish for 1: Tailwind =)

It is not documented, but run `deno run -A -r https://fresh.deno.dev my-app --twind` :)

Re: Fresh is a new full stack web framework for Deno

#26

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…

I think that particular metric (or one very like it) was originally about… Amazon.com.

So, y’know, maybe a slightly different ballgame.

Re: Fresh is a new full stack web framework for Deno

#28

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 personally believe full-stack is fuzzy, because what if we also provided a UI layer, or a payment interface framework, or a notification handling system, or similar as part of the "full stack" system? It's hard to draw a line as to where something becomes "full stack."

However... it's definitely closer to what I want "full stack" to mean than... this. Or a pile of bash scripts.

Re: Fresh is a new full stack web framework for Deno

#29
post #7

Earlier quoted context omitted.

I would assume the idea is that this is native to the deno runtime whereas some other frameworks like NextJS and Remix are "node native?"

Isn't DENO just AWS Lambda@Edge but you can't use anything other than JS/TS? edit: whoa whats with these downvotes? and im being accused of being a troll for asking a legitimate question? I am trying to evaluate this and my comments are being flagged for no reason Dang This is the second or third time just asking innocent questions on a YC linked company resulted in mass downvotes and flagging.

No post body was provided.

Re: Fresh is a new full stack web framework for Deno

#30

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…

> Or is it just being able to run code on the server enough to be "full stack"?

To me, "full stack" would entail having responsibility for logic on both the front-end and back-end, which Fresh does.

Personally, I would not consider Laravel a full stack framework (Although it can work well with front-end frameworks to make a full-stack application). Instead I'd consider it a back-end framework.

Post reply on HN