orisomething.bsky.social
Advocate for โon-call driven developmentโ and TypoScript
๐ www.orilivni.com
2,623 posts
265 followers
212 following
Regular Contributor
Active Commenter
comment in response to
post
ืื ืืฉ ืื ืืกืคืง ืฉื ืืืชืจ ืืืฆื ืืื ืขืืืื ืฉืืืืื ืชืืื. ืื ืื ืื ืื ืืขืฉืืช ืืฉืืื ืืขืจื, ืืืืจืื ืื ืืืจื ืืื ืชืืื ืืืช ืืืจืืช. ืืื ืงืฉืจ ืฉืื ื ืืืจื ืฉืืืข ืฉื ืืื ืงืื
comment in response to
post
rendering using co routine with cancellation. i donโt think i have ever seen anything that seems good enough for risking using this rendering technique
comment in response to
post
Letโs wait the the browser Scheduler be a thing. But it least with React I doubt theyโll use it
comment in response to
post
Itโs issue I had a lot with the runloop
comment in response to
post
ืืื ืฉืจืืืชื ืชืืื ืืช, ื ืืืจืชื ืืชืืื ืืช ืฉืื, ืืื ืื ืืืืื ืชื. ืื ืขืื ืืชื ืืจืืืื ืคืืืืช ืืืืื, ืื ืคืฉื ืืืื ืืืืฉื
comment in response to
post
I'll give you a different context. I don't think if Wiz (their web framework) would be public, it will be mainstream. The fact it's got good integration with Google services, doesn't mean it would work well outside
comment in response to
post
ืื ื ืจืืืชื ืืื ๐คทโโ๏ธ
comment in response to
post
ืืืื ืื ืฉืื ืฉื ืืกืขืื ืืืืื
comment in response to
post
ืงืืื, ืื ื ืืื ืงืื, ืืืงืฉื
comment in response to
post
ืืืฉืืช ืืืืืช!
comment in response to
post
classes are successor to the prototype chain
comment in response to
post
ืืื ืงืืข ืืืื ืื ืืคื ืฉืืื ืขืฉื ืืฉื ืืกื ืืฉืื ืื ืืืฉืื ืฉืื ืืืขืื. ืื ืืืื ืฉืื ืืืชื ืืฉืคืื, ืืื ืืื ืืงื ืืช ืื ืืืงืื ืฉื ืืชื ืืืืช ืืืื ืื ืืคื ืืฆืื ืืงืืข ืฉื ืดืืื ืืืฉืื ืืกืืืืืช ืื ืกื ืืฉืื ืื ืืืช ืฉื ืจืืช ___ืด
comment in response to
post
Maybe, but Google bought the company I work for anyway, so I might need to get used to anyway ๐คทโโ๏ธ
comment in response to
post
I know because friends. Seriously, even for developers and physicians it's hard
comment in response to
post
ืืืืจ ืืืฉืื ืฉืืื ืืืืื. ืืคืขืืื ืื ื ืืชืคืงืข ืืฆืืืง ืืืฉืืืข ืืื ืื ืืฉืืืจ ื ืจืื ืืืืื (ืืชืืืืืช ืืืชื ืื ืืช ืื ืืืื, ืืื ืืืงื ืืืื ืขืจืกืื), ืืื ืืฉ ืืงืจืื ืฉืื ืื ืืืืจืื ืื ืกืืืจื ืืืชืืืืืช ืฉืื
comment in response to
post
ืฉื ืืฆืืื ืืืืื ืื ืืฉืืื ืื ืืืืื
comment in response to
post
Some of it comes down to SSE on HTTP < 2 sucked. Users were limited to 6 connections max across all tabs.
Data is also UTF-8 only, so if you need binary data, you're fucked.
Some servers have limited SSE support isnt great.
Umm..and probably just familiarity? Most people aren't familiar with SSE.
comment in response to
post
Iโm trying to understand more why SSE is under used in many places in the wild where itโs make very little sense to use WS. I worked in two companies we had a proprietary sync engine with WS, and I really donโt understand why the WS (which needed REST fallback) has been used. No one remember
comment in response to
post
As I said: money, but the 3 questions relevant to the answer
comment in response to
post
Letโs say, Iโm not taking into account the difference between technologies. Yes, it means in SSE the client will need to make a fetch to send data, but other than that, Iโm trying to understand how it translates to money costs. (I donโt care about the milliseconds can saves after WS started session)
comment in response to
post
ืชืืื ืืืจืชื. ืื ื ืื ืกืืื ืืืืจืื. ืืืืื ืชื Space Girls ืื ืืืชืจ ืืขื ืืื ืืืืืจืื
comment in response to
post
ืื ืืขืื ืฉื ืืืงืืืจืื?
comment in response to
post
I'm waiting to DOOM in CSS
comment in response to
post
Me and Claude have been to elementary school together
comment in response to
post
More exiting than "if"
comment in response to
post
You have to take in to account, today, you pretty much can only use Ember as a new project. And if you have issues with the Build system of the Router (for example why in previous place we left Ember) you can't have the full package. Also using Ember inside (for example) React project is too painful
comment in response to
post
I know. And it both Glimmer projects couldn't succeed because the people are invested heavily in Ember (rightfully). But I think it's a bit nailed part of the Ember pain. What used to be a strength of like Ember CLI and the Router are the pain points for introducing it to existing code bases
comment in response to
post
I think you didnโt understand it was a joke
comment in response to
post
I'll try to explain Remix 3 become a new thing which is a remix of what was React Router and a bundler but not a bundler that will stop using React for a new version with is a for of Preact so you use it directly in the browser without a bundler after they bundle the JSX for you
comment in response to
post
ืืืื ืฉืื ืืฉืืื ืืืืืืืืช ๐
comment in response to
post
ืืืืืืืื
comment in response to
post
Theyโre doing this for 10 years