@donmccurdy

9 Followers
197 Following
174 Posts
Graphics, data visualization, and web technologies. New York Times R&D. Contributor to #glTF, #threejs, and #aframevr. he/him.
Websitehttps://www.donmccurdy.com/
Twitterhttps://twitter.com/donrmccurdy
GitHubhttp://github.com/donmccurdy/
“Toot!” is the good client app for iOS. Icon looks half baked, but the app itself is really polished.
Three.js is now also available in the Engine dropdown on https://physicallybased.info/ so you can see values relevant only to Three.js #threejs #webgl #rendering
Physically Based - The PBR values database

A database of physically based values for CG artists

Physically Based

Anyone know what happened to pxlfd.me? I'd created an account in 2019, kind of forgot about it, and the whole site just seems to have disappeared sometime since then... didn't lose anything, but I'm surprised.

#pixelfed

There's A LOT of discussion about content moderation right now and very little of it touches on the fact that we've all lived on the big social sites for the last decade-plus thanks to the massively exploitated labor of mostly-invisible moderation workers. The social web at scale wouldn't have happened without these laborers, who in addition to shit wages, have been exposed to literally every imaginable horror.

If we're remaking this world, let's do better on that front.

if you've worked on a documentation website for a #typescript library, would love to hear what's worked for you, what hasn't, and any ideas here. 🙂

tl;dr —

1. generate API model with "API Extractor" (microsoft/api-extractor)
2. convert API model to display-ready wire format (greendoc/parse)
3. render the API model using framework of choice (greendoc/svelte, ...)

Particularly with #Svelte, the output can be static HTML, or SSR, or a SPA... you choose. And hopefully the lift to support other frameworks, or just static HTML and markdown, is light enough.

Weekend #projects — I've been frustrated by existing tools for documenting #javascript and #typescript libraries. Won't go into details on the frustrations, but I really want:

1. type-safe JSON representation of API
2. composable pieces to format the API as HTML/MD

Here's where I'm headed:

https://github.com/donmccurdy/greendoc

GitHub - donmccurdy/greendoc: 🌿 An adaptable system for generating documentation of TypeScript and JavaScript APIs.

🌿 An adaptable system for generating documentation of TypeScript and JavaScript APIs. - GitHub - donmccurdy/greendoc: 🌿 An adaptable system for generating documentation of TypeScript and JavaScript...

GitHub
A partial entry into the #projects stream: a few years ago I got to a pretty solid alpha place with making maps for Kindle Paperwhite. (I love e-ink, and my impetus was... explore cities, with a map, but no smartphone.) With the forthcoming Kindle Scribe (an full-on e-ink tablet) I'm strongly considering baking this project into a place where I could get folks good maps for a bunch of major cities. (Maybe also #maps)

👋 Hey, friends! I should do an #Introduction

A few things I love:

❤️ creating things on the web
❤️ exploring novel interfaces
❤️ turning data into meaning
❤️ empowering devs with AI

I'm currently exploring novel UIs + playing with ML on GitHub Next (a tiny R&D team within GitHub).

Previously, I did client work with pudding.cool and spent many years building dashboards for startups.

A long time ago, I worked in a lab, training to be a prison psychologist, but that's a story for another day...

hm it's right there, this should be correct...