@cstrotm That's a container or a docker. AppImage is only a set of libraries, Data, and the executable in an image of a file system. It doesn't have the entire OS in it. This would be similar on DOS of compiling statically, then putting all your data inside the executable as well.
@cstrotm I love listening to Jonathan Blow, even if I don't always agree with everything he says. You can just copy a program to a system on linux, it's called AppImage. And his comment about the OS layer... without it there's a lot of things you couldn't just do across those systems, like accessing the hard drive would be different on each system if you tried to go direct instead of through the OS. Same for shaders. You would shift it from metal/hlsl/glsl to Nvidia/Intel/AMD/Adreno/Mali.
@loweel @cstrotm I love playing with Forth and Oberon both, in fact one of the projects I've always wanted to work on was a low end computer based on ESP32 that could run Micropython, OberonOS, and Forth natively. Both of them have an incredible economy of code size to accomplish a lot, but they're definitely not modern systems or designed to be efficient on new computers. I need more hours in the day because I also want to dabble more with Erlang...
@loweel @cstrotm In the work with low end systems I've done in the past (ZWorld DynamicC), those OS features might just be part of the library that you're compiling into your program though, so you're booting straight to your code, but all of the features that would be in the OS, file systems, TCP, ASIC drivers, etc would be in the libraries you're using and be compiled in. Thus, a very thin OS in your application container.
@loweel @cstrotm Asics to manage memory and IO, you mean like the Amiga's Copper asic? Those certainly can speed things up, but everyone had pretty much gone away from that sort of thing and to much more generic hardware after the 80's. It would be interesting to have that, but again you're then tying your application to specific hardware, so you lose significant portability in your application. You still need features like an OS to interact between your asic and the CPU software you're writing.
@cstrotm Interesting. And a new company too. With a name like "Oxide" and a podcast called "On the Metal" it makes me wonder how much Rust they'll be using.
@cstrotm https://youtu.be/HgtRAbE1nBM Bryan Cantrill is the one who talked about select/poll/epoll/events in another video, but I can't find that one right now, but here's him doing a dive into Rust as an opportunity for doing the OS components in something other than C. I find his videos to be entirely fascinating, though often very long. He's with Joyent and works on SmartOS. (I don't think Illumos/SmartOS are the future either, just because of CDDL and Oracle. But they are cool systems.)
Primitive systems sometimes did things like that, but it meant that you basically had to implement the OS right inside of your program, which then locked you down to a subset of hardware. I think things like that are fun to play with, but I don't think that it's really the future of computing.
Thin hypervisors that don't actually run much software directly, and everything is in containers with a thin OS on each is a direction people are starting to go.
@cstrotm Personally, I'm watching RedoxOS, Haiku, Magenta, and Genode to see what interesting developments come from them.
@cstrotm That one point is, like I said, one I agree with. I just haven't seen such a bad defense of it before, and he barely spent any time on that before moving on to all the other points. If he had mentioned Plan9, it would have been more interesting. His epoll/select complaints are much better addressed in presentations by Illumos/SmartOS developers. His comments on it were just snarking at the API, not really diving into why it is that way. the "ioc-tl" pronounciation was grating too.
@cstrotm Yeah, Especially after seeing that and other things like the xorg.conf dig re-contextualized the first 10 minutes and made me think that he's probably doing the Unix part of the USB driver the hardest possible way as well. All the stuff I watched the video for (what was the alternate path to Unix?) was superficial, and came down to "The guy who made VMS ended up making Windows NT, too bad that we're not using that, and it's not 90+% of the desktop market, right?"
@cstrotm Well, it was just a really bad defense of a bunch of premises that I agree with. The entire thing with the command line for example. There's plenty of unix tools for doing it exactly how Mac does it, as well as there being much simpler ways of doing it from the command line. It's like he went out of his way to make the unix way awkward and do it how you would only usually do it in scripts.
@cstrotm The most disappointed I've ever been between my expectations of a piece of content and the reality that it delivers was an anime called Popotan, which promised me a Japanese version of Doctor Who in the description, but delivered something completely vapid. This video is a close second.
@burek First answer: It depends on which one the mother is, and which one the father is. Other answer: Autism?
Every once in awhile I go digging around my memory for comics that I used to follow, but don't have in my RSS anymore. Today's one I dredged up was this one: http://wingsofchange.comicgenesis.com which went on Hiatus in 2007ish and never returned.
@cstrotm Yeah, the devs of Minecraft just screwed up and made it not work with IPv6, even though it was fully supported by the OS and language. When you have users connecting in, you don't want to have them following elaborate steps to connect to your server, but that may end up being what you have to do whenever IPv4 finally goes away, if they haven't fixed it by then. Luckily that's my only v4 only service!
@cstrotm I run a Minecraft Java server, and Minecraft Java, as of the last time I looked, didn't support IPv6, so I would be affected at least a bit.
Enjoyed watching them wander around California looking for authentic chinese food. https://youtu.be/tzRTlnx0MCc
https://twitter.com/Scobleizer/statuses/764673949 << An old tweet. This also explains why Microsoft refuses to put exfat on linux themselves. They're trying to make sure they can still sue people for using exfat on linux at some point in the future.
The usual. Software developer, former BBS sysop. Atari XE, Dos, OS/2, BeOS, Windows 2000/7 former user, Linux/FreeBSD/Haiku/OpenIndiana current user.
An instance for Kazriko