throwme211345

A field of butterflies in the cow pasture feeding on manure. Pure joy. Rarely seen now, more the lone floater on the wind.

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.

Data structures and ADTs are the key in general.

pseudocode and application logic is absolutely necessary. Visualization is cumbersome and unnecessary except in large codebases.

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.

Hrmmm. I've avoided two by knowing the stop was coming and watching the rear view -> move to shoulder.

Yes, but that is avoided by years of experience and pattern learning, something AI should be able to figure out quickly.

90s: Blind Guardian, made up for the death metal and thrash crap.

Amen.

I see your design is lacking and your fud quotient is high. Good on you!

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.

Fuck this. freebsd is now the way forward. Linux has been compromised and in a way that is understandable to anyone conversant with the design philosophy of the underlying userspace tools.

Yeah, this is common. Don't modify firewall rules, fuck with interface settings and addressing without another way in.

Oh fuck moment.

I once deleted the entire contents of /bin and /sbin on an HPUX box ~2004 with the HPUX servers origin circa 1996. Live ssh session: non-standard location. scp from a convenient near-replica and voila. Without the near-peer I would have quit and never went back to IT.

Interesting. I also start in bash. I then move to sed|awk|bash (extremely powerful). Then I move to TCL or Python. Then I move to swig libraries for either language. Maybe C or intel asm if I miscalculate the problem. But I sometimes move to C first if speed is the issue and I have reusable code for the problem available.

Garbage feedback from a prima-donna. Yay: I can't code in your crap because it's 2017 bro. Twitwit nonsense.

man script.

"We" is inclusive - 'most developers' is exclusive. Mystery solved.

Why would someone do that?

Rust is the ugliest, least palatable, alternative to C for me. Seems like they said "Let's chain function calls together like java(script) as the preferred expression and throw in lispy looking declarations and logic constructs. When people get frustrated with our safety paradigm there will always be unsafe..for experts."

I love you man.

But we do know how to write secure C. It's just time consuming and requires discipline. Two things that most developers don't have or want.

You like to characterize as vague (or worse) what can be reasonably inferred or researched and have a knack for constructing positions by pleading ignorance: which makes it simpler when creating straw men and redirecting|reducing conversation scope.

You sound naive and well meaning but I think that is artifice. Your comments reflect the essentially reactive nature of the PC movement (to me) which is to reject what you find distasteful and inject whatever you believe in (edit: with no real historical consciousness).

Do you believe that experienced white men should be displaced (by default) by persons of color or women in a profession because of skill equivalency? Is there a ratio for that displacement? Is it based on merit or is it based on something else?

You didn't tackle any of the real criticism in my message.

You remark on a discrete symptom (which is a precursor) and you affirm it's essential importance to your life without any historical consciousness. And that is my basic gripe with PC culture: sensitivity to every little thing that you feel hurts you or impairs you or makes you feel included. Hell is other people, get over yourselves.