Näin se tehdään oikein:
Bose lakkauttaa vanhimpien älykaiutintensa tuen lähiaikoina. Mutta yhtiö julkaisi rajapintojen kuvaukset avoimena lähdekoodina - ja siirtää ison osan toiminnallisuudesta suoraan kännykkäsovellukseen.
Eli tuen loppumisesta huolimatta älykaiuttimet eivät muutu "tyhmiksi", vaan niihin voidaan luoda jopa uusiakin toimintoja.
https://dawn.fi/uutiset/2026/01/15/bose-avoin-lahdekoodi-kaiutin
#bose #avoinlahdekoodi #oss #iot #älykoti #uutiset #teknologia #tekniikka
Näin se tehdään oikein:
Bose lakkauttaa vanhimpien älykaiutintensa tuen lähiaikoina. Mutta yhtiö julkaisi rajapintojen kuvaukset avoimena lähdekoodina - ja siirtää ison osan toiminnallisuudesta suoraan kännykkäsovellukseen.
Eli tuen loppumisesta huolimatta älykaiuttimet eivät muutu "tyhmiksi", vaan niihin voidaan luoda jopa uusiakin toimintoja.
https://dawn.fi/uutiset/2026/01/15/bose-avoin-lahdekoodi-kaiutin
#bose #avoinlahdekoodi #oss #iot #älykoti #uutiset #teknologia #tekniikka
Simon Willison on porting OSS code:
> I think that if “they might train on my code is enough to drive you away from open source, your open source values are distinct enough from mine that I’m not ready to invest significantly in keeping you. I’ll put that effort into welcoming the newcomers instead.
https://simonwillison.net/2026/Jan/11/answers/
This feels very much like colonialism; take over all the #OSS code, drive the original developers away, and give the colonizers the code as a welcome present.
Simon Willison on porting OSS code:
> I think that if “they might train on my code is enough to drive you away from open source, your open source values are distinct enough from mine that I’m not ready to invest significantly in keeping you. I’ll put that effort into welcoming the newcomers instead.
https://simonwillison.net/2026/Jan/11/answers/
This feels very much like colonialism; take over all the #OSS code, drive the original developers away, and give the colonizers the code as a welcome present.
Simon Willison on porting OSS code:
> I think that if “they might train on my code is enough to drive you away from open source, your open source values are distinct enough from mine that I’m not ready to invest significantly in keeping you. I’ll put that effort into welcoming the newcomers instead.
https://simonwillison.net/2026/Jan/11/answers/
This feels very much like colonialism; take over all the #OSS code, drive the original developers away, and give the colonizers the code as a welcome present.
So who’s coming to #EverythingOpen in #Canberra 21-23 January?
Who am I looking out for in the hallway track to tell me about their adventures in #OSS?
(If you’ve not yet organised yourself … hurry up!!!)
https://2026.everythingopen.au
So who’s coming to #EverythingOpen in #Canberra 21-23 January?
Who am I looking out for in the hallway track to tell me about their adventures in #OSS?
(If you’ve not yet organised yourself … hurry up!!!)
https://2026.everythingopen.au
Does the #rust #rustlang community know of a crate that I can include for editing config files from CLI?
I want to be able to `myapp config set foo.bar 5` but I don't want to write everything myself for doing that.
There's `toml-cli` and `toml-edit`, the former is not a library, the latter is a library but I would need to write the CLI bindings myself.
maybe someone gets nerdsniped here?