• 0 Posts
  • 40 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
  • Just to lob a controversial thought in there: There may be some challenges the game industry faces that aren’t solely “capitalism bad”. The most compelling one I’ve heard is that, as games as a medium they have to increasingly compete with a growing back catalogue of classics.

    Between that and the rise of indie games, it gets increasingly risky to invest in large projects.

    (To try and preempt some comments: I am not saying that investors are “right” to pull out of the games industry. I just want people to consider whether the problem, and hence the solution, is more complicated than they first thought)


  • I think it means client-server basically. You can host a server in “the cloud” then access a frontend to it via your browser.

    Might also mean it has features relevant to debugging/deploying cloud services.

    Cloud is often a BS marketing word, but I’m sure there’s ways to make it justifiable in this case. (Not that any of us has to like these features. I for once can’t stand the idea of having my editor run inside a browser…)


  • Be aware there are basically two different things called Owncloud. There’s still the original php version, which is similar to nextcloud but worse (not open source, smaller plugin ecosystem I think)

    On the other hand is owncloud “infinite scale” (or ocis). This is the thing entirely written in go. But as others have pointed out, it’s little more than a file server at this point.

    IMO the self-hosting community is really missing a self-contained “all the DAVs” server (files, calendar, contacts). Baikal etc seem like a great start, but it would be great to have somewhere to get those parts pre-assembled. Until then, nextcloud works for me.







  • Reading time 105 minutes…

    And worth every second!

    I decided to have another go at learning C++ given all the recent work that I had heard about regarding memory safety and support for functional programming. This gives me a lot less confidence that my efforts will be worth it in the long run.

    Time to check out rust I guess 🤷.




  • The big downside is that, for backwards compatibility, the default must still be unsafe code. Ideally this could be toggled with a compiler flag, rather than having to wrap most code in “safe” blocks (like rust, but backwards).

    One potential upside that people don’t seem to be discussing is that the safe subset could also be the place to finally start cutting down the bloat of C++. We could encourage most developers to write exclusively in the safe subset, and aim to make that the “much smaller and cleaner language” trying to get out of C++.


  • Please somebody correct me if I’m wrong, but I really don’t find the “chip makers don’t have to pay licence fees” a compelling argument that RISC-V is good for the consumer. Theres only a few foundries capable of making CPUs, and the desktop market seems incredibly hard to break into.

    I imagine it’s likely that the cost of ISA licencing isn’t what’s holding back competition in the CPU space, but rather its a good old fashioned duopoly combined with a generally high cost of entry.

    Of course, more options is better IMO, and the Linux community’s focus on FOSS should make hopping architectures much easier than on Windows or MacOS. But I’d be surprised if we see a laptop/desktop CPU based on RISC-V competing with current options anytime soon.


  • In my experience it Just Works ™️. I spin up a distro/toolbox, compile some software (e.g. Emacs) then run the executable inside the container, and up pops the GUI window.

    If you use distrobox, you can even distrobox-export desktop files, at which point a containerised gui application is practically indistinguishable from one installed on the host system