Sasha Firsov

Open source fan and believer in competition as primary driver of progress.
Pushing Declarative Web Application concept

@[email protected]

[Sasha Firsov @SashaFirsov]

Looking for wildest wishes within structural data life cycle https://t.co/xE8FthvDmm via @LinkedIn

[Sasha Firsov @SashaFirsov]

Check out my latest article: Consumer Semantic UI Theme https://t.co/dWiGESVUDv via @LinkedIn

[Sasha Firsov @SashaFirsov]

10 ONNX models in ensembly project for mobile, desktop, and web - my learning scope for today.

[Sasha Firsov @SashaFirsov]

Inwiting #WebDev to bring the IFRAME evolution ideas on

https://t.co/Aoq0MveCoG

[Sasha Firsov @SashaFirsov]

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

[Sasha Firsov @SashaFirsov]

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

[Sasha Firsov @SashaFirsov]

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

[Sasha Firsov @SashaFirsov]

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

[Sasha Firsov @SashaFirsov]

If you think the #HTML templating worth improvement, please take your vote or opinion on #wicg proposal

#webcomponents #customelements

https://t.co/PNjk8j3LGh

[@[email protected] @psvensson]

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

[Sasha Firsov @SashaFirsov]

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.

[Sasha Firsov @SashaFirsov]

Open Source & Saying "No" https://t.co/o4JZN96X1d

[Sasha Firsov @SashaFirsov]

turned off my twitter email notifications, only DMs left. Would visit just once in a while, may be weekly.
Instead, @[email protected] is live.

[Sasha Firsov @SashaFirsov]

I will not participate on Twitter while D*nald Tr*mp has an active account. #VoteWithYourTweet

Use your voice. Join us on https://t.co/F2Cu3kJWjI

[Sasha Firsov @SashaFirsov]

@reznik_andrew @phiggins It is, just one more domain in mastodon federation

[Paul Irish @paul_irish]

Yeah, fuuuuck this.

You can find me on mastodon.

I'm not gonna hang out on Parler 2.0

[Noah Smith 🐇🇺🇸🇺🇦🇹🇼 @Noahpinion]

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.

[Sasha Firsov @SashaFirsov]

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

[Sasha Firsov @SashaFirsov]

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

[Sasha Firsov @SashaFirsov]

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