Lmst

Refactored a Build Pipeline and used esbuild instead of webpack and replaced #react with #preact.

As a result of all the refactoring, the codebase is modernised and just 38% of the bundle size what it was previously. Even the non-minified bundle is smaller than before.

I just realized I'm importing too much from #Preact, while it is not importing anything from me.

Should I start putting tariffs on the imports? Is there a TC39 proposal for tariff syntax?

I'm warning you @developit

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

😹

#JavaScript #Tariffs

My esteemed followers, you have posted a total of 375,809 statuses to the #fediverse. 22% of you have posted in the last 24h. You are a chatty bunch! ;-)

Check out my new #sideproject: *fedi-followers*. A privacy-friendly fediverse #followers explorer as #localonly #staticwebapp, decentrally hosted on the #ipfs. See who's actually following (and unfollowing) you over time and much more.

https://fedi--followers-data0-one.ipns.dweb.link/

#decentralization #mastodev #esmodules #importmaps #nobuild #indexeddb #preact

I've built a thing.

Sometimes my follower count seemingly fluctuates at random. To understand why, I dug into the #MastodonAPI and created "fedi-followers":

A privacy-friendly #fediverse #followers explorer as local-only static web app, decentrally hosted on the #ipfs. See who's actually following (and unfollowing) you over time and much more.

https://fedi--followers-data0-one.ipns.dweb.link/

#mastodev #javascript #webapp #staticwebapp #nobuild #esmodules #importmaps #indexeddb #preact #htm

Vue3 has a dangerous relationship with #typescript

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

#vueJS

@emmanueltouzery A year ago I took a risk and started building a big-ish app with #Preact where I would have otherwise used #React. So far it's going great. It also encouraged everyone to use much less external dependencies and build out more stuff themselves which in turn makes maintenance much easier and the whole app more future-proof. And it turned out the `compat` module needs to be used much less than originally thought.

Even though I'm a backend developer I've got to keep abreast of some frontend stuff so that I can lend my general developer brain to designing or advising or fixing things wherever it happens, and it looks like I've now got to get up to speed on #Preact and #TailWind and #WebPack for the next phase of work. That'll keep me busy for a bit.

I want to rebuild AirDrop on WebRTC, with QR codes / links to find one another in the same room. Happy to build the backend and collaborate on frontend internals, looking for a #preact #webdev interested in this open source project. I'm rather serious about this side project and have experience in similar fields. Portfolio @ https://pcarrier.com

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

@davidshq I've built many such applications over the years. The ones built with #vue are still quite easy to maintain, even 5+ years later - Vue 3 + #typescipt + #vite is a great stack to work with.

If you must JSX, then use #preact. It's not a bad choice either, but maintaining the hook soup isn't fun in the long run.

@Isabella_uy Do you know if #Preact Signals + #React is a good idea?

💻 Supported development environments:
* Complete support for #Chrome #Firefox and #Edge browsers
* Built-in compatibility with modern frameworks including #React #Vue #Svelte and #Preact
* Seamless integration with ESNext features and Web Standards

🚀 Quick start features:

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.

Should I upgrade to #React 19 or transition over to #Preact?

#webdev #frontend #javascript

#Development #Techniques
Managing reactive state using custom elements · Signals work great in custom elements too https://ilo.im/160x7y

_____
#Signals #WebComponents #CustomElements #Framework #Preact #WebDev #Frontend #DOM #HTML #JavaScript

If you are migrating your code from #preact to #svelte using #cursorai be sure to think through svelte’s concepts (like stores & reactivity) rather than just migrating code from one to another.

@aoristdual I'd probably look for something that doesn't need another toolchain (i.e. compilation) to keep things as simple as possible. Using #preact as a native es module together with #htm to write #jsx-style template tags for example.

https://preactjs.com/guide/v10/getting-started/#alternatives-to-jsx

An SSR Performance Showdown

🔍 Comprehensive #SSR Performance Testing:
• Test setup: 2398 div elements spiral rendering on #NodeJS v22, #M1Mac with 8GB RAM

📊 Performance Rankings (requests/second):
• #fastifyhtml: 1088 (baseline templating)
• #Vue: 1028 (best full-featured performance)
• #Svelte5: 968 (pre-release version)
• #SolidJS: 907 (impacted by hydration IDs)
• #Preact: 717 (lightweight alternative)
• #React19: 572 (RC version)

🛠️ Testing Environment:
• Built using #Fastify and @fastify/vite
• Production builds tested
• Consistent styling and template implementations
• No client-side reactivity features

💡 Key Findings:
• #Vue and #Svelte offer best balance of performance and ecosystem maturity
• Hydration markers impact performance (demonstrated in #SolidJS)
• Simple templating (#fastifyhtml) outperforms full frameworks

Source: https://blog.platformatic.dev/ssr-performance-showdown