115
you are viewing a single comment's thread
view the rest of the comments
[-] sailor_sega_saturn@awful.systems 90 points 5 months ago* (last edited 5 months ago)

The one catch is that because responses from the blockchain can take variable amounts of time, it’s best to request and receive from blockchains using asynchronous methods.

"You may be used to writing websites that actually load in fractions of a second, and so rely on obsolete web2 technologies like synchronous fetches. But don't worry! With modern techniques like async / await your loading spinner will animate flawlessly while the blockchain spends 20 minutes burning down a forest in the background."

[-] henfredemars@infosec.pub 37 points 5 months ago* (last edited 5 months ago)

By using these newer technologies, you can provide a more bloated and slow user experience, converting your web users into app users so they can avoid this garbage you wrote that requires a 100 MB download every time they visit the page.

But the kicker is we can put the same web site into the app!

UX is more uniformly garbage than ever.

this post was submitted on 19 Jul 2024
115 points (100.0% liked)

TechTakes

1481 readers
365 users here now

Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.

This is not debate club. Unless it’s amusing debate.

For actually-good tech, you want our NotAwfulTech community

founded 1 year ago
MODERATORS