[emmanueloga_]

> There were missteps along the way. A big example was the TV software that was originally an acquisition, SageTV [2]. Somebody decided it would be a good idea to completely rewrite this Java app into Web technologies on an embedded Chrome instance on a memory-limited embedded CPU in a set-top box. Originally planned to take 6 months, it took (IIRC) 3.5+ years.

I worked on the "misstep" with a small team, and it’s wild to see Fiber still around and even expanding to new cities. As far as I can tell, the set-top box software had nothing to do with why Fiber was scaled down. Also, usability surveys showed people really liked the GUI!

The client supported on-demand streaming, live TV, and DVR on hardware with... let’s call them challenging specs. Still, it turned out to be a pretty slick app. We worked hard to keep the UI snappy (min 30 FPS), often ditching DOM for canvas or WebGL to squeeze out the needed performance. A migration to Cobalt [1], a much lighter browser than embedded Chromium, was on the table, but the project ended before that could happen.

Personally, it was a great experience working with the Web Platform (always a solid bet) on less-traditional hardware.

--

1: https://developers.google.com/youtube/cobalt

[shadowfu]

+1 to what was said above; the UI didn't take 3.5 years to make - we launched it fairly quickly and then continued to improve on it. Later there was large UX refresh, so maybe that's where OP is getting confused? Either way, that software continued to work for years after the team was moved on to other projects. SageTV was good, but the UI wasn't java - it was a custom xml-like layout.