blog VS svg_parser

Compare blog vs svg_parser and see what are their differences.

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
blog svg_parser
1 1
337 5
- -
3.4 10.0
5 months ago over 8 years ago
TypeScript HTML
GNU General Public License v3.0 or later -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

blog

Posts with mentions or reviews of blog. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-06.
  • Plain Text. With Lines
    12 projects | news.ycombinator.com | 6 Jun 2022
    becomes a colored bar chart with three bars. So the file is both kinda readable in a plain text editor, in a browser with js disabled (with React server side rendering), and in the richest version with JS enabled. I don't have a WYSIWYG editor for the widgets though, that's pretty neat.

    Full example:

    Markdown:

    https://github.com/phiresky/blog/blob/master/posts/2021/host...

    Corresponding post with interactive widgets:

    https://phiresky.github.io/blog/2021/hosting-sqlite-database...

svg_parser

Posts with mentions or reviews of svg_parser. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-06.
  • Plain Text. With Lines
    12 projects | news.ycombinator.com | 6 Jun 2022
    Congratulations, now you replaced a trivial file format that (from a quick glance at the code) needed about ~35 of easily readable and self-contained Lua code to parse with an external dependency that would be much larger and harder to follow and either having (at least) an XML parser as its own dependency or implementing its own XML parsing, as well as being at the mercy of their developers. Also unless you are using some highly popular library, you may end up with some abandoned dependency.

    Examples of both are at [0] (C++ based parser, you'd also need to write some bindings for lua) and [1] (Lua based parser for a subset of the format, abandoned for almost a decade).

    There are times when using an external dependency might be a good idea, but a text-based file format that describes lines and can be implemented in a few lines of code is not one.

    [0] https://github.com/svgpp/svgpp

    [1] https://github.com/luapower/svg_parser

What are some alternatives?

When comparing blog and svg_parser you can also consider the following projects:

eastend-notebook-syntax - Atom syntax theme - East End Notebook

TekGraphics - Sample data for Tektronix graphics terminals and code for use with xterm

json.lua - A lightweight JSON library for Lua

DrawIt - Ascii drawing plugin: lines, ellipses, arrows, fills, and more!

docs - Logseq documentation

logseq - A local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base. Use it to organize your todo list, to write your journals, or to record your unique life.

SVG++ - C++ SVG library