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

help-circle


  • Autopilot is just adaptive cruise control that keeps the car in lane.

    Anyone who watches the video in question knows this statement is misleading. Autopilot also stops when it detects an obstacle in the way (well, it’s supposed to, but the video demonstrates otherwise). Furthermore, decades old adaptive cruise from other brands will stop too because even they have classic radar or laser range-finding.

    If even the most basic go no-go + steer operation based on computer vision can’t detect and stop before obstacles, why trust an even more complicated solution? If they don’t back-port some apparent detection upgrade from fsd to the basic case, that demonstrates even further neglect anyway.

    The whole point that everyone is dancing around is that Tesla gambled that cheaping out by using only cameras would be fine, but it cannot even match decades-old technology for the basic case.

    Did they test it against decades old adaptive cruise? No, that’s been solved, but they did test it against that technology’s next generation, and it ran circles around vision not backed by a human brain.




  • Dude, thank you for this. IMO reducing that down to simply “cloud native” is doing a disservice to how absolutely cool that methodology is.

    I loved RancherOS in the server space, and always wished there could be a desktop version of it, but I realize that the isolation of docker on docker would be very difficult to deal with for desktop applications. From your description, I feel like Bazzite has done the next best thing.

    If I may frame things in RancherOS terms and perspective briefly, given your description of what’s going on with Bazzite, the System Docker container image is being built in the cloud every day, and you could pull it down, reboot, and have the latest version of the OS running. The difference, I am gathering from context, is that while RancherOS “boots” the system image in docker, Bazzite simply abandons RancherOS’s hypervisor-esq system docker layer, and does something like simply mount the image layers at boot time (seeing as how the kernel is contained within the image), and boots the kernel and surrounding OS from that volume. The image is simultaneously a container volume and a bare metal volume. In the cloud, it’s a container volume for purposes of builds and updates, which greatly simplifies a bunch of things. Locally, the image is a bootable volume that is mounted and executed on bare metal. Delivery of updates is literally the equivalent of “docker pull” and a boot loader that can understand the local image registry, mount the image layer volumes appropriately, and then boot the kernel from there.

    Do I have this roughly correct?


  • Hey there, I’m the founder of Bazzite.

    Hey man, so great you are here! What an opportunity that you came here to provide clarity. Thanks for being here!

    Just wanted to confirm that we have no interest in VC funding. we’re [not] marketing to people with too much money and a lack of sense

    That’s super great to hear. Refreshing in fact.

    Putting a whole distro together is a monumental task. Why have you gone to all the effort to do so? What does Bazzite bring to the table that can’t be found by using any other distribution? For everyone who is currently using, say, fedora, why should they all switch to Bazzite today? (I am currently running fedora and I am thinking about a change, can you give me a reason to jump?)


  • As someone who builds and deploys software in the cloud all day, seeing the term “cloud native” used for a desktop OS just reads as jibberish to me, no offense. Nobody can seem to explain clearly in simple terms what is actually meant by it.

    Does it just mean all of the compilation of binaries and subsequent packaging have all been designed and set up to run in a uniform build pipeline that can be executed in the cloud? Or is bazzite just basically RancherOS (RIP) but for the desktop? I am seeing people in this thread talking along the lines of both of these things, but they are not the same.

    Can you explain what the term “cloud native” means as it relates to bazzite in a way that someone who can build Linux from scratch, understands CI/CD, and uses docker/kubernetes/whatever to deploy services in the cloud, could grok the term in short order?








  • Interesting. I wonder how that compares to a similar Li-ion cell. Also it’s a shame there wasn’t a close-up on the markings of the battery in that video to know what it is exactly. I don’t imagine all cells are equal.

    The battery packs from the article, for instance, are not constructed from cylindrical cells, but from large thin and flat square cells. The cathode material appears to be unique as well, as far as I can tell; who knows what’s in those blue cylindrical cells.






  • Thanks for your response. Sorry I didn’t get the joke.

    As promised, here’s a “simple” explanation of SCADA, or as simple as I can make it at least. It will probably be rudimentary enough to be controversial, and long enough to be boring. Oh well.

    It stands for supervisory control and data acquisition, and if you think that’s a weird mouthful, it’s because it’s old and comes from a time when clicking graphics on a screen was a novel idea, and logging swaths of data with a computer and searching within it and rendering graphs from it was cutting edge. The term is basically relegated to plant, industrial and manufacturing type processes where a bunch of engineering has gone into it. Processes like brewing, water treatment, factories, assembly lines, etc.

    Those processes are automated with special computers called PLCs that are basically “robot brains” that control things like (but not limited to) motors, valves, pumps, conveyers, robot arms, all kinds of stuff to manipulate the physical world, and can receive information from sensors like (but not limited to) pressure, speed, flow, weight, on/off, open/closed, temperature, distance, or anything else that someone has built a physical world sensor for. You can put all that stuff together with a program in the PLC and automate practically anything from beer making to zebra counting.

    And that’s all well and good, but if you want to see what the process is doing (supervise it), or stop it if it’s gone off the rails (control), or see what it did last time (data acquisition), you need SCADA. There’s special software to build a SCADA system with, and it’s mostly special because it needs to talk to the myriads of PLC (and related) gear out there, and until relatively recently, it’s been tied to an ancient Windows technology called OLE, meaning if you wanted SCADA in your industrial process, you had to suffer with the rather unindustrial wart of Windows in the middle of it. OP is seeking the industrial Holy Grail of a windowsless process in their plant.

    We take it for granted today that we can build an interface in a web browser, and hook it up to control a USB device, all in one day, but 40+ years ago there was Windows 3, serial devices, and no commonly established way to communicate with gear (which OLE kinda solved), or standard design of how interfaces should look or work. Ignition brings all of that old shit into the modern world.

    A relatable example you could call “baby SCADA” would be a smart thermostat, if it has an onboard temperature trend graph. The process it controls is your automated home heating and cooling. The smart thermostat can tell you if the AC is running, you can change the target setting that you want the room temperature to go to. And if it has a graph of the temperature for the last 24 hours so you can see that the schedule you set worked, then it’s basically a 'lil SCADA.

    Cheers.