mort96

12 ms·

301.
by mort96 4mo ago
Look I'm just a dude who happened to land on DO a decade ago due to podcast ads and now wants to move away from it. Not due to prices but because I would prefer a European alternative. I didn't bring up Russian spies and I don&#x2
302.
by mort96 4mo ago
I was doing the same here, trying to set up a Hertzner account. Getting away from US companies and buying European and all that. But after I had made the account (and wasting a lot of time on back and forth with their buggy sign-up flow),
303.
by mort96 4mo ago
Those loops aren’t tight, they sleep for like 10-16ms for live windows or much longer for background windows. You were talking about receiving updates at 1000Hz.
304.
by mort96 4mo ago
They’re right on this one, shared memory isn’t some scary dangerous thing. Both processes will just have some region of their respective virtual address space which are mapped to the same physical memory, which they can use to share data. W
305.
by mort96 4mo ago
Wait how do you solve that with shared memory command buffers? Don’t you need to involve the kernel to notify the receiver that you’ve written stuff to the command buffer? Or would the receiver spin in a tight loop on a memory load from som
306.
by mort96 4mo ago
You don’t have to hit the kernel for 20 bytes. Buffer up all your commands and send them to the kernel with a single write(). The other side can then read them all (or however many fit in its receive buffer) with a single read(). The only r
307.
by mort96 4mo ago
Optimise how? There already is only the local case in Wayland, pixel data is shared using shared memory which only works locally. Only small communication messages are sent via the socket. And the Wayland protocol also uses native endiannes
308.
by mort96 4mo ago
Yeah, that’s correct; I implied it by only talking about sending small messages but it’s worth stating explicitly.
309.
by mort96 4mo ago
So .. still using sockets, but not documenting how the messages on the socket look? Why?
310.
by mort96 4mo ago
What would you rather they use to communicate with the server? Message passing via shared memory? UNIX sockets are perfectly fine for IPC with small amounts of data, and is how everything in UNIX has always done it, network transparency or
311.
by mort96 4mo ago
I mean the collapse of the AMOC has been a hypothesized consequence of climate change for at least many decades. I was taught about it as something scientists think could happen in primary school; it's not new (tho it was framed in t
312.
by mort96 4mo ago
It's also a command line tool, where you can design (limited) media graphs: sources, sinks, filters, encoders, decoders, muxers, demuxers. You don't express it as directly as gst-launch's pipeline syntax, but it's very m
313.
by mort96 4mo ago
Or .. their operating system and kernels
314.
by mort96 4mo ago
GStreamer is not "just a different front end to ffmpeg". GStreamer is a pluggable media graph system. "GStreamer" doesn't link against libav. The GStreamer plugin "gst-libav" links against libav. If you&#x
315.
by mort96 4mo ago
100%, VAT is a regressive tax. Poor people use a large portion of their wealth on products and services. Rich people use a much, much smaller portion of their wealth on those things. Plus rich people all have companies pay for a lot of th
316.
by mort96 4mo ago
And the fact that Mozilla used licenses for FirefoxOS which allowed a closed-source fork to come in and take the market is a huge loss.
317.
by mort96 4mo ago
To some degree, yeah they did, by leaving space for a lean and mean competitor like Google Chrome to come around and eat their lunch. And when it was introduced, Google Chrome truly was the lean and mean browser, less bloated than both Fi
318.
by mort96 4mo ago
What exactly is it that's now retired that used to be deprecated? Isn't this just a collection of breaking changes to defaults?
319.
by mort96 4mo ago
Really? Retired? What does that even mean in this context, why not "breaking" or something else that suggests breaking change?
320.
by mort96 4mo ago
Hahaha that's amazing, just a big red "RETIRED" badge above their blog post? What the hell
321.
by mort96 4mo ago
The interpreter knows types at runtime, not at parse/compile time. The interpreter already does a lot of dynamic type checking. It has a much stricter type system than e.g JavaScript; JavaScript will pretty much always convert operan
322.
by mort96 4mo ago
I do think it is somewhat of an all or nothing thing. I can write dynamic languages, sure; I prefer having static types, but I have written a lot of dynamically typed code. However if I'm working in an editor with LSP integration, th
323.
by mort96 4mo ago
I would say that pipes and shared memory are the IPC mechanisms? Controlling the state of the exec'd process's file descriptors would counts as a way to set up interprocess communication, but once that's done, it's the
324.
by mort96 4mo ago
fork/exec is not an IPC model...
325.
by mort96 4mo ago
CoW is probably a good idea regardless, yeah. Overcommit is more questionable. Regardless, both ought to be argued based on their own merits. It's unfortunate that both are necessary as a consequence of fork().
326.
by mort96 4mo ago
"Faster IPC model" than what? Faster than writing to and reading from a pipe? Faster than POSIX shared memory?
327.
by mort96 4mo ago
anarazel's comment focuses entirely on performance, indicating that they have an impression that the discussion about why fork is bad is about performance. I'm not entirely sure where this impression came from, as it's not me
328.
by mort96 4mo ago
Yeah but now you have the world's biggest foot gun in your API.
329.
by mort96 4mo ago
What do you mean by consistency here?
330.
by mort96 4mo ago
Didn't I just say that "the problem with fork isn't really that it's slow"? It's all the other OS design choices it forces on you if you want it to be fast.

More ›