正在加载视频...

视频加载失败

💧 Technical Showcase: A piece of WebGL history, rebuilt for WebGPU. Evan Wallace's 2011 water demo helped convince Dylan Field (Dylan Field) that Figma could exist. Yong Su (jeantimex) ported it to WebGPU with full caustics, raytraced reflections, and the GitHub repo to study. 🔗 #WebGPU #WebGL #GraphicsProgramming #Shaders #Figma

18,778 次观看 • 6 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Dylan Field on his biggest learnings from Figma’s 0 to 1 phase Figma’s 0 to 1 phase was notoriously long. The company was founded in 2012, but it took four years before they publicly launched their product in 2016. Figma co-founder Dylan Field reflects on what he learned from this period: “From August 2012 to June of 2013, that was a period where we were pivoting constantly trying lots of things. But then we had a thesis, felt like there was an opportunity, and started to build it out more. Then it was like, ‘Okay, this is going to take a while.’ In retrospect, we were lucky to have raised money and have resources, but I should have hired faster once we started to get signal from the market that we had product/market fit.” Dylan recalls going to a user study with a friend who was a designer at Coursera. The following day, his friend sent over a 12-page document listing all of the stuff he wanted Dylan to build into Figma. “I should’ve taken something like that and gone, ‘Okay, this is clear product/market pull.’ The market was pulling the product out of us. I should’ve then gone and hired faster. But instead I was still very cautious. And so that’s something where I wish — if I could go back in time — we would’ve gone a little faster there.” Sam Altman gives similar advice: “In the early days, when you’re experimenting and zig zagging, you’re like a fast little speed boat and want to be able to turn the whole company on a dime. You can’t do that if you’re a big company—cash burn aside, which is another problem. The flexibility of the company basically decreases with the square of the number of employees, so you want to stay really small until you’re sure things are working. Once things are working, then you can get really big.” Video source: Y Combinator (2025)

Startup Archive

39,718 次观看 • 1 年前

Around $100 trillion in global assets runs on what Chris Hladczuk calls “human duct tape,” accountants in back offices stitching together data that lives across QuickBooks, Excel, Bill, and a patchwork of other services. His startup, Hanover Park, aims to replace that legacy stack with AI. Find out how they went from $1B to $20B in assets administered in just 15 months. PLUS a fresh look at Jason’s prescient (except about COVID) March 2020 chat with Figma CEO and co-founder Dylan Field. 0:00 Hanover Park & the fund admin problem 3:32 Why funds outsource instead of building 5:44 Why fund accounting is so complex 10:38 The "one-click migration" goal 10:48 Northwest Registered Agent - Get more when you start your business with Northwest. In 10 clicks and 10 minutes, you can form your company and walk away with a real business identity — Learn more at 13:51 Context vs. intelligence gaps 16:11 No PMs, No Designers 20:46 Vanta - Get $1000 off your SOC 2 at 23:18 This is a $100T opportunity 25:36 Flashback w/ Dylan Field of Figma 29:15 Sentry - Your team should be focused on shipping features — not chasing down bugs. New users can get $240 in free credits when they go to and use the code TWIST 31:22 Pre-AI enterprise security worries 36:30 SaaS overload and SaaS burnout 37:30 The evolution of Figma pricing 42:38 The rise and fall of Mahalo dot com 51:38 The work-from-home revolution begins cc: Chris Hladczuk, Hanover Park, Dylan Field, Figma, @jason, alex 🏴‍☠️🇺🇸🇺🇦, Lon Harris 🎥 Watch the full episode here 👇

This Week in Startups

13,955 次观看 • 20 天前

I built a Three.js rendering study inspired by Tiny Glade’s painterly aesthetic, and got it running at 120fps in the browser. Over the past few weeks, I’ve been studying how stylized games achieve that soft, handcrafted look in real time. Tiny Glade was a huge inspiration, and I wanted to use the browser as a constraint: no compute shaders, no native GPU access, and single-threaded JavaScript. As part of this study, I implemented: - GPU-driven instanced brick walls with procedural noise jitter and elastic build animations - Tree, bush, and flower rendering with billboard card expansion, wind sway, and grow animations - Procedural grass with terrain conformance and interactive push deformation - Animated water with layered noise, interactive ripples, and Fresnel-based reflections - Procedural terrain with slope-aware triplanar materials, dirt paths, and rocks - A 7-pass post-processing stack with TAA, bloom, depth of field, painterly filtering, ACES tonemapping, 3D LUT color grading, and film grain The hardest part wasn’t writing any single shader. It was making all of these systems work together at high frame rates inside WebGL, where every millisecond counts and performance problems compound quickly across animation, materials, post-processing, and scene management. Some techniques in this study were inspired by analyzing Tiny Glade’s rendering approach, while others were original implementations built from scratch from visual reference. That contrast taught me a lot: recreating an effect is one challenge, but designing your own shaders and systems to achieve a similar feel is a very different one. This is a private educational rendering study. Some temporary placeholder content is being used during the research phase, and any public or production version would use original or properly licensed assets. Huge credit to Pounce Light for the incredible art direction and rendering work in Tiny Glade: Three.js #gamedev #webgl #threejs #rendering #graphics #realtimerendering #shaderdev

Ibrahim Boona

58,625 次观看 • 3 个月前