Nate Jacobs

Dev things at @shopify. Formerly @hearsparkbox.

[Nate Jacobs @nathanAlan]

@myockey noted

[Nate Jacobs @nathanAlan]

There are _so_ many reasons to use deno, but lint and fmt with zero config is reason enough.

[Nate Jacobs @nathanAlan]

@myockey Yeah I was jk. Clearly JS. 🙃

[Nate Jacobs @nathanAlan]

@BryanEBraun

[Anthony Frehner 🐽 @frehner_a]

If you want external import-map support (eg an import map that can be referenced by a script src tag) then please give the first comment in this issue a thumbs up! Otherwise it’s going to be removed from the spec :(

https://t.co/r0f6ohSVNs

[Nate Jacobs @nathanAlan]

@anastasialanz

[Ben Callahan @bencallahan]

I'm excited to be doing an overview of the Design System Maturity Model 2 more times this year! It's just an hour-and-a-half out of your day, but I believe it will reframe how you think about the #designsystem work that's necessary for healthy maturity.

https://t.co/D0IuHy26kL

[Design Tokens Community Group @DesignTokens]

📣 The Design Tokens Format Module specification reaches First Public Editor’s Draft status.

https://t.co/5orsbu498w

📝 We wrote this draft in partnership with design tool vendors, and are now collecting feedback from the community 👐🏻

Full announcement: https://t.co/SYmoguiQed

[Nate Jacobs @nathanAlan]

@buildsghost I think `var` is better than `^` but could still cause confusion. `^` looks like exponentiation to me. Is there a reason to avoid more keyword options like val, value, topic, etc? Restriction on introducing keywords?

[Nate Jacobs @nathanAlan]

@cromwellryan @BryanEBraun 😆 I'm dying over here! Bryan is a mad scientist.

[Nate Jacobs @nathanAlan]

@BryanEBraun @jcubic Just a couple small modifications to the source code and here's a demo of accentColor used to render full color. I think I still like the original demo better though! 😀

[Bryan Braun @BryanEBraun]

I made a webcam filter out of html checkboxes.

Try it out here: https://t.co/1lBHfEgmhw

[Nate Jacobs @nathanAlan]

@cromwellryan It’s a lot of pressure but I know you can handle it.

[Nate Jacobs @nathanAlan]

@jayphelps In all seriousness, I'm excited about deno. I hadn't thought about window being kinda weird. Or this incompatibility. But duck typing is not an actual standard while deno is attempting to converge on standards. I appreciate your point of view.

[Nate Jacobs @nathanAlan]

@jayphelps

[Nate Jacobs @nathanAlan]

@jayphelps @matthewcp @rauschma 👀

[Nate Jacobs @nathanAlan]

Happy to see deno getting more attention. ❤️

[Chrome for Developers @ChromiumDev]

🎬 In this brand new HTTP203 @DasSurma gives @jaffathecake an introduction to Deno.

They talk about:
➡️ Module and package management
➡️ Security & permission model
➡️ Web compat
➡️ ... and more

(Did you know that Deno supports `localStorage`?)

👀👇
https://t.co/VO32UTONm0

[Nate Jacobs @nathanAlan]

@anastasialanz Open a PR!! 😄

[Nate Jacobs @nathanAlan]

Spent some time with React #hooks over the weekend. I have to admit, I am a little excited. https://t.co/9LzEFwefTJ

[Nate Jacobs @nathanAlan]

@patrickfulton @_alanbsmith If the popup is unique to your app, then I would ask if the composed structured is optimal. Does the right team have ownership of the feature? Any way you slice it, communication and documentation will always help! But that's just my experience, there are probably other ways. 😀

[Nate Jacobs @nathanAlan]

@patrickfulton @_alanbsmith This is always tough. Things I've done in MFE...

Have the owning MFE handle UI updates by passing messages via pub/sub or custom browser events.

For more coordinated things, having a library that all MFEs use can provide a central abstraction around singletons or queues.