Well Portland OR has Planet Argon, and pdx-ruby and weekly drop in
code-sprints at cubespace - typically starting with a ROR framework .... so
it seems like the town is Ruby crazy....
So it seems geographic... at least from where I am standing.
There was a fun little event recently at pdx-ruby where somebody presented
snippets of twenty obscure languages and people had to guess. The
grey-beards blew everybody else away across the board.
Lua is also used; and there's a fairly hefty embedded controller movement
such as dorkbot pdx . I see very little python... a little java { most of
the ruby devs also know java and use it for EE type projects } .
Still, to get back to the original question; there seems to be no pseudocode
convention; everybody is pretty fluent at everything - and largely stick to
c-like syntax...
- a
On Jan 21, 2008 2:53 PM, Sean Gillies <[EMAIL PROTECTED]> wrote:
> Different industries have different demographics too. The GIS biz is by
> all reports rather advanced in age.
>
> Sean
>
> Steve Lombardi wrote:
> > I suspect more important than age is industry. Just a hunch
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Sean Gillies
> > Sent: Monday, January 21, 2008 2:34 PM
> > To: [EMAIL PROTECTED]; [email protected]
> > Subject: Re: [Geowanking] Standard for Pseudocode
> >
> > Maybe, but it wouldn't be geographic. It would be demographic. Strongly
> > determined by the age of the programming population, I suspect.
> >
> > Sean
> >
> > Anselm Hook wrote:
> >> Mentioned before but I've often wondered if there are geographic
> regional
> >> variations in favored programming languages; ranging from merely
> dialects to
> >> full blown language preferences... SFO might be a php town... Seattle
> might
> >> be a Python town etc... Portland a Ruby town...
> >>
> >> - a
> >>
> >> On Jan 21, 2008 2:20 PM, Artem Pavlenko <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> "Python is executable pseudocode. Perl is executable line noise."
> >>> - Old Klingon Proverb
> >>>
> >>> HTH
> >>> Artem
> >>>
> >>>
> >>>> I was about
> >>>> to say
> >>>> http://www.perl.org but
> >>>> then realized that
> >>>> having the freedom
> >>>> to put whitespace wherever I want
> >>>> and
> >>>> indentation wherever I
> >>>> want can
> >>>> be too
> >>>> much wanking
> >>>> for some people
> >>>> :
> >>>> );
> >>>>
> >>>> On 1/21/08, Sean Gillies <[EMAIL PROTECTED]> wrote:
> >>>>> I was about to say. Or http://python.org/doc. No $@ noise and
> >>>>> mandatory
> >>>>> whitespace and indentation to enforce readability :)
> >>>>>
> >>>>> Sean
> >>>>>
> >>>>> Andrew Turner wrote:
> >>>>>> What about http://www.ruby-lang.org/en/ ?
> >>>>>>
> >>>>>> ;)
> >>>>>>
> >>>>>> On Jan 21, 2008 4:26 PM, Landon Blake <[EMAIL PROTECTED]> wrote:
> >>>>>>>
> >>>>>>> Have any Geowankers come across a standard for pseudocode?
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> We were talking about using pseudocode for programming language-
> >>>>>>> neutral
> >>>>>>> information on spatial reference system transformations,
> >>>>>>> calculations and
> >>>>>>> algorithms. This information would be part of a possible project
> >>>>>>> at the
> >>>>>>> OSGeo on spatial reference systems. I was hoping to find a
> >>>>>>> pseudocode
> >>>>>>> standard, but Google didn't turn up much:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> http://users.csc.calpoly.edu/~jdalbey/SWE/pdl_std.html<http://users.csc.calpoly.edu/%7Ejdalbey/SWE/pdl_std.html>
> <http://users.csc.calpoly.edu/%7Ejdalbey/SWE/pdl_std.html>
> >>>>>>>
> >>>>>>> http://www.csd.abdn.ac.uk/~pedwards/teaching/CS3007/requirements/<http://www.csd.abdn.ac.uk/%7Epedwards/teaching/CS3007/requirements/>
> <http://www.csd.abdn.ac.uk/%7Epedwards/teaching/CS3007/requirements/>
> >>>>>>> pseudocode.html
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks for any suggestions.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Landon
> >>>>>>>
> >>>>>>> Warning:
> >>>>>>> Information provided via electronic media is not guaranteed
> >>>>>>> against defects
> >>>>>>> including translation and transmission errors. If the reader is
> >>>>>>> not the
> >>>>>>> intended recipient, you are hereby notified that any
> dissemination,
> >>>>>>> distribution or copying of this communication is strictly
> >>>>>>> prohibited. If
> >>>>>>> you have received this information in error, please notify the
> >>>>>>> sender
> >>>>>>> immediately.
> >>>>>>> _______________________________________________
> >>>>>>> Geowanking mailing list
> >>>>>>> [email protected]
> >>>>>>> http://lists.burri.to/mailman/listinfo/geowanking
> >>>>>>>
> >>>>>>
> >>>>> _______________________________________________
> >>>>> Geowanking mailing list
> >>>>> [email protected]
> >>>>> http://lists.burri.to/mailman/listinfo/geowanking
> >>>>>
> >>>> _______________________________________________
> >>>> Geowanking mailing list
> >>>> [email protected]
> >>>> http://lists.burri.to/mailman/listinfo/geowanking
> >>> _______________________________________________
> >>> Geowanking mailing list
> >>> [email protected]
> >>> http://lists.burri.to/mailman/listinfo/geowanking
> >>>
> >>
> >>
> ------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> Geowanking mailing list
> >> [email protected]
> >> http://lists.burri.to/mailman/listinfo/geowanking
> >
> > _______________________________________________
> > Geowanking mailing list
> > [email protected]
> > http://lists.burri.to/mailman/listinfo/geowanking
> > _______________________________________________
> > Geowanking mailing list
> > [email protected]
> > http://lists.burri.to/mailman/listinfo/geowanking
> >
>
> _______________________________________________
> Geowanking mailing list
> [email protected]
> http://lists.burri.to/mailman/listinfo/geowanking
>
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
