throwme211345

6 ms·

1.
by throwme211345 9y ago
A field of butterflies in the cow pasture feeding on manure. Pure joy. Rarely seen now, more the lone floater on the wind.
2.
by throwme211345 9y ago
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 does
3.
by throwme211345 9y ago
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?
4.
by throwme211345 9y ago
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.
5.
by throwme211345 9y ago
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.
6.
by throwme211345 9y ago
Data structures and ADTs are the key in general.
7.
by throwme211345 9y ago
pseudocode and application logic is absolutely necessary. Visualization is cumbersome and unnecessary except in large codebases.
8.
by throwme211345 9y ago
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
9.
by throwme211345 9y ago
Hrmmm. I've avoided two by knowing the stop was coming and watching the rear view -> move to shoulder.
10.
by throwme211345 9y ago
Yes, but that is avoided by years of experience and pattern learning, something AI should be able to figure out quickly.
11.
by throwme211345 9y ago
90s: Blind Guardian, made up for the death metal and thrash crap.
12.
by throwme211345 9y ago
Amen.
13.
by throwme211345 9y ago
I see your design is lacking and your fud quotient is high. Good on you!
14.
by throwme211345 9y ago
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
15.
by throwme211345 9y ago
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 peop
16.
by throwme211345 9y ago
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 you
17.
by throwme211345 9y ago
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.
18.
by throwme211345 9y ago
Yeah, this is common. Don't modify firewall rules, fuck with interface settings and addressing without another way in.
19.
by throwme211345 9y ago
Oh fuck moment.
20.
by throwme211345 9y ago
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 woul
21.
by throwme211345 9y ago
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 t
22.
by throwme211345 9y ago
Garbage feedback from a prima-donna. Yay: I can't code in your crap because it's 2017 bro. Twitwit nonsense.
23.
by throwme211345 9y ago
man script.
24.
by throwme211345 9y ago
"We" is inclusive - 'most developers' is exclusive. Mystery solved.
25.
by throwme211345 9y ago
Why would someone do that?
26.
by throwme211345 9y ago
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. W
27.
by throwme211345 9y ago
I love you man.
28.
by throwme211345 9y ago
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.
29.
by throwme211345 9y ago
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 conversat
30.
by throwme211345 9y ago
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 gr

More ›