Sasha Firsov
679 posts

Sasha Firsov
@SashaFirsov
Open source fan and believer in competition as primary driver of progress. Pushing Declarative Web Application concept @[email protected]
Bay Area CA Katılım Şubat 2010
70 Takip Edilen14 Takipçiler

Inwiting #WebDev to bring the IFRAME evolution ideas on
github.com/openui/open-ui…
English

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! viteconf.org/24/tickets/sas…
English

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. github.com/EPA-WG/custom-…
English

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.
youtube.com/live/QBMBdxo7x…
#HTML5

YouTube
English

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.
github.com/WICG/webcompon…
English

If you think the #HTML templating worth improvement, please take your vote or opinion on #wicg proposal
#webcomponents #customelements
discourse.wicg.io/t/proposal-ful…
English
Sasha Firsov retweetledi

turned off my twitter email notifications, only DMs left. Would visit just once in a while, may be weekly.
Instead, @Suns@fosstodon.org is live.
English

I will not participate on Twitter while D*nald Tr*mp has an active account. #VoteWithYourTweet
Use your voice. Join us on votewithyourtweet.com
English

@reznik_andrew @phiggins It is, just one more domain in mastodon federation
English
Sasha Firsov retweetledi
Sasha Firsov retweetledi

@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.
English

@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:😜
English

@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.
English

@WestbrookJ @passle_ Independent render roots is a big advantage, actually. It just naturally leads to scoping / pruning of updates, incremental hydration, and all kinds of good things.
The assumption that there needs to be central control needs to be broken across the framework world.
English
Sasha Firsov retweetledi

Alright, I'm doing the Mastodon thing, at least a little:
@justinfagnani@fosstodon.org
Reply with your account so I can follow you!
English






