datashare
cue
datashare | cue | |
---|---|---|
4 | 28 | |
545 | 3,181 | |
2.0% | - | |
9.8 | 9.1 | |
5 days ago | almost 3 years ago | |
Java | Go | |
GNU Affero General Public License v3.0 | Apache License 2.0 |
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.
datashare
-
Leaks! how to organize them?
Datashare just came out, with full-text index NLP etc https://github.com/ICIJ/datashare Enjoy
-
Journalism/research/information linking/graph db
If you are doing investigative journalism, there is the OCCRP's Aleph for working with big amounts of data and connecting entities https://aleph.occrp.org/ . It's open source and self-hostable. Also for big messy dataset, the ICIJ's Datashare might be interesting.
-
Ask HN: What you up to? (Who doesn't want to be hired?)
I have slowly collected a large (several million file) ebook library from open directories over the past few years. I am now trying to set up a search solution for it.
Recoll doesn't seem to work well headless, so I am taking a look at: https://github.com/ICIJ/datashare
which claims to be able to do some distributed indexing.
-
Datashare a tool to better search files
There's a github too, https://github.com/ICIJ/datashare
cue
- The Perfect Configuration Format? Try TypeScript
- YAML: It's Time to Move On
-
Ask HN: What you up to? (Who doesn't want to be hired?)
I'm continuing to work on https://concise-encoding.org which is a new security-conscious ad-hoc encoding format to replace JSON/XML and friends. I've been at it for 3 years so far and am close to a release.
In a nutshell:
- Edit in text, transmit in binary. One can be seamlessly converted to the other, but binary is far more efficient for processing, storage and transmission, while text is better for humans to read and edit (which happens far less often than the other things).
- Secure by design: Everything is tightly specced and accounted for so that there aren't differences between implementations that can be exploited to compromise your system. https://github.com/kstenerud/concise-encoding/blob/master/ce...
- Real type support because coercing everything into strings sucks (and is another security risk and source of incompatibilities).
XML had a good run but was replaced by JSON which was a big improvement. JSON also had a good run but it's time for it to retire now that the landscape has changed even further: Security and efficiency are the desires of today, and JSON provides neither.
I've got the spec nailed down and can finally see the light at the end of the tunnel for the reference implementation in golang. I still need to come up with a system for schemas, but I'm hoping that https://cuelang.org will fit the bill.
-
No YAML
Has anyone taken a look at Cue who can share any experiences?
https://cuelang.org/
It's mentioned on the site as an alternative to Yaml. Recently watched (~half of) this intro to it: https://youtu.be/fR_yApIf6jU
- Ask HN: Is there a good way to run integration tests on Kubernetes?
-
Cue: A new language for data validation
the most interesting summary explanation of cue lang and its differences is from a bug filing - https://github.com/cuelang/cue/issues/33
>CUE is a bit different from the languages used in linguistics and more tailored to the general configuration issue as we've seen it at Google. But under the hood it adheres strictly to the concepts and principles of these approaches and we have been careful not to make the same mistakes made in BCL (which then were copied in all its offshoots). It also means that CUE can benefit from 30 years of research on this topic. For instance, under the hood, CUE uses a first-order unification algorithm, allowing us to build template extractors based on anti-unification (see issue #7 and #15), something that is not very meaningful or even possible with languages like BCL and Jsonnet.
-
CMake proposal: Unified way of describing dependencies of a project
I agree with you. Personally, I think Cue is much better than either YAML, TOML or JSON because it adds the concept of types to the idea of describing configuration.
-
Cloud Infrastructure as SQL
true, but the tooling and workflow remains the same.
Not sure of any tool that could abstract the details sufficiently to be widely adopted. There is just too much nuance in cloud config.
I'm exploring using CUE (https://cuelang.org) to define TF resources, exporting as JSON for TF. So far it's much nicer
What are some alternatives?
aleph - Search and browse documents and data; find the people and companies you look for.
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
peterburk - Github page [Moved to: https://github.com/peterburk/peterburk.github.io]
dhall-lang - Maintainable configuration files
resholve - a shell resolver? :) (find and resolve shell script dependencies)
jsonnet - Jsonnet - The data templating language
mpack - MPack - A C encoder/decoder for the MessagePack serialization format / msgpack.org[C]
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
PropertyWebBuilder - Create a fully featured real estate website on Rails in minutes! ⛺
ytt - YAML templating tool that works on YAML structure instead of text
create-rust-app - Set up a modern rust+react web app by running one command.
starlark-rust - A Rust implementation of the Starlark language