@douglaspurdy My 9-year-old is a Beatles fan, my 16-year-old almost an expert. Same pride here :-)
@alexkli I get that. I’m wondering whether a lib can be built in a safe lang, and then be combined with C, without a lack of efficiency
@alexkli But that’s a different thing. Clearly there’s no protection against the users using a lib wrongly
1
Don’t blame the author of the Heartbleed bug code for making a mistake unless you a) don’t make mistakes yourself or b) are Bruce Schneier
5
14
6
@frankgerhardt Ganz schön scheiße, was fefe da macht; grenzt ja schon fast an Rufmord.
1
@assaf Of course you can do anything in any language. Doesn’t mean you actually would.
2
@assaf If your language doesn’t allow you to do memory management, that seems like a plus
1
Any pointers to a good treatment on why one can’t build an efficient library usable from C in a language that prevents raw memory access?
5
2
3
Quite embarrassing, AWS: “This was a text book example of how to do bad communication on very serious issues” blog.opbeat.com/posts/amateu…
1
11
8
@viktorklang @hseeberger Maybe it qualifies as a double anti-pattern then
1
I think implementing a BPM engine using a BPM engine has become my new favorite architectural anti-pattern.
6
11
6
Das (wie ich finde großartige) Booklet, das wir beim Girls’ Day benutzt haben: innoq.com/de/news/2014/04/fu… innoq.com/de/news/2014/04/fu…
1
2
1
Very good “Diagnosis of the OpenSSL Heartbleed Bug” by @ex509: blog.existentialize.com/diag… BTW: “Start writing alternatives in safer languages”
2
4
6