HN user
Incorrect translation, Allahu Akbar means “the god is the greatest”
Allah is not a name that came with Islam but existed before, it just means deity. the Al prefix is the definite singular form. It just says one thing: god is a singleton and nothing is above it.
Sorry to disagree, but no, they are not dozens of different languages. The challenge with Arabic is that it has a rather large vocabulary, and different regions use slightly different vocabularies.
That being said, Darija, or rather North African Arabic is a messy mix of Arabic and Tamazight. Which can be difficult for Middle East Arabic speakers to understand.
For reference, I speak Darija and understand both classical and modern Arabic. It would take me a few days to adapt my speech to other regional variations of arabic.
Yes Arabic from 1000 years ago is very much understandable today[1].
Not Linux syscalls, they are a stable interface as far as the Linux kernel is concerned.
`gen_server` is an abstraction over the a client sending a `request` that a server services to produce a `response` to be sent to the client.
The `gen_server` implementation takes care of things like timeouts, servers terminating before a response is produced as well as maintaining the server state.
You can read more here at [1], [2] and [3].
[1] https://learnyousomeerlang.com/clients-and-servers#callback-...
Why do things have to be comparable? Why did you cherry pick infant mortality? Yes reducing infants mortality is one of the things where we improved.
The most dangerous thing about Capitalism is imho its universal equivalence, its ability to make us covert everything into a monetary value.
In other words, it’s just like a programming language where everything can be implicitly converted to a given top type.
In the progress we certainly made over the last century or so, we certainly also lost other things whose value is not representable in our modern value system.
REINDEX INDEX CONCURRENTLY[1]
[1] https://www.postgresql.org/docs/current/sql-reindex.html
Yes, but you don’t end up with different glyphs. Arabic script has letter shaping, that means a letter can have up to 4 shapes based on its position within the word. If you chop off the last letter, the previous one which used to have a “middle” position shape suddenly changes into “terminal” position shape.
The underlying problem is lack of isolation, and this is an area where the Erlang process model shines: processes are fully isolated and you can send a signal externally to terminate any process you want.
No global GC. Each erlang process does its own GC, and the GC only happens when the process runs out of space (ie. the heap and stack meet).
You can for example configure a process to have enough initial memory so as not to ever run into GC, this is especially useful if you have a process that does a specific task before terminating. Once terminated the entire process memory is reclaimed.
GC determinism is one of the things you get. Another one is non cooperative asynchronous termination.
Vala is very much used among other things by Frida.
I have been involved with Vala in it’s early day and some hardcore GObject/C users never quite liked the C code that Vala generated although it was perfectly valid and exposed a very clean C header to interface with it.
I think that Vala is a really great tool for building applications that make use of Glib/GObject. For example Gtk applications, but also GStreamer and DBus applications.
I don’t have an example of fully non-cooperative cancellation available off the top of my head.
That would be Erlang.
The UUID spec update has not been finalized yet.
It would be quite unfortunate to end up with a UUID v7 in PostgreSQL that’s not quite the standardized one because the patch got merged too quickly.
EDIT: here is the IETF working group page https://datatracker.ietf.org/wg/uuidrev/about/
Their milestone seems to submit the final proposal by March.
You might want to check out the Swedish Doro phones: https://www.doro.com/en-us
It's quite unfortunate that this article mixes up what's necessary for podman quadlets with coreOS concepts.
With quadlets, the only thing required is to drop a `.container` file in the right place and you end up with a container properly supervised by `systemd`. And this of course also supports per-user rootless containers as described in [1].
ISO8601 is a standard managed by ISO, you can buy a digital or printed copy of the standard from here: https://www.iso.org/standard/70907.html
RFC 3339 is managed by the IETF, and their documents are accessible free of charge.
Faster doesn’t mean more responsive, in fact very often an increase in throughput leads to an increase in latency.
I think you are confusing Vale with Vala[1] :)
Each RTP packet has a 32bit timestamp, and a 32 bit SSRC. Each "sender" in an RTP session must use the same SSRC, this is how synchronisation between audio and video streams from the same sender (lip-sync) is achieved.
The timestamps have a resolution defined by the clock rate communicated externally through a signalling channel.
The maximum number of simultaneously alive Erlang processes is by default 262,144. This needs to be raised to avoid the `system_limit` error.
This is really neat. I have been using `podman generate systemd` for a large number of deployments. This just makes it so much simpler.
For anyone wondering, the main difference between this and docker/docker-compose is that podman can run in a daemonless mode such as containers are running directly under systemd which makes them integrate into the existing systemd infrastructure and appear as any other normal service.
Shouldn’t be necessary if you configure your release to start in interactive move instead of embedded mode as modules would then get loaded lazily
I am far from being an expert in the field, but I have seen property based tests used to verify complex stateful systems.
I remember more circa 2010 attending a presentation by the guys from QuviQ who mentioned that their solution was used by the automotive industry in Sweden to verify embedded systems.
I personally like "The Mess We're In" https://youtu.be/lKXe3HUG2l4
An `iolist()` or `iodata()` structure is mainly designed for I/O.
The idea is rather simple but powerful.
Let's say you want to send `"Hello " + name`, where `name` is a string, over the network. Traditionally, in C, you would allocate a buffer that is large enough and copy the "Hello " literal into it and then copy the `name` string before calling `write(fd, buffer, length)`.
If you wanted to avoid allocating the buffer and doing the copy, you would make use of `writev(fd, iovec, count)`, and this is exactly what the `iolist()` structure allows for. The erlang runtime system (erts) makes use of efficient `writev` calls instead of having to allocate temporary buffers just to send data over the network (something Erlang is notoriously good at) when you make use of `iolists`.
Also known as QCIF format
I have to admit that I included Portugal without giving it much thought.
I was honestly mostly thinking about Spain and added Portugal assuming they would be the same from the perspective of identity. I stand corrected.
I find it hard to believe that there would be no cultural heritage after ~700 years.
What I think you want to say is that the "identity" of modern Spain and Portugal has been shaped and defined by its opposition to the moor/muslim/north-african identity.