This is very good, because billing the EU is quite strict, and having someone get the format right for me is super useful :)

I just made my own invoice generator using a json spec and a HTML -> PDF pipeline that wasn't so simple to get going. I might use this!

> This is very good, because billing the EU is quite strict, and having someone get the format right for me is super useful :)

Is it? In my (EU) country there is basically a list of things the invoice must show, without any strict template, even if they converge on very similar designs in the end. Basically to allow branding and alleviate physical -> digital transition struggles.

In the beginning the most popular "invoicing" software was Excel :D

thank you, if you notice any problems, don't hesitate to create an issue on github or contact me :)

I totally agree

The sentences are all roughly the same length too

Because historically appeal systems are well crafted and efficient? Please... at least read your comment out loud to yourself.

I would hedge most businesses don’t need the full offering of 365. You could get away with an email provider, a way to author documents and some file storage which are abundantly offered on other platforms like infomaniak.

They might not need it if they started today. But once you have a few hundred TBs of data in Sharepoint, you've foreclosed any alternatives.

That's not generative AI, just source separation which has existed way before large language models and transformer architecture were big.

You can already do this, but the platformised generative AI is sloppy by comparison and not that interesting.

https://github.com/acids-ircam/RAVE

> My friend bought me lunch. I used that energy at my job. Do I owe them part of my paycheck?

No but you owe him lunch next time. Wait till you find out that you have to share your birthday cake on your birthday.

How does this compare to using Plato or KOreader? I currently use Plato for its simplicity.

Love Plato- it’s so performant! I’ve always wondered why Kobo doesn’t just throw out what they’ve got and fork it.

While I do like Plato, it's got a lot of bugs and design issues... It can't handle epubs without chapters/really large chapters, it is noticeably worse on battery life than KOreader or the stock firmware, the amount of time taken to load the dictionary is proportional to the number of dictionaries, etc.