• 5 Posts
  • 153 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle








  • aluminium@lemmy.worldtoTechnology@lemmy.worldWhy is UI design backsliding?
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    2 months ago

    no, I’m willing to die on the hill that the ribbon UI is one of the greatest UIs period - especially how it was done in office 07 and 10. As a computer noob at the time, it was a huge improvement over the previous office 2003 UI.

    The icons always gave you a good idea what something was doing, important functions were bigger and when you for example selected a table the table tab was visible and with a different color so you knew that you could do things with that table.

    I think however many 3rd party programms did the ribbon UI poorly or had not enough features for it to make sense.









  • Last time I checked ARM v7 is not the issue, there are still up to date builds available from Chrome itsself or Brave, rather Android 6 is. Google seems to have a cycle where roughly every fall they drop another Android version.

    Right now the minium requirement is Anroid 8 and if the cycle continues it will loose support in a few months and Android 9 will be the new minimum requirement.

    However I also have a a few Android 6 or 7 devices and usually firefox runs fine on them if they at least have two proper large CPU cores. But using two year old Chromium based browsers, I never ran into any sites that wouldn’t work correctly.




  • No, open source means that its public HOW something is done, down to every single line of code (along a lot of other things when it comes to licensing, redistribution, … but thats not the main point)

    With a open standard its public WHAT something is doing, but HOW its achieved can be public or not.

    To give you a example, HTML is a open standard for displaying Webpages. Somewhere its defined that when a <button> element is found, the browser has to render a button which looks a certain way behaves a certain way when interacting with the mouse, keyboard, javascript, css … . This is WHAT your browser needs to do.

    But HOW you do it is up to each browser. Do you use the CPU or GPU to render it? Do you first draw the border, then the text or the other way around? It doesn’t matter to the standard as long as the end result complies with the spec.

    With open source browsers like chromium and firefox it is public HOW they are implementing this feature, down every line of code.

    With a proprietary browser like Internet Explorer which follows (or rather followed) the same open standard nobody knows HOW they are implementing it. We only know that the end result is adhering to the HTML Standard.

    The hardware equivalent it would be someone releasing the exact schematics of for example a RISC V CPU where somebody could see HOW they implement the specifications of the Architecture and where someone could without much hassle go to a Manufacturer and get the chip into production or make modifications.