📝 Articles🗞 News 👓Tutorials 🤔 UI/UX thoughts
console.log returns undefined you actually don’t need to suffer - adding braces, enters, return etc when trying to log something within arrow function?
Have you ever tried that? Answer in comments.ReactDOM.render(<App />,
document.getElementById('root'));
Kudos to @fromaline and waiting for the next one 🔥
🔗 Link
👓 17 minfaker.js and colors) that in return blew up tons of projects that had it as a dependency / peer dependency.
More on the story
Mark's justification TLDR: world is unfair, monetising open source is hard.
This reminds me of a situation when someone started to add ads in a terminal and got into so much problems with the community.
This is an important precedent though, showing that we probably might be relying too much on open source and current module's versioning creates a room for blowups with just minor version auto updates.
At the same time, I can understand the frustration the guy had.
What do you guys think? Share in comments.
My humble opinion here is super simple - if you are not happy with the money you get for your work, then open source is probably not the right place.
PS I also find it interesting that he had a bug in his initial "fuck it all up" attempttransform, opacity and filter properties as much as you can instead of e.g. height/width or position. I’ve personally caught myself relying on position properties too much whereas using transform with translate can be less obvious, but so much better for performance.
Next time you want to increase height/width try using scale and when using eg left consider translate