Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

jewgold

Name: Anonymous 2009-02-19 0:26

lisp    $79,000
c++    $87,000
java    $86,000
c#    $86,000   
python    $83,000
ruby    $78,000
smalltalk $90,000   
php    $74,000

source:
http://www.indeed.com/salary?q1=lisp&l1=&q2=c%2B%2B&l2=&q3=java&l3=&q4=c%23&l4=&q5=python&l5=&q6=ruby&l6=&q7=smalltalk&l7=&q8=php&l8=

what is this shit?
do php programmers really get $74K salaries? what the hell is wrong with the world?

ITT: programming languages you have been paid to use, what you were doing with them, how much you were paid a year, and a time frame.

eg:
scheme
calculating Fibonacci numbers
$0.00.P.A
1972 - now

Name: Anonymous 2009-08-28 17:41

>>33
Here's how CL performs on it, generates slightly less garbage:


CL-USER> (time (fibs3 10001))
Evaluation took:
  0.000 seconds of real time
  0.000000 seconds of total run time (0.000000 user, 0.000000 system)
  100.00% CPU
  10,383,444 processor cycles
  4,458,784 bytes consed
 
54438373113565281338734260993750380135389184554695967026247715841208582865622349017083051547938960541173822675978026317384359584751116241439174702642959169925586334117906063048089793531476108466259072759367899150677960088306597966641965824937721800381441158841042480997984696487375337180028163763317781927941101369262750979509800713596718023814710669912644214775254478587674568963808002962265133111359929762726679441400101575800043510777465935805362502461707918059226414679005690752321895868142367849593880756423483754386342639635970733756260098962462668746112041739819404875062443709868654315626847186195620146126642232711815040367018825205314845875817193533529827837800351902529239517836689467661917953884712441028463935449484614450778762529520961887597272889220768537396475869543159172434537193611263743926337313005896167248051737986306368115003088396749587102619524631352447499505204198305187168321623283859794627245919771454628218399695789223798912199431775469705216131081096559950638297261253848242007897109054754028438149611930465061866170122983288964352733750792786069444761853525144421077928045979904561298129423809156055033032338919609162236698759922782923191896688017718575555520994653320128446502371153715141749290913104897203455577507196645425232862022019506091483585223882711016708433051169942115775151255510251655931888164048344129557038825477521111577395780115868397072602565614824956460538700280331311861485399805397031555727529693399586079850381581446276433858828529535803424850845426446471681531001533180479567436396815653326152509571127480411928196022148849148284389124178520174507305538928717857923509417743383331506898239354421988805429332440371194867215543576548565499134519271098919802665184564927827827212957649240235507595558205647569365394873317659000206373126570643509709482649710038733517477713403319028105575667931789470024118803094604034362953471997461392274791549730356412633074230824051999996101549784667340458326852960388301120765629245998136251652347093963049734046445106365304163630823669242257761468288461791843224793434406079917883360676846711185597501


Implementation:

(defun fibs3 (n)
  (labels ((rec (prev cur k n)        
         (if (= k n)
         cur
         (rec cur (+ prev cur) (1+ k) n))))
    (rec 1 0 0 n)))

;;; I also have an imperative one, a parallel setf one, 2 memoized implementation of simple (doubly) recursive fibs. They perform more or less the same in speed, but the hashtable memoized one eats a bit more memory due to hashtable lookups. The one which is memoized using arrays is just as fast though, except for the memory usage as it remembers all previous fib numbers.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List