Struggling with this right now at my current job as one of four lead devs tasked with implementing our design system with using a React component library.
I am of the opinion that we only theme the components and provide snippets for how to use them for larger UI elements; the rest are of the mindset that we should be building more components in addition to the library for simple things like: a button that has a chevron in it for dropdown menus; a specific component for combining a tooltip with an info icon; a dialog with just an okay button, in addition to the dialog with both cancel and okay buttons; etc. etc.
Just the other day I got flak for saying no to accepting another version of a tooltip that had a different icon -- what's hard about using the tooltip with the icon you want...
Why does he even need to apologize? If anything, npm should apologize and thank him for revealing a huge issue in their unpublishing policies unmaliciously.
I’ve started thinking package management has too much trust now. Ideally, but probably unpractically, projects should check in their packages like they used to under /lib or /third_party, and be much more suspicious of new package dependencies.
Basically, you would need to start accepting that you are responsible for any dependencies you choose to include. Any upstream changes you would need to evaluate and bring in or patch yourself.
Definitely an impossible task given how broad and deep modern package dependencies are, but at least you’d start feeling the insanity of having all if them in the first place :P.
A very rough prototype of a game library with modern functional React. After seeing only a few game libraries in React, and all being relatively old and class-based, I wanted to learn how to make a React-based version of some simple games.
So far I got pong and some walking/animating sprites on a map, but hopefully will find more time in the future to flesh it out.
One big issue I found out was it’s incredibly difficult, if not impossible, to dynamically add/remove react components in and out of the dom. React very much encourages not touching or modifying “children”, with most apis that do that being obsolete and deprecated.
Thanks! I didn't realize that I had to set it to all regions/countries, and so it was only available in Canada. I updated the app regions and it should be available now, so hopefully you can try it out :).
That wouldn't increase the dynamic range, it's just preventing the overlaps from clipping. Both tracks would still have the same dynamic range, the relative overall volume might be different for the track you lowered/increased to match the other one, but I doubt the transition between the two would be considered increasing the dynamic range.
In order to increase the dynamic range of a mastered track you would have to uncompress/master it in the first place. If you are just decreasing/increasing the overall volume, you would have the same dynamic range just at a quieter or louder listening level.
And of that 10% the vast majority are unread, untranslated Latin. I believe there are more untranslated medieval texts than all of the Roman literature we’ve recovered.
I actually forked and added a JS audio engine to play sound effects, ambience, etc. and it made it back into the official browser version of the game at http://adarkroom.doublespeakgames.com
Definitely should be aware, and I would highly recommend static files over large JS apps. The options are there to have both now with frameworks like Gatsby and Next.
SSR would extract all the styles out for the styled components, but I guess now it would have an advantage as all the html/js would be as well.
My point is, the comparison seems more “js runtime stylesheets” vs “regular static stylesheets.” Styled Components, or CSS-in-JS, isn’t really the main focus here. There are options to get the static stylesheets generated, and I predict most CSS-in-JS frameworks will eventually provide the tools to do so.
This is an apples to oranges comparison -- a run-time compiled stylesheet vs. a statically-generated stylesheet. Styled Components has options for statically-generating their stylesheets (https://styled-components.com/docs/advanced#server-side-rend...), so why wouldn't you compare those?
nitpick - in the Rust example it seems the events are not passed into rendering the events.html template.
https://unplannedobsolescence.com/blog/what-dynamic-typing-i...