cl-test-grid VS go-concise-encoding

Compare cl-test-grid vs go-concise-encoding and see what are their differences.

cl-test-grid

Collaborative testing of Common Lisp libraries (by cl-test-grid)

go-concise-encoding

Golang implementation of Concise Binary and Text Encoding (by kstenerud)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
cl-test-grid go-concise-encoding
3 8
82 30
- -
1.9 6.9
9 months ago 6 months ago
NewLisp Go
MIT License 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.

cl-test-grid

Posts with mentions or reviews of cl-test-grid. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-06.

go-concise-encoding

Posts with mentions or reviews of go-concise-encoding. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-15.
  • Ask HN: How long does it take for you to release your open source project?
    7 projects | news.ycombinator.com | 15 Mar 2023
    I'm not sure, TBH... Maybe I'm just a glutton for punishment?

    I'm currently partway through refactoring all of the portable unit tests for Concise Encoding ( https://github.com/kstenerud/go-concise-encoding/tree/master... ) and it is a SLOG! I mean, so goddamn boring and tedious that I wanna stick an ice pick through my skull. There's easily another 200 hours of this terrible work ahead and I'll be right back to it the moment Dogma v1 is published in a few weeks (Dogma has been kind of a vacation from it in a lot of ways).

    Do I dread it? Yes. Am I still going to do it? Yes. Because at the end of the day I want to be able to stand back and say "I made that. I completed it - ALL of it. It's not perfect, but it's doing its job and people are using it."

  • Working in the software industry, circa 1989 – Jim Grey
    5 projects | news.ycombinator.com | 11 Jul 2022
    It's still in the prerelease stage, but v1 will be released later this year. I'm mostly getting hits from China since they tend to be a lot more worried about security. I expect the rest of the world to catch on to the gaping security holes of JSON and friends in the next few years as the more sophisticated actors start taking advantage of them. For example https://github.com/kstenerud/concise-encoding/blob/master/ce...

    There are still a few things to do:

    - Update enctool (https://github.com/kstenerud/enctool) to integrate https://cuelang.org so that there's at least a command line schema validator for CE.

    - Update the grammar file (https://github.com/kstenerud/concise-encoding/tree/master/an...) because it's a bit out of date.

    - Revamp the compliance tests to be themselves written in Concise Encoding (for example https://github.com/kstenerud/go-concise-encoding/blob/master... but I'll be simplifying the format some more). That way, we can run the same tests on all CE implementations instead of everyone coming up with their own. I'll move the test definitions to their own repo when they're done and then you can just submodule it.

    I'm thinking that they should look more like:

        c1
  • Ask HN: What are some tools / libraries you built yourself?
    264 projects | news.ycombinator.com | 16 May 2021
    I'm building a general-purpose data format for the modern age. The old ones are too bulky, too insecure, and too limiting.

    * Secure: As a tightly specified format, Concise Encoding doesn't suffer from the security problems that the more loosely defined formats do. Everything is done one way only, leaving less of an attack surface.

    * Efficient: As a twin binary/text format, Concise Encoding retains the text-based ease-of-use of the old text formats, but is stored and transmitted in the simpler and smaller binary form, making it more secure, easier on the energy bill, and easier on the planet.

    * Versatile: Supports all common types natively. 90% of users won't need any form of customization.

    * Future-proof: As a versioned format, Concise Encoding can respond to a changing world without degenerating into deprecations and awkward encodings or painting itself into a corner.

    * Plug and play: No extra compilation steps or special description formats or crazy boilerplate.

    https://concise-encoding.org

    Reference implementation (golang): https://github.com/kstenerud/go-concise-encoding

  • I'd like to review your README
    7 projects | news.ycombinator.com | 17 Apr 2021
    One thing golang did right is the go playground. When I put code in my README, I also include a playground link.

    Example: https://github.com/kstenerud/go-concise-encoding#library-usa...

  • Architecture.md
    11 projects | news.ycombinator.com | 6 Feb 2021
    I've started doing this in my larger projects e.g. https://github.com/kstenerud/go-concise-encoding/blob/master...

    An architecture document should be the code equivalent of a combined street map and tourist guide. Its purpose is to bring strangers up to a minimum level of familiarity with the code as quickly as possible. That includes where things are, why it was architected this way, things to look out for, and a few interesting points of weirdness perhaps.

  • Ask HN: Show me your Half Baked project
    154 projects | news.ycombinator.com | 9 Jan 2021
    Concise Encoding: https://concise-encoding.org

    The friendly data format for human and machine. Think JSON, but with 1:1 compatible twin binary and text formats and rich type support.

    * Edit text, transmit binary. Humans love text. Machines love binary. With Concise Encoding, conversion is 1:1 and seamless.

    * Rich type support. Boolean, integer, float, string, bytes, time, URI, UUID, list, map, markup, metadata, etc.

    * Plug and play. No schema needed. No special syntax files. No code generation. Just import and go.

    I'm in the process of finishing up the reference implementation (https://github.com/kstenerud/go-concise-encoding), after which I'll start on the schema specification. Once that's done, I have a low-level communication protocol that will use this format under the hood.

What are some alternatives?

When comparing cl-test-grid and go-concise-encoding you can also consider the following projects:

diem - Diem’s mission is to build a trusted and innovative financial network that empowers people and businesses around the world.

logsuck - Easy log aggregation, indexing and searching

thgtoa - The Hitchhiker’s Guide to Online Anonymity

Joplin - Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS.

cargo-readme - Generate README.md from docstrings

Outline - The fastest knowledge base for growing teams. Beautiful, realtime collaborative, feature packed, and markdown compatible.

vaku - vaku extends the vault api & cli

Tabula - Extract tables from PDF files

Task - A task runner / simpler Make alternative written in Go

lowdefy - The config web stack for business apps - build internal tools, client portals, web apps, admin panels, dashboards, web sites, and CRUD apps with YAML or JSON.

gutenberg - A fast static site generator in a single binary with everything built-in. https://www.getzola.org