Marvin;
When I came to Deno, I was a developer that had retired young in 2000 (I'm 75).
I avoided tech for many years, and took up wood-working as a hobby.
My only computer use was browsing for tools, materials and woodworking articles.
Sometime In 2014, I was approached to do a project for a California NGO working in Cambodia.
One of their engineers had seen one of my graphical real-time desktop apps running in a Toyota plant.
They needed something similar for the detection of underground Unexploded Ordnance (UXO).
I volunteered, and suggested the use of a three-tiered solution.
- An embedded acquisition device (Bluetooth DAQ) (written in C), that streamed raw events to
- a local data collection laptop (Dotnet C#)
- The laptop wifi connected to a remote base system (DB + data analysis).
This multi-year project was very successful and sucked me back into tech land.
I read about Deno and was very interested (hated JS but liked TS).
I imediately fell in love with Fresh because of the clean DX.
Unfortunately, with zero Web-Tech experience (I had no HTML, CSS, nor JSX experience), in order to
learn Preact, I was basically forced to learn React.
Without technical context, I found React to be a bloated turd! I eventually learned enough React to grok Preact.
I eventually used that knowledge to port a Dice-game of mine, from a Canvas2D UI, to Fresh-Preact jsx.
Getting to the point. I find it unfortunate that the Preact docs make so many assumptions about what a new user knows about React. I’m sure originally Preact was trying to lure React users to this new framework. It would be a shame to keep making new Preact users to go down the path I did. In my opinion, Preact needs docs that are stand-alone; make no reference to React.
What are your feelings on this?