I totally agree. I have written in LaTeX extensively and Typst is a game changer and a life saver. The community is also a plus. I love it and I will never go back to TeX.
rxdb has a toxic license and tried to do too much in too many different ways and does things like have open source components that are just working worse and are slower. its something that a lot of people were appalled by including me. they also changed so much it was hard to keep track of how things actually worked.
pouchdb is definitiely the OG local first database, and it inspired rxdb and was the core of it for a long time. it has definitely flaws mainly the developer ergonomics and not very up to date and non homogenic ecosystem. my feeling is non of these issues were the reaason rxdb parted ways, they could just have decided to > contribute < by fixing them and improving, but that would not have allowed them to create moat that they can enforce users switching to pro feautures with.
Great news!! Shiny for Python 1.0 is now available! As an enthusiast, I've been eagerly anticipating this release. Congratulations to the Posit team, who, with Quarto, Shiny, and so many other open-source projects, are bringing superpowers to a whole new kind of user. Shiny's ease of use is a bliss for a lot of new coders, including those who don't see themselves as traditional programmers.
The article doesn't explain why Shiny _is_. I see both an AI chat, and data tables, from a thirty-second skim of the blog post. And the main page says, "fresh, interactive approach to telling your data story". That doesn't actually help!
Since you know the tech, would you mind explaining to readers like me what this is about, please?
The main issue is that "CSV" isn't one format with a single schema. It's one format with thousands of schemas and no way to communicate them. Every program picks its own schema for CSVs it produces, some even change the schema depending on various factors (e.g. the presence or absence of a header row).
RFC 4180 provides a (mostly) unambiguous format for writing CSVs, but because it discards the (implied) schema it's useless for reading CSVs that come from other programs. RFC 4180 fields have only one type: text string in US-ASCII encoding. There are no dates, no decimal separators, no letters outside the US-ASCII alphabet, you get nothing! It leaves the option for the MIME type to specify a different text encoding, but that's not part of the resulting file so it's only useful when downloading from the internet.
It allows non-ASCII text but does not provide any way to indicate charset within the file, instead requiring it out-of-band. Once the file is saved, the text encoding becomes ambiguous. Likewise for the presence or absence of a header row.
Likewise for whether double quotes (`"`) are allowed in fields (rule 5). This one gets even worse, since the following rule (6) uses double quotes to escape line breaks and commas, but they may not be allowed at all so commas in fields may not be escapable.
It only supports text, not numbers, dates, or any other data, and provides no way to indicate any data type other than text.
```
pandoc input.html -t typst -o output.typ
typst compile output.typ output.pdf
```