I seriously cannot wrap around my head how in 2022 people really like JSX and all that X-in-JS crap, it's like people doesn't know about separation of concerns or clean code at all.
Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
11–20 of 57 posts
Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#12I seriously cannot wrap around my head how in 2022 people really like JSX and all that X-in-JS crap, it's like people doesn't know about separation of concerns or clean code at all.
For almost anything more interactive than a static document, modularizing UI code primarily based on component boundaries makes a lot more sense than modularizing primarily based on markup / interactivity / styling boundaries.
Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#13I seriously cannot wrap around my head how in 2022 people really like JSX and all that X-in-JS crap, it's like people doesn't know about separation of concerns or clean code at all.
Separating which concerns?
Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#14I seriously cannot wrap around my head how in 2022 people really like JSX and all that X-in-JS crap, it's like people doesn't know about separation of concerns or clean code at all.
There are quite a few motivations for this, but the primary advantage is that it causes markup elements to become first-class entities within your code, allowing your view composition to be checked by the compiler as well as allowing you to design your own reusable markup elements that fold up application level concerns. It's also nice when your views have lexical access to your application state variables so you don't have to pre-render a big string template and interlace it with an explicit map of serialized parameters - it's very nice when the compiler lets you know a view simply cannot display the type of data you're trying to shove into it rather than rendering a broken looking page.
Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#15Anybody here used Fresh for a non-toy project yet? Have anecdotal experiences to share?
Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#16Hey folks, author of Fresh here. Very excited for this rather significant release. Happy to answer any questions you may have :)
Solid release! It fixes most of the rough edges I encountered.
Was Twind chosen to stay true to the "no build step" idea?
Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#17I've been writing a simple single page form app the past few days and I like Fresh a lot. I really appreciate the simplified project layout vs my last setup of a react app project nestled in a parent express project. It just makes the devops, if you would even called it that, of writing a one-person full stack app easier. Deno running TypeScript without a compile to JS adds to this. I'm happy to see the Preact Signals demo to help manage state between islands in 1.1. Thank you for this great framework. :)
Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#18Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#19Hey folks, author of Fresh here. Very excited for this rather significant release. Happy to answer any questions you may have :)
Fresh is looking awesome Luca! The only thing I'm missing to try it out is some sort of SASS support.
This is actually something I am planning a plugin for, just like we have for Twind.
Re: Fresh 1.1 – Automatic JSX, plugins, DevTools, and more
#20Hey folks, author of Fresh here. Very excited for this rather significant release. Happy to answer any questions you may have :)
How big is the “team” working on Fresh? Is there a primary product which it spawned off of (the demo website?)?
Yes, it was a tech demo for some internal projects. I maintain the framework itself, but a lot of the work in other parts of the Deno system (Deno Deploy, Deno CLI) that are related to Fresh are done by other folks on the team :)