|2 months ago||2 months ago|
|Apache License 2.0||GNU General Public License v3.0 or later|
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.
Ask HN: Show me your Half Baked project
Interesting! I have it in the backlog that I want to support structured logging via JSON at some point. It's pretty far down the list right now though since I personally haven't used structured logging very much.
I added an issue about it: https://github.com/JackBister/logsuck/issues/7 - if you want to chip in with any comments or even help out with implementing it it'd be much welcomed!
I think it's a little bit beyond "half" baked, but I built a thing I call Logsuck last year: https://github.com/jackbister/logsuck
The idea is to have a free Splunk alternative which you can set up with just one binary. I use Splunk at work and love it, but it just doesn't seem like a product for solo developers (I can't even find a pricing page on splunk.com), and the primary free alternative, the ELK stack, seems a bit complicated to set up.
I am sure that I'll never be competitive with Splunk or Elastic in terms of features or scalability but I'm trying to build something that is at least useful for my own projects.
I built it in Go and use SQLite with the FTS (https://sqlite.org/fts3.html) extension to store the log events in a way where they can be searched quickly.
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 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:
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.
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.
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
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?
ht - Friendly and fast tool for sending HTTP requests
UsTaxes - Tax filing web application
diem - Diem’s mission is to build a trusted and innovative financial network that empowers people and businesses around the world.
go-live - 🗂️ go-live is an ultra-light server utility that serves files, HTML or anything else, over HTTP.
learn-anything.xyz - Organize world's knowledge, explore connections and curate learning paths
thgtoa - The Hitchhiker’s Guide to Online Anonymity
pegao - Pegao is a community about lists of links on topics of interest.
dflex - The sophisticated Drag and Drop library you've been waiting for 🥳
hacn - A "monad" or DSL for creating React components using Fable and F# computation expressions
pcopy - pcopy is a temporary file host, nopaste and clipboard across machines. It can be used from the Web UI, via a CLI or without a client by using curl.