learn or at least become familiar with lisp, game theory and take physics 101 (specifically vector diagrams), program in python and c, look at perl, watch all of starwars, and you will understand 100% of it... or go insane
as I am going to "rural" srilanka in 2 months, I'll be sure to tell em to send you the prototype when its done. theres not much in the way of raw materials so they've designed a manufacturing process using bamboo and stones.
cheers
the term "method" isn't necessarily limited to java. a method is mearly a function which exists as a an instance of a prototypical function and refers to instance level variables. IE: instance functions
as for a first language, I subscribe to the "if you don't get t within the first week(I'd prefer to say day but I decided to be generous), you probably never will" school of cs education theory. call me crass but I've put in time trying to explain things as simple as variable asignment (visavie x = 6; java/c++ style, (I wouldn't even bother with asignment schemes in functional languages lke haskell or erlang)) and you know, it just does not click no matter how many diagrams and metaphors one uses.
now as far as those that do get the main ideas of procedural rogramming, object orientation tends to follow pretty smoothly regardless of weather you follow the smalltalk or simula approach to OOP .
I for one reccomed teaching c first nothing too complicated within that mix, but basic input and outut and the concept of pointers. then once they understand this, engage in the delightful journey into abstaction masturbation that is lisp and teach all the paradigms from there.
ok, several more things...
1.) while Hemp may be a strain of cannabis sativa, there are in fact plenty of sativa strains containing thc among a cocktail of other euphoria inducing cannabinoids. Purple Haze for nstance is a sativa, not an Indica. Also, Indica is a hardier plant actually and there are stains that grow up to 6 feet tall
2.) never heard of "Indo" but the effects garnered from indica are diffrent from sativa, Indica strains are heavier leading to an intense body high while sativa strains more to a cerebral heady awake kind of high. I wouldn't descrive either as "LESS"
3.) Agreed
Why is that? Do you have an objective reason to damn server side code written in Java, other than the fact that you don't like it? What are you proposing is better? Please tell me you're not stuck in 2006 advocated ruby on rails or its ilk. These are optimized for consultants to get in and quickly deliver code that doubles the amount of long term maintenance you'll have to buy from them.
well I for one have programmed in java and rails and I'll tell you for anything that needs to scale alot I'm going with erlang.
first of all, ruby on rails was designed for startups, not consultants. it was optimized to get fledgeling apps created quickly using sane conventions that allow for rapid development and relatively easy maintenance as anyone who has worked with rails knows the source tree for just about any rails app and can get off the ground much faster.
java feels like a toy. Ruby has first class functions, closures and is a hell of alot more OO than java. the compile run cycle takes too much time as the app gets bigger.
ruby is great for its features but the metaprogramming features eat away at its performance. So while java takes a long time to build. you'll need more boxes as you scale in ruby.
the sad thing is, metaprogramming does not have to be a performance hit. Lisps dialects make extensive use of macroexpanion at compile time essetially giving you performance for free. ruby on the other hand does all its stuff at runtime. while you can do this in common lisp, its generally avoided.
anyways, I'd say erlng is the future. te erlang web server, yaws, can handle up to up to 80,000 connections wheras apache breaks down at 4,000. its a purely functional language so its very easy to write full robust programs that scale across processors. This is to my knowledge not possible in haskell due to lazy evaluation.
anyways, I'll reserve my last words about java so as not to incurr the wrath of the moderator gods...
Slashdot Mirror
I believe torque uses a javascript derived language for scripting
You also need to understand the social zeitgeist, live on the internet and have -->experience of good and bad sexual relationships.
All in all, a fun life ;)
I think someone's asking a bit much of the /. crowd aren't we :P
learn or at least become familiar with lisp, game theory and take physics 101 (specifically vector diagrams), program in python and c, look at perl, watch all of starwars, and you will understand 100% of it... or go insane
actually, Tesela was a dig digger at one point in his life...
as I am going to "rural" srilanka in 2 months, I'll be sure to tell em to send you the prototype when its done. theres not much in the way of raw materials so they've designed a manufacturing process using bamboo and stones. cheers
the term "method" isn't necessarily limited to java. a method is mearly a function which exists as a an instance of a prototypical function and refers to instance level variables. IE: instance functions as for a first language, I subscribe to the "if you don't get t within the first week(I'd prefer to say day but I decided to be generous), you probably never will" school of cs education theory. call me crass but I've put in time trying to explain things as simple as variable asignment (visavie x = 6; java/c++ style, (I wouldn't even bother with asignment schemes in functional languages lke haskell or erlang)) and you know, it just does not click no matter how many diagrams and metaphors one uses.
now as far as those that do get the main ideas of procedural rogramming, object orientation tends to follow pretty smoothly regardless of weather you follow the smalltalk or simula approach to OOP .
I for one reccomed teaching c first nothing too complicated within that mix, but basic input and outut and the concept of pointers. then once they understand this, engage in the delightful journey into abstaction masturbation that is lisp and teach all the paradigms from there.
12 feet? well I for one worship our impending medicinally laced overlords...
ok, several more things...
1.) while Hemp may be a strain of cannabis sativa, there are in fact plenty of sativa strains containing thc among a cocktail of other euphoria inducing cannabinoids. Purple Haze for nstance is a sativa, not an Indica. Also, Indica is a hardier plant actually and there are stains that grow up to 6 feet tall
2.) never heard of "Indo" but the effects garnered from indica are diffrent from sativa, Indica strains are heavier leading to an intense body high while sativa strains more to a cerebral heady awake kind of high. I wouldn't descrive either as "LESS"
3.) Agreed
Why is that? Do you have an objective reason to damn server side code written in Java, other than the fact that you don't like it? What are you proposing is better? Please tell me you're not stuck in 2006 advocated ruby on rails or its ilk. These are optimized for consultants to get in and quickly deliver code that doubles the amount of long term maintenance you'll have to buy from them.
well I for one have programmed in java and rails and I'll tell you for anything that needs to scale alot I'm going with erlang. first of all, ruby on rails was designed for startups, not consultants. it was optimized to get fledgeling apps created quickly using sane conventions that allow for rapid development and relatively easy maintenance as anyone who has worked with rails knows the source tree for just about any rails app and can get off the ground much faster. java feels like a toy. Ruby has first class functions, closures and is a hell of alot more OO than java. the compile run cycle takes too much time as the app gets bigger. ruby is great for its features but the metaprogramming features eat away at its performance. So while java takes a long time to build. you'll need more boxes as you scale in ruby. the sad thing is, metaprogramming does not have to be a performance hit. Lisps dialects make extensive use of macroexpanion at compile time essetially giving you performance for free. ruby on the other hand does all its stuff at runtime. while you can do this in common lisp, its generally avoided. anyways, I'd say erlng is the future. te erlang web server, yaws, can handle up to up to 80,000 connections wheras apache breaks down at 4,000. its a purely functional language so its very easy to write full robust programs that scale across processors. This is to my knowledge not possible in haskell due to lazy evaluation. anyways, I'll reserve my last words about java so as not to incurr the wrath of the moderator gods...