Anyone remember:
- FTP’ing a PHP script to your server
- put the URL in the address bar
- and seeing your web page
And if it didn’t look right you could just edit it and do it again?
<iframe> is the original async primitive on the web.
Something on your page isn't ready yet? Put it in an <iframe> and let the browser load it in a separate request.
It's an async HTML "include".
No "suspense", no special compiler or wire format. Just good ol' HTML and HTTP.
React hooks are full of footguns that make it easy to introduce bugs in your code.
I have trained hundreds of developers on React and how to use React hooks effectively.
Here are a few of the most egregious and common ways people misuse hooks.
1/n
Honestly, it makes a ton of sense for Microsoft to buy GitHub. After this acquisition, they will control:
- VS Code
- TypeScript
- Electron
- GitHub
This puts them pretty much front and center of the modern development stack for a lot of people.
I’m growing increasingly disillusioned with React hooks. Everything about them just seems so unnecessarily complex.
It’s just so funny because for a while there I thought they were great.
Stockholm syndrome.
If coding doesn't feel like being totally lost and having no clue what you're doing, followed by hours of trying different things and short bursts of stuff kinda working, you have at least another level to master before calling yourself a programmer.
Under @satyanadella, @Microsoft has developed an "Alternative Interview Framework" that involves:
- 2 interviewers at a time
- sharing questions with candidates ahead of time
- working on actual problems the team is facing
- blind feedback
So good! 👏
I know you think you like React hooks. useState, useEffect, useMemo, useEffectEvent.
You like the way they compose. The way they're "just functions".
I will destroy them.