With Preact, you create user interfaces by assembling trees of components and elements. Components are functions or classes that return a description of what their tree should output. These descriptions are typically written in JSX (shown underneath)β¦
Sasa is a highly driven full stack software developer with background in finance and accounting. A relentless problem solver who is passionate about finding elegant solutions to problems at hand.
I'm kinda saddened by the fact that more and more people are leaving the old school approach, Turbolinks is a nice alternative for a smooth UX in my opinion, and Stimulus looks promising as well. I'm not the biggest fan of "javascript rich" front-ends :(
If I remember right, Ben once said that performance is the most important part of UX, and Preact delivers that. Also he doesn't like Facebook. Feel free to correct me if I made a mistake here. π
Yes, it's an app where 90% of the traffic is people just coming here to read a server-rendered article. While we have interactions, we mostly just want to get people started on what they came here to do as quickly as possible.
But also I really believe that Preact's creator @_developit
cares about the same things I do, so as things evolve in the future I just feel like things are in good hands.
No such thing as too amateur, whatever that even means. Yeah, server-side rendering using "old-school" Rails html.erb files. I believe those is are EJS is inspired by, so pretty much the same thing I think.
Sasa is a highly driven full stack software developer with background in finance and accounting. A relentless problem solver who is passionate about finding elegant solutions to problems at hand.
Sasa is a highly driven full stack software developer with background in finance and accounting. A relentless problem solver who is passionate about finding elegant solutions to problems at hand.
Sasa is a highly driven full stack software developer with background in finance and accounting. A relentless problem solver who is passionate about finding elegant solutions to problems at hand.
Top comments (16)
Part Vanilla JS, part Preact.
preactjs / preact
βοΈ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
Fast 3kB alternative to React with the same modern API.
All the power of Virtual DOM components, without the overhead:
π More information at the Preact Website β
You can find some awesome libraries in the awesome-preact list π
Getting Started
Tutorial: Building UI with Preact
With Preact, you create user interfaces by assembling trees of components and elements. Components are functions or classes that return a description of what their tree should output. These descriptions are typically written in JSX (shown underneath)β¦
I'm kinda saddened by the fact that more and more people are leaving the old school approach, Turbolinks is a nice alternative for a smooth UX in my opinion, and Stimulus looks promising as well. I'm not the biggest fan of "javascript rich" front-ends :(
I'm also was not a fan of FE frameworks before I try vue.js.. :)
what do you mean the old school approach?
old school approach is jQuery :)
Why did you guys use Preact instead of React. The main motivation?
If I remember right, Ben once said that performance is the most important part of UX, and Preact delivers that. Also he doesn't like Facebook. Feel free to correct me if I made a mistake here. π
Yes, it's an app where 90% of the traffic is people just coming here to read a server-rendered article. While we have interactions, we mostly just want to get people started on what they came here to do as quickly as possible.
But also I really believe that Preact's creator @_developit cares about the same things I do, so as things evolve in the future I just feel like things are in good hands.
Does that mean it is server side rendering? I'm just practising node.js/express.js with EJS templates so just curious.
Sorry if this was amateur question
No such thing as too amateur, whatever that even means. Yeah, server-side rendering using "old-school" Rails
html.erb
files. I believe those is are EJS is inspired by, so pretty much the same thing I think.Ooh Cool, with EJS I seem to work on the standard tech right now
Ben wrote about that some months ago:
dev.to/ben/why-we-went-with-preact...
Thanks for the link, I haven't been that active here previously so I probably missed it
I'll take a guess since Dev.to's backend is Ruby if I'm correct, then they probably use Turbolinks to some extent. But what else do they use?
does dev.to have a mobile app ?
I donβt think so, their website is what is considered a Progressive Web App, I think they wrote an article about it some time ago.