Hi Kashis! This question is pretty similar :)

Makes sense. Thank you. :D

Hi again Carlos! You can learn that and much more from my first answer on my GitHub AMA. :)

Hey Lewis!

This is an awesome question. So I think that managers need to understand the value of using and creating open source projects. A huge part of that is the end result will be better. Just one example is bugs will be found by other developers rather than your users.

I think that business users can see the value better if they see $$$ attached to it. So let's say you have a situation where a library is almost what you need except for some bug or something. So you can say this:

Hey, listen, so this open source software is almost just what we need except for this one thing. So I can either spend a day contributing back, or I can spend 6 weeks building a less-good version myself. What would you like me to do?

Try to bring things back to money/time/etc. Also, I think more of the world is starting to embrace open source. So it really is often just a matter of asking. Good luck!

Hi Alex!

PayPal and others have been using Node.js for YEARS and YEARS. It's beyond ready for enterprise. It's already working. Good luck!

Hey Tobias! I'm so glad you stopped in to ask! I actually was working on a precompiler for css-in-js that would do this, you can find it here: css-in-js-precompiler. It actually works really well and can even track some dynamic values (even if they come from import statements).

I stopped working on it though when I realized that CSS-in-JS is pretty far down on the list of bottlenecks for my application's performance and my users would be better served if I focus my efforts on other areas.

I expect this is the same with many other people (CSS-in-JS is NOT their bottleneck), however, many folks desperately want static css files and for those folks I say that if perf is that important, they should server render their apps! And, if they server render their apps, then they don't need static css extraction!!! Oh my! Because you get critical CSS by default with CSS-in-JS which I think is awesome.

All that said, if you really want to work on it, I'm sure folks would be willing to forego dynamic CSS-in-JS to get css files. If that's what you want, then I suggest emotion.

Thanks again for the question, and thank you for all your work on Webpack! My open collective sponsorship money for webpack was sent again and I'm always happy to see that email come in because I love what webpack is doing for the web. Keep it up!

Hi Peter!

Privilege awareness is realizing that we all have certain amount of privilege, and being aware of how much you have. It would actually take me more time than I have to express all my feeling son this subject, but I think that those with privilege (aka having things others don't when you didn't do anything of yourself to get those things) should really be aware of that fact. Not to guilt them, but to motivate them. For me, my privilege motivates me to help other people. That's one of the reasons why so much of my stuff is free (or I make a free version of it). Because not all people work at a big company that can afford to pay for a subscription to Frontend Masters (for example).

I'd love to chat about this more later, but time is running out on this AMA!

Hi Peter!

Unfortunately, I haven't taken the time to look into exactly what happened, but I think I get the gist. I'm sad that the code of conduct was broken and things weren't dealt with super well (in my unresearched opinion). I think that Ayo will not have the success that io.js had back in the day because things are a bit different. It's more social, so I expect the only people who move to Ayo are those who know or care about the situation. Also many folks will just think that io.js will happen all over again and Ayo will be merged eventually so they have no need to switch.

We'll see though. Thanks!

Hi Horacio! Thanks for the question. I love CSS-in-JS. I think it's made me more productive and create more maintainable components.

To say the focus is not on performance is inaccurate. It may not be as fast as regular CSS, but it has many other benefits while still being fast enough. I suggest you read this blog post by my friend Mark: "A Unified Styling Language".

Good luck!

P.S. I'll also add my talk on the subject which I think justifies some things as well.

Great question Tony!

I LOVE Netlify. I'm a huge fan of the JAMstack concept. I think that if you can manage it (don't need SEO) then it's the way to go (otherwise, SSR with Next.js is the BOMB 💣).

Reasons I love the JAMstack:

1. It's conceptually simple.
2. It's easy to deploy/rollback: Ship a few files to a CDN 🤷‍♂️
3. "Perceived performance" is super because you can show your user something very quickly even if they're on a bad connection or low-end device.
4. It forces you to separate your client from the backend which makes development much simpler.

I hope that's helpful!

I have just started to use Netlify heavily and also LOVE it!

You have reinforced my feelings on the subject and believe we need to move away from the bloat on server side rendering where possible.

Hi Alex, thanks for the question :)

Ummmm.... I'm not huge on backend stuff. I like Express?

I really love React and Next.js. I think those are two really cool technologies.

Sorry, that's probably not super helpful 😅

Hey Carols! 👋

Hmmm... Well, I don't really read much, but I do listen to a lot of podcasts and subscribe to a lot of newsletters (find a list in that link).

I think the best way to find best practices is to experiment and try things. Build build build, then teach. That's been a great way for me to gain experience in software.

I hope that's helpful! Good luck!

Hey PK! Welcome to the JavaScript community!

I think that you've got the right idea to start your JavaScript journey getting into open source! There are so many things you can learn from open source.

As for getting better at it. I think the best thing you can do is just do it a lot! There's no shortcut to experience. It just takes a lot of time. I did answer a similar question on my GitHub AMA which you might find interesting (also this one).

Also, you might be interested in this blog post as well.

Good luck!

Hi Eli!

So, I represent PayPal on the TC39 and try to keep up with what's coming in the language. I think that JavaScript will continue to cater to people of varying preferences. We're seeing a lot of attention on classes recently, but I'm looking forward to some other enabling features (like realms) and some nice functional programming syntax (like es-pipeline-operator).

Often people will ask me when we'll get types in JavaScript. I think that will never happen. One of the problems is we need backward compatibility and that's often a real show-stopper for some things we're doing.

I'm excited about the features coming into JavaScript. I think the language is so much fun to write now. Huge thank you to Babel for making it accessible to those of us still supporting IE10 or lower.

Hey David! How are you doing!? :) Thanks for the question.

I type really fast :P also, I type things and use things that make it so I don't have to type as much in the future. My GitHub AMA, oss project generator, semantic-release, prettier, etc. etc. etc.

Also, I should mention that even though I churn out a lot of stuff, I don't think I really do a whole lot more than other folks. I just make what I do public (if I can). Recording talks and workshops, doing tech chats and livestreams, and open sourcing as much as I'm able to (even work stuff) gives the illusion that I'm doing a ton of stuff.

Good luck!

Hi Pulak, I think this is a similar question: hashnode.com/ama/with-kent-c-dodds-cj6qfi23p002z9…

Thanks!

Hey Jon! Thanks for the question! So, I can appreciate "one format for all," but I just have my preferences. I don't like enforcing those preferences on others (I'm loosening up my stylistic ESLint rules thanks to prettier), but I've got them, and because it's so easy to auto-format with prettier and configure it the way I like, I'm sticking with that 😀

Hey Marcus!

I actually have thought about some sort of library or tool. I think something that could make controlled components and prop getters easier would be nice. When I was building react-toggled I realized I was copy/paste/modifying quite a few things that would be kinda nice to just have in a library.

So maybe someday :) I definitely want to see more components using these patterns in the future, so I'm motivated :)