In an unexpected turn of events, this silly project of mine got a funding offer that makes sense to me I just got off a call with like-minded peeps. I get to create this thing according to the RFC here with no influence or "direction" ❤️ github.com/Sheek-org/rf... #dev #buildinpublic #webdev

Today's 🌶️ take The internet was designed so that a bunch of nodes that contain a bunch of documents can respond to requests for those documents. See how there's no "central authority" here? Using mega corps to host your docs or to "protect you from bots" defeats that purpose. #dev #buildinpublic

Part of the RFC I shared is "The whole promise is this: you get a cheap server, you run one command, and your community is live" Getting to that point needs a bit of planning. #javascript #dev #infra #buildinpublic #webdev #community

I asked for "forum" spec a while back. I want to make one. This is an RFC that summarizes most of the conversations I've had with a number of peeps The RFC is here github.com/Sheek-org/rf... share your thoughts here github.com/Sheek-org/rf... #community #forum #javascript #buildinpublic #dev

Doing some exploration for uploads 🕵️ I want to anchor uploads to content (no orphaned uploads) I tried Quil as the "blessed" editor and it works really well with pocketbase Quil handles most of the UI, pocketbase handles file storage and permissions #javascript #dev #buildinpublic #webdev #dx

Today's 🌶️ take The fight for the javascript trademark championed by the folks at Deno makes sense crowdfunding $200k for it to lawyer up against an $800 billion company does not. I don't care what what it's called. I'll still use it that $200k could have gone to better causes

I integrated OAuth for social logins 💁 You get your client id and secret from some provider (like google or github) and add them in an .env file That's all you need to do 🦄 Everything else is wired up. Pocketbase does most of the heavy work 🏋️ #javascript #dev #buildinpublic #webdev #UX #oauth

The latest work on real-time subscriptions 🏃 You no longer need any server routes. All the subscription stuff can be client-side. This is mostly thanks to pocketbase apis In other words, a component can be fully isolated, data and all. #javascript #dev #buildinpublic #pubsub #webdev #dx

I added Mailpit as a dev mail server 📬 mail.localhost will give you a place to catch emails sent locally in dev This will ship with project templates. One less thing you need to worry about configuring. Plus Mailpit is a single binary 🔥 #javascript #dev #buildinpublic #webdev #dx

golang 🤝 javascript

I got a first pass of work done integrating Caddy 👀 The immediate impact: removed all static file handling and all the compression logic from the node app 🔥 enabling zstd (gzip fallback) is literally one word 🦄 #javascript #dev #buildinpublic #webdev #performance

The beatings will continue until the code readability improves.

There's very few things in life that bring me more joy than deleting code.

I've been shopping around for a reverse proxy / file server and Caddy is the best fit. I'll be working on that next Single executable binary, automatic certs, easy to configure, and tons of other features esbuild, pocketbase, caddy... I'm noticing a pattern... #javascript #dev #webdev #golang

I can't think of anything to caption this with, so here it is 💁 Real, live, performant db search in the content field of posts. The thing on the left is the entire thing. the war on boilerplate continues 🤸 #javascript #dev #buildinpublic #performance #dx #webdev

Playing around with Pocketbase 👀 What an amazing piece of software ❤️ There's no need for app-level endpoints The official SDK is designed to be run in the browser. It talks directly to the db server (single Golang binary) This is all client code #javascript #dev #buildinpublic #webdev

I revisited this with a fresh pair of eyes after working on the SSR component and I managed to cut down boilerplate a bit with an #SSE component 👻 Essentially, you give it an endpoint, a render function, and a method (replace or the default "append") for what to do #javascript #dev #buildinpublic

Another example of "static islands" 👀 This time with "live search" everything is CSR except <SSR /> but it responds to client URL which is modified with a CSR input The product cards are essentially static links, so, skip the middle JSON part and just SSR them #javascript #dev #buildinpublic

I spent a bit more time on this 🍿 I see a path forward with this pattern.

Experimenting with a new thing⚗️ You've heard of "dynamic islands" but have you heard of "static islands" Instead of SSR with dynamic client stuff, we start with CSR and add JSX SSR endpoints that return static HTML partials All wrapped in a declarative <SSR /> #javascript #dev #buildinpublic

A little detour 🤸 HTTP out SSE in plus code colocation makes it possible to have an (example) counter work as a real time thing that can skip optimistic updates Still lots of boilerplate to cut even thought the whole thing is 40 LOC in two files next to each other #javascript #dev #buildinpublic

I continue to explore the "bundle all the thingz" approach 🍿 With the CSS + JS for all the deps an entry point being rolled into a single file, the next step is to inline that file into the html response instead of a separate request More in the replies #javascript #dev #buildinpublic #webdev

