doc VS podlite-desktop

* list of list literals (1,2; 3,4) eqv ((1,2), (3,4));

to paraphrase Larry Walk “everyone wants the [semi] colon”

https://docs.raku.org/

amen to this … i recommend thinking about your problem in terms of effective data structures and then apply even a very simple DSL to handle access and transformations … fwiw the built in Grammars and Slang support in raku https://docs.raku.org are fantastic tools for this job.

When I was looking at the language, I didn't find the documentation "really poor". In fact I was impressed at how much of a one-stop-shop the official docs site was for both conceptual docs and API docs.

https://docs.raku.org/

The Raku Programming Language documentation already contains most (if not all) the documentation you need to deal with the issues you will confront in migrating Perl code to Raku. But, as documentation goes, the focus is on the factual differences. These blogs will try to go a little more in-depth about specific issues and provide a little more hands-on information based on my experience porting quite a lot of Perl code to Raku.

I will start working on the new version of Pod as a branch in https://github.com/raku/doc.

Well, performance has been improved by several orders of magnitude since the first release. So maybe it's time to look at https://raku.org again (or first have a look at its new documentation site https://docs.raku.org)

go to https://docs.raku.org/ and type "IO" into the search field. Behold the list that appears. Check out IO::Path or IO::Handle or whatever looks interesting. Maybe it's just me but I go "Ooh, look at all the things!".

Related: The Raku documentation does an excellent job explaining hashes/dictrionaries/associative arrays. If you've any issues, please submit a Github issue.

Raku has a lot of syntax. My first attempt at learning the language failed because I couldn't get past all the strange syntax I saw at https://docs.raku.org/. Sometimes I didn't know what the syntax was called, so I didn't know what to search for.

In the course of figuring this out, I realized that our docs also (slightly) misstate what \d means in a Regex, which led to this PR. So thanks for bringing all this up!

Unbound by any specific domain, programming language, or concept, Podlite stands out as a universal markup language

In addition, the support for Markdown markup as a standard block adds convenience and allows for the use of familiar syntax for text formatting

It's perfect for documentation, educational materials, blogging, and much more for organizing knowledge.

One of the key features of Podlite is its extensibility. This allows for defining unique and domain-specific blocks and expanding the language's functionality according to the requirements of your project.

The Podlite specification is published under the Artistic license 2.0.

Site: https://podlite.org

Podlite, a lightweight block-oriented markup language that's all about flexibility and ease of use.

My focus has mainly been on tools and products built on top of Pod. One of my well-known contributions is Podlite, a free Pod6 desktop editor. I have also implemented Pod6 in Perl 5 (Perl6::Pod) and JavaScript/TypeScript, which you can find at https://github.com/podlite.

Checkout full RELEASE NOTES

thank you, u/raiph for the mention. Totaly upvoted for "semantic markup group". Keep me in the loop! [0] Podlite desktop https://github.com/zag/podlite-desktop/releases Some previous projects use pod6: [1] https://github.com/zag/p5-Perl6-Pod [2] free suite for bookmakers https://github.com/zag/writeat [3] Book in pod6 https://github.com/zag/ru-perl6-book

⬇️ Podlite download 💻 Podlite GitHub

=code - add =Diagram component - add export to pdf - switch to using shared polite library - refactor main app, no more beta - save windows state between app restarts - open external URL in the browser - update export to HTML - =Image: fix show assets from disk - fix macOS and windows distributions - use flexible application windows size