that’s your interpeetation. what’s missing for me is “must be freely (as in not only by specific entities) obtainable”. with this wording i could just say: “this data is not obtainable” and be done with it.
that’s your interpeetation. what’s missing for me is “must be freely (as in not only by specific entities) obtainable”. with this wording i could just say: “this data is not obtainable” and be done with it.
no it doesn’t. it only says the weights an information about the training data must be open, not the training data itself. which is honestly useless.
In austrian german dialect, “Mit da Ua, draht ma zua.” which in standard german would be “Mit der Uhr, dreht man zu.” and in english “With the clock, turn it closed.” or something like that.
BUT IT’S A SINGLE BINARY! UNACCEPTBLE!!! THE BLOAT OF IT ALL!
it was a joke xD i like busybox (and systemd) i don’t particularly subscribe to the unix way, but to each their own ¯\_(ツ)_/¯
“Noooooooo! One tool should do one thing and one thing only! Blasphemy! Heresy! Anthema! Systemd!” crying in unix design philosophy
It’s so funny because in the article it is even mentioned, that the agricultural minister did the same thing a few weeks ago, but he is from the chancellors party, the People’s Party. Also, Nehammer (the chancellor) doesn’t dissolve the government because his party is scared shitless of elections right now. They would (and in November at the general elections probably will) be painfully reduced. Sadly in favor of the super right wing FPÖ (fReEdOm party 🤡, as in freedom to be an asshole).
Sources: article and general knowledge as an informed austrian citizen
laughs/cries in embedded we are currently changing from mbed to zephyr rtos. at the beginning it was decided we will never replace mbed, the thing i am currently replacing, so all the code is using parts of mbed everywhere. there’s not enough space on the chip to have both mbed and zephyr in parallel. yay. you desktop/server/web/whatever people don’t how good you have it.
have a look at nix
As an embedded firmware guy for 10ish years:
C can die in a fire. It’s “simplicity” hides the emergent complexity by using it as it has nearly no compile time checks for anything and nearly no potential for sensible abstraction. It’s like walking on an infinite tight rope in fog while an earth quake is happening.
For completely different reasons: The same is true for C++ but to a far lesser extent.
On the official page it says that it is pronounced For Jay Yo (at least close enough)