Seems like a pretty fun language with an unfortunate amount of 90s baggage.

However, I firmly believe that trying to de-parenthesise lisp is a distraction. The main reason being that s-expressions make the beloved code=data concept very obvious.

A suitable editor makes it really easy to ignore the parens (until they’re useful, e.g. for navigation). When reading, the structure of the code is inferred from indentation and line breaks. Just like C.

If you’re able to easily migrate issues etc to a new instance, then you don’t need to worry about a particular service providers getting shitty. At which point your main concern is temporary outages.

Perhaps this is more of a concern for some projects (e.g. anything that angers Nintendo’s lawyers). But for most, I imagine that the added complexity of distributed p2p hosting would outweigh the upsides.

Not saying it’s a bad idea, in fact I like it a lot, but I can see why it’s not a high priority for most OSS devs

The project’s official repo should probably exist in a single location so that there is an authoritative version. At that point p2p is only necessary if traffic for the source code is getting too expensive for the project.

Personally I think the source hut model is closest to the ideal set up for OSS projects. Though I use Codeberg for my personal stuff because I’m cheap and lazy

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…)

Keep the files in a dedicated torrents folder then make symlinks to where you actually want them?

Are there any new features in particular you’re hoping for?

For me, those two are the only things I can remember thinking it would be nice to have. Q

I use magit in Emacs in a similar sort of way. Bringing up the magit status page instantly presents a list of hunks I can browse and stage. When committing, there is also an option to “instant fixup” into an existing commit, which you can select interactively from the commit log.

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++.

Obviously there’s a lot of caveats about how representative this survey (or any other survey) is of the broader population, but I think this is a good reminder of how weird we all are. Nobody on here claims to use Ubuntu or Manjaro, yet they are more popular than Fedora (and potentially even arch, when steam decks are discounted).

There’s nothing wrong with that, I love the weirdness of the Lemmy Linux community! I just always think it’s good to appreciate when opinions (like my love of ublue) aren’t as popular as you think they are.

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

Its all about how an application goes from “I would like to display X on a screen” to how X actually gets displayed. Wayland is effectively a language (technically a protocol) that graphical applications can speak to describe how they would like to be drawn. It’s then up to a different program more deeply embedded in your OS to listen to and act on those instructions (this program is called a Wayland compositor). There’s a lot more to it (handling keyboard input monitor settings, etc), but that’s the general idea.

Wayland is a (relatively) new way of thinking about this process, that tries to take into account the wide variety of input and output devices that exist today, and also tries to mitigate some of the security risks that were inherent to previous approaches (before Wayland, it was very easy for one application to “look at” what was being displayed in a completely different app, or even to listen to what keys were being typed even when the app isn’t focussed).

Thing is, change is hard, doubly so in the consensus driven world of Linux/FOSS. So, until the last couple of years or so, adoption of Wayland was quite slow. Now we’re at the point where most things work at least as well in Wayland, but there’s still odd bits of software that either haven’t been ported, or that still rely on some features that don’t exist in Wayland, often because of the aforementioned security risks.

Its just the symbol The Register uses at the end of an article. Like how some papers use a filled in square.

Kotlin targets the JVM right? I think you’d need either a port of the runtime (dalvik?) Or an api translation later a la WINE.

But I don’t actually know anything, so don’t listen to me. Having a fully Foss phone with support for the android app ecosystem would be wonderful though

Machine learning is just gradient descent through a subset of algorithm-space

There’s a former apple designer on the team I think, which they’ve been leaning into hard to get the hype train rolling.

How bloody dare you!

Isn’t production JavaScript usually minified/obfuscated to make it hard to read?

Also wasm is actually bytecode, which I believe has a 1:1 conversion into a text-based format called wat.

I agree with your main point though, it’s kinda creepy when you realise just how much we are expected to allow other people’s code to run on our machines.

By default, XWayland apps are now allowed to listen for non-alphanumeric keypresses, and shortcuts using modifier keys. This lets any global shortcut features they may have work with no user intervention required, while still not allowing arbitrary listening for alphanumeric keypresses which could potentially be used maliciously

This is… very smart actually. Any reason this is limited to Xwayland? (Is that XDG portal a thing yet?)

The point of Linux on phones isn’t to have a phone that requires you to constantly fix it with CLI tools. The point is to have a free and open software platform for a device that is increasingly necessary for daily life.

As a side effect, developing Linux for phones would probably help us eliminate the need to reach for the terminal on desktop Linux as well. I believe snaps (which laid the groundwork for flatpaks) were originally developed for Linux on “smart” devices. The whole ecosystem improves when we try to bring Linux into a new domain.

P.S. I use termux (a terminal for android complete with its own tiny Linux environment) from time to time when I need to access my server over SSH. It’s a bit clumsy, but super handy!