I just started using it and love it. Not needing XCode/Android Studio, and being able to load in-development apps on a real device by taking a photo of a QR code with the Expo app is awesome.
I am the author of the article. Only meant to make people chuckle, not to offend. It’s just a silly little one-off article that happened to catch some eyes. Sincere apologies to anyone offended by it. I can see how it is not everyone’s cup of tea.
I wouldn't let the HN rabblement get to you too much, I thought it was kind of amusing and silly. There's a huge survivorship bias favoring those who are willing to be vocal about not being able to find humor in certain things. Personifying technology isn't allowed to be funny? I don't buy it. I say, loosen up.
Yes! I'm very excited to see what the CSS landscape will evolve into over the course of 2018. I'm consistently encouraged by the creativity of the open source community.
Agreed! It is an exciting time for CSS right now. In my next two articles I plan on: (1) covering the origins of CSS-in-JS and CSS Modules, and then (2) developing a strategy for choosing the right CSS methodology or framework for your project.
Thank you for your feedback on the article! I am glad to hear this has not been a problem in your development career, but I cannot say the same for myself. Conversations revolving around when code should be commented vs. refactored are commonplace among a number of my coworker.
I expect articles on this topic are common because it is a problem faced by developers of any language, and the opinions on the topic actually differ quite a bit from author to author. And while I admit I am far from a seasoned veteran in tech blogging, the contentiousness of the subject made me weary about choosing it for an early topic in my blogging career. However, how and when we comment code struck me as an interesting topic that I have opinions on, and which I hadn't seen expressed in the way I attempted to say them.
My goal is to share my thoughts with other developers, so that dialogs are opened, and so that we can all benefit from openly sharing our opinions.
Thanks for your input on the article! In my my experience and research, it is very difficult to find "a rule of thumb [that] is generally accepted" regarding comments. While commenting on classes and public methods the way you describe is a common practice, my argument is that this is a largely arbitrary method of commenting code that can lead to comments that are not always maintained with the same care as the code it is describing. By only commenting when the code is not self explanatory, and cannot reasonably be refactored so as to make it self explanatory, your code will become easier to read and will be less prone to harboring unmaintained, misleading comments.
And I couldn't agree more with your sentiment regarding code that is so "slick and clever" that it requires comments. Readability is better than slick and clever any day of the week.
