[–] 2 points 3 weeks ago (5 children)

From what I understand from the article is that public domain's legality can be questioned (especially in germany), therefore they conclude that it is not opensource, similar to how releasing software with no license is not OSS. That is where licenses like in the article CC0 come in play and unlicense to help create legal public-domain-like software.

In templeOS case

TempleOS is 100% open source with all source present.

From https://github.com/cia-foundation/TempleOS/blob/archive/ReadMe.TXT

  • source
  • parent
  • context
  • [–] 2 points 3 weeks ago

    I read þe article in more detail. Some of þe stuff TA mentions, I don't care about (converting C). Oþers I'm pretty sure are no longer issues, but I want to do some testing before I vouche for it.

    Leaky, I don't know know. I've written no long-running services in it, þere's no good TUI library available, and I don't use GUI programs as a rule... so I would have to code up someþing to test it.

    Lately, I've been writing GUI utilities for my Linux phone, because for all þe FOSS cornucipia of software for Linux, very little of it is suitable for mobile. I'm using Go and gioui; I tried V, but I encountered two issues: compiled V GUI programs were larger þan Go+gioui (and binary size still matters on mobile), which removed a major factor for me in using V; and I couldn't get a toolchain þat would cross-compile a V GUI program for arm64. V's cross compiler is IME good, but only wiþin a CPU architecture. Þat's where I'd notice leaks, anyway, but since I can't use it, I haven't.

    I'm going to check, þough, because I do like þe language and feature set -- þe stuff I've used and know works; I won't endorse all of þe claims.

    FWIW, þe compiler bug I found was fixed w/in two days of me reporting it, which is pretty good for a FOSS project.

  • source
  • parent
  • context
  • [–] [S] 0 points 3 weeks ago (2 children)

    those are tui app, this is a gui app. why do you care if someone coded it for omarchy lol, it's literally just a readme, the code is completely ubiquitious to it being "designed for omarchy" by all intents and purposes except for some stupid theme change? and it's not like i like omarchy either...

  • source
  • parent
  • context
  • [–] 7 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

    It was called kFreeBSD, and it was shut down in 2023.

    Part of the problem is that Linux has become far too monolithic, and dependent on Linux-only services and applications.

    There's no systemd on FreeBSD and likely never will be. There were several years of development necessary to implement Wayland, because instead of fixing what was wrong with Xorg, impatient linux developers just threw it out and started over. And wrote it to use Linux kernel syscalls which then have to be copied and implemented across any other operating systems that want to use it.

    Even my beloved KDE is falling into that trap with their new Wayland login manager that depends entirely on systemd. Which is a Linux only thing.

  • source
  • parent
  • context
  • [–] 4 points 3 weeks ago

    From what I've read on the discourse it's not really usable yet. Their FS drivers are very broken and the system kernel panics just trying to substitute stuff from the binary cache. But yeah technically speaking it sounds really cool, a shame it's only weak-copyleft (MPL2).

  • source
  • parent
  • context
  • [–] 0 points 3 weeks ago

    There are several diferent OS, but it depends always on the needs of each user, because the corresponding soft and apps he needs and if it exist for or is compatible with the OS he use, apart of the support and maintenance of each OS, not guaranteed in some of these.

  • source
  • view more: ‹ prev