deco VS fresh

Gui, Lucis, and the deco.cx team here — we're a bunch of Brazilians building an open-source, all-in-one web editor for the modern TypeScript dev. Check out our GitHub at https://github.com/deco-cx/deco and discover more at our site https://deco.cx/.

We built frontend tools at a hyper-growth e-commerce platform for 9 years. Deco.cx is the thing that we wish existed when we were managing hundreds of enterprise-grade React-based websites.

The gist is: JSX, HTMX, TypeScript, Tailwind and Deno. All visually editable in a beautiful, collaborative, REALTIME (!) admin UI. Great for devs, great for content.

In essence, we're a git-based TypeScript-first configuration management system. We take TypeScript code that represents your site, your entities, your UI, and we allow anyone to "save" configuration and content based on those types.

It's great for developers, because you can code directly on the web, or on your machine, and get instant feedback. You "export interface Props" and boom, an automatic form is generated. It's great for the business users, the content editors, because you just press "." (dot) in your keyboard and you go into a visual edit mode for the page you're at right now. Everything the developer exported in TypeScript is editable.

And when you hit "publish", it's already live, with a proper CDN, proper caching, everything already setup and just working. Ready to scale!

But you can't fly blind. We're democratizing pro-level tools for web analytics and observability by bundling in our Pro plan: fully-managed Plausible analytics and HyperDX observability. Check them out — these are great tools on their own, and they shine in the deco.cx platform bundle.

We don't want to be the only answer, we don't claim to be right about anything, we just want to make the friendly and accessible open-source tool that we wish existed when we were junior developers. If you want to participate, please join our discord community at https://deco.cx/discord

on open-source: our admin UI core is not ready for prime time, we're working to open-source it this year. but basically everything else, our integrations, templates and configuration management runtime are all open-source already! take a look at these: https://github.com/deco-cx/deco https://github.com/deco-cx/apps https://github.com/deco-sites/storefront Making the admin UI core extensible and open source is a MAIN OBJECTIVE for this year, so expect news here soon!

Thanks for your support!

Deno: Deno with one of it's frameworks (like Fresh

The road to Fresh 2.0 (https://github.com/denoland/fresh/issues/2363) by Marvin Hagemeister Can't wait for seeing the end of the road! All in all great changes ahead.

Because I have secret magical powers that you probably don't, it's basically free for me. Here's the breakdown though:

The application server uses Deno and Fresh (https://fresh.deno.dev) and requires a shared-1x CPU at 512 MB of ram. That's $3.19 per month as-is. It also uses 2GB of disk volume, which would cost $0.30 per month.

As far as post generation goes: when I first set it up it used GPT-3.5 Turbo to generate prose. That cost me rounding error per month (maybe like $0.05?). At some point I upgraded it to GPT-4 Turbo for free-because-I-got-OpenAI-credits-on-the-drama-day reasons. The prose level increase wasn't significant.

With the GPU it has now, a cold load of the model and prose generation run takes about 1.5 minutes. If I didn't have reasons to keep that machine pinned to a GPU (involving other ridiculous ventures), it would probably cost about 5 minutes per day (increased the time to make the math easier) of GPU time with a 40 GB volume (I now use Nous Hermes Mixtral at Q5_K_M precision, so about 32 GB of weights), so something like $6 per month for the volume and 2.5 hours of GPU time, or about $6.25 per month on an L40s.

In total it's probably something like $15.75 per month. That's a fair bit on paper, but I have certain arrangements that make it significantly less cheap for me. I could re-architect Arsène to not have to be online 24/7, but it's frankly not worth it when the big cost is the GPU time and weights volume. I don't know of a way to make that better without sacrificing model quality more than I have to.

For a shitpost though, I think it'd totally worth it to pay that much. It's kinda hilarious and I feel like it makes for a decent display of how bad things could get if we go full "AI replaces writers" like some people seem to want for some reason I can't even begin to understand.

I still think it's funny that I have to explicitly tell people to not take financial advice from it, because if I didn't then they will.

Deno has also created a Next.js competitor, Fresh. I found it a few weeks ago and am starting to go through the docs, looks like a good overall concept. https://fresh.deno.dev/

https://fresh.deno.dev/ - Fresh embraces the tried and true design of server side rendering and progressive enhancement on the client side.

Along the way, I not only got the oppurtunity to revise old concepts that had blurred in my memory, but also learnt about new technologies like Fresh.js, a framework from Deno (a js runtime engine) that uses Preact, a React Routing library and used Chakra UI for the first time.

A whole project might be released as a server or framework. Frameworks like fresh, and astro) both have had things deep within them that I've wanted to reuse, within fresh it's the esbuild configuration, and islands functionality, and within astro it's the rendering of astro files themselves.

The Fresh framework by Deno cited an improved developer experience due to tighter feedback loops.