Live data from Hacker News

Fresh is a new full stack web framework for Deno

deno.com

121–130 of 249 posts

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

#121
post #69

Earlier quoted context omitted.

Quoted post unavailable.

deno has been around for a little while, i think some commentators may have taken your responses as satirical because of how often deno shows up in conversations surrounding the web platform. think of deno as a node.js successor, it's a separate javascript runtime; with that, it'll need to compete with node's ecosystem (vast and diverse tooling). the deno company is spearheading that movement by creating things like…

today was the first time i heard of deno and i innocently asked whether it is something like AWS lambda edge.

That was grounds for:

- death threats to my twitter account

- flagging all of my comments

- justifying how i deserved it.

Just wow.

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

#122
post #95

I listened to a conference talk[0] where Dylan talks about fresh framework and he says quoting: "We have this little project at Deno ... it's not a web framework that we're really promoting or you know intending to utilise long term. More of kind of a demo of what this post unix web frameworks might look like" Is it worth investing in this now? It really put me off. [0]: https://www.youtube.com/watch?v=pBcFJmQ6UVM at…

“Post Unix”?

https://tinyclouds.org/javascript_containers

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

#123
post #54

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. Aren't those back-end frameworks? I always undestood full-stack to mean "front-end + back-end".

Rails definitely has a front end, by default anyway.

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

#124
post #63
post #4

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

Prisma is a nice product but I wouldn’t use it in production yet. It is prone to race conditions as it does not use native upserts, opting instead for Rails-style check-if-exists-insert-if-doesnt.

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

#125

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…

To me, a PHP file in an Apache server which includes some JS counts as full stack. To me, fullstack = frontend + backend. I don't think Django counts as full-stack, as you don't have a default front-end framework, like Rail's Stimulus.

Historically, I don't think you could call something that sits on top of Apache full stack if you didn't also control Apache, so maybe, depending on whether you're just dropping on some webhost?

If you get to ignore threads/forks and number of workers as well as memory management of them because it's someone (or something) else's responsibility, then that's not full stack. The stack is OS (slightly, and can often be ignored), webserver, application, and client (HTML/JS). If you hand off responsibility of any of that then it isn't "full".

The term originally came from referring to people that handled all these things. You could be a back-end developer, dealing with the OS and webserver and maybe application, front-end developer where you dealt with HTML, JS and maybe some application code, or you could do both and be a "full stack" developer.

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

#126

Earlier quoted context omitted.

“Post Unix”?

well many of us think that the excellent ideas of computing in the 1970s (those that produced Unix) are no longer the best ways to do things, and believe that the community should be innovating much more. a lot of those innovations are over 50 years old, now. do we REALLY believe that the Unix Philosophy is the best thing in the history of computing? past and future? really? I don't. and what about in another 50 year…

Massive eyeroll

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

#128

This looks like something I'd like to try but I don't like JSX (TSX). Is it possible to use Fresh with Vue in place of Preact, and write Vue components that split HTML templates from script and style tags?

Yes, same here. Hate JSX/TSX. Would love to have choice of templating engine so can stick to pure HTML/CSS as much as possible. I still prefer simple template engines like Mustache which respect HTML.

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

#129
post #95

I listened to a conference talk[0] where Dylan talks about fresh framework and he says quoting: "We have this little project at Deno ... it's not a web framework that we're really promoting or you know intending to utilise long term. More of kind of a demo of what this post unix web frameworks might look like" Is it worth investing in this now? It really put me off. [0]: https://www.youtube.com/watch?v=pBcFJmQ6UVM at…

“Post Unix”?

The way people use modern Linux systems is moving past how most people used Unix systems back in the day. Instead of piles of shell scripts glued together we now use a monolith (systemd) to manage most of the low level services and initialization. No one really cares or tries to setup proper multi-user systems and instead we focus on multiple roots with each application given an exclusive root filesystem, view of the system, etc. (i.e. containerized). Computing is a lot different than it was 50 years ago, and that's not a bad thing.
Post reply on HN