From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: [9fans] current state of thread programming
Date: Mon, 28 Jul 2008 11:11:19 -0600 [thread overview]
Message-ID: <14ec7b180807281011k2ccffe12i5739998193c18024@mail.gmail.com> (raw)
found this snippet today and decided to share it with the list. every
once in a while a look at how "the rest of the world" does things is
beneficial :)
"I don't know about you, but every time I have to program with threads
and shared resources, I want to remove my face incrementally with a
salad fork. Locks, mutexes, the synchronized keyword; all of these
things can strike fear into the heart of a green developer. Most
seasoned developers just fall into a rut of depression when it's time
for multi-threading. Developers like me simply talk our way out of it.
It's easier than thinking."
full article: http://www.theregister.co.uk/2008/07/28/sun_dziuba_tm/
next reply other threads:[~2008-07-28 17:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 17:11 andrey mirtchovski [this message]
2008-07-28 17:50 ` tlaronde
2008-07-28 19:52 ` Pietro Gagliardi
2008-07-28 21:07 ` Russ Cox
2008-07-28 21:33 ` Skip Tavakkolian
2008-07-29 18:40 ` Roman V. Shaposhnik
2008-07-29 19:12 ` Bakul Shah
2008-07-30 11:35 ` tlaronde
2008-07-30 11:50 ` Roman V. Shaposhnik
2008-07-30 13:50 ` Paweł Lasek
2008-07-30 17:42 ` tlaronde
2008-07-30 18:07 ` tlaronde
2008-07-30 18:17 ` andrey mirtchovski
2008-07-30 11:58 ` Robert Raschke
2008-07-30 13:53 ` David Leimbach
2008-07-30 14:00 ` andrey mirtchovski
2008-07-30 15:35 ` Roman V. Shaposhnik
2008-07-30 16:53 ` Bakul Shah
2008-07-30 12:50 erik quanstrom
[not found] <9b1933b61c606e89a4cbbc93a4b5a204@quanstro.net>
2008-07-30 17:31 ` tlaronde
2008-07-30 18:58 ` Sape Mullender
2008-07-30 20:04 ` tlaronde
2008-08-05 10:34 Richard Maxwell Underwood
2008-08-05 15:28 ` Eris Discordia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14ec7b180807281011k2ccffe12i5739998193c18024@mail.gmail.com \
--to=mirtchovski@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).