#LitElement
hard time imagining it's a common stance. I don't think it's wrong, but it definitely goes against conventional wisdom.
4. Vanilla's dominance aside, the other three seem fairly explainable by popularity. #vue is a very beloved framework with the explicit goal of working well outside of a build step, so it doesn't seem crazy that it came in second place. #preact is generally more popular than #litelement, but I'm guessing most of those NPM installs are still using build tools. (to be continued)
is so unthinkable for an SPA that I would pretty much always want to use some sort of third party tool. #litelement is my personal favorite, but I'm looking forward to trying #preact someday.
3. I wonder if Mastodon introduces a bit of a sample skew. The fact that you're signed up for something using ActivityPub suggests some willingness to go against the proprietary grain for something more interoperable and independent. Perhaps that's why Vanilla won out—again, I just have a (to be continued)
If you were building an SPA with no build step, which framework would you use?
Comment if you don't see your choice. Boosts welcome!
#javascript #reactjs #preactjs #litelement #js #react #preact
“React Is Not Modern Web Development”
@jaredwhite’s personal thoughts on a great entry by @collinsworth into the growing body of work which details why greenfield #WebDev projects are better served by other frameworks…or none at all.
https://thathtml.blog/2023/08/react-is-not-modern/
#React #JavaScript #frameworks #Preact #Svelte #Vue #SolidJS #LitElement
More adventures in using #jsdoc with #litelement:
The LitElement superclass generates reactive properties at runtime based on a static object in the subclass. Type systems don't like this--the types don't show up on the superclass because they're generated, and they don't show up on the base class because `ChildClass.properties.property` is not the same thing as `new ChildClass().property`
One thing that gets me really excited about #webcomponents is the ability to change course.
I had a project written in #vanillajs , but that was a pain, so I started writing new code using #webcomponents . But that was still a pain, so I decided to write any new components using #litelement .
For my next project I’m thinking about using #hauntedjs and #ionicframework , but there’s peace of mind knowing that if I don’t like it I can go back to #litelement or #vanillajs .
I recently updated my website to use #LitElement. I don't need to use a frontend framework for a dinky personal site, but I like reimplementing my personal site with a new frontend framework whenever I'm curious about it.
LitElement feels like being back in the days of Vanilla JS. And that's because well, I am! It's not even a framework really, more like a library. It's essentially just a reactive wrapper and templating utility for the browsers customElement registry!
Pro: #Storybook renders #LitElement
Con: I can't copy the file as-is to #Eleventy and have it execute (I believe a compilation step is needed.
Time to look into #WebC and #WebComponents then, I guess.
Hey everyone, I'm Dean! (he/they) I'm a software engineer professionally, but I'm also a big fan of #tech, #gaming, and #anime!
Programming:
#Java
#ReactJS
#LitElement
#RustLang
#GoLang
dabbling in any new technologies :)
Gaming:
#GenshinImpact
#Overwatch
#Valorant
#osu
#HonkaiStarRail
Anime:
#DarwinsGame
#KomiCantCommunicate
#SPYxFAMILY
#Naruto
#KaguyaSamaLoveIsWar
#BocchiTheRock
and a few more... maybe I should start a proper anime list :)
:AYAYA:
@kulykov ah, I remember interacting with #OpenWC docs, and I wasn't particularly pleased to see marginal focus on how to do things with #LitElement. You can imagine what my thought process was ATM: a lot of Lit talk = vendor lock-in = bye. I'll investigate it better.
#WebComponents experience :underheart:
:sadness: Browsers don't have the same baseline styles.
:fatyoshi: 2 hours figuring out how to avoid #frameworks and #bundlers.
:AngeryCat: 3 hours of searching framework anyway, only to stumble upon options that either, like #LitElement, have minified bundle without #TS declaration or, like #StencilJS, require building.
:tinking: Ending up writing my own nano-framework with adoptedStyleSheets #polyfill.
RT @PowersBenny@twitter.com
Let's build a colour-picker #html element with #css, #javascript and @buildWithLit@twitter.com reactive controllers...
...but without #LitElement 🤯
🙃 Curious yet? 😜
https://dev.to/open-wc/let-s-build-a-colour-picker-web-component-2j3n
#webcomponents #weekendreading
🐦🔗: https://twitter.com/PowersBenny/status/1408364002594496514
I'm not done yet with replacing #conversejs Backbone views with web components.
I've managed to shave off another 30 seconds on the tests. They now complete in about 95 seconds.
#ConverseJS has over 400 functional tests.
By replacing the Backbone views with web components, the tests now complete one whole minute faster!
From 190 seconds to 130 seconds.
I'm currently busy rewriting large parts of the UI layer of Converse.js to use web components via #LitElement.
Very impressed so far with the rendering speed of lit-html.
Lots of improvements still in the pipeline.
RT @thomasloven@twitter.com
Just published my first webcomponent! A round slider using @polymer@twitter.com #LitElement! Thanks a lot to
@balloob@twitter.com for holding my hand! Now to get it into
@home_assistant@twitter.com! I'm excited! Exclamation point!
https://www.npmjs.com/package/@thomasloven/round-slider/v/0.2.0
RT @sergicontre@twitter.com
Web Components: Seamlessly interoperable.
This is my small laboratory for interoperate Web Components with frameworks and libraries. @polymer@twitter.com #LitElement #WebComponents
https://medium.com/@sergicontre/web-components-seamlessly-interoperable-82efd6989ca4
