Re:GNU Guile 2.0.9 released
by threedaymonk on Wednesday April 10, 2013 @09:08AM
(#5524845)
Note: 2.0.8 was a brown paper bag release that was never announced, but
some mirrors may have picked it up. Please do not use it.
I'm a native speaker of English, but I don't understand the idiom of "brown paper bag release". A search shows that it's quite widely attested, however.
Re:GNU Guile 2.0.9 released
by rvasco on Wednesday April 10, 2013 @09:17AM
(#5524894)
"A bug in a public software release that is so embarrassing that the author notionally wears a brown paper bag over his head for a while so he won't be recognized on the net. Entered popular usage after the early-1999 release of the first Linux 2.2, which had one. The phrase was used in Linus Torvalds's apology posting."
Re:GNU Guile 2.0.9 released
by guan on Wednesday April 10, 2013 @09:14AM
(#5524874)
It refers to the practice of wearing a brown paper bag over your head if you don’t want people to see your face. In this case, the developers are (figuratively) doing this because they are embarrassed over some aspect of version 2.0.8.
Re:GNU Guile 2.0.9 released
by omaranto on Thursday April 11, 2013 @11:05AM
(#5532377)
For me the best feature of the 2.0.9 release is that the documentation builds again! I tried compiling 2.0.7 and got some weird errors from texinfo. I couldn't figure out how to fix them quickly so I just installed without documentation. But 2.0.9 builds fine, including documentation, on my system.
Re:GNU Guile 2.0.9 released
by frozenport on Wednesday April 10, 2013 @12:00PM
(#5525933)
One of my favorite simulators, Meep (http://ab-initio.mit.edu/wiki/index.php/Meep) uses Guile as a control interface. From my experience using Guile presents an unnecessary obstacle to even the most brightest programmers. I frequently see bash scripts writing HERE scheme files because for loops are too difficult in scheme.
Re:GNU Guile 2.0.9 released
by outworlder on Wednesday April 10, 2013 @12:12PM
(#5526034)
> I frequently see bash scripts writing HERE scheme files because for loops are too difficult in scheme.
Why? Loops in general are quite easy to do in Scheme, specially the "for-each" variety.
"The most brightest programmers", if bothered by the lack of a C-like for construct, would be able to fix that, for them and for others, in 5 minutes with a macro.
Scheme is easy and incredibly powerful. Its only issue is that knowledge in other languages does not necessarily translate directly to it. In other words, you have to take some time to learn, which is not a good thing nowadays with the instant gratification culture.
Re:GNU Guile 2.0.9 released
by frozenport on Wednesday April 10, 2013 @03:10PM
(#5527339)
Scheme certainly isn't hard, but given a choice between working on their codes or using a dirty hack to get on with their lives. Everybody I know choose to get on with their lives. A python interface would have been better.
What does it mean (and what's its origin)?
racket is the goto if you need r6rs compat though
http://wingolog.org/archives/2013/01/07/an-opinionated-guide...
tl;dr - he recommends the SICP mode for Racket.
See: http://www.gnu.org/ghm/2011/paris/slides/andy-wingo-guile.pd...
Why? Loops in general are quite easy to do in Scheme, specially the "for-each" variety.
"The most brightest programmers", if bothered by the lack of a C-like for construct, would be able to fix that, for them and for others, in 5 minutes with a macro.
Scheme is easy and incredibly powerful. Its only issue is that knowledge in other languages does not necessarily translate directly to it. In other words, you have to take some time to learn, which is not a good thing nowadays with the instant gratification culture.
for-each? http://www.gnu.org/software/guile/manual/html_node/SRFI_002d...
or how about a named let?
or how about using SRFI 42? http://srfi.schemers.org/srfi-42/srfi-42.htmlIt's a pretty trivial transformation -- not hard at all. I think these "most brightest" programmers just didn't want to learn the freakin' language.