recentpopularlog in

mcherm : brianhurt   7

The problem with STM: your languages still suck
Software Transactional Memory (STM) doesn't play well with anything imperative or mutable. It's a natural for Haskell but every other programming language is in trouble. And it might be the only way to sanely use ever-increasing numbers of cores.
programming  functional  concurrency  haskell  stm  via:reddit  BrianHurt  threading  concurrentprogramming  parallelprogramming  softwaretransactionalmemory 
august 2011 by mcherm
Steve Yegge is an idiot [A rant about specifying contracts for code]
A rant, but it's a useful rant. Making a distinction between what's part of the API and what isn't is important. Documenting this is important. "public" and "private" help enforce that.
via:BrianHurt  BrianHurt  yegge  programming 
august 2010 by mcherm
Apple is just Microsoft with better marketing
Yet another well-written description of how Apple's recent actions cross the line to abusing its monopoly power even worse than Microsoft ever abused theirs. (Although he thinks Apple isn't a monopoly: I'm not so sure.)
via:BrianHurt  BrianHurt  apple  appstore 
may 2010 by mcherm
Why I Quit Twitter
I quit using Twitter because without the long form it is impossible to say anything deeper than a bumper sticker.
BrianHurt  via:BrianHurt  twitter 
march 2010 by mcherm
The “Hole in the middle” pattern | Enfranchised Mind
Observations of how C# makes it awkward to create small anonymous functions that access local variables whereas Ocaml makes it easy. He notes that this changes how the programmer works in the two languages.
languagedesign  programming  functional  via:BrianHurt  BrianHurt 
november 2009 by mcherm
Responses to The Problem with STM | Enfranchised Mind
Interesting observation: pure immutable data structures tend not to be compatible with concurrent programming, because sharing between threads would require a mutable current-state-of-the-structure variable.
programming  immutable  concurrency  parallelprogramming  via:BrianHurt  BrianHurt  softwaretransactionalmemory 
may 2009 by mcherm
The problem with STM: your languages still suck » Enfranchised Mind
Software Transactional Memory works GREAT in Haskell, but it's just never going to work in Java, C, and such because they are too full of side effects -- it's just not a good match for the behavior of STM. STM is the best of possible solutions to concurrent programming (I don't think I agree with that!), so programming languages will have to change.
concu  concurrency  concurrentprogramming  languagedesign  haskell  functional  stm  softwaretransactionalmemory  progra  programming  parallelprogramming  BrianHurt 
january 2009 by mcherm

Copy this bookmark:





to read