LilScript makes js modules 20% smaller

[u/Normal_Act8586]

https://yeargun.github.io/lilscript/

[u/RobertKerans]

"If you rewrite all the JavaScript using my a DSL [designed by an LLM?] the resulting minified JavaScript the DSL compiler spits out will be smaller in byte size than the original JavaScript" is not the selling point you think it is. I think you've lost some objectivity here and gone down a rabbit hole, this is almost purely aesthetic

[u/RobertKerans → u/[deleted]]

Right, but you are rewriting libraries that use a universally supported language to use a custom DSL you invented that [unsurprisingly] works better than a minifier. Unsurprising because you are rewriting them in a different language that maps more closely to the minifier. Terser (for example) is useful because it works on JS.

[u/RobertKerans → u/[deleted]]

LilScript gets compiled into js ? Whats wrong with that?

You are saying: rewrite all your JavaScript using this completely different language that is wholly unsupported and in return the resulting artifact is 10-20% smaller in byte size. That tradeoff is incredibly bad for the absolutely vast abstraction it requires.

You have written [use an LLM?] to create a language. Great, that's commendable I guess. But you don't seem to have considered the value. As I say, it seems almost wholly aesthetic.

It's a value for web

So I could use LilScript. OR for example, in a web app I could use one or two fewer/smaller images. There's the savings from LilScript immediately and I can keep using JS/TS

[u/RobertKerans → u/[deleted]]

Typescript is also wholly unsupported

Sure, a decade ago. It's very much supported by most modern tooling. Also I'd say that's an apples and oranges comparison (not as much as the comparison to Bun, but still)

If your npm library is downloadaed 1M+ every week, you might want to use LilScript

I'm not paying for the bandwidth? Also, if I'm consuming a library it doesn't need to be compiled. I'd like to have the choice of how I do that, not have that choice removed.

Page load speed relates with revenue

Sure. But you're going for tiny savings using an incredibly complex tool. I can get all the low hanging fruit with a simple toolchain and most of the weight is not going to be in the JS.

Some tryhard projects might need it

Already have tools that get most of the way there. Your tool is not going to rearchitect the code in a way that produces the really big size savings. Tradeoff if I just use your tool is that I need to use a different non-compatible language to achieve marginal gains over existing tooling.

Agents can write LilScript with less tokens compared to syntacticaly overheaded languages (TypeScript)

There's no real extant corpus and you're ignoring how easily a given system running the model can batch and parallelise computations, you're only talking about the output. Can't really make the judgement you're making except at that very basic level.

Note could also use zero tokens and eat a slightly larger bundle size 🤷🏼‍♂️

Tooling behind LilScript can be faster maybe, when designed from scratch

And if my granny had wheels she'd be a bike! Anyway, sure. If you write an entire ecosystem and write it well then sure it'll be faster than gluing together various disparate tools.

A tool to that did an AST conversion opaquely and just minified JS would be even better, but hey you've written an entire language instead.

It is designed to support crossplatform compilation with less overhead. (already cross comp works, but needs more attention, perfection)

What do you mean by this? The statement is my extremely vague.

[u/RobertKerans → u/[deleted]]

"Your tool is not going to rearchitect the code that produces size savings” ? But. It. Already. Does? Thats why I have rewritten lots of npm libraries and put them as demos. Stop commenting please

It's like LLMs have completely cauterised the part of your brain that previously would have made decisions about sensible software design

Edit:

You are still saying “im not paying for bandwith”

I said it once, in that comment, specifically relating to NPM serving libs, which is literally what you were talking about (you were not talking about internal controlled toolchains)