z0mbie42

hi, it's a matter of consistency.

It has been discussed here: https://github.com/bloom42/sane/issues/3

TL;DR: modern languages (Rust, Scala... except Go) use spaces. Allowing both will cause pain. And if in the future Tabs alongside spaces is really needed, It can be added in a non-breaking release, while allowing then disallowing tabs if they cause too much pain is non backward compatible.

Hi author here,

I've been developing an open standard since some time to replace the ugliness of YAML and TOML and the flaws of JSON for configurations files.

Configuration files (Human to machine) have some needs that TOML/YAML do not satisfy (clarity, tooling/linting friendliness, consistency, safety, parsers friendliness...) and JSON neither (as it was designed to be mahcine to machine it does not have comments, have null...).

It's currently used in production with success.

Here is the website for the standard: https://opensource.bloom.sh/sane

Here is the repo for the standard: https://github.com/bloom42/sane

and here is the repo for the Go parsing library: https://github.com/bloom42/sane-go

Going shortly towards a v1.0 any feedback is welcome.

Living part time there, this claim is false.

Hi,

I've ported the kickstarter's event sourcing framework (https://kickstarter.engineering/event-sourcing-made-simple-4...) to Go. It's similar to the flux architecture in the backend.

Any feedback is welcome.

Hi,

First I want to make it clear that my preferred licenses are 'by default of better'. That mean, regarding the news (re licensing of famous open source projects) we clearly lack of License for real world use case (With cloud providers abusing open sources projects and being unfair to companies behind them.

- Apache 2.0 (or an 'official' CCL) for libraries or small projects because it's simplicity and protection

- AGPLv3.0 (or an 'official' SSPL) for large projects, or project I would like to sell as a service.

The ideal would be to 'make official' Confluent Community License (Apache 2.0 minus SaaS) and Server Side Public License (AGPLv3.0 minus SaaS) to protect the ecosystem and fund the open source actors.

I think those 'hybrid' licenses are a great move toward open source and free software sustainability and hope we will see some 'official' Licenses soon.

After measuring the (negative) impact of social networks on my productivity and how I interacted with them, I took radical steps to reduce their usage.

I do not believe that weeks long break are a good idea, but instead reduce their daily/weekly usage.

- reduce their accessibility to not machinaly open them. for e.g do not have the application on your mobile (+ a great win against data harvesting) - reduce the social networks number (I left Facebook because it didn't bring any value to me, but kept twitter)

Hi, I acknowledge this, but as those 2 projects are not similar I think there can't be a confusion between the two.

I know but I also find this is the perfect name for this project (the goal of analytics is to discover signal in the noise, privacy oriented like the messenger app) so I don't want to exclude all names already associated to existing projects and restrict to some weird or badly orthographed names

Hi author here.

Logging is hard but you can't avoid it (https://kerkour.com/post/logging) so I'm trying to create an improved experience across all programming languages, let me introduce to you: Astroflow - The unified logging layer.

An unified API for fast and configurable logging libraries.

There is currently the Go version: https://github.com/astrocorp42/astroflow-go

and the JavaScript version: https://github.com/astrocorp42/astroflow-js

An issue is opened for discussion. Feel free to explain your real life use case for the use of a date type

1) Can I ask what? because I did my research but didn't found anything

2) https://astrocorp.net/san/versions/v1.0.0/#string

Very pragmatic, I love it!

I will explore this.

Yes, The problem is that we want a pure data configuration format. We think that very few application require a full turing complete language for their configuration.

Bazel have too it's own (turing complete ?) Programming configuration language

That's the point, we didn't ever find a good reason to use heterogeneous lists.

They can all be replaced by maps which may seems more verbose but carry in fact far more information and clear

Hi, good reply.

The reason for brackets are auto formatting by the san CLI (think go/rust fmt)

Thank you, it's very encouraging!

The second point is acknowledged

Ack

I've opened an issue https://github.com/astrocorp42/san/issues/12

Hi, HCL was one of the source of inspiration. We wanted to push it 1 step further by providing a clear and open specification which allows to create parsers for languages other than go.

So the main differences are the ecosystem: a CLI to auto format - think go fmt) and validate SAN files, parsers for languages others than Go

