Jesse Pence

3.5K posts

Jesse Pence banner
Jesse Pence

Jesse Pence

@JessePence5

JavaScript Framework Nerd

Vancouver, WA Katılım Şubat 2020
1.8K Takip Edilen984 Takipçiler
Sabitlenmiş Tweet
Jesse Pence
Jesse Pence@JessePence5·
So, in order to explain RSC's, I wanted to give some background about the development of JavaScript promises, streams, workers, etc. With each concept, I kept finding myself jumping back and forth through time. So, I decided to start at the beginning. jessedit.tech/articles/react…
English
2
0
9
2.6K
Jesse Pence retweetledi
Ben Lesh
Ben Lesh@BenLesh·
A lot of smart folks have been working on this proposal to bring native signals to JavaScript. …Also I’ve been helping the smart people. Have a look. github.com/proposal-signa…
English
21
129
728
114.7K
Jesse Pence
Jesse Pence@JessePence5·
@fredkisss Be genuinely curious about the other person. Most people love to talk about themselves. If you actually want to talk to them, you probably have questions. Just ask. You don't want to make it like an interview though, so try to also relate it to yourself with short anecdotes.
English
2
0
3
231
Fredkisss
Fredkisss@fredkisss·
How do you talk to people in real life and hold conversations with someone ? I can barely start a conversation and every time, I either just spew out 1-2 sentences before having nothing left to say. If you catch me in a long conversation, it’s the other one doing 78% of the job
English
10
1
9
2.1K
teej dv 🔭
teej dv 🔭@teej_dv·
"I use JavaScript for backend development," I state proudly to the unkempt, bearded developer. He swivels around in his ergonomic chair with a smug look, ready to mansplain with extreme precision. "Actually," he says with a smirk, "JavaScript is just for the frontend. You should use a real backend language." I don't miss a beat and reply with a grin, "I use Node.js, a runtime that allows JavaScript on the backend. It's JavaScript, but it's not just for the frontend." The smile quickly drops from the developer's face. His fingers begin twitching and he stares at the screen as he slumps back in his chair with a dazed look. As he struggles to find his words, he mutters "But... but JavaScript is single-threaded!" I interrupt his response with "and Node.js is built on the Chrome V8 engine, which is highly efficient and uses non-blocking I/O. Even if you were correct about JavaScript, you won't be for long when it comes to Node.js."
English
20
15
359
74.5K
Jesse Pence retweetledi
Nikhil Saraf
Nikhil Saraf@nkSaraf98·
This is a typical vinxi config for a SSRed Solid app. solid-start's actual config is not very far from this. I just want to get a sense of how much of this makes sense intuitively. Feedback?
Nikhil Saraf tweet media
English
6
2
18
2.9K
Jesse Pence retweetledi
Devon Govett
Devon Govett@devongovett·
👀
Devon Govett tweet media
QME
5
6
103
14.2K
Jesse Pence
Jesse Pence@JessePence5·
@JLarky I'm honestly just surprised that IE6 usage has finally dropped that low.
English
0
0
1
84
JLarky
JLarky@JLarky·
JLarky tweet media
ZXX
3
0
5
889
JLarky
JLarky@JLarky·
your would expect querySelector to be 100, but it's not 🤯
JLarky tweet media
English
13
2
44
12K
Jesse Pence retweetledi
Danny Moerkerke
Danny Moerkerke@dannymoerkerke·
Here's a new demo of Custom States that works in all browsers. Chrome, Edge, Safari Tech Preview with CustomStateSet feature flag and Firefox 122 with dom.element.customstateset.enabled set to true. Codepen link 👇
English
2
7
16
3.5K
Jesse Pence
Jesse Pence@JessePence5·
@WInvincible4397 @teej_dv V8 is a JavaScript engine. The code is multithreaded, but the event loop API that it exposes is not. Node.js is a JavaScript runtime built on V8. It provides worker threads, and it also runs on libuv which uses a thread pool. Any questions?
English
1
0
2
140
WInvincible
WInvincible@WInvincible4397·
@teej_dv node is single threaded... always has been... multithreaded node is a nightmare to get right
English
2
0
3
5.2K
Jesse Pence retweetledi
Ben Lesh
Ben Lesh@BenLesh·
A concise example of why I really don't like decorators that much. IMO, decorators should have been metadata only. We already have enough ways to duck-punch JavaScript into oblivion. 👊💥🦆
Ben Lesh tweet media
English
33
24
283
57.3K
Jesse Pence retweetledi
Ryan Carniato
Ryan Carniato@RyanCarniato·
Ever wonder about how we got here? Tomorrow's stream I'm going to look at what's been going on the past several years in front-end web dev, and what that means for the future. youtube.com/live/aA7Xeh7WG…
YouTube video
YouTube
English
4
18
138
19.1K
Jesse Pence retweetledi
Tanner Linsley
Tanner Linsley@tannerlinsley·
This is very important, so 👀. I’ve believed for a while that commoditizing end to end the setup, bundling utilities, low level primitives and consumption of RSCs is required for them succeed and actually grow beyond one of two routers on a single framework running on canaries.
Devon Govett@devongovett

