@crabmusket@aus.social
@crabmusket@aus.social avatar

crabmusket

@crabmusket@aus.social

Christian anarchist, reluctant technophile. Web developer, co-founder at https://pylon.solar

This profile is from a federated server and may be incomplete. Browse more on the original instance.

baldur, to random
@baldur@toot.cafe avatar

And, bonus , this neighbour came for a short visit and did a routine inspection tour of the flat ๐Ÿ˜„

The neighbour cat walks past my comics library on her inspection tour
Now the cat is back at my stairs, looking up at the spiders I need to clean out of the window
But, before the neighbour cat leaves, she has aa quick relaxing roll and rub on the stair carpet.

crabmusket,
@crabmusket@aus.social avatar

@baldur I couldn't help but think of the Narcos meme ๐Ÿ˜†

danluu, (edited ) to random
@danluu@mastodon.social avatar

Naive question: why do React apps in the real world tend to be slow?

I tried doing a React tutorial and the result was quite fast (w.r.t. latency & CPU utilization on low-end devices) until the tutorial has you replace "manual" / "low-level" react calls with commonly used libraries, e.g., using TanStack Query instead of useEffect plus a manually instantiated cache.

Is the main issue that libraries tend to be big and slow or is there another major cause of React app slowness?

crabmusket,
@crabmusket@aus.social avatar

@acdha @danluu I actually think this explains a lot about why the JS ecosystem is the way it is. I wrote about that here: https://listed.to/@crabmusket/14061/javascript-s-ecosystem-is-uniquely-paranoid

crabmusket, to random
@crabmusket@aus.social avatar
  • This is a bad way to treat your customers.
  • This is a bad way for your customers to have to treat their customers.
  • Does anyone know of an open source alternative?

https://au.pcmag.com/ai/104223/docusign-tapping-user-data-to-train-ai-models-offers-vague-privacy-promises

tonofcrates, to random
@tonofcrates@mastodon.social avatar

I wrote some ideas for how to actually make HTML documents a viable replacement for PDFs.

https://willcrichton.net/notes/portable-epubs/

crabmusket,
@crabmusket@aus.social avatar

@tonofcrates @mcc I wonder if setting the tone in the ecosystem early could help?

  1. make use of standard elements where possible, e.g. your <def> should already be covered by a standard without scripting shouldn't it? Another interesting one might be invokers for this kind of behaviour: https://thathtml.blog/2023/11/invokers-are-coming/ (This means that when using a browser-based client, one might need to polyfill those standard elements)

  2. provide a set of "blessed" extended components for common interactive elements that browsers don't provide? e.g. a data grid? This may let publishers go farther without needing to provide their own scripting. Reader apps should bundle these builtin components so they don't need to be downloaded on document load.

  3. this is a significant one - don't render custom elements by default, but prompt the user to allow this document to render interactivity. WCs could render as blocks with a prompt to enable interactivity. This could encourage interactivity used only where it's valuable.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • โ€ข
  • megavids
  • kavyap
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • InstantRegret
  • GTA5RPClips
  • Youngstown
  • everett
  • slotface
  • rosin
  • osvaldo12
  • mdbf
  • ngwrru68w68
  • JUstTest
  • cubers
  • modclub
  • normalnudes
  • tester
  • khanakhh
  • Durango
  • ethstaker
  • tacticalgear
  • Leos
  • provamag3
  • anitta
  • cisconetworking
  • lostlight
  • All magazines
    •