411 karma · joined September 29, 2011
A software author has the right to set terms for use of their software, including requiring that manufacturers provide end users certain freedoms.
>Another important note - some binary blobs and other non-free software components are used today in PebbleOS and the Pebble mobile app (ex: the heart rate sensor on PT2 , Memfault library, and others). Optional non-free web services, like Wispr-flow API speech recognizer, are also used. These non-free software components are not required - you can compile and run Pebble watch software without them. This will always be the case. More non-free software components may appear in our software in the future. The core Pebble watch software stack (everything you need to use your Pebble watch) will always be open source.
100% should mean 100%
However, aren't Moq, Avalonia and MassTransit free software?
As for Automapper and MediatR, their owner changed from a free software license to only an open source one (Reciprocal Public License), but these are probably the simplest libraries of the ones you mentioned and have either been forked (MagicMapper) or have alternatives.
We need to get EU on this case.
That being said, the fact that quick maths can give you a 6 orders of magnitude difference between functional code and the package is probably reason for concern.
I notice you use the word choice and classify the pro-life position s "anti-choice" which makes it seem like a bad thing. However the "choice we are talking about here is directly and intentionlly causing death to an innocent human being. I think it is very important to understnd that.
To borrow an atheist trope, you and I agree that murder is evil and immoral in most cases. I just think it's wrong in one more case, when the victims are yet unborn too (I reckon murder is intrinsically evil and immoral)
Using a pointer, I'd prefer to just be able to click on the oval to zoom into, maybe double-click to zoom back out a level, use the back button to go to the place I came from.
The first sentence of your link reads:
>The C/Unix time- and date-handling API is a confusing jungle full of the corpses of failed experiments and various other traps for the unwary, many of them resulting from design decisions that may have been defensible when the originals were written but appear at best puzzling today.
I was expecting something more like sqlx, which I believe provides compile-time checking for SQL queries without a DSL, but for Rust
If that doesn't work, they could introduce premium features. Stuff that obviously has to cost money would make the pill easier to swallow, for example, features that depends on third party services (only LLMs come to mind right now), or human assistance (real-life instructors). Admittedly, this would be a compromise. One could argue it fails on the 100% part, but another could argue that 100% of existing features remain free.
>We did think about it for about three seconds - was it a betrayal to my parents, to my father's [wishes]? And we decided, yes, it was a betrayal. But that's what children are for.