1,893 karma · joined June 30, 2010
If we look deeper, we see that GNU/Linux is a C system, and I'd argue that this is the most essential characteristic ("An operating system is a collection of things that don’t fit inside a language; there shouldn’t be one” — Dan Ingalls, Design Principles Behind Smalltalk). Of course, GNU system supports many programming languages, but they all use C to interface with the system. Get familiar with non-C systems like Smalltalk or Oberon to see how programming language is essential. Also web browsers grew to become operating systems of their own (running on top of C systems for now) — the JavaScript systems.
AFAIK Firefox on GNU/Linux uses Gstreamer. Maybe you need to install gstreamer codec packages.
Update: Firefox switched to FFmpeg and removed Gstreamer support some time ago. I have FFmpeg installed from rpmfusion, but I don't know if that's relevant to WebRTC and Jitsi.
There are even much cheaper virtual server offerings, as one probably doesn't need 1 GB of RAM and a dedicated IP for personal VPN or proxy.
Alan Kay said in 2004: «You could think of it as putting a low-pass filter on some of the good ideas from the ’60s and ’70s, as computing spread out much, much faster than educating unsophisticated people can happen. In the last 25 years or so, we actually got something like a pop culture, similar to what happened when television came on the scene and some of its inventors thought it would be a way of getting Shakespeare to the masses. But they forgot that you have to be more sophisticated and have more perspective to understand Shakespeare. What television was able to do was to capture people as they were. So I think the lack of a real computer science today, and the lack of real software engineering today, is partly due to this pop culture.» https://queue.acm.org/detail.cfm?id=1039523
Thinking about it I came to realize that there is a much deeper cultural problem: it became the norm for users to run lots of opaque untrusted code on their computers. Every application is a threat, as it represents interests of the vendor rather than the user, and this can not be solved just by isolating UIs (the line of death) and code (sandboxing), we must reconsider the models of software distribution that we use. Maybe the Web should not at all be used as an application platform and instead focus on content and give more control of its representation to user agents.
And there actually is a software distribution model that gives grounds to trust — the one used by GNU/Linux distributions where software is not pushed to the users by vendors directly, but reviewed, built from source and packaged by distribution maintainers who represent the interests of their users. And of course, for the maintainers to be trusted, their work must be maximally transparent and verifiable. Some distributions, like GNU Guix, managed to advance this model really well, while others are unfortunately now going in the opposite direction by adopting things like Flatpak and Snap.
> An important design feature is that it is 'anti-DSL' --- the syntax is exactly the Clojure syntax.
This is not "anti-DSL", this is what gives Anglican embedded DSL qualities.
And yet there are limitations: «The border between Clojure and Anglican is subtle and usually will pose no problem to most programmers, however, some confusion can arise from the fact that Anglican programs are macro compiled into CPS-style Clojure functions. This means that some wrapping of “native” Clojure functions needs to happen in order to use them in Anglican. Errors arising due to misunderstanding this boundary crop up in the form of “wrong number of argument” exceptions».
Would that language border, wrapping of functions and transformation to CPS be still necessary in a language with native support for continuations?
Also, the GNU project appear to have capable designers: https://www.gnu.org/software/guile/