fresh VS core-js

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.

This is surprisingly common. The other example off the top of my head, a single maintainer of a very popular project who had to temporarily abandon it due to lack of funds, is Denis Pushkarev (zloirock) and core.js (https://github.com/zloirock/core-js/blob/master/docs/2023-02...).

The majority of OSS projects have most of their contributions by one person (the project leader), and the vast majority of OSS contributors don't do it for their job. It seems nearly every single popular OSS project is like this (one unpaid, maybe sponsored, volunteer doing most of the work); it's not even worth listing projects and names, because you can just pick a couple projects you know and I bet at least one will be an example. Fortunately, most of these people seem to be well-off (probably in part due to the quality of programming jobs), but every once in a while there's someone who's not so fortunate. It should be more common to sponsor maintainers, especially if they are asking for donations provided they can prove that they really need the money (the world we live in, some people who have plenty fake issues to solicit donations, then others who genuinely need and deserve the money are scolded and left unfunded because of them).

Funny you say that, I was just thinking earlier today back to the core-js drama.

In short: the creator of a NPM package that is used by approximately everyone, everywhere, was facing a legal battle. He had been developing this package full time for years and did not have the cash on hand to hire a lawyer. He added a console log that ran on installing his package that said something like "If you're using core-js please consider donating". Queue an absolute shitstorm of people screaming at him in the github issues and him going to prison for around 10 months. Luckily he seems to be back on the grind nowadays, with a decently robust cross-platform slush fund to boot (~200k USD across Pateron, Open Collective, Bitcoin).

It can be a rough world out there for the folks building for the "focus, productivity and anti-distraction" platform.

https://github.com/zloirock/core-js

I think everyone here knows that, at some point, the site would start costing a lot of money and would need to be funded in some way. I would love for the Wikipedia donation model to work for a site like this but everything I find points to that not being the case. Reddit gold not covering server costs and open source devs not tied to a corporation struggling to continue working on their projects being two prime examples. If anyone has anything that can convince me to give it a try, please let me know and I will switch this to a non-profit.

Open source developers are not being paid. They published under licenses that allow zero cost and businesses won't pay.

If you want to write open source code for living, you have to find a business model that works. In this case, it is even under permissive license.

* code freeze - code is under open source license only a certain time after commit/release. Maybe add "support", aka you get security fixes in timely manner.

* open core - put some features behind commericial door.

* go ImageSharp way of split license. That one is fun, because MS deprecated/killed (throws exceptions on attempt to use) official image/font library and that was was intended replacement. Rather blatant offloading of costs.

This has been rehashed several time (core-js recently https://github.com/zloirock/core-js/blob/master/docs/2023-02...).

The gist of it is: Companies are not going to pay if they don't have to. That is the reality and it's not going to change.

This is one of the few examples. https://github.com/zloirock/core-js/blob/master/docs/2023-02-14-so-whats-next.md

Open source: It sounds pretty nice. Open to everyone... But it sucks in general. People really don't care to contribute to open-source. (e.g. here). It is a really good resource for development but for people who don't know anything about development, it is not important. There needs to be some financial income / support for good open-source.

there is https://github.com/zloirock/core-js but is more or less a 1 guy team and he is grossly under paid and well just read this https://github.com/zloirock/core-js/blob/master/docs/2023-02-14-so-whats-next.md im shocked he still works on it

Choice is good to a point but at some point it becomes crippling. It still haunts me on Rails. Is it yarn, is it brunch, is it npm, is it webpacker, is it esbuild, is it import maps... plus personally the pad-left debacle left a bad taste in my mouth and this little nugget about core-js was heartbreaking. For me it's hard to pick JS for anything other than what I absolutely must.

There's a real story behind that (but the software is core-js, not nginx)

npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. \> [email protected] postinstall /home/daniel/src/test/node_modules/core-js > node -e "try{require('./postinstall')}catch(e){}" Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > https://opencollective.com/core-js > https://www.patreon.com/zloirock Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)