31–40 of 236 posts
Earlier quoted context omitted.
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?
I don't actually own a Rivian. I've seen them from afar. They look cool. I have not held a Pebble Time up to a Rivian yet. Maybe I'll creepily do that in downtown Palo Alto today :)
"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.…
https://ericmigi.notion.site/Core-Devices-Software-Licensing...
I understand that some Pebble fans are all about the customization, and will be with you forever. But probably many people care mostly about the battery life, which is severely lacking in watches from Apple, Google, etc.
If Apple realized there was a big enough market to justify making a $200 Apple Watch Basic, how much could that undercut your business?
Relatedly, when will we learn more about the other "core" devices that you're contemplating, and which you alluded to in the video? Building more of a unique ecosystem could help with the moat.
I'm excited that the back will screw off so we can replace the battery. I'm curious about waterproofing. Will that hold? Will we need to replace a gasket or other parts, in addition to the battery?
In the video, the green thing is the gasket. It should be reusable, but nothing's guaranteed in the world of waterproofing.
https://www.ifixit.com/News/113620/the-pixel-watch-4-is-the-...
It is the *end user* who decides which feeds to trust, as it should be. And since it's built right into the app as a core concept, it doesn't take massive engineering effort to switch feeds if some sort of drama occurs.
[0] I'd normally call these repositories, but I've used Eric's term for consistency with the article.
In terms of long-term market viability, have you considered whether your success could encourage Apple or other large competitors to make a battery life-optimized version of their smartwatches? I understand that some Pebble fans are all about the customization, and will be with you forever. But probably many people care mostly about the battery life, which is severely lacking in watches from Apple, Google, etc. If Ap…
Companies like Garmin, Coros and Suunto already make less-smart-watches with weeks of battery life, and those haven't convinced Apple to budge from only making watches that do everything under the sun but barely last a day. Another long-lasting watch from a tiny brand probably isn't going to move the needle.
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 your point, but it feels more like the difference between 99% fat free and 100% fat free. Technically measurable, but irrelevant in practice when the alternatives are all basically closed source.
"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.…
Learned a new word, thank you!
"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.…
Please note our CLA explicitly include a clause to require Core Devices to distribute all contributions under an OSI-compatible FOSS license (e.g. GPLv3). So no contributions can be 'stolen'. https://ericmigi.notion.site/Core-Devices-Software-Licensing...
What we need is more awareness that looking at the license alone is not enough to make an informed decision if contributing to a project is aligned with the contributors attitude and personal goals.
With that in mind: Thank you for putting the CLA right in the repo where it belongs and people can easily find it. Many organizations put a license upfront and bury the CLA. For a particularly bad example try MonoDB.