Twitter | Pretraživanje | |
Paul
Code and aesthetics.
1.510
Tweetovi
191
Pratim
486
Osobe koje vas prate
Tweetovi
Paul 23 h
I'm starting to feel server-side rendering + client hydration serves a small niche. The content can't be too dynamic (hydration issues). If it's very static, rerendering the whole page is wasteful.
Reply Retweet Označi sa "sviđa mi se"
Paul 3. velj
Odgovor korisniku/ci @dan_abramov @sebmarkbage
I like the idea of having multiple representations for known types. e.g. flipping to a visual editor to edit markup/CSS. Dreamweaver/Frontpage v9999
Reply Retweet Označi sa "sviđa mi se"
Paul 3. velj
Odgovor korisniku/ci @cpojer
I was thinking less about the source of truth than the ways we manipulate it (abstraction layers like you said). Text is more portable but not necessarily more compact. Invalid programs are representable with text.
Reply Retweet Označi sa "sviđa mi se"
Paul 30. sij
Odgovor korisniku/ci @retweeewter
Reply Retweet Označi sa "sviđa mi se"
Paul 29. sij
Odgovor korisniku/ci @sebmarkbage
There are good ideas in this haha. Hard to find concrete artifacts of their work. I'm curious what happens if you apply these principles to today's stack (React, TypeScript, etc.)
Reply Retweet Označi sa "sviđa mi se"
Paul 29. sij
Odgovor korisniku/ci @_patlego
You'd have human-readable labels on identifier nodes. Maybe on collections of nodes as well.
Reply Retweet Označi sa "sviđa mi se"
Paul 29. sij
Odgovor korisniku/ci @jakerunzer @darklang @jetbrains_mps
Yeah! I really like what is doing and need to learn more about MPS. I wonder if there's a middle-ground approach where you flip between text and AST. VSCode and IDEs have AST-aware operations which use text as source of truth.
Reply Retweet Označi sa "sviđa mi se"
Paul 29. sij
Odgovor korisniku/ci @_paulshen
Imagine if syntax errors weren't a thing. It'd be huge for engineers new to a language. Version control on AST would be pretty crazy. A function rename would go from N lines to a single operation. And code review!
Reply Retweet Označi sa "sviđa mi se"
Paul 29. sij
Odgovor korisniku/ci @_paulshen
Text has many inherent advantages. Humans communicate with words and are experts at reading and manipulating text. Keyboards are optimized for text entry.
Reply Retweet Označi sa "sviđa mi se"
Paul 29. sij
Why do we code with text instead of something closer to ASTs? 🤔
Reply Retweet Označi sa "sviđa mi se"
Paul 29. sij
The hardest thing about React hooks is useEffect interacting with closures (e.g. setTimeout, event listeners, subscriptions). Most of the time you don't want to reattach when a dep changes.
Reply Retweet Označi sa "sviđa mi se"
Paul proslijedio/la je tweet
Daniel Destefanis 28. sij
It's live! 🥳 Design Lint, my new plugin is available on Figma. Lint your designs for missing styles without logging in or signing up. It's also open source! More information at
Reply Retweet Označi sa "sviđa mi se"
Paul 27. sij
Odgovor korisniku/ci @_idkjs @discordapp
No Reason/OCaml unfortunately. TypeScript, Rust, Python, and Elixir. The language principles are appreciated though!
Reply Retweet Označi sa "sviđa mi se"
Paul 27. sij
Odgovor korisniku/ci @jordwalke @discordapp
Going to be writing a lot of Reason 😀
Reply Retweet Označi sa "sviđa mi se"
Paul 26. sij
Odgovor korisniku/ci @discordapp
I'm going to spend time thinking about tools for product engineers. Mess around with ASTs. Ways to visualize code bases. It's not well-defined yet but I'm excited! More tweets to come.
Reply Retweet Označi sa "sviđa mi se"
Paul 26. sij
I just left an honestly great job at . The team is made of good and talented people with big plans. Let me know if you want an intro! As for what I'm doing next /
Reply Retweet Označi sa "sviđa mi se"
Paul 21. sij
Odgovor korisniku/ci @sabrina
I was just in Tulum this weekend too!
Reply Retweet Označi sa "sviđa mi se"
Paul 30. lis
Odgovor korisniku/ci @jaredforsyth
This seems consistent with TypeScript's decisions (closest one is bivariance). The call to mutate doesn't invalidate the refinement.
Reply Retweet Označi sa "sviđa mi se"
Paul 11. lis
Odgovor korisniku/ci @_rishichandra @reasonml i 3 ostali
I find it useful to have state outside React components. It acts like a global but is convenient to not have to wire to the correct component's state/context. I'd be careful using context for state that changes often.
Reply Retweet Označi sa "sviđa mi se"
Paul 11. lis
Odgovor korisniku/ci @_rishichandra @reasonml i 3 ostali
Obviously biased but check out . Looks like Reductive has been updated to work almost the same so that might be the more popular solution.
Reply Retweet Označi sa "sviđa mi se"