Drew Lyton
2.6K posts

Drew Lyton
@drewlyton
📝 Writer | 🎬 Video Creator | 👨🏻💻 Product Engineer. Currently working on an open source video editor in the browser https://t.co/Im4A4Ruhl0 😅
Charlottesville, VA Katılım Şubat 2011
487 Takip Edilen317 Takipçiler

An update:
Friday is my last day working for my favorite grocery store (H-E-B)
September 11th (unfortunate start date) will be my first day working on my favorite framework
I am incredibly thrilled and honored to be joining @Shopify as the Remix Developer Relations Manager

English

@therealsamreid Lead by example. Can’t push people. Can only pull them 👍
English

@michaelaubry I’m actually exploring a solution to this using the new WebCodecs API 👍
English

Anyone doing video, I just had a brilliant idea (I dont care sharing my secrets)
Cloud editing is not cheap, ideally we do processing on the users machine, there is a problem
WASM sucks because (read the image)
It wont be easy, but you can compile a binary that you have users install @figma does this, then you could interface with the locally installed binary from your web application using some form of Inter-Process Communication (IPC), like a WebSocket connection or an HTTP server running locally

English

@readwise @SparkMailApp @YouTube It is not actually National Pay for Software Day. But it National Grape Popsicle Day, National Sunscreen Day, and National Cellophan Tape Day....so basically the same.
buff.ly/45umY8v
English

It's National Pay for Software Day! Here are 3️⃣ software subscriptions I love paying for:
- @readwise
- @SparkMailApp
- @YouTube Premium
English

Created a little writeup of my experiences testing out some of the new in-browser unit testing frameworks. I'm so excited for the future of these projects!
buff.ly/3BW3Hiu
English

@drewlyton @edbzn @modern_web_dev @playwrightweb @vite_js I believe vite was originally a fork of (or a wrapper around?) the modern web stuff before going it's own direction. As a little bit of history
English

This is the mindset every founder should have 👇
"If somebody came to me and said, 'Hey, we actually [already solved the problem your company is working on]' - I'd be pumped" - @t3dotgg
youtube.com/watch?v=KLSKM0…

YouTube
English

@WickyNilliams @edbzn @modern_web_dev @playwrightweb @vite_js Yeah, it's super slick! I'm using a vite plugin that just allows me to compile TS and everything with vite and so truly there's almost no difference now between test, development, and production. I'm confused why more people aren't talking about WTR!
English

@drewlyton @edbzn @modern_web_dev @playwrightweb @vite_js WTR is excellent. If you configure it right you can have a build-less dev and test setup, and if you need TS you can use the esbuild plugin to transform modules on the fly, since it's so fast. Then use tool of choice for actual release build
English

@edbzn @modern_web_dev @playwrightweb @vite_js @vitest_dev All-in-all, this experience has opened my eyes to @brophdawg11's take that we shouldn't rely on mocking the DOM for our unit tests. Testing our code where it will actually run is the way to go 🤘 buff.ly/3IGc3il
English

@edbzn @modern_web_dev @playwrightweb @vite_js @vitest_dev Will also be keeping my eye on @playwrightweb's component/unit testing feature 👀 buff.ly/3MV3Xoh
English

😱 Thanks @edbzn! I’ll try this one out too! Alright having very little luck with @vitest browser mode sadly
Edouard Bozon@edbzn
@drewlyton @Vjeux You could also have a look at Web Test Runner, a browser-based unit test runner. modern-web.dev/docs/test-runn…
English






