geraldbauer

Love it a great way for encouraging more syntax experimentation in the wild. A less functional and more conceptional library is the pragma gem [1] - that lets you turn on the future today or add your own ideas for easy (re)use for everyone - let's evolve the ruby language together by experimenting in the wild in a pragma(tic) way.

[1]: https://github.com/s6ruby/pragmas

See http://isrssdead.com

For my part I'm currently building and updating a feedreader / feedparser kit that lets you build a newsfeed in minutes [1] or use a ready-made client such as rubynews [2]

[1]: https://github.com/feedreader/news.rb [2]: https://github.com/planetruby/planet/tree/master/rubynews

PS: The stats on Planet Ruby for RSS vs ATOM are:

Q: What feed formats are in use? Formats (n=51)

  atom        (52%) | ******************************* 27

  rss 2.0     (47%) | **************************** 24

A little more light-hearted but the same style to learn Ruby with Entirely Too Many Fizz Buzzes. See https://yukimotopress.github.io/fizzbuzz

FYI: You might enjoy my talk notes titled "Using Git (and GitHub) for (Publishing) Data" [1] includes many real-world examples too.

[1]: https://github.com/geraldb/talks/blob/master/git_for_data.md

To quote from an academic study and the commentary from a world-class economist from the article titled "Initial Coin Scams" it reads "There are now nearly 1,600 cryptocurrencies, and the number continues to rise. It is time to start recognizing their issuers' utopian rhetoric for what it is: self-serving nonsense meant to separate credulous investors from their hard-earned savings. [..] 81% of ICOs are scams created by con artists, charlatans, and swindlers looking to take your money and run." [1]

[1]: https://www.project-syndicate.org/commentary/ico-cryptocurre...

About the author David Gerard - The Book "Attack of the 50 Foot Blockchain" [2] is an unmatched gem in a sea of 24-hour non-sense crytpo promotion. Ironically another voice of reason is "pseudonymous" Trolly McTrollface [3]

[2]: https://davidgerard.co.uk/blockchain/table-of-contents/

[3]: https://bitsblocks.github.io/bitcoin-maximalist

FYI: I've put together some classic ICO myths in the "Awesome Initial Coin Offerings (ICO) Truths" page [1] with the subtitle "The Art of the Steal - The Scammers' Big Lies". [1]: https://github.com/openblockchains/awesome-ico-truths

You might like the Comma-Separated Values (CSV) Format Specifications (and Tests) org @ https://github.com/csvspecs Trying to improve the world's most popular plain text format (and - surprise, surprise - nobody cares).

> rather than using something generic like 'jq' is telling.

The best generic tool for managing (structured) data is SQL. Once you have the datasets imported (via the custom readers / loaders) it's just plain SQL (and works with SQLite, PostgreSQL, MySQL, etc.)

JSON and YAML qualify as plain text, for sure. Plain text is a spectrum. Let's say from "free form" english text as your comment to more machine-oriented structured formats like JSON and YAML. YAML, for example, tries to be a more human plain text format than JSON e.g. it supports keys without enclosing quotes or it supports comments and it supports variants and many shortcuts and much more. JSON is pretty "inhuman" if start hand-editing from scratch and NOT recommended, see Awesome JSON Next for "Why JSON is NOT a good / great configuration format" or "How to fix JSON" and so on - https://github.com/json-next/awesome-json-next

Good point. See the football.csv project :-) @ https://github.com/footballcsv Here's, for example, the Premier League 2019/20 match schedule example - https://github.com/footballcsv/england/blob/master/2010s/201...

The point is as you say - the .csv format is easy to read / parse / write with a script for automation BUT it's way harder to start from scratch to input / type and keep it up-to-date. That's why you need both type of formats (one for hand-writing and one for easy auto-generation).

See above the world cup match schedule [1], for another other examples with geo tree (e.g. country/province/city/district/etc.), see the Belgian Football clubs, for example [2] or for yet another example the Football leagues [3] with tiers (1,2,3, etc.) and cups and supercups, playoffs, etc. The .txt version are pretty compact with "tight" / strict error checking and JSON, YAML and friends I'd say it would be 2x, 3x or even more effort / typing. [1]: https://github.com/openfootball/world-cup/blob/master/2018--... [2]: https://github.com/openfootball/clubs/blob/master/europe/bel... [3]: https://github.com/openfootball/leagues/blob/master/europe/l...

> If it's anything more structured, why exactly?

It is way easier to input / type and change / update. And compared to lets say JSON, YAML or friends at least 5x times more compact (less typing is better). See the world cup all-in-one page schedule in .txt [1] and compare to versions in JSON, XML and friends that are page long dumps, for example.

[1]: https://github.com/openfootball/world-cup/blob/master/2018--...

Great collection of tools and articles. Plain text is also a great (and the best) choice for datasets. Do NOT use JSON, YAML and friends, for example, as your input format but use plain text with a custom parser to import into any SQL database and than you can easily export to JSON, YAML and friends. See the football.db and the Premier League or World Cup match schedule as living examples [1]. [1]: https://github.com/openfootball

Of course not :-) Python, Ruby and friends can do so much more (and you can run your pipes on your own computer, for example, ...).

You can use modern scripting languages such as Python, Ruby and friends. They will never go out of fashion if you want to put together a pipeline (also known as workflow or script :-).

