As courtecy to StackBlitz, sharing my ticket.
Would be happy to meet Vite users there.
I have my ticket for @ViteConf! The ViteConf community is going to be there! https://t.co/IBobn4vqfU
The more I am diving into HTML DOM as the web application structure model with multiple languages/stacks involved, the more generic pattern of OS with apps fusion appear. LLVM as glue between apps/libs, and OS would make a single binary organizm. https://t.co/ZwqnxYjIFe
The Declarative Custom Elements comming into web applications stack.
<custom-element> DCE implementation would enable to build apps and embed safely multiple vendors ones using HTML markup without JavaScript.
In 2024 XML Prague Conference.
https://t.co/tKQP8MIwON
#HTML5
Next week on april 20 on WCCG conference I will be presenting the Declarative Web Application concept to the #W3C community and browser vendors. If you like the idea or find it useful for your web applications, vote up the 1st w3c proposal from DWA stack.
https://t.co/FRClqhxQ4t
If you think the #HTML templating worth improvement, please take your vote or opinion on #wicg proposal
#webcomponents#customelements
https://t.co/PNjk8j3LGh
Since several of you aren't yet on mastodon, here's a little cross-post (stolen from Tim Bray);
Mastodon growth;
8,001,321 accounts
+1,968 in the last hour
+54,827 in the last day
+387,289 in the last week
One of criteria to use OSS lib is availability of commercial support so if main maintainer capacity is limited, the feature request/bug fix can be addressed via $ contract.
What kind of twisted subculture has college kids sitting around on social media fantasizing about "leaving countries to the wolves"? It's just not healthy.
@abanduk Looking into thread, do not see much reasonable answers. To avoid legacy support issues: the language syntax has to be expandable (see C++ extensions ) and support most recent patterns: OOP, AOP, multi-threading, async programming. Decorators and generics are just part of AOP.
@abanduk Language backward compatibility is simple. Keep the legacy as valid runtime. Language version should be a part of deployment descriptor. Look into jar format as a sample. The cross-version is a tricky one, I have an answer:😜
@justinfagnani@WestbrookJ@passle_ The concept of render roots is a trouble itself. The hydration has to be available on any DOM level, hence its API should account for it.
The shadow root & multiple scope types been blended into convo, but is an orthogonal problem not to be associated.