#qwik — Public Fediverse posts

I Built an App in Every Frontend Framework, by (not on Mastodon or Bluesky):

https://dev.to/lissy93/i-built-an-app-in-every-frontend-framework-4a9g

#frameworks #libraries #react #vuejs #svelte #angular #lit #marko #jquery #alpinejs #solidjs #astro #qwik #comparisons

#Development #Comparisons
I built an app in every frontend framework · “12 frameworks, 12 apps (and 12 years of pain).” https://ilo.im/169m55

_____
#Frameworks #Angular #jQuery #Qwik #React #SolidJS #Svelte #Vue #WebDev #Frontend #JavaScript

I Built the Same App 10 Times: Evaluating Frameworks for Mobile Performance, by @cheddybop.bsky.social:

https://www.lorenstew.art/blog/10-kanban-boards

#frameworks #mobile #performance #comparisons #nextjs #tanstack #nuxt #angular #marko #solidjs #sveltekit #qwik #astro #htmx

React Won by Default—and It’s Killing Frontend Innovation, by @cheddybop.bsky.social:

https://www.lorenstew.art/blog/react-won-by-default

#react #svelte #solidjs #qwik #frameworks #checklists

[Перевод] React-монополист: как мы сами убиваем развитие фронтенда

Команда JavaScript for Devs подготовила перевод статьи о том, как доминирование React сдерживает развитие фронтенда. Автор утверждает: выбор React «по умолчанию» тормозит инновации, мешает развитию альтернативных фреймворков и превращает всю экосистему в монокультуру.

https://habr.com/ru/articles/948072/

#React #фронтенд #инновации #фреймворки #Svelte #Solid #Qwik #веб_разработка #экосистема #выбор

#Development #Analyses
React won, innovation lost · ”React is no longer winning by technical merit.” https://ilo.im/166wd5

_____
#Frameworks #React #SolidJS #Svelte #Qwik #JavaScript #TechDebt #WebPerf #WebDev #Frontend

JavaScript Framework Reality Check: What’s Actually Working, by @TheNewStack:

https://thenewstack.io/javascript-framework-reality-check-whats-actually-working/

#javascript #frameworks #qwik #solidjs #sveltekit #fresh

Between diapers 👶 baby books and frontend frameworks 💻

In the past, I kept failing to set up my own blog because I couldn't decide on a frontend framework. I wanted to try out multiple options, evaluate the pros and cons, and then make the "right" choice. VitePress, #solidjs, #astrojs, #nuxt Content, #Qwik —I wanted to experiment with them all.

With a 2-month-old baby, my requirements have completely changed: it needs to be quick and easy, using methods I already know or that are entirely self-explanatory. I want to focus on writing the blog articles, not implementing the website

