21–30 of 236 posts
Is it me or is the "Rivian blue" that he refers to in the video not that close to the color of actual Rivians? IMO the watch band/insert color is less green and quite a bit lighter. Not bad, per se, but I feel like this is not the best descriptor since it might make people think it's a different color.
Earlier quoted context omitted.
Sure; I'm aware that embedded sucks. And to be clear, this is (IMHO) tolerable so long as the blobs are redistributable. But then maybe don't headline with "100% open source". It's better to be honest about it.
I see that kind of thing more often labeled "open hardware" rather than open source.
> We’ve also published electrical and mechanical design files for Pebble 2 Duo. Yes, you can download the schematic (includes KiCad project files) right now on Github! This should give you a nice jumpstart to designing your own PebbleOS-compatible device.
But this is about the software/firmware running on it.
Is it me or is the "Rivian blue" that he refers to in the video not that close to the color of actual Rivians? IMO the watch band/insert color is less green and quite a bit lighter. Not bad, per se, but I feel like this is not the best descriptor since it might make people think it's a different color.
Material color is very tough, especially comparing metallic paint to polycarbonate. Lighting matters, reflections matter. We tried our best, but yes, obviously it's not exactly the same.
> Yesterday, Pebble watch software was ~95% open source. Today, it’s 100% open source. You can download, compile and run all the software you need to use your Pebble. We just published the source code for the new Pebble mobile app! Except... > 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 , Memfa…
Earlier quoted context omitted.
Material color is very tough, especially comparing metallic paint to polycarbonate. Lighting matters, reflections matter. We tried our best, but yes, obviously it's not exactly the same.
And of course, video adds another layer of complexity. Would you say that the video looks accurate to you, or does calling it "Rivian blue" help people understand what it looks like in real life?
* The companion app is now completely open source, ensuring that the community can continue supporting the watches if Core goes under.
* You can subscribe to multiple app stores while optionally paying for services, and Core will maintain their own store. This seems to placate Rebble so they can do their thing and provide their paid services.
Seems like very good steps forward overall.
A few years from now we will see the usual HN thread were contributors lachrymosely complain about how their precious work was stolen by a good-turned-evil organization.
Cheers to Eric for bringing back pebble in the way that he has !
"Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to Core Devices and to recipients of software distributed by Core Devices a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.…
Earlier quoted context omitted.
Part of this is driven by necessity, for example, cellular network chips are typically binary blobs, etc. as mentioned, the heart rate sensor is a binary blob and that's likely because there are no good OSS solutions for those components. A lot of battery firmwares are closed source, the way that they fixed this for the early pinephone was literally just staring at a memory listing and aiming a heat gun at the batter…
Sure; I'm aware that embedded sucks. And to be clear, this is (IMHO) tolerable so long as the blobs are redistributable. But then maybe don't headline with "100% open source". It's better to be honest about it.