RT @PixiJS: We’ve just released PixiJS Create – a CLI tool that makes setting up PixiJS projects faster and easier! 🚀 Choose from bundler t….

RT @PixiJS: 🚀 #PixiJS v8 brings a massive performance boost with the new ParticleContainer! Even faster than v7! Render 1M+ particles, perf….

On @PixiJS's Discord this morning, a dev was having an issue with how to use HTMLText with Renderer's Extract functions (image, base64, etc). There are some gotchas because HTMLText is rendered async. Here's an example how to do it:.

RT @PixiJS: 🚀 #PixiJS v8 is out! 🌟 Enjoy over 200% performance boosts with our new #WebGPU & #WebGL renderers 🎉 Raising the bar for #2D #We….

Fun npm bug I found today:. Two identical packages, both made of 60K files and the same download size, but one is a flat list the other is nested in various folders. Install time is 5s (flat) vs 85s (nested). Yarn showed a smaller delta. Any thoughts why?.

By contrast, Figma’s dev experience is a delight. Complete docs, good examples, paved path tools, sane extension format, modern runtime. I wish publishing was more automated, but it’s solid. Now that they own it, Adobe should throw everything away from CC and copy Figma. Please!.

Aside: AE needs an overhaul. Text layout and vector rendering are so dated when compared to more contemporary software. Preview render is sluggish and ugly. Interoperability stinks for anything other than PS. There has to be a startup disrupting this software somewhere??.

If you have to make Adobe extensions for your job, I’m sorry! I’m building an After Effects tool now and it feels painful. In 2023, I can’t use the VSCode extendscript debugger on Apple Silicon without crippling VSCode with Rosetta.

Adobe’s dev experience is garbage. Decades of poor docs, outdated examples, changing terminology every few years (CEP, CXCS), searching random forums, half-baked publish tools (exchange, developer console), bad CLI and debugging experience, horrible ES3 runtime.

RT @PixiJS: After many years, PixiJS has decided to refresh our branding 🧵

RT @PixiJS: We just wrapped our 3rd #AMA on Discord with Mat Groves (@Doormat23) and Matt Karl (@bigtimebuddy) where we talked about v7, v8….

A new feature of @PixiJS v7 is that I'm excited about is support for Web Workers. Here's an example: Lots of performance opportunities here. I'd likely use this for Electron apps to not slow React/DOM rendering.

What ideas do you have #STEM Twitter? What type of opportunities should she consider? (3/3).

She's deeply motivated by a company or team that is mission-driven. She cares a lot about the negative impacts of industrial chemistry and its relationship to racial and environmental justice. She's the most thoughtful and talented written communicator I know. (2/3).

My spouse is looking for a new job. She has a PhD in chemical oceanography from MIT, has worked in environmental consulting and most recently in safer consumer products regulation at CA EPA. She's skilled in R, SQL and Tableau and analytical data and incredibly hard-working (1/3).

I just published Rendering Fast Graphics with PixiJS @PixiJS.

As someone who's use Adobe software for 2 decades, what the uninitiated don't understand is that Adobe is the Comcast for professional designers: bloated bundling of services, overpriced, giving users things they didn't ask for, no alternatives, and unresponsive to real needs.

Keep your dirty CEP hands off Figma.

Looking for some dancing ants in @PixiJS? The project get this request sometimes and it doesn't have anything built in, so I built a demo using TilingSprite objects.

I've been working with @hypermatic over the last month to request more features in their Convertify plugin for @figma. Adam has been incredibly responsive to our needs. Highly recommend this company and their products.