
☀️ founding engineer at SwiftKitchen 🌔 seeing whats out there former @variable_io
London
Joined June 2015
- Tweets3K
- Following666
- Followers1.5K
- Likes7.9K
Simon Harris retweeted
We're looking for a hands-on Art Director to join Lusion.
If you know someone who’d love to make something memorable with us, ask them to drop us an email!
Simon Harris retweeted
the surprise conclusion of the machine consciousness debate will be that people are machines.
Simon Harris retweeted
Giving away a free membership to fragments.supply — the course I built to teach you to create shaders you love
Gutted to be missing @threejsconf, so this is my way of celebrating anyway 🙏
Reply with your favourite #threejs or #creativecoding work and I'll pick a random winner 24 hours from now
Capability overhang means too many gaps today between what the models can do and what most people actually do with them.
2026 Prediction: Progress towards AGI will depend as much on helping people use AI well, in ways that directly benefit them as on progress in frontier models themselves.
2026 will be about frontier research AND about closing this deployment gap — especially in health care, business, and people's daily lives.
Simon Harris retweeted
can't believe i spent my whole life becoming Good At Computer only for Computer to become Better At Computer
Simon Harris retweeted
Replying to @WigangSsi
I do think there is some truth to this tbh for better or worse
Simon Harris retweeted
I am Malenia. Blade of Miquella. And I have never known defeat.
brutalist poster made in my node powered graphics tool
Simon Harris retweeted
Using React with canvas rendering engines:
simonharris.co/using-react-w…
Simon Harris retweeted
In recent years, a recurring question has emerged regarding the React framework and its ability to foster ecosystems compared to imperative platforms. Specifically, this observation applies to React's integration with Three.js, although it can be generalized to other platforms React interfaces with.
Ecosystems necessitate principles that object-oriented programming (OOP) or classes alone are not designed to provide. The concept of components, operating one paradigm higher, becomes the foundation for enabling ecosystems. This can be likened to the role of composition in libraries like lodash or Ramda, where the underlying paradigm enables the ability to curry and chain functions. While OOP excels at forming and managing data containers, it falls short in terms of composition. When misused, OOP may substitute composition with dependency injection, resulting in the common critique that "the problem with OOP is the implicit environment it carries around. You wanted a banana but what you got was a monkey holding the banana and the entire jungle."
A real-life example illustrates this point within the React ecosystem. Components that have no knowledge of each other can seamlessly collaborate. For instance, in the given example (codesandbox.io/s/portal-shap…), the <PivotControls> component operates within an unfamiliar context without requiring modifications. Previously, the content of the letter shape was a separate demo, but now it integrates effortlessly.
Consider the scenario if we aimed to achieve the same result without React, using something like THREE.TransformControls. This class, like any other, expects your application to adhere to its specific requirements. It disregards side effects and demands injection of all its dependencies, such as the scene, canvas, camera, etc. This approach leads to a lack of self-containment and results in its intrusion throughout the entire codebase—represented metaphorically as a banana-holding monkey in a jungle.
In such an environment, it becomes challenging for anything to truly operate as a self-contained entity. Without a common foundation, it becomes evident why imperative platforms lack ecosystems and only have scattered collections of independent parts.
To illustrate the relationship between these technologies: WebGL operates at a low level, focusing on operations. Three.js serves as an intermediary framework built around WebGL, utilizing classes to encapsulate operations into behavioral units like cameras, controls, and meshes. React, being a high-level framework, enables declarative and self-contained behaviors, facilitating sharing and thereby enabling ecosystems. React complements Three.js in a manner similar to how Three.js complements WebGL.
Simon Harris retweeted
u say banger but i dont feel anything anymore, i close twitter and slide another zyn as i join the architecture meeting to discuss protobuff schemas
the zyn starts to dissolve, i take a sip of coffee
"can u see my screen" i hear as i get a slack notification for a quick sync
Simon Harris retweeted
I'm seeing a lot of bun vs pnpm install speed comparisons but would like to provide some nuance: the absurd perf difference usually is a result of one tool running with a network API call overhead, while the other not.
Simon Harris retweeted
Looking for a Blender/C4D freelancer to top up my studio @variable_io #archviz game for upcoming project concept renders.
Share your work below or visit our website for contact details variable.io/jobs/2023-05-arc…
Simon Harris retweeted
I hope the exact opposite will happen, because the average software of today (ie in the cloud) is embarrassingly slow. Twitter, GitHub, Flickr, etc all like 100x laggier than they should be on today’s hardware. Let’s not settle for mediocre :-)
Replying to @github
“I think the shift to the cloud will happen at such a rapid rate, that in just a few years I predict there will be no more code on your local computer.”
Simon Harris retweeted
Following up on my #WebGPU exploration, here's an article where I compare #GLSL to the soon-to-be final spec of #WGSL, highlighting pain points & hopes for the future of shaders on the web.
📝 Blog post: dmnsgn.medium.com/from-glsl-…
🧮 Example (Canary only): dmnsgn.github.io/dgel/?id=fu…






















