Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 10 submissions in the queue.
posted by martyb on Tuesday February 07 2017, @09:41AM   Printer-friendly
from the window-systems-need-window-shades dept.

What is Unity 8 and why's it a big deal?

Unity as a name and project began life in 2010 as a new UI for desktops and laptops and it arrived swiftly – in the following year. However, the idea morphed to offer the same screen and user experience on all devices regardless of mouse or touch. Put Ubuntu running Unity 8 on a phone and it'll render as a phone, put it on a PC and it'll render as a PC, put it on a tablet and it'll render as a tablet. That's the idea anyway, and it was analogous to ideas floating around Redmond for a single version of Windows running on PCs, phones and tablets – the same UI and same "experience". One brand, development and runtime.

That was part of the idea of Windows 8 anyway, and the Metro UI.

Coming with Unity 8 is Mir, the planned display server replacement to the predominant X Windows[sic] System, which Canonical announced in March 2013.

X Windows[sic] System is an industry standard for bitmap displays in Unix-like systems such as Ubuntu and is the product of Stanford University, MIT and IBM. Canonical wants to build its own display server, however.

Four years on, though, the dream remains unrealised with Mir like Unity 8 available only as a preview.

Unity 8 is, by the reckoning of Ubuntu daddy Mark Shuttleworth, a year late.

Windows 8 was an amazing innovation and totally worth replicating?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Tuesday February 07 2017, @10:33AM

    by Anonymous Coward on Tuesday February 07 2017, @10:33AM (#463967)

    Define secure keyboard.

  • (Score: 1) by butthurt on Tuesday February 07 2017, @10:52AM

    by butthurt (6141) on Tuesday February 07 2017, @10:52AM (#463971) Journal

    One that can't be intercepted by a key-logger, I assume. This advert introduces it.

    http://www.youtube.com/watch?v=NF3xbgQ5gAA [youtube.com]

    See also RFC 3514.

    https://tools.ietf.org/html/rfc3514 [ietf.org]

  • (Score: 1, Informative) by Anonymous Coward on Tuesday February 07 2017, @11:07AM

    by Anonymous Coward on Tuesday February 07 2017, @11:07AM (#463975)

    From the xterm man page:

    The xterm menu (see MENUS above) contains a Secure Keyboard entry
    which, when enabled, attempts to ensure that all keyboard input is
    directed only to xterm (using the GrabKeyboard protocol request). When
    an application prompts you for a password (or other sensitive data),
    you can enable Secure Keyboard using the menu, type in the data, and
    then disable Secure Keyboard using the menu again.

    • (Score: 0) by Anonymous Coward on Tuesday February 07 2017, @09:21PM

      by Anonymous Coward on Tuesday February 07 2017, @09:21PM (#464296)

      https://www.x.org/releases/X11R7.6/doc/xextproto/security.html [x.org] copyright 1996, over 20 years old. So the problem is not X11, the problem is the programs that ignore the things already provided. Two decades of "X11 is insecure" bullshit. No, your fucking program or toolkit is insecure.

      Same style than blaming X11 for being slow (xlib, yet someone put effort in coding xcb to fix many issues), being unable to refresh without jaggies (SYNC & DOUBLE-BUFFER exts), etc. Ignore what is there (run xdpyinfo if you wonder what you got) or the option to create a fix (new extension... like XFIXES when it was new), and just go full NIH.

      Oh, BTW, if you need to go paranoid and fix a crappy program, you can go with Firejail + Xpra, no need of dumping X11.