Maybe(oz)
boosted
So what do I tell my students? Give up and go home?
So what do I tell my students? Give up and go home?
Greg Lloyd
and 1 other
boosted
Happy birthday to trailblazing American computer scientist Frances Elizabeth Allen (1932 – 2020) who made foundational contributions to optimizing compilers, optimizing programs and parallel computing. She was the first woman to become an IBM Fellow, where she worked from 1957 to 2002 and as an emeritus fellow afterwards. She was the first woman to win the Turing Prize.
IBM Research was recruiting teachers 🧵1/n
#printmaking#womenInSTEM#histSci #mathematician #sciart #compsci#mastoArt
Happy birthday to trailblazing American computer scientist Frances Elizabeth Allen (1932 – 2020) who made foundational contributions to optimizing compilers, optimizing programs and parallel computing. She was the first woman to become an IBM Fellow, where she worked from 1957 to 2002 and as an emeritus fellow afterwards. She was the first woman to win the Turing Prize.
IBM Research was recruiting teachers 🧵1/n
#printmaking#womenInSTEM#histSci #mathematician #sciart #compsci#mastoArt
Joseph Nuthalapati :fbx:
and 1 other
boosted
The Big OOPs:
Anatomy of a Thirty-five-year Mistake – BSC 2025
by Casey Muratori
https://www.youtube.com/watch?v=wo84LFzx5nI
I don't watch or attend a lot of conferences and talks these days, probably for the same reasons you shouldn't watch as much tv and believe it all as you used to.
But to me, at least, this is a deep and serious one worth your time in a fundamental way. If you are a programmer who actually cares about code, anyway.
The Big OOPs:
Anatomy of a Thirty-five-year Mistake – BSC 2025
by Casey Muratori
https://www.youtube.com/watch?v=wo84LFzx5nI
I don't watch or attend a lot of conferences and talks these days, probably for the same reasons you shouldn't watch as much tv and believe it all as you used to.
But to me, at least, this is a deep and serious one worth your time in a fundamental way. If you are a programmer who actually cares about code, anyway.
just small circles 🕊
boosted
Native JS templating: helps JavaScript developers. Direct WASM→DOM: helps EVERY language. Rust, Go, C#, Zig, Swift, Kotlin... all get first-class web UI performance. That's real platform evolution. We shouldn't be adding more JS-specific APIs when we could be opening the web to all languages equally. The web platform should be language-agnostic at its core. #compsci#webdev #webassembly#programming
Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. #compsci#webdev #webstandards#opensource
Direct WASM→DOM access doesn't leave JavaScript behind - JS could use the same fast path! We could even build Fagnani's exact templating API as a reference implementation on top of it. But unlike a JS-only solution, the platform stays open for potentially superior approaches in ANY language. Rust might build something faster. Zig might build something smaller. That's the kind of competition through collaboration that drives innovation. Everybody wins wins wins. #compsci#webdev #wasm#javascript
Instead of standardizing one templating syntax (that'll be bikeshedded to death), give us the primitive: fast DOM access from any language. Let a thousand templating libraries bloom - in any language. Lower-level primitives enable more innovation than high-level APIs. That's the Unix philosophy. Simple, composable, powerful. Build the foundation right. #compsci#webdev #wasm #frontend#unix
Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. #compsci#webdev #webstandards#opensource
Frameworks already solved templating. They're good at it! What they CAN'T solve is the JS monopoly on DOM access. Open that up and watch innovation explode across the entire ecosystem. React, Vue, Svelte - they all work great. But imagine what could be built if any language had direct DOM access. New paradigms, new approaches, new frameworks we can't even conceive of yet. #compsci#webdev#javascript
Instead of standardizing one templating syntax (that'll be bikeshedded to death), give us the primitive: fast DOM access from any language. Let a thousand templating libraries bloom - in any language. Lower-level primitives enable more innovation than high-level APIs. That's the Unix philosophy. Simple, composable, powerful. Build the foundation right. #compsci#webdev #wasm #frontend#unix
The performance argument for native templating is weak - we're talking 2% gains, max. But remove the JS bridge for WASM? That's where real performance wins live. Fix the actual bottleneck. Every DOM call through JS is overhead we don't need. Direct access would unlock true native speeds for web UIs. Imagine game engines manipulating DOM at 60fps without JS overhead. #compsci#webdev #performance #wasm
Frameworks already solved templating. They're good at it! What they CAN'T solve is the JS monopoly on DOM access. Open that up and watch innovation explode across the entire ecosystem. React, Vue, Svelte - they all work great. But imagine what could be built if any language had direct DOM access. New paradigms, new approaches, new frameworks we can't even conceive of yet. #compsci#webdev#javascript
Native JS templating: helps JavaScript developers. Direct WASM→DOM: helps EVERY language. Rust, Go, C#, Zig, Swift, Kotlin... all get first-class web UI performance. That's real platform evolution. We shouldn't be adding more JS-specific APIs when we could be opening the web to all languages equally. The web platform should be language-agnostic at its core. #compsci#webdev #webassembly#programming
The performance argument for native templating is weak - we're talking 2% gains, max. But remove the JS bridge for WASM? That's where real performance wins live. Fix the actual bottleneck. Every DOM call through JS is overhead we don't need. Direct access would unlock true native speeds for web UIs. Imagine game engines manipulating DOM at 60fps without JS overhead. #compsci#webdev #performance #wasm
Native JS templating: helps JavaScript developers. Direct WASM→DOM: helps EVERY language. Rust, Go, C#, Zig, Swift, Kotlin... all get first-class web UI performance. That's real platform evolution. We shouldn't be adding more JS-specific APIs when we could be opening the web to all languages equally. The web platform should be language-agnostic at its core. #compsci#webdev #webassembly#programming
Why add yet another JS templating API when WASM + direct DOM access solves the root problem? Every language could build efficient UIs without the JS bottleneck. More universal than blessing one syntax. Think beyond JavaScript - imagine Rust components with zero overhead, Go templates that actually perform, or C# Blazor without the bridge tax. That's true platform evolution. #compsci#webdev #wasm #webstandards
Some people still weren't born, or came of age recently and are building the future, but never before had the luxury afforded to them and they have never known a world without React, or a world with non-stupidly complex technology so they keep reinventing things like Mustache.
#mustachejs #mustache#javascript #compsci#programming#tech#technology
