jfcg/rng: v1.1.1 release

[jfcg...@gmail.com]

Hi Go community,

jfcg/rng v1.1.1 was released with pseudo random number generator (just 24 bytes) and updated benchmarks.

It uses a minimal sponge. I am also interested in ideas to determine/guess the period of the permutation used here (Prng.Get()).

Let me know what you think..

[Jason E. Aten]

Hi Serhat,

A sponge implementation sounds kind of interesting, but the MPL license rather

than something friendly like MIT/BSD means I won't bother with it or even really looking at it.

Best wishes,

Jason

[Serhat Sevki Dincer]

Hi Jason,

- MPL is a file based license, covering only files released under it. Unlike GPL, it does not “spread” to other files in a project that uses MPL libraries.

- Users of MPL libraries (who do not own copyright on those libraries) must disclose their changes “only” on those MPL libraries IF they want to modify AND distribute those MPL licensed files in some form (like source code or an executable).

- If you don’t modify an MPL library source you don’t have to do anything, you can use it in anything including your closed source commercial software. Many commercial software regularly use MPL licensed libraries.

I think it is a great and flexible library license, it ensures fixes/improvements on the library only to be contributed back to the library. That’s why I chose it for almost all of my open source work.

Regards..

--
You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golang-nuts/ygDcOuTd1RE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/32b2970a-9538-4fdb-b38c-a25bc827397en%40googlegroups.com.

[Jan Mercl]

On Tue, Aug 5, 2025 at 6:49 AM Serhat Sevki Dincer <jfcg...@gmail.com> wrote:

> - MPL is a file based license, covering only files released under it. Unlike GPL, it does not “spread” to other files in a project that uses MPL libraries.
>
> - Users of MPL libraries (who do not own copyright on those libraries) must disclose their changes “only” on those MPL libraries IF they want to modify AND distribute those MPL licensed files in some form (like source code or an executable).
>
> - If you don’t modify an MPL library source you don’t have to do anything, you can use it in anything including your closed source commercial software. Many commercial software regularly use MPL licensed libraries.
>
> I think it is a great and flexible library license, it ensures fixes/improvements on the library only to be contributed back to the library. That’s why I chose it for almost all of my open source work.

TIL how much better MPL is than I thought before. Thanks for posting!

-j