You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2025-01-26-the-future-of-rebble.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ and will accelerate our efforts to produce new hardware.
17
17
18
18
Previously, we have been working on our own replacement firmware: [RebbleOS](https://github.com/pebble-dev/RebbleOS). As you can see by the commit history though, progress was slow.
19
19
Building a production-ready realtime OS for the Pebble is no small feat, and although we were confident we'd get there given enough time, it was never our ideal path.
20
-
Thanks to the hard work of many people both within Google and not, we finally have our hands on the original source code for PebbleOS. You can read [their blog post on it here.](https://opensource.googleblog.com/2025/01/see-code-that-powered-pebble-smartwatches.html)
20
+
Thanks to the hard work of many people both within Google and not, we finally have our hands on the original source code for PebbleOS. You can read [Google's blog post on this for even more information.](https://opensource.googleblog.com/2025/01/see-code-that-powered-pebble-smartwatches.html)
21
21
22
22
This does _not_ mean we instantly have the ability to start developing updates for PebbleOS though, we first will need to spend some concentrated time getting it to build.
23
23
But before we talk about that, let's talk about Rebble itself.
0 commit comments