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

help-circle





  • Eh, it’s the same on the Android side of the fence. There are big and small features that Google has been comically slow to crib from iOS.

    I’ve definitely said “fucking finally” to things like overflow scrolling animations,

    Those things like overflow scrolling, keyboard peak, etc… were only held back because Apple would patent it prevent it from being put into Android and would file frivolous lawsuits against other phone manufacturers to try and get them not to use them, even when some android variants already had it built in before apple patented it in the first place. (I still facepalm at apple trying to sue others over a rounded rectangle shaped phone)

    And those patents lawsuits only stopped because other phone companies called bullshit and started threatening apple with their own patents.

    and the “wild” idea that users should get 5+ of major OS releases.

    TL;DR on this point: not much of an issue anymore.

    This isn’t an android/iOS thing, it’s a manufacturer thing. If a chip isn’t supported by it’s manufacturer, then no software on it can be supported. Different manufacturers had different support windows, but Qualcomm became notorious for making chips, then only supporting them for 2 years so they could sell a new “supported” one (and watch the money roll in). Once they saw other the larger players getting pissed off and poking around with the idea of making their own chips, Qualcomm quickly decided that they could support their chips for longer. Now they have to since both Google and Samsung have made public promises for 5-7 year support cycles. Of course, that hasn’t stopped other phones from already reaching 7 years of official support before. (A notable example being Fairphone 2 who used a Qualcomm chip while they were still in their shitty behaviour phase and managed to support it for 7 years, 2 years Qualcomm support then 5 years of their own support despite Qualcomm.)

    Also, when Google was pissed at Qualcomm they decided to start modularising their OS and pulling chunks out of it out of needing direct hardware support. This means that even if chip support were to stop, it would only affect the background / lowest-level-invisible-to-the-user parts of the OS, and all the user visible parts of the OS could be updated independently (starting with Project Treble, and going all out with Project Mainline). This basically means that entire chunks of the OS can be updated the same way an app can be, early 2010 Qualcomm companies be damned.

    This also has the weird thing of android not really being a “version” per se, one phone might have different components of Android 10/11/12/13/14/etc… running at the same time. The components themselves have their own versions.





  • I’m assuming for your example that only one tab is shown at a time?

    In that case, you can do that in vscode, the only difference is the semantics of what is considered a “window”, and what is considered a “tab”.

    To do this in vscode:

    Have one window with four panes, and another window with three panes:

                             
            Window 1         
     ┌──────────┬──────────┐ 
     │          │          │ 
     │  Pane 1  │  Pane 2  │ 
     │          │          │ 
     ├──────────┼──────────┤ 
     │          │          │ 
     │  Pane 3  │  Pane 4  │ 
     │          │          │ 
     └──────────┴──────────┘ 
                             
            Window 2         
     ┌──────────┬──────────┐ 
     │          │          │ 
     │  Pane 1  │  Pane 2  │ 
     │          │          │ 
     ├──────────┴──────────┤ 
     │                     │ 
     │       Pane 3        │ 
     │                     │ 
     └─────────────────────┘ 
                             
    

    You can then switch between your windows (or “tabs” in your example) by keyboard shortcut.

    In vscode, you can make the Panes different files, or even different views of the same file.










  • Your question:

    what things did the LHC discover that have real practical applications right now other than validating some hypothesis

    Is really multiple questions:

    1. Is doing fundamental research with no application in mind useful?

    2. Has the LHC led to practical applications usable today

    The answer to question 1 is yes.

    There’s different types of research programs made to target different goals. Some aim for short or medium term applications, and others are just pure fundamental research.

    Just because pure research doesn’t have an application in mind, doesn’t mean it’s not useful. The application isn’t the goal, the expansion of our knowledge base is. Everyone who ever thought up of an application for something did so based on their own knowledge base. If the knowledge base never expands, then we run out of applications to think up. This is why pure research is useful.

    And all of history supports this:

    • The discovers of rays shooting off cathode-ray-tubes in the 1800s were just doing pure research and had no idea it would lead to TVs
    • particle accelerator research lead to invention of cat scans
    • chemists trying to research heavier elements leading to the discovery of nuclear fission, leading to nuclear power
    • electrolysis research lead to the invention of lead (and rechargeable) batteries
    • etc…

    The answer to question 2 is also yes:

    The obvious ones are:

    • improved manufacturing processes
    • improved supercooled superconductors
    • improved large scale vacuum chambers
    • Improved data processing
    • Trained a new cohort of experienced scientists/engineers/workers/etc (who can now work on new projects outside of the LHC)

  • you have to fix the indentation because if not then the document won’t work or mean something completely different

    Whitespace has no meaning in json. You can indent however you want, or not at all.

    I’m assuming you’re running into issues because you’re writing json in a yaml file which does care about indentation, and you’re only writing json in yaml to get access to comments.

    In which case it circles back around to: why not use toml? Whitespace formatting doesn’t corrupt the file, and it has built in comments.