Vue3 has a dangerous relationship with #typescript

If you can, please choose a TSX based framework #preact #react #solidJS

can't actually find if/where #preact documents its handling for `style` properties. even in React it's kinda glossed over. just by example in https://react.dev/learn/javascript-in-jsx-with-curly-braces#using-double-curlies-css-and-other-objects-in-jsx although I suppose somewhat via TypeScript definition at https://react.dev/learn/typescript#typing-style-props

Weeknotes for 2024, week 51: https://denisdefreyne.com/weeknotes/2024-w51/

Weeknotes for 2024, week 50: https://denisdefreyne.com/weeknotes/2024-w50/

A Quick Way To Evaluate Software Frameworks

One of the most impressive bits of #software I’ve used is #Python. When I started to learn Python, it was version 1.5, a long time ago. I was immediately impressed with the tutorial. It was the first port of call. Here it is now:

<https://docs.python.org/3/tutorial/index.html>

Read the tutorial basics and you could start exploring the language library

<https://docs.python.org/3/library/index.html>

knowing you could master enough to move to more advanced concepts. Want to do something more complicated? Say build a web server?

First you might try the #HOWTO pages trying #sockets:

<https://docs.python.org/3/howto/index.html>

After reading about the limitations you might try the #PEPS (Python Enhancement Proposal) What is a PEP? Try reading this page:

<https://peps.python.org/pep-0001/)

Finally you might decide #WSGI is what you want and read the specification at
<https://peps.python.org/pep-0333/>. I travelled this path in 2007/8 to build a version of my blog engine.

<https://seldomlogical.com/redux.html>

So I go the latest build on #Deno, install it and try a simple blog engine to see how it works

<https://deno.com/blog/build-a-blog-with-fresh>.

The example code fails, the source code fails. I see the basic documentation for it (yet to try, but skimming through, it appears okay.) The tutorial only a couple of years old has rusted, the source is unmaintained. The issue is with JS / #React / #Preact where plain old #HTML5 and #CSS will do.

A quick example how the basics have to documented, correct in bite sized pieces. The #HOWTOS maintained and blog #examples periodically revised.

Why don't we have scoped styles in Preact natively?

I've already regretted going down the rabbit hole of trying to find a nice, simple #Preact/ #Vue #dashboard #template that doesn't require a gazillion niche #npm invocations. All I wanted was a nice #vanilla #javascript and #css starting point…

I really like the combo of Signals with JSX (via #Preact).

Add a bit of Context to avoid passing state through the tree and I'm PRODUCTIVE plus I've got a #NoBundle web app solution.

@developit

After spending the past few months wrangling nested hooks and contexts, Preact's Signals library sounds beautiful

https://www.youtube.com/watch?v=SO8lBVWF2Y8

https://preactjs.com/guide/v10/signals/

#Development #Explainers
HTML attributes vs. DOM properties · What fewer and fewer developers seem to know https://ilo.im/15ynz8

_____
#Framework #React #Preact #Lit #VueJS #WebDev #Frontend #DOM #HTML #JavaScript

I have occasionally been asked why Preact's string renderer doesn't do scheduling and defaults to synchronous. Here's your reason (it's so fast that doing so is generally net-negative for both response time and throughput, making it undesirable by any metric)
#preact

Has anyone here got opinions about Preact vs React?

Specifically, I'm weighing up migrating a large-ish codebase to Preact instead of upgrading React, and I'd be interested to hear from anyone who a) has done this, b) has decided not to do this, c) can think of solid reasons to stick with React.

I can't see much benefit to choosing React over Preact, but is there anything I'm overlooking?

I built this POC to demonstrate how I'd use CustomEvents to implement Signals. Please criticize my approach and tell me why I need a native browser API for this.

https://card-calc.surge.sh/

I've known about Preact Signals for a while but, I took the time to read the source code and I'm very impressed. Preact, and by extension Signals, feels a lot like backbone.js, clean, elegant and clearly written by people who understand the problem they're trying to solve.

https://github.com/preactjs/signals/blob/main/packages/core/src/index.ts

Oh yeah, I'm doing it this week: I'm refactoring #Preact signals to a highly complex #React component.

The starting point is a component that currently takes in 26 props, and some of those props can be very complex.

And yes, that is somewhat poor original design considerations combined with 5 years of feature development on top of it. I already refactored lots of the internals 3 years ago for better functionality and performance.

preact + signals + HTML Drag and Drop API is pretty clean.

demo: https://2gtlk9.csb.app

code: https://codesandbox.io/s/preact-signals-dnd-2gtlk9?file=/src/index.tsx