‹ BackHN Continuity

Thread

Ideas on modernizing the open-source desktop

407 points · 545 comments · signa11

  1. Naru41 · · focus · HN ↗
    <a href="https:&#x2F;&#x2F;www.eclipse.org&#x2F;articles&#x2F;Article-UI-Guidelines&#x2F;Contents.html" rel="nofollow">https:&#x2F;&#x2F;www.eclipse.org&#x2F;articles&#x2F;Article-UI-Guidelines&#x2F;Conte...

    In 2004, the Eclipse IDE established consistent UI guidelines, built upon a cross-platform GUI library. API desgin is great, Looks and feels robust. The future of desktop GUIs looked bright. Little did we know that 25 years later it would turn out to be such a disaster.

    1. arijun · · focus · HN ↗
      Care to elaborate? How is eclipse a disaster, and how does that pertain to pushing new ideas for an OS?
      1. 6581 · · focus · HN ↗
        I&#x27;d assume &quot;disaster&quot; refers to &quot;future of desktop GUIs&quot;, not to Eclipse.
        1. someonebaggy · · focus · HN ↗
          Eclipse is also a disaster internally though, it&#x27;s not CADT but it&#x27;s extreme loose coupling, everything setting observers on everything else and keeping its own mirror copy of the data up to date with no idea of the context they&#x27;ll run in, and if the updates arrive out of order you get state desyncs, and sometimes you get deadlocks because nobody really knows what&#x27;s calling what, so you can&#x27;t have a lock hierarchy.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.