Discover and read the best of Twitter Threads about #internals
Most recents (2)
Your #Linux #internals tip of the day: On Linux, there's a magical directory called /proc. In it, every process get a subdirectory according to its PID. Inside of this /proc/pid (that framework is called procfs) you can find a lot of information about the process, (1/3)
everything from it's memory allocation mapping (/proc/pid/maps) to the command line that executed the process (/proc/pid/cmdline) and more... An interesting file to check there is "status". Status sums up a lot of interesting pieces of information such as the PPID, owner (2/3)
uid/gid and more. If you're new to Linux internals, give yourself a tour of the /proc directory. The full documentation of procfs can be read here:
kernel.org/doc/Documentat… (3/3)
kernel.org/doc/Documentat… (3/3)
Let’s make a #thread about what @zeevs posted and proposed a few hours ago in the #PHP #internals.
There was a little confusion about what was proposed, despite his words being quite clear. This is going to be VERY long, for I have no idea how to sum up things. ¯\_(ツ)_/¯
🔽🔽🔽
There was a little confusion about what was proposed, despite his words being quite clear. This is going to be VERY long, for I have no idea how to sum up things. ¯\_(ツ)_/¯
🔽🔽🔽
@zeevs First, let’s rewind the timelines a little, and have a look at history. I hate the past and history, but as pure facts, it sometimes is needed.
@zeevs PHP emerged in its raw, primitive form, circa 1994. It’s now 25 years old. The first idea was to get rid of CGI backends, crashing segfaults, maintenance nightmare, not suited for a web world. All that in the form of scripts, parsed through a slower but safer interpreter.
