I’m building a free, open-source invoice generator with live PDF preview — all browser-based, no sign-in needed.

It supports multiple languages, currencies, European VAT deductions, and more.

Originally made it for myself, so it’s a bit of a personal tool — but I hope others find it useful too :)

https://easyinvoicepdf.com/en/apphttps://github.com/VladSez/easy-invoice-pdf

An "JIT interpreter" for Emacs Lisp [1] with Graal Truffle [2] in Java. And it is really amazing how the frameworks these days simplify building a JIT runtime for a language. Currently I'm working on a pdump[3]-like feature for it.

[1] https://codeberg.org/gudzpoz/Juicemacs/src/branch/main/elisp

[2] https://www.graalvm.org/latest/graalvm-as-a-platform/languag...

[3] https://www.gnu.org/software/emacs/manual/html_node/elisp/Bu...

> Can you use it to do something useful already?

Unfortunately not. There's three steps:

1. Parse HTML into a tree.

2. Compile the search queries into a binary form.

3. Apply the compiler query onto the tree.

Steps #1 and #2 are done (with tests). You can see it here: https://gist.github.com/lelanthran/896a2d1e228d345ecea66a5b2...

Unfortunately, now it is the weekend, and with kids around I may not get around to step #3 until around Sunday :-(

JSX is useful not just for advanced string interpolation but for representing/generation of tree alike structures / literals in PL. JSX is not only about HTML but XML too.

I don't know how JSX is made in LuaX but in my QuickJS fork [1] JSX allows to generate as tree literals as procedure calls (JSX(tag,props,kids)) that can be used for various purposes - DOM population, VDOM generation, HTML/XML string composition, etc.

And being embedded into a compiler JSX a) prevents common mistakes like non-closed tags and b) effective internalization ( translation happens at compile time once ).

[1] JSX implementation for QuickJS : https://gitlab.com/c-smile/quickjspp/-/blob/master/quickjs-j...

The author works as a back end engineer @ Google. I appreciate his "outsider" approach as it is quite a bit simpler than other UI libraries & even reactive state management libraries such as Nanostores. I'm sure if he were in a different development role, his technique would be refined to account for full stack development use cases.

I don't mean to throw any shade on Tao. He is very talented & his approach is beneficially novel. I just don't think he as much experience what life is like as a full stack (or front end) developer as many here.

I forked his work to create relementjs & rmemo. Tao didn't want to support server side reactivity & I heavily use it. Also, Andrey (maintainer of Nanostores) didn't want to add my PR for autosubscriptions due to the complexity cost that would be added to Nanostores...So I wrote my own set of libraries. I hope library simplicity trends more because it is very nice to work with simple libraries.

Tao's approach is sound. He just relies on the DOM to manage the reactive state, so SSR reactivity would require a different approach. I ended up using WeakRef, which is significantly smaller than the approach used by traditional reactive state management libraries.

I have spent a ton of time refining use of sockets and test automation these past years in personal projects. These are winning me employment in areas that are far less opinionated.

Matanuska Telecom Association | Software Engineer - Systems Engineer | Full-Time | Alaska (UTC-9): REMOTE

MTA is an Alaskan ISP serving the southwest area of the state. The software team consists of 7 devs who support a relatively complex business enterprise environment. We're looking to add another Software Engineer and a dedicated Systems Engineer (DevOps) to our team.

As the hiring manager I want to be clear about a few things:

- This is a 70 year old enterprise telecom, not a high speed startup

- This job may interest you if you want great benefits and long-term job stability

- We have an existing environment running onsite on VMWare; the Systems role is designed to support, improve, and make adjustments to our tech stack over time

- Our core backend language is F# these days (replacing Haskell after 5+ years in production), frontend is React

- Our DevOps tooling is built around Terraform, Chef, Nomad, Vault, Concourse CI, Sensu, Prometheus, etc

- Must be authorized to work in the US

Software Engineer: https://mta.csod.com/ux/ats/careersite/4/home/requisition/59...

Systems Engineer: https://mta.csod.com/ux/ats/careersite/4/home/requisition/60...

Brazil and India are fake democracies ?