I’m quite attached to stateless functional components too.
1,032 karma · joined October 4, 2017
I’m quite attached to stateless functional components too.
Life’s pretty good if all you have to get really mad about is Microsoft buying github.
I think the most valuable advice in getting rich is from people who are moderately rich.
Advice from people who aren’t rich is stupid.
Advice from billionaires seems irrelevant because their circumstances are so exceptional.
How did the friend of a friend make $20million ... there’s an interesting question.
I could give you advice on how to not get rich.... just make what are in hindsight a constant flow of wrong decisions about things that could have led to financial gain. I’m an expert at that.
Reddit/r/startups
But if you want a quick opinion.... sue them for underpaying you and report it to the tax department and demand full pay for the work you did and also point out to them that you own the intellectual property rights of all the work you did and threaten to sue them if they don’t pay you for it.
Just throw it to a lawyer.
Are you sure you are correct or are you just guessing?
The backticked string style tag shown above already solves all the issues with CSS limitations in reactjs.
Here’s what the article you linked to says:
“Why does this matter? Not all CSS features can be aliased with JavaScript event handlers , many pseudo selectors (like :disabled, :before, :nth-child) aren’t possible, styling the html and body tags isn’t supported etc. With CSS-in-JS, you have all the power of CSS at your fingertips. Since actual CSS is generated, you can use every media query and pseudo selector you can think of. Some libraries (like jss, styled-components) even add support for neat, non-CSS-native features like nesting!”
All addressed by backticked strings in style tags.
What’s the purpose/benefit of generating classes from CSS versus just using CSS?
Couldn’t I just inject a CSS string into a component and put that string into a style tag?
Holy shit there’s a lot of code there. What is it all doing - can anyone summarize?
As far as I can tell it’s main selling point is letting you use pure native CSS in reactjs.
You can do that anyway in ordinary reactjs by writing:
<style>’put your css here’</style>
Put that straight into your react code and you can use any native CSS in ReactJS.
It’s not really clear what this is.
Lack of a giant obvious demo link really annoys me with this sort of thing - “hey look at the code and all these words about our new visual offering”.
Successful features are those that surprise in the easy direction (arrrow functions) rather than in the hard direction (proxies).
Notice their natural interests and try to apply your adult brain to getting them access to more resources to explore and practice those interests.
Aim without hoping to get there, at zero screen time.
Actively personally participate in their interests with them.
Search out and try new hobbies and activities for them to get exposure to.
Make most things optional, but make adult decisions about things that they must continue to do even if they don’t much like it.
Turn off that TV.
Containers aren’t even encapsulated like virtual machines, they are tightly bound to the kernel of the host. Ugh, nightmare.
Then management of all this. Ugh.
Complex, complicated and has necessitated effectively building operating system infrastructure within an already complex operating system to facilitate all this complexity.
Which bit of this is simple?
These “Im the center of the world” posts by VCs really make me want to snark in response.
I think that technology is driven mainly by waves of simplification, not added complexity.
Indeed this is exactly why I don’t like docker because it introduces fresh new deep complexity.