
{PuruVijay}.svelte
13.7K posts

{PuruVijay}.svelte
@puruvjdev
💼 Schneider Electric. ai slop solver, performance freak. @sveltejs team. 12 years experience. Conference Speaker ex-@stackblitz, @beyonk.


Qwen3.8 is launching and going open-weight soon!🌐 With a massive 2.4T parameters, this model is continuously evolving. We believe it’s one of the most powerful model available today, compatible to leading frontier AI models , second only to Fable 5. You don't have to wait to test it. Just now, the Qwen3.8-Max-Preview made its debut on Alibaba’s Token Plan, Qoder, and QoderWork. Be among the very first to try it out. Can't wait to hear what you build. Stay tuned! 🚀 Token Plan international:qwencloud.com/pricing/token-… China:platform.qianwenai.com/pricing/token-…




ORBIT ACHIEVED. 🚀 Vikram-1 Test Flight-1 has reached orbit. India's first privately developed orbital rocket has completed its final burn and injected its payloads into a ~450 km orbit, making India the third country in the world with private orbital launch capability. History is made. 🇮🇳 #Vikram1 #JourneyToOrbit #SkyrootAerospace








There are different ways to keep libraries small. You can make them incrementally additive the way Preact ships a core and then install only the addons you want (hooks, signals, react-compat). You can have them treeshakable so you only pay for what you use. Solid 1.x was really good at that. Almost everything was gated, one install but only the code paths that could be hit based on imports are included. If you make certain global flags only writable there, code can be pruned at a conditional block level. This is super powerful when the boundary between features isn't so clean. The end result is both frameworks can make a counter example using signals in slightly under 5kb minzipped. Solid 2.0 unfortunately is a lot less treeshakeable because of how streamlined the API is. Because no single API determines whether there is async in the system.. no createResource/Async or `use`, lazy and Loading(Suspense) are completely optional, and no explicit transition wrapper, and no specific keyword like await, the async part isn't treeshakeable or addable. If a promise or async iterator makes it into the graph in anyway Solid handles it properly. And it can get in to the system anywhere that it makes sense to. So that same example now is just under 10kb minzipped because almost 5kb of async code can't be automatically dropped and it doesn't make sense to have special version for it because it wouldn't compose with the ecosystem, async like the passing of time itself is pretty unavoidable. So we won't be winning any of the toy app size comparisons anymore. But the runtime packs the atleast same capability of systems much much larger. So its a choice we will have to live with. Here was the journey: github.com/solidjs/solid/…



Statement on the MEA Official's Remarks on Prime Minister Modi’s Media Engagement

Ok codex is good