Now, I’ve started a project with 11ty (https://www.11ty.dev/). Was it a good decision? What do you think? 😊

#Development #Techniques
The hype around signals · How signals reshaped our approach to UI reactivity https://ilo.im/1613s6

_____
#Signals #Reactivity #Library #Angular #Qwik #SolidJS #Svelte #VueJS #WebDev #Frontend

Towards #Qwik 2.0: Lighter, Faster, Better

https://www.builder.io/blog/qwik-2-coming-soon

Web devs keep introducing new frameworks and changes to make sure current ai never becomes capable of replacing them 😄

#NextJS15 #React19 #React #NextJS #Svelte5 #Svelte #Remix #Tanstack #MillionLint #SolidJS #Angular #AngularSignals #Qwik #Vue #VueJS

I thought this post on Twitter about the #CoreWebVitals of the homepages of #javascript tools and frameworks was interesting, and I thought I’d cross post it here

🛠️ It uses this tool: https://page-speed.dev/

Here’s how some of my favorite tools do: @eleventy, @astro, @deno_land Fresh, #Qwik

🐥 Original post: https://x.com/fredkschott/status/1756407637087010947?s=61&t=9qVqQJY7E1ikFhtau9dXug

#performance #accessibility

Ported the website of the famous internet radio station Dinxper FM to #qwik + #qwikcity . It features an audio player (duh!) w/ custom controls.

The custom constrols are reused on the listing page of past broadcasts. The broadcasts themselves are listed and streamed from an FTP server.

Have a look right here: https://qwik-dinxperfm-nl.toffe.site

Code: https://github.com/jaroel/dfm_site/tree/qwik-site

I had a great conversation @allthingsopen with Miško Hevery, creator of #Angular and #Qwik. We discussed the importance of performant JavaScript and maintaining great developer AND user experience. Enjoy and please subscribe! https://openatintel.podbean.com/e/performant-javascript-with-qwik/ #openSource #JavaScript #podcast

#Development #Reviews
Things you forgot (or never knew) because of React · “The world which crowned React king no longer exists.” https://ilo.im/14uklm

_____
#WebDev #Frontend #Frameworks #Libraries #React #Astro #Fresh #Qwik #Preact #Solid #Svelte #Vue

#Qwik ha le potenzialità per diventare la prima scelta per molti progetti frontend, e se non lo avete ancora scoperto vi consiglio di dargli un'occhiata perché ha dei vantaggi competitivi niente male.

Ho pensato di condividere il mio "primo contatto" in questo post sul tech blog di @sparkfabrik, se vi va dategli un occhio e fatemi sapere che ne pensate!

#javascript #frontend #coding

https://tech.sparkfabrik.com/en/blog/qwik-and-the-power-of-loaders-and-actions/

#Qwik è probabilmente la cosa migliore capitata ai framework javascript dai tempi di Angular.

@fogoplayer This is a more nuanced look at reactivity in different frameworks 🔗 https://www.builder.io/blog/reactivity-across-frameworks

I’ve been looking for this link for ages! I saw Miško Hevery give this blogpost as a talk live a few months ago and I think it’s very well put together

#reactjs #reactivity #qwik #solidjs

Comparing reactivity models between #fontend frameworks
#react #angular #vue #svelte #solid #qwik - a good talk by
@mhevery , founder of #angularjs at #Geektime Code conf.
#Coding #programming #javascript
@angular
@vuejs
@sveltejs
@solid_js
@qwikdev

Been hearing about #qwik for JS. Let’s give the site a look…

Immediately mad:
• I’m still skeptical about “the edge” for most web apps as this usually
• Social media in header options are _all_ proprietary
• Theming is treated as binary (light | dark)
• JSX is awful & base example shows it
• Can’t click the other ‘tabs’ to see the other benefits (doesn’t work without JavaScript even though it’s a) a pitch site whose sole purpose is to maximize delivering content to users, not be some interactive web application b) you are not showcasing the actual use case for the framework if it can’t render without JS but you’re using it to deliver that content… further in the case of web apps, the extra loading time isn’t as much an issue as users expect a load time & expect to stick around a while so this hydration may be a premature optimization that adds a _lot_ of complexity)
• Scroll down to get a “Loading...” because it doesn’t work without JS (and can’t even be bothered to give the correct ellipsis symbol in “…”) & it’s a _massive_ white block to get to the footer.
• Delivers useless element class names that will make it difficult for scraping, or providing users with the tools they need to make a site better or more accessible (think userScripts & userStyles).
• Community page doesn’t expand to any open source, decentralized, or private options: just expanded to more horrible social media. No self-hosted forums (like Discourse), no decentralized chat (like IRC, XMPP MUC, Matrix Space).

Temporarily enable JS for the domain…

• Batteries included talks about the big cabal of edge compute options it is “optimized” for which explains some things but it’s presupposing that you want or need “the edge”
• The marketing with YouTube-thumbnail-inspired images is so heavy-handed it hurts.
• Seems one of the main things it’s trying to sell is Builder.io
• Oddity: docs page uses giant emoji, but from different sets … why?
• Why Qwik has an entire section dedicated to the ‘numbers’ on how a fast site leads to good things, but you can build static sites that are way faster without all of this complicated tooling. The focus of these numbers is on web pages / multi-page app candidates, not SPAs or PWAs which is where a heavy framework like this should be preferred to just using a static site generator or a allow refreshes with a multi-page app. A lot of these sites eliminating all of their analytics and JavaScript would probably see better numbers and responsiveness as well.

Kinda neat

• The ‘resumability’ problem
• Ship less JavaScript is a pretty good motto, especially for a framework to admit