Alexis Munsayac 🇵🇭
@lxsmnsyc
Followers
880
Following
564
Media
438
Statuses
3,492
I make things. I teardown things. Hanging out @solid_js @milliondotjs
Philippines
Joined May 2017
Don't wanna be here?
Send us removal request.
Explore trending content on Musk Viewer
NuNew 3rd Showcase
• 373606 Tweets
Cohen
• 114019 Tweets
$GME
• 89563 Tweets
#LovelyRunnerEp11
• 77426 Tweets
#キュウゴー
• 53012 Tweets
MY LOVE IS LIKE
• 44436 Tweets
GameStop
• 39150 Tweets
#CBÖğretmeneMülakatıKaldır
• 36604 Tweets
TREASURE COMEBACK
• 33124 Tweets
Aziz Yıldırım
• 28685 Tweets
LINEの新機能
• 27718 Tweets
Roaring Kitty
• 24524 Tweets
Hot Sale
• 21003 Tweets
Square Enix
• 20912 Tweets
Childish Gambino
• 19938 Tweets
Ravens
• 17538 Tweets
GET WELL SOON GYUVIN
• 16667 Tweets
Deco
• 15403 Tweets
$AMC
• 15336 Tweets
ACEITA ANITTA
• 14135 Tweets
Atiku
• 12885 Tweets
McDavid
• 12331 Tweets
Stevie Wonder
• 12015 Tweets
Qちゃん
• 10234 Tweets
Finally after months of attempts, it's now a reality. Partial Hydration for rigidity, an SSR framework for
@solid_js
that I've been working on. The feature is heavily inspired by
@astrodotbuild
and React Server Components.
4
9
115
Working on a "simple tool" that converts
@tailwindcss
classes into a single CSS sheet. Made in
@solid_js
8
3
70
Always been thankful to
@RyanCarniato
and
@davedbase
Feels great when the community you supported supports you back.
10
1
66
Probably the first time I'm writing a compiler from scratch
5
2
61
Everyone's excited for signals and reactivity syntax (specially Svelte 5), what I'm excited is the thing me and
@RyanCarniato
have been working for in upcoming SolidJS 1.8
4
2
59
I know I haven't really announced anything but as of January, I'm now part of the Core Teams of both
@solid_js
and
@milliondotjs
which framework is next (no, not a pun), I wonder?
3
3
57
Got a little bit of progress with
@solid_js
+ partial hydration
- Works like Astro (islands, hydration hints/scheduling)
- Works like RSC (client components with server children)
- on-demand SSR
- Built on top of Vite!
Works as expected, but still needs a lot of work to be done
4
6
55
Released solid-use 0.5.0
This release adds the `fetch` utility, a utility similar to the native `fetch` but with reactivity and Suspense in mind.
1
7
53
1.7 just dropped!
My biggest contribution in this release is how
@solid_js
now uses seroval for serializing resources in SSR. If you want to know more about seroval:
Solid 1.7 was not the easiest release. There were some challenging decisions around types. But it brings some great improvements that should make all the TypeScript users out there very happy.
2
29
186
2
3
49
so this is what the Church of React looks like
5
2
47
@davedbase
@alexxubyte
TS just redirects the entire power grid to its language server just so it can resolve a template string type
2
0
48
Cooking something for this weekend, can you guess what it is? 👀
13
2
44
Fun stuff. I was given an opportunity by
@RyanCarniato
to work on solid-refresh.
The new solid-refresh:
- Allows local components to be hot-reloaded.
- Preserves component lifecycle (effects, signals, etc.) of unchanged components
- Granular component replacement
Exciting!
1
1
44
Now let's try other frameworks.
React:
- Directly creates text nodes
- escape strings on the server:
3
8
46
Unironically,
@RyanCarniato
demo'd this on his Server Actions stream two weeks ago.
JS as a data format
Hear me out
a javascript library that returns javascript from the server and runs it on the client
49
14
356
0
2
44
I should probably make a demo of the new capabilities
Maybe streaming server functions? 🤔
SolidStart Beta 2 is finally out.🎉
⚡️Nitro backed, and Vinxi powered
🤑New super serializing Server Functions
🕵️Router/Metadata Library Agnostic
💅Fully CSR SPA capable
14
92
615
2
2
41
Released waystone 0.1.0, a library that allows to turn MPA navigation similar to SPAs, no full reloads!
(since this is the initial release, I expect some myth-busting)
4
3
41
Released Forgetti 0.6.0
This release adds JSX auto-memoization (bye `React.memo`!)
1
3
38
Released `solid-cache`, a way to create cached resources while also allowing simultaneous refetching as well as a way to allow background refetching while keeping the old UI
Inspired by React's upcoming Cache API
2
4
38
I came, I saw, I contributed
4
1
37
Why does
@RyanCarniato
look like he's about to drop a music album in the tech community
3
0
34
Initial release of `solid-pebble`, a "global" state management library for
@solid_js
. Inspired by Recoil
4
2
35
Yet another Partial Hydration experiment in
@solid_js
It's been a year, it took me that to figure out the last remaining pieces:
- semi-automatic code-splitting
- JS serialization
- closure extraction
A lot better than the previous `*.client.tsx`
Got a little bit of progress with
@solid_js
+ partial hydration
- Works like Astro (islands, hydration hints/scheduling)
- Works like RSC (client components with server children)
- on-demand SSR
- Built on top of Vite!
Works as expected, but still needs a lot of work to be done
4
6
55
1
2
32
Ryan has always been public about how he appreciates Remix and React Router since last year. Some of the insults were uncalled for.
I wish I could reply to at least one of the Tweets
@ryanflorence
has made. Some mistakes were made and probably should have been more diligent. But every intention was made to credit remix. Like this commit for Session management 5 months ago:
21
29
368
1
2
31
Released solid-styled 0.7.0!
- optional StyleRegistry
- support for multiple roots (which means Astro is now supported!)
- new scoping attribute format
1
2
30
Why are we calling islands "islands" when they are being hydrated? shouldn't we call them "oasis" and the rest of the web page as "desert"?
1
7
30
Big release! (probably the biggest release of this plugin)
Adds lots of CTFs, then I'll make
@solid_js
an 100% auto-import library soon 😍
2
7
28
in SolidStart too, since last year.
We had the question of "How to do getServerSideProps for every component?", and here we are.
Everyone is flipping out over server actions in
@nextjs
(and
@reactjs
)...
This was already in
@QwikDev
pre v1...
Love seeing great ideas spread around.
(That
@samselikoff
meme generator is 👨🏽🍳💋
@rauchg
)
14
25
201
0
2
28
Despite me having a bit of a burnout with solid-headless in the past year (although I have been successful with the rewrite, the docs are still... 😵💫), I would like to thank
@FUTO_Tech
for this microgrant.
I never really expected to get paid for doing something I love.
This month, the Summer '23 FUTO Fellows got to pick which open source projects will receive a $1000 FUTO Microgrant. Watch this space for the big reveal!
1
1
18
1
2
28
Forgetti makes debugging React more fun 🤣
Rollup and Vite plugins coming soon.
5
1
27
Honestly, it's been weird about how React team focused on RSC when majority isn't going to use it nor would be able to use it.
Unless of course if they enforce the paradigm, but like Context Selectors still feels like React's greatest miss
outside the bubble of obsessing over frontend here’s what it feels like for someone just trying to make a decision
can nitpick the details but broadly it’s a good data point to consider
123
60
785
5
0
26
Released `solid-headless` 0.12!
Adds the Tabs implementation, data-sh attributes for headless tag selection, better Vite SSR support and more
0
3
27
Released a tiny utility library called "seroval", stringify JS values into valid JS code.
1
0
27
Released solid-styled 0.9.0
Rewrote some compiler-related stuff, the biggest change is moving from postcss and csstree to
@lightningcss
, which should improve in performance.
Also added unplugin support
0
1
26
Released solid-headless 0.10.0, introduces the CommandBar component and rework on how states are managed in uncontrolled vs controlled behavior
0
2
24
I'm so glad I'm no longer touching React code on a daily basis
2
0
24
Date pickers
Combobox required me to rethink my implementation for two years, and Date picker, which is a kind of it, is what I call "a monster amongst monsters"
What's the hardest UI element to build, and why?
Bonus points if it reaches across the stack, like image uploaders or pagination.
313
27
806
1
0
23
Release use-server-directive 0.3.0
This release adds "use server" blocks.
0
0
25
My wild ideas:
- Make an islands framework for Stellis
- Make a server components framework for Solid
- Make a partial hydration framework for Solid
- Make a PoC React Forget with just Babel
- Continue working on solid-headless
4
0
24
Let's start 2024 with a new experiment.
'use server' blocks
2
2
24
today I just learned about this piece of code. I always forgot that Promises and async/await behaves this way.
If only there was a `Promise.shallowResolve` 🤔
2
0
23
Decided to give seroval's playground a bit of an upgrade.
I'll most likely add options soon.
1
1
22
Ported solid-headless' CommandBar demo to rigidity, an upcoming SSR framework for
@solid_js
It also demonstrates how rigidity now works with PostCSS and Tailwind!
Credits to
@RyanCarniato
for enlightening stuffs about how Solid's SSR, always bet on it!
0
1
21
There's 3 kinds of devs:
- Those who like this
- Those who do not understand tagged templates
- Those who think this exists on the client
3
4
22
Ryan demonstrating server functions serializing a Response object inside a Response object is probably one of the funniest things I've contributed to SolidJS
Stream today I'm going to be talking about the movement to compile RPC and how this plays a different role than RPCs in the past:
3
17
104
1
2
22
Released solid-marked 0.6.0!
This release adds the Markdown component
0
2
22
oh I thought I was the only one lmao, funny how this has been existing for years now
My professional opinion is that you should build new apps with Remix instead of Next.js
It feels like next.js has become too complex to manage. Made extra challenging that it’s not directly driving revenue, so hard to justify the investment it really needs.
This is after…
123
73
839
3
1
21
Well that took a year, finally released compostate out of beta!
It's a been timely given that fine-grained reactivity is gaining attention, and so why not join the fun?
4
2
21
Released forgetti 0.2.0
This release now adds support for `useRef` (via `ref` kind in preset.hooks)
2
0
21
I guess Forgetti can now memoize loops
How does it work? It uses branched caching, that is, a new cache is generated for dynamically-sized statements like a loop. Another tiny cache is created inside the loop, which can then produce its own branches
1
1
21
Released `solid-use` 0.4.0 which adds a set of utilities to emulate React's Suspense mechanism in SolidJS
1
2
21
Reworked `solid-sfc`. I can't turn a blind eye on how good the JS/TS tooling is, and so I just turned SFC into "module-as-components"
3
1
21
Released Forgetti 0.8.0
2
1
21
This is probably one of the most cursed toy projects I've ever did
4
1
20
React: architecture
Dislike: features are too late (e.g. `use`)
Vue: Composition API, ref sugar
Dislike: too much syntactic sugar
Svelte: simple SFC
Dislike: SFC compiled output
Solid: everything
Dislike: but the ecosystem is small
My personal likes/dislikes of the popular frameworks:
React: I love TSX and hooks.
Dislike: useEffect, callback arrays, and over pushing immutability.
Vue: I love SFCs, simple proxy-based mutable state management.
Dislike: would like to see a solution to having less…
54
63
874
1
0
19
Working on a universal code splitter for custom directives.
Example here uses "use server" and splits the code on block-level (not function-level, making it more granular)
0
0
19
3 months and I'm still partially jobless. I was almost going to have a job however some person decided to waste their time on some unimportant stuff. Kinda ruined my plan for the entire year 🙃
2
1
18
I'm still in the dilemma where someone offered me a job I half-dislike, but has an opportunity to be sustainable.
The other, has the job I like, but with no guarantee to be sustainable.
Or I can just give up all these and live the rest of my days planting crops (ikigai).
🤣
2
0
18
@tannerlinsley
Funny thing is the only reason I stayed away from React is not because of the performance, but because dependency arrays is a hell hole I want to escape
0
0
19
Crazy how
@solid_js
has this built-in, and how this makes sense
You should still initiate the fetch in the owner component, but await it in the child, otherwise you’re slowing down the page.
24
31
552
1
1
18