thesephi

5 ms·

1.
by thesephi 2y ago
Hi, I just wish to update that: since fullsoak@v0.9.0, support for Cloudflare Workers has been added in experimental mode :) Enabling this on Cloudflare Workers has been a rather challenging journey, due to the fact that the file-system API
2.
by thesephi 2y ago
Completely agreed! And "trade-offs" is the perfect keyword here. In exchange for zero cognitive load (ie. complexities in managing build config & consistency between dev & prod setups), we get a bunch of ESM, rendering the
3.
by thesephi 2y ago
I keep a #buildinpublic blog for FullSoak on my bsky page: https://bsky.app/profile/mrkha.ng Not sure if it's better than a Discord or sth like Tulips chat, but imho it doesn't matter, as long as there's
4.
by thesephi 2y ago
Hi! Kudos for the work on SmallWeb. I actually attempted to run this on your platform as well. I was able to run it partially on Cloudflare workers, so I trust it's compatible with environments like SmallWeb as well. Let's see!
5.
by thesephi 2y ago
that's a nice perspective :) I totally had no intention for 'taking credits' as I assumed it's a 'given' that we run TS directly with Deno, Bun, or Node.js with the experimental flag. I'll take this to my
6.
by thesephi 2y ago
I managed (with some struggles) to get it deployed with Cloudflare Workers here: https://fullsoak-cloudflare-example.dklab.workers.dev/ But it's a long way until it's groomed & released as a standard feature.
7.
by thesephi 2y ago
Ah please don't get me wrong, there's no build command in my example. The command to start the app directly is: `deno src/main.ts` and `main.ts` is an original source file, it's not a "bundle" of many files tog
8.
by thesephi 2y ago
i like that sound of that. Possibility for a nice logo image too!
9.
by thesephi 2y ago
it's a valid question. In the JavaScript / TypeScript community, we usually understand "fullstack" as "isomorphic": https://www.lullabot.com/articles/what-is-an-isomorphic-appl... Laravel
10.
by thesephi 2y ago
and that's a totally valid concern :) So far I only wish to check the concept in general (ie: "does it work"). As for "does it work fast / at scale", definitely a future topic. I do wish to elaborate: since we
11.
by thesephi 2y ago
Hi! My apologies if the wording was confusing :( By "no build" I mostly meant "no bundling" (so: we're not combining all files into a single js bundle entry). As for JSX itself: if we choose to use it, for sure we s
12.
by thesephi 2y ago
my appreciations! You're absolutely correct at the "problems that build steps do". One example is the whole loader stuff (e.g. SCSS, Less, and the plethora of other things we can "just import (tm)" into our TSX comp
13.
by thesephi 2y ago
kudos to the MithrilJS project & also for having earned visibility on OpenCollective <3 I can see the (much respected) history track of this project. Having "survived" the "Internet Explorer ages" of the www, I ca
14.
by thesephi 2y ago
ahh good to know :) Thanks - I'll try it out for sure. Also irrelevant but VanJS does have a way more invested logo & better name than "FullSoak" which I cooked up at 4am xD
15.
by thesephi 2y ago
thank you! You may find a Live Demo example (deployed as a Bun app) mentioned in this wiki: https://github.com/fullsoak/fullsoak/wiki/Concepts-&-Example... And Jude was kind enough to roll out a Deno exam
16.
by thesephi 2y ago
Wonderful!!! I wanted to provide a Live Demo, I tried with Deno Deploy, but I got a brick wall there because of some unintended blocker (ironically haha): https://github.com/denoland/deploy_feedback/issues/802
17.
by thesephi 2y ago
My apologies if the wording made it confusing :D By "no build" I only meant "no bundling". You can check the generated source code of the example deployment to see how it's deployed: https://fullsoak.onre
18.
by thesephi 2y ago
my apologies for using controversial wording. I'd love to confirm that we still must have some sort of transpilation / transformation because no Web Browser can consume JSX code directly (after all, JSX is just syntactic sugar, no
19.
by thesephi 2y ago
Thanks for your thoughts! I do adore Fresh. In fact, I have run production projects on Next.js and Remix, and played around with Deno Fresh, and I enjoy them in different ways. When I wrote "no build", I simply meant that we do no
20.
by thesephi 2y ago
thank you! You are both right that the wording could use some revamp. Perks of hacking on sth til 3am and writing a dirty README that leaves a stigma for years haha. Also by "no build" I mostly meant "no bundling". If yo
21.
by thesephi 2y ago
i wouldn't really introduce this as "a problem solver" :) It's more like an exploration of an alternative approach that combines base concepts such as: - import map: https://preactjs.com/guide/v10&#x
22.
by thesephi 2y ago
wow I wasn't aware of VanJS before. It looks nice! in my limited exploring of VanJS so far, I like that it also takes the direction to simplify things. That said, afaik VanJS simplifies the "JSX" part (so: we don't have
23.
by thesephi 2y ago
thank you for your approval of the 'no build' approach. We don't have to necessarily discuss the "framework perspective" of this topic - this all is more like a concept, a "lego mashup" of several standard
24.
by thesephi 2y ago
no I had completely no idea. Is this a generation gap thing, or maybe I just lived under a rock for too long - thank you for the heads up haha. If this causes too much friction, for sure it should be renamed..
25.
Show HN: A no-build fullstack SSR TypeScript web framework(jsr.io)
75 points by thesephi 2y ago|71 comments