• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2024

help-circle




  • Yeah sorry, I kind of went on a tangent.

    Regarding the source, I was under the impression that manufacturers get some kind of devkit for the SoC that works against a given kernel version (one of the LTS ones Android usually uses) and binary drivers for the non-open parts. One could sue the manufacturer after buying a phone and demand release of the source, but this won’t hit meditated because the vendors won’t go after them or their license gets terminated. Legally difficult but similar to the grsecurity situation: yeah you have rights, but if you exercise them, we choose not to do business with you anymore.

    Shameful situation and I think Google wanted to get out of this legal area when they developed Fuchsia as this concept would solve technical and legal issues for manufacturers.

    I’m not sure where this discussion stemmed from because from my knowledge, the Fairphone does allow custom ROMs, though you lose some boot security functionality? I didn’t read too much into it yet








  • A lot of people have no idea about aviation safety, it shows in these kind of threads. I worked in aviation for about 5 years, so I at least have an idea, though I’m far from an expert (about a year as a technical officer in the German Air Force, more of a management role but you still get the basic safety courses like Maintenance Resource Management training, four years of procurement for a maintenance IT system), and how some people approach the subject stumps me. Flying isn’t the safest mean of travel because of its nature, but rather because of rigid rules at every step of the process that are enforced by supervisors and inspectors.

    Literally heard this phrase Sunday: Accidents don’t happen – they’re caused.


  • I’m not worried. I don’t live my life around freak accidents. This really doesn’t need to be national news ruining her life if there wasn’t a crash before hand, that’s the real issue.

    I mean she literally crashed her car on the way to the flight she was finally removed from? I agree it’s weird that this makes the news, but it’s probably because the case is so odd…

    Expecting a shit wage employee to act better than cops (let’s set that bar real low) in a dangerous event is silly.

    It’s shameful that Virgin pays so little. But then again it doesn’t excuse going on the job drunk. Don’t take the job, go on strike for better conditions, all fine by me. But don’t show up drunk to your job where you operate safety equipment. Too much to ask? Also I do expect cops not to be drunk





  • I’m not even sure what strucrued data would really mean, so I’m pretty sure it’s not useful to my usecase lol

    Probably not, but to give an easy example:

    ~> ls | where modified >= (date now) - 30day
    ╭───┬───────────┬──────┬────────┬────────────╮
    │ # │   name    │ type │  size  │  modified  │
    ├───┼───────────┼──────┼────────┼────────────┤
    │ 0 │ Downloads │ dir  │ 4,0 kB │ 4 days ago │
    │ 1 │ Musik     │ dir  │ 4,0 kB │ a week ago │
    ╰───┴───────────┴──────┴────────┴────────────╯
    

    Here, ls doesn’t just return a string representing directory content as text, but a table where each file is an entry with attributes that have their own data type (e.g. size is Filesize while modified is Datetime). That’s why I’m able to filter based on one of them; that part isn’t part of ls, but of the shell itself. In a classic shell, this filtering would need to be handled in the originating binary in its own specific way, or you’d need to parse its output, transform it using tools like sed and awk etc. This here is a special case because ls is built into the shell; for non-builtin commands, if they offer it, you can have them output structured data as json or something else and read it into nu, like

    ~> ip -j a | from json | where {|device| $device.address? != null and $device.addr_info? != [] and $device.link_type =~ "ether"} | get addr_info.0 | select -o local broadcast scope
    ╭───┬────────────────────────────────────────┬─────────────────┬────────╮
    │ # │                 local                  │    broadcast    │ scope  │
    ├───┼────────────────────────────────────────┼─────────────────┼────────┤
    │ 0192.168.178.72192.168.178.255global │
    │ 12001:9e8:4727:2c00:3071:91ff:fed1:9e26 │                 │ global │
    │ 2 │ fdaa:66e:6af0:0:3071:91ff:fed1:9e26    │                 │ global │
    │ 3 │ fe80::3071:91ff:fed1:9e26              │                 │ link   │
    ╰───┴────────────────────────────────────────┴─────────────────┴────────╯
    

    It’s kind of cool, but I don’t need it that often either, so I just play around with it when I feel like it.


  • I’m glad you mentioned nushell (it sounds like) is a more poweruser thing.

    It serves a different niche. nushell is very good for working with structured data. fish on the other hand is a “conventional” shell that’s not POSIX compliant. I guess that’s why they call it “a command line shell for the 90s” because it doesn’t incorporate modern concepts, it’s just more convenient than POSIX shells.

    This results in some notable differences: nushell for example has actual data types (https://www.nushell.sh/book/types_of_data.html, though they are dynamically typed by default).

    All this doesn’t mean that one is better than the other. I use fish daily and just sometimes dabble in nushell because most of my workflow doesn’t require all the stuff nu offers.