Hi, HCL was one of the source of inspiration. We wanted to push it 1 step further by providing a clear and open specification which allows to create parsers for languages other than go.

Hi, on of the major benefits pf adding braces is the support for auto format (think go/rust fmt).

Furthermore, how would you explain to a non developer that ``` a: b: nested ```

is different than: ``` a: b: non nestee ```

Hi, the main concern with your solution is that it does not support auto format (think go fmt). While adding braces and not being indentation based allow auto format and large file to be read more easily

Hi, it's very interesting!

Do you test if TimescaleDB affect the performances of the relational part of Postgres ? In other words, can I use TimescaleDB as my primary DB to store both my users and time series data ?

Hi author here.

We've created a new file format designed specifically for configuration: SAN (pronounce /seɪn/ like sane).

You can find a Go parser here: https://github.com/phasersec/san-go

Vim syntax here: https://github.com/z0mbie42/vim-san

SAN was created because of a need to have a Simple And Neat configuration format (with comments, unlike JSON, easy to parse unlike YAML....).

The main killer features compared to YAML/TOML are the following:

* Comments as first class citizens which means programs can manipulate and modify files with comments without destroying them.

* Safe

* Human and parser friendly

* Easy to use, even without syntax coloration

It's an open format and any feedback is welcome.

Hi author here.

We've created a new file format designed specifically for configuration: SAN (pronounce /seɪn/ like sane).

You can find the spec here: https://astrocorp.net/san and Vim syntax here: https://github.com/z0mbie42/vim-san

SAN was created because of a need to have a Safe And Neat configuration format (with comments, unlike JSON, easy to parse unlike YAML....).

The main killer features compared to YAML/TOML are the following:

* Comments as first class citizens which means programs can manipulate and modify files with comments without destroying them.

* Safe

* Human and parser friendly

* Easy to use, even without syntax coloration

It's an open format and any feedback is welcome.

Hi author here.

We've created a new file format designed specifically for configuration: SAN (pronounce /seɪn/ like sane).

You can find a Go parser here: https://github.com/phasersec/san-go and Vim syntax here: https://github.com/z0mbie42/vim-san

SAN was created because of a need to have a Safe And Neat configuration format (with comments, unlike JSON, easy to parse unlike YAML....).

The main killer features compared to YAML/TOML are the following:

* Comments as first class citizens which means programs can manipulate and modify files with comments without destroying them.

* Safe

* Human and parser friendly

* Easy to use, even without syntax coloration

It's an open format and any feedback is welcome.

Thank you for the feedback! What kind of error do you have? On safari with IOS ? The frontend is VueJS with https://vuetifyjs.com so it should work

Thank you! It was the whole point to be simple and beautiful

Omg you are right! As I can't longer edit here is the URL

https://github.com/astrocorp42/rocket

Hi,

Here is the GitHub: https://github.com/astrocorp42/rocket

It started with the need to automate assets uploading for github relases for go binaries but then it appeared that it could be awesome to add other providers like Heroku, Firebase, Netlify, AWS S3 to simplify and automate the process of software delivery.

rocket is the D in CI/CD: It allows to easily deliver software to a large range of providers from any CI pipeline.

It should be as easy as possible to use, Any feedback is welcome : )

Hi, author here.

As a user of both travis and gitlab-ci I wanted a more unified and simple deployment experience across various providers, whether it be GitHub releases, Heroku, Firebase, AWS S3...

As said rocket is the D in CI/CD: It allows to easily deploy software across a large range of providers from any CI/CD pipeline.

It does not replace your build system but instead help you to easily push your code in your various environments (dev, staging, production...).

It should be as easy as possible to use, Any feedback welcome.