It's not only Twitter or politics. I've been playing some Heroes of the Storm as team building with my company and when we are not a full team the toxicity can get intense, with some people going far beyond just in match flaming to harassing with death and rape threats in direct messages long after the match is over.
Mind you this in a no-stakes free to play game and the phenomenon seems common. Sometimes I think our culture is not ready for a substantial part of our communication not to be face to face.
> some people going far beyond just in match flaming to harassing with death and rape threats in direct messages long after the match is over.
It sounds like your company needs to fire these toxic individuals ASAP before the company gets taken to the cleaners in a lawsuit for allowing this to go on.
Well, as IOTA targets embedded devices (I guess the reason Bosch is interested) they should have enough knowledge to form an opinion about transaction sizes:
"transactions in IOTA are 10KB (in contrast, Bitcoin transactions are on average 600B)" [1]
> The first explanation was that the flaw was intentional—that it was meant to serve as a form of “copy protection.” If anyone used this code in their own work, he said, the IOTA developers would be able to exploit the flaw and damage other systems that were using the hash function.
Is this a common practice in the cryptocurrency community? Seems sort of pointless to put flaws and bugs in an open source project as copy protection instead of just keeping it closed source.
Think about what kind of engineer would try to save face by claiming to have deliberately introduced a critical security vulnerability into their payment system.
This article purposefully misrepresents React in favor of the author's own framework Binding.scala, all the criticism are either superficial like class being className (which is a good thing because JSX is not HTML) or has nothing to do with React like JavaScript's dynamic typing system and handling of asynchronous updates.
He also seems to believe that React is framework when it's a library, if his knowledge of React is so shallow that he didn't even read the first sentence on the React website I can't take his opinions on it seriously.
I don't like these kinds of articles which are only thinly veiled advertisements that do not offer any thoughtful criticisms, what I would really like is to hear from someone who has actually worked on a huge project which includes React and what troubles if any they ran into.
I agree, as I read the article I got the same impression. This sentence did it in for me:
> However, after a few weeks, as I became more skilled in React
Do it for a year and a half and I'll accept your criticism. A few weeks is not enough time to claim enough expertise to be making the claims the article makes.
Many people (especially beginners) appreciate automatic updates of their dependencies. If you eject straight away you’ll have to manage them yourself, which is a big turnoff to many.
> Couldn't they just offer a "facebook-certified" starter pack/bootstrap?
No, because Facebook engineers don't use or need that. Facebook only open sources or releases stuff they use—except for this. This is actually the first and probably only open source project from Facebook that they don't use in production.
It's just an example to show what type of code `reactpack` builds, ES6 and JSX with style loading in this case. If you want a more minimal React-like build you can switch out React with lightweight alternatives like Preact or React-lite.
For reference, I build a standalone datepicker module with preact + redux at under 20kb (min + gz)... worked out really well. By comparison, went with regular react recently, and the payload quickly got over 200kb, though I needed a couple relatively heavy libraries for the app in question.
Another point worth mentioning is using react-icons individually (svg based), same for component libraries where you are only using a few components... tends to work out much lighter. Also, if you do use bootstrap as a base css library, work from the source instead of monkey patching the .css output.
Just a small utility for people who are tired of remembering what babel presets or Webpack loaders they need to build a relatively up to date React project.
Looks good! We've been working on something similar at reddit, https://github.com/reddit/node-build, to solve the same issue. It has defaults for react/es6, and I'm also using it without react for building es6 libraries for NPM distribution.