Made some progress on supporting React Server Components in Parcel over the weekend. Will be very different from other implementations: • Not a framework. No router, server, networking layer, cache, etc. — just the raw bundling primitives. • Use with any server/router (eg express). Instead of an HTML file, your server JS file is the entry point. In each route, dynamic import a server component and render it to HTML or RSC payload. Client components and styles used by that server component are optimally bundled and loaded automatically. • You can fetch a server component whenever you want, with any networking layer. Doesn’t need to be on a route boundary (eg infinite scroll), can be sent via a web socket if you want, etc. My hope is that by exposing the raw primitives, it’ll be easier to see how RSC works and enable more freedom to experiment. Parcel is particularly well suited for this because it already supports multi-target module graphs with a single entry point. Will share more soon!

English
0
1
66
16.4K
Jesse Pence retweetledi
Dev Agrawal
Dev Agrawal@devagrawal09·
YES PLEASE RSCs have a very strong future if they can be used and adopted with much more minimal and customizable setups Which means commoditize bundling and generalize routing Can’t wait for Parcel, Vinxi, Turbopack, and hopefully Bun to make RSCs a first class citizen
Devon Govett@devongovett

Made some progress on supporting React Server Components in Parcel over the weekend. Will be very different from other implementations: • Not a framework. No router, server, networking layer, cache, etc. — just the raw bundling primitives. • Use with any server/router (eg express). Instead of an HTML file, your server JS file is the entry point. In each route, dynamic import a server component and render it to HTML or RSC payload. Client components and styles used by that server component are optimally bundled and loaded automatically. • You can fetch a server component whenever you want, with any networking layer. Doesn’t need to be on a route boundary (eg infinite scroll), can be sent via a web socket if you want, etc. My hope is that by exposing the raw primitives, it’ll be easier to see how RSC works and enable more freedom to experiment. Parcel is particularly well suited for this because it already supports multi-target module graphs with a single entry point. Will share more soon!

English
2
2
29
2.8K
Jesse Pence retweetledi
Devon Govett
Devon Govett@devongovett·
Made some progress on supporting React Server Components in Parcel over the weekend. Will be very different from other implementations: • Not a framework. No router, server, networking layer, cache, etc. — just the raw bundling primitives. • Use with any server/router (eg express). Instead of an HTML file, your server JS file is the entry point. In each route, dynamic import a server component and render it to HTML or RSC payload. Client components and styles used by that server component are optimally bundled and loaded automatically. • You can fetch a server component whenever you want, with any networking layer. Doesn’t need to be on a route boundary (eg infinite scroll), can be sent via a web socket if you want, etc. My hope is that by exposing the raw primitives, it’ll be easier to see how RSC works and enable more freedom to experiment. Parcel is particularly well suited for this because it already supports multi-target module graphs with a single entry point. Will share more soon!
English
16
38
483
96.7K
Jesse Pence
Jesse Pence@JessePence5·
@zeeg Duck is so gamey and gross. It's definitely a c-tier meat. I've had a few decent dishes with it, but those dishes would usually be better with something like lamb or chicken thigh. Turmeric is good in curry, but it should never be a noticeable flavor or the star of the show.
English
1
0
1
158
David Cramer
David Cramer@zeeg·
Y’all Peking Duck is not that good. Gonna put it into the turmeric bucket. Sorry not sorry.
English
8
0
4
2.8K
Jesse Pence retweetledi
Ryan Carniato
Ryan Carniato@RyanCarniato·
I wonder when people will start talking about the difference between loading data in Server Components and Client Components. There are many benefits to using SCs to load data but it comes with tradeoffs. Having optimal SC fetching doesn't necessarily excuse poor CC fetching.
English
7
9
78
17.5K
Jesse Pence retweetledi
Bramus
Bramus@bramus·
I built a thing last week: it’s a Scroll-Driven View Transition. Yep, you read that right: the View Transition is controlled by you scrolling! There’s a lot to tell about this one, so let’s take a look …
English
8
75
773
113.4K
Jesse Pence retweetledi
Jason Lengstorf
Jason Lengstorf@jlengstorf·
there’s no denying that ai is changing how we work and’s finding its way into many of our workflows. that being said, there are things I WON’T use it for new video up now (link in next tweet)
Jason Lengstorf tweet media
Portland, OR 🇺🇸 English
2
3
16
2.1K

Keşfet

@fredkisss @solid_js @MultithreadedJS @WInvincible4397 @teej_dv @JLarky @niklas_wortmann @Enea_Jahollari