Content pfp
Content
@
0 reply
0 recast
2 reactions

grin pfp
grin
@grin
what's some programming advice that's considered common sense or that you hear often, but is actually bad advice?
18 replies
7 recasts
16 reactions

Max Jackson pfp
Max Jackson
@mxjxn.eth
"you should build it in react"
1 reply
0 recast
1 reaction

Darryl Yeo 🛠️ (at Devcon) pfp
Darryl Yeo 🛠️ (at Devcon)
@darrylyeo
🚩🚩🚩
1 reply
0 recast
0 reaction

Max Jackson pfp
Max Jackson
@mxjxn.eth
I think I can now measure the time I've spent dealing with react bugs in years
1 reply
0 recast
0 reaction

Max Jackson pfp
Max Jackson
@mxjxn.eth
And I'd like to clarify, I don't want that as a career anymore 😅😩
1 reply
0 recast
0 reaction

Darryl Yeo 🛠️ (at Devcon) pfp
Darryl Yeo 🛠️ (at Devcon)
@darrylyeo
Same. So done with this virtual-DOM-diffing optimize-it-yourself useState()/useEffect()/useMemo()/useCallback() create-react-app/CSS-in-JS/state-management-library choose-your-own-adventure. I just wanna write HTML/CSS/JavaScript.
1 reply
0 recast
0 reaction

Max Jackson pfp
Max Jackson
@mxjxn.eth
I have an app that is like 75% built already, in react/nextjs. I'm spending 90% of my time on bugs already. This is hell. I should have had the entire damn app built in two weeks and its been two months. Seriously considering starting from scratch.
1 reply
0 recast
0 reaction

Darryl Yeo 🛠️ (at Devcon) pfp
Darryl Yeo 🛠️ (at Devcon)
@darrylyeo
Highly recommend SvelteKit https://kit.svelte.dev/
1 reply
0 recast
0 reaction

Darryl Yeo 🛠️ (at Devcon) pfp
Darryl Yeo 🛠️ (at Devcon)
@darrylyeo
It had layout and page files before Next.js 13.0 thought it was cool
0 reply
0 recast
0 reaction