A quick note about json next. I collect new JSON variants, extensions and formats at the Awesome JSON Next page [1]. [1]: https://github.com/json-next/awesome-json-next

In theory (and practice) you can also (easily) create "classic" epubs or mobis from the Manuscript book source (it's just a meta datafile and structured text). One dream would be to have all Gutenberg books in Manuscripts - it's only a small step from "plain" text to structured text. I'd say way easier than to convert everything to HTML source as Standard Ebooks project is doing - https://standardebooks.org - for example. Anyways, books in (structured) text (formats) will outlive all formats and will still work even without special ebook readers. It's a format like the alphabet (that is, it's forever). If you read it on paper or on a screen or as a codex (paged) or as scroll - it's all possible by design. Anyways, thanks for your kind words.

The new format is (way) easier / simpler and yes, you can use pandoc for markdown processing. If you create an online book than you can just use HTML & CSS e.g. a "standard" website or a webpage is a book. You should ask why the book industry created a new format, that is, EPUB :-).

PS: That's also the direction the World Wide Web Consortium (W3C) tries to go (but failed). See the upcoming https://www.w3.org/TR/wpub/ recommendation / standard / spec trying to replace EPUB. Compare the book manifest of manuscripts with the book manifest of wpub to see what format keeps it simple.

PPS: And to keep apple and oranges apart - FYI: pandoc is NOT a book format (it's a text processor), thus, you should compare Manuscripts to EPUB or the new WPUB.

FYI: I've put together a free book format called Manuscripts. See http://manuscripts.github.io and find an example bookshelf @ http://yukimotopress.github.io Happy book writing. Happy book reading.

FYI: I collect (awesome) articles about Libra incl. official posts and pro & contra. See https://github.com/openblockchains/awesome-libra#articles

FYI: You can run / publish your own planet news sites using pluto -> http://feedreader.github.io See the Open Street Map Blogs Planet as a live example -> https://blogs.openstreetmap.org Are making Planets a comeback :-) ?

If you'd like to program / code your own ponzis and ponzi simulations on the blockchain, see the free "Programming Crypto Blockchain Contracts Step-by-Step Book / Guide" [1]. [1]: https://github.com/openblockchains/programming-cryptocontrac...

Sorry you are misreading and misstating what I said - markdown is a language and can of course be improved as many flavors / dialects / extensions and so on proof. Evolution is usually way better in finding conventions than your top-down Docbook in Ascii (Asciidoc) flavor. Again (re)read the post above and tell me how the Asciidoc ordered list using . and .. is more readable or the heading level 3 or 4 using ^^ or ++ and so on.

So how is:

.Ordered

. number

. number

  .. letter

  .. letter

better and more readable than

1. number

2. number

   a. letter

   b. letter

For sure Markdown has some cruft but isn't it better to improve Markdown itself than to try to "establish" a completly new format with some weird conventions such as:

Level 3 Heading

^^^^^^^

Level 4 Heading

+++++++++++++++

Why? ^^ or ++ is this in any way intuitive or an established convention that is so much better?

PS: See Text with Instructions (.texti) for a (better) Markdown evolved variant / flavor :-) - https://texti.github.io

You're misreading what texti is all about. A comment is unix-style # and a heading (title) is using the wikipedia markup convention. You can put as many spaces before as you like it makes no difference to a comment or to a heading (title). See some samples @ https://github.com/texti/texti.github.io/tree/master/samples to compare markdown, texti and wikipedia markup using a real-world article (from wikipedia itself on markup languages).

About extensible - it's no different from markdown with two additions - 1) evolution / changes are more than welcome and 2) texti (like wikipedia markup) has (recursive) template extensions / includes built-in.

For a more pragmatic alternative to Markdown see Text with Instructions (.texti) that gets you the best of Markdown, Wikipedia Markup, LaTeX & Friends. See https://texti.github.io

Great article. I've added the opinion piece / commentary to the Awesome Libra page / collection [1] to cover both sides (that is, for and against). [1]: https://github.com/openblockchains/awesome-libra#articles

Good points. I'm the author of the simple book theme. For more book theme alternatives see the https://github.com/bookdesigns repo that includes a jekyll copy of the "famous" (old/classic) gitbook style (see http://bookdesigns.github.io/book-git ). Another project I started a while ago is called octobook that lets you - surprise, surprise - use jekyll for (online) books, see https://github.com/octobook and https://github.com/geraldb/talks/blob/master/octobook.md Anyways, you're right all book themes still a work-in-progress.

For an alternative slides maker / builder from markdown sources, see the slideshow (s9) tool [1]. Slides template packs include s6, reveal.js, shower,js, impress.js, and many more [2]. [1]: http://slideshow-s9.github.io [2]: http://slideshow-templates.github.io

PS: Note - slideshow (s9) templates are just jekyll (liquid) templates and, thus, work out-of-the-box with github pages and friends.

PPS: What's jekyll :-)? It's the world's most popular (static) website compiler / builder.

FYI: The RubyKaigi 2019 Progress Report on Ruby 3 Talk Slides have more (from the source) info. See the slides titled "Static Analysis" [1]

Ruby 3 static analysis will have four items:

1. Type signature format 2. Level-1 type checking tool 3. Type signature profiling / prototyping tool 4. Level-2 type checking tools

and so on. [1]: https://docs.google.com/presentation/d/1z_5JT0-MJySGn6UGrtda...