software engineer; https://teapaw.org/t.co/qWiFmjqMOj; front-end, half back-end, one third designer;
🌍
Joined December 2008
- Tweets6.1K
- Following436
- Followers1K
- Likes14.9K
chewingCode retweeted
bitcoin's inception is magical:
- pseudonymous founder
- Satoshi never spends his sats
- leaves at right time
- perfect timing post-2008
- "Chancellor on brink of bailout" stamped on 1st block
- ideal monetary policy (21M hard cap, 4-year halving)
- near perfect tech from day 1
chewingCode retweeted
When everyone is debating how X framework is better than Y language, remember what Why the Lucky Stiff taught us:
> when you don't create things, you become defined by your tastes rather than ability. your tastes only narrow & exclude people. so create.
chewingCode retweeted
Time for a new mind-bending project!
#QLOCK — A JavaScript Quine Clock
aem1k.com/qlock
It displays the current time in a seven-segment style, embedded within its own JavaScript source code.
🕔 🕝 🕢 🕤 🕑 🕜
(321 bytes)
chewingCode retweeted
Laravel is fine.
Rails is fine.
React is fine.
Vue is fine.
Svelte is fine.
Use whatever tools you like.
You can build amazing products with any of these. Don't get lost debating tools and forget about the "building the product" part.
chewingCode retweeted
Dan Abramov's "React for Two Computers" was a seminal talk. It makes the case for the inevitability of the Server and Client component paradigm.
Every time you visit a page, you're witnessing computation distributed over time and space. When a page gets server-rendered, Computer 1️⃣ did some work, sends it to you, the client, and then Computer 2️⃣ can pick up from where 1️⃣ left off and do more work.
This is the 'fundamental physics' of rendering. Even if you claim "well, I only have a client-rendered app, your server components make no sense…" Imagine I turned off SSR for the @vercel dashboard. Visitor gets linked to the Usage page and gets this:
That 'static shell' of the page would have been built in a 'distant time and space', namely build time and in a server environment (the CI computer). The only distinction is that a static page is Computer 1️⃣ being in 'memoization mode'. For each input, there's a constant and equal output.
Whether Computer 1️⃣ gets activated 'on-demand' (SSR upon request), or at 'build time' (static exports or partial pre-rendering), is irrelevant here. The fact is that React has evolved to be able to model this handoff.
It's indeed possible you refuse to leverage the power of 1️⃣ altogether, which you're free to ship: a completely blank page that starts up a bunch of `<script>` bundles on 2️⃣. That case, however, is somewhat exotic these days. If a CDN served your page, you'd be going out of your way to not give your customer a fast FCP (first contentful paint)… And you'll really want to ensure that Computer 2️⃣ has data locality, otherwise after the script load it'll have to go back and forth to some other computer over the internet to `fetch` some data, wasting time.
I believe this paradigm is so fundamental that it'll outlive React. If tomorrow we switched to Rust SSR + a wasm client runtime for interactivity, you'd want to account for the handoff and distance between the computers involved in the client-server exchange. If React didn't exist, it'd be re-discovered.
I really enjoyed this talk and I'll likely watch it again. It's that good, check it out:
youtube.com/live/T8TZQ6k4SLE…
ALT A static shell of the Vercel dashboard showing the skeletons of the usage page
chewingCode retweeted
Need a file from a different branch in your clipboard on a mac?
git show main:src/containers/Settings.tsx | pbcopy
chewingCode retweeted
W
"I will make certain declarations which I am satisfied are useful and are necessary to do justice between the parties. First, that Dr Wright is not the author of the Bitcoin White Paper. Second, Dr Wright is not the person who adopted or operated under the pseudonym Satoshi Nakamoto in the period 2008 to 2011. Third, Dr Wright is not the person who created the Bitcoin System. And, fourth, he is not the author of the initial versions of the Bitcoin software. Any further relief will be dealt with in my written judgment. I will extend time for filing any appellant's notice until 21 days after the form of order hearing, which will be appointed following the hand down of my written judgment and I ask the parties to seek to agree an order giving effect to what I have just stated."
