• 0 Posts
  • 28 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle







  • droans@midwest.socialtoMemes@sopuli.xyzPretty but pointless
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    2 months ago

    This is definitely AI but similar ovens used to be built and, I’m sure, still are.

    However, there are still plenty of issues.

    Open flame plus a flammable painting. And the painting is right over the oven where it will get covered in grease. And that’s a gas range with no hood.

    There’s a reason ovens usually open from the top these days. It’s safer and allows you to peak without opening the entire oven or leaning at an odd angle. Locking handles are also no longer used because little kids can climb in and accidentally get stuck.

    The multiple drawers sounds like a good idea but it just means that you can’t cook large dishes. Usually you’d only see styles like this in restaurant kitchens because they will know how large of an oven they need and can benefit from having multiple sizes for different dishes.












  • They could still use whatever config format they wanted - this would just be for providing their config schema. It also doesn’t need to be YAML, that’s just the easiest one for me to type on my phone. In fact, I think most schema validation programs rely on JSON as it is.

    I also don’t think programs should be required to provide it. Many core programs and kernel modules would likely take years if they ever were able to add it just to avoid the risk of mistakes causing any major issues, especially if they haven’t needed an update in years. There are also many config files that use their own nonstandardized schema. A possibility is that they could be allowed to provide a CLI tool which could update the config or they could just ignore it entirely.

    But creating a common schema for… well, the config schema would make it easier for systems to provide a frontend interface for updating your configs.


  • Seriously - Linux needs a standardized config schema spec. Something that programs should provide which an application can read and provide a frontend interface for the users to adjust config files.

    Could be something like:

    schema_version: 1.0
    application:
      name: Poo Analyzer
      icon_path: /etc/pooanalyzer/images/icon.png
      description: Analyzes photos of poo
    schema:
      - config_file:
          path: /etc/pooanalyzer/conf/poo.conf
          conf_type: ini
        configs:
          - field: poo_directory
            type: dir_path
            name: Poo Image Directory
            description: Directory of Poo Images
            icon_path: /etc/pooanalyzer/images/poo.png
          - field: poo_type
            type: list
            name: Poo Types
            description: Types of Poo to Analyze 
            values:
              - dog
              - cat
              - human
              - brown bear
            icon_path: /etc/pooanalyzer/images/animal.png
              ...
    

    Any distro could then create any frontend they’d like to manage this - the user could even install their own.