That is complete crap. Programmers have the same ladder as professional athletes. You can be amazing at 17 or 36 without collegiate training and indoctrination.
He is totally right excepting popular extrapolation.
The basic idea is that people 'eventually' identify with idea venues, not ideas. If (at venue maturity) a venue stops including your ideas you are internet-dead for the masses.
Idea venues are created through existing outlets at the time of inception and through superior propaganda and propagation models to the point of maturity.
Google is a case in point. They tout themselves as the best and brightest but they pay their bills on advertising.
Every move they make is focused on consumption of their product(s) and they give it away to see who will bite. They collect their data and learn the model. They play the model.
This is sales 101. You don't need to be smart to be google. You just need to know who is smart and who isn't.
If you want an OS environment virtualize. If you want a jail containerize. But containers are basically misused as lightweight vms so this type of conversation is inevitable.
I don't see the point of complicating operations monitoring based on a solutions model that involves containers as virtual machines. This also ignores the fundamental issue between host<->guest that exists in most hypervisors where monitoring must be dual scoped and integrated.
As you say except I explicitly noted '..type approaches' and '..semantics'. If a library designer does things in a way that makes you doubtful of state then don't fork. If you do fork block signals and exec. It doesn't help the race but it does help your peace of mind (i did what i could).
Apple still sucks BTW. Heavy handed nonsense. Let developers deal with the consequences of their actions.
What you don't like the fact that apple sucks for breaking userspace (as usual) or that pthread_atfork() type approaches should be in every programmers toolbox?
fork() is not gets and you don't f*ck with process creation. If a programmer commits an error that deadlocks or corrupts data by using fork() unsafely they really should have known what they were doing in the first place.
LOL. mac osx breaks fork() to avoid state inconsistency in threaded applications. How about pthread_atfork() semantics? But ,as usual, apple heavy hands userspace and breaks things. Nothing new to see here, move on.
30 arc second permutation on a TC forecast track as it impacts multiple points of interest across multiple impact models. Heavily parallel amenable and in RT not an async endeavor.
Not giving you more 'hints'. You webdevs are kind of dull anyway. I/O this and I/O that and you'll accept untrusted input until the sec industry all drive ferraris on your mistakes.
All the time. Web development is a sad excuse for experience in HPC environments. But node guys always think I/O processing in an event loop must work for everything!!!!
With that approach we can go back to the happy openmpi/mpich days and take the gargantuan performance hit that ended MPI clustering for any serious real time scientific processing.
Disagree. Threaded programming is not that difficult. Design matters. If you are trying to back fit threads into legacy code that has a traditional process based model with massively shared data structures it can be a little ugly.
Most peoples problems come with being over clever with their per thread data/stack, priorities, affinities, attributes, etc..a simple threaded program with a couple of locks for shared data and a flat schedule is efficient and easy to understand on multi-core systems.
Event loops and aio are nice but they are not a superior standalone solution as evidenced by nodes use of libuv.
Lennart: you are a well paid tool and your designs and causes are not the causes of those of the prior generation of *nix users. When you understand that you will stop winking at us and understand that people will always be unhappy with your aggregations and the power that abets that aggregation. In the meantime we who can will look elsewhere and adopt and improve the model we understand and love because it is not broken and not improved by another design.