frontend is a lie. It never ends. 🤕

CSS bundling 👀🔥 long story short when you use Header.jsx, Header.css is automatically loaded if it exists all the components and their css that "a page" uses are bundled into a single tree-shaken file you can enable sourcemaps and debug code as authored #javascript #dev #buildinpublic #webdev

typescript bad

I like checking the performance tab in dev tools as a sanity check on framework overhead Checked it again with the "bundle all the thingz" approach and... me likey 🙈 It's amazing how much JS modern browser will churn throw in milliseconds 😯 #javascript #dev #buildinpublic #webdev #performance

Live reload now works with single entry bundles 👀 Change a CSS files, a JSX client side file, or a server JSON endpoint, you'll get instant live feedback One thing I really don't like is the "difference" between dev/prod dev should mirror prod as much as possible #javascript #dev #buildinpublic

The "single executable binary" story in bun.js looks a lot more polished than Node. I'm rooting for Node, but Node SEA doesn't support ESM.

javascript? in this economy??!!1!1!

Busy few days but I did get chance to do some work 🏃 the "bundle everything for an entrypoints" path seems very good You get incredible treeshaking and very tiny CSR JS payloads with just what the page uses. This includes your code and the framework code! #javascript #dev #buildinpublic #webdev

Today's 🌶️ take Be nice, please. That's it. We kind of need more of that right now.

Today's 🌶️ take The world is beautiful, amazing place, and you only get a limited time to enjoy it. The people around you are a lot more important than random internet strangers and the drama that comes with it

Given this was kind of a dead end, I'm moving to the next thing The plan for this experiment is to fully embrace bundling and see where that goes. A top-level overview you go to /thing /@thing.jsx gets bundled, like fully. your code, framework code, npm code /thing is a self-contained entry

I put some time aside today to make a drastic change. This will be a live thread as I work on this, mute it if you don't want the noise Essentially, I'm ditching bundling. I don't know if this will be a dead end, but I want to try it. Here's the idea. Flatten all static imports

I bought the domain brainrot.church a while back. I have no use for it now. DM me your use case. Will transfer* it to you if your idea makes sense. boost appreciated *I own the domain. I don't know what transfer entails in terms of cost. For my part, I'm giving it away and don't want anything

This "invalid handle" stuff is kind of growing on me 👻 I can fix it, but do I really want to? 👀

Today's 🌶️ take No shade, but the recent NPM stuff is an absolutely valid thing to point to whenever you run into one of those "don't reinvent the wheel, bro" conversations Yes. You should reinvent small wheels. You should reinvent stuff you understand code ownership is underrated #javascript

Today's 🌶️ take if you don't like javascript... don't use it.

skill issue

A cool feature of the new Store primitive is named stores 👀 If you give a store a name, it becomes public You call getStore to find it and you get a read-only but reactive reference to it. This works great for inter-component state sharing 🤝 #javascript #dev #buildinpublic #dx #webdev

Exciting new stuff 🙂 A new primitive instead of obscure magic and weird prop injections. new Store() create a store assign stuff to it ... profit (it's reactive) create as many stores as you want, even in the same component #javascript #dev #buildinpublic #webdev

I started working on this and here's a walkthrough of what I have in mind Everything is based on code colocation getUserById.sql lives in the /users concern folder sql file imports are treated as JS modules. The file is raw #SQL but the transformed default export #javascript #dev #buildinpublic

Lifting others up good

Finally put time aside for a "proper" live reload 🙂 I had a thing before but the new pattern is both seamless and fast, like real fast 🔥 #dev #buildinpublic #fullstack #javascript #devex

I'm very much settled on /feature folders I'll be working on removing the JSONB abstraction for SQLite db.users.insert({...}) is nice but it's a dead end. The idea is... import an .sql file... get a prepared statement. All plain raw SQL. rough example #javascript #dev #buildinpublic #webdev

ORMs bad

Bring back tech autonomy On an individual level or as part of a collective group being autonomous The internet is the only thing that you can truly point at and say that it is owned by "US" as a collective. Whatever you want us to be here Sure, mega evil corps own big corners, but not everything.

Website used to be more creative because the pool of people making them used to be much wider You literally used to chuck a local file somewhere accessible on the internet and you're done. Yes. I am being simplistic. No wonder "all websites look the same" They're all made by the same people or

Client-side rendered MPAs with real time updates 👻 removing the websocket connection in the last sprint meant we lost real time updates. Those are now back but better @live-thread-list.js is a handler file like any other, but you can upgrade it to an SSE connection #javascript #dev #buildinpublic

premature optimization bad