Hey y'all,

So, I'm grateful for w3schools, don't get me wrong, but any recommendations to a newb looking to

learn

  JS and

PHP

 ? 

 
no reason for the barfing smiley but how the f*&k could i pass on it?  you sick fishs. 

oh yeah, nice to meet you. 

I can only speak from what works for me. You'd do well to just think of something you want written, then start writing it. Ask for help and use Google prodigiously.

Personally I find the pissing squirrel or the bukkake circle-jerk smilies (hidden ATM) to be much more delightful and disgusting. No worries mate, you'll see them at some point...

VS is right - the first step is to decide what you want to code, rather than just generalized

learn

 ing . There are books we can all recommend and lots of folks here willing to help... but if you pick out a task then go at it piece by piece it will be easier to build a frame of reference for your

learn

 ing  as well as increase your retention.

For

PHP

 : consider simple web-page enhancements that you'd like to try, followed perhaps by integrating with a database or some such.

For JS, consider form enhancement or validation first, followed perhaps by graphic tricks you've seen and want to duplicate.

I would stay away from

AJAX

  or anything of that caliber for a while.

I'd also start and get comfy with

PHP

  before I moved hard into JS because JS will

teach

  you bad habits - it being an essentially crappy implementation of a limited language. Better to

learn

  something that's more stock first.

Thanks guys. 

Nice to see everybody here is in the "jump right in" camp.

I'll get crackin then and come back with questions

in the meantime, this site is awesome.  I saw it on stumble today:
for that special someone 
http://www.shitsenders.com

HAHAH that gorilla poo looks awesome.

i agree with vs too, pick a project like
a sample loginsite , hork the code, try to make
it work and then post it here...(after doing your
best googling which a lot of times points me here
anyways.)

Yea

javascript

  is useful but not much for
science in my opinion, i mean if a JS dies
out their somewhere over the rainbow on
the client side, how do you know?

Someoneinaudience:  WRITE AN ERROR LOG AND CHECK IT LATER.

me:  well what if the error kills the computer, connection or both.

Someoneinaudience:  Empty thought cloud.

At least with

php

  you know your code completed...
I agree with perk, stick with

php

  first to keep
your head straight and then wax JS
later.. The reason being that by the
time you realize the output of

php

  is html and
in that html there could be

javascript

 .
Now the html/

javascript

  (dont forget their could
have been mysql code in the

php

  to make it
four different languages now) is then shot
to the browser. After that, the
browser (and hopefully you wrote seperate

javascript

  for every browser you may now
or ever be running on) parses and executes
the

javascript

  hopefully and all is well on the
clients

mac

 hine you have never seen or cant
be sure of the environment your running in,
your brains may end up exploding so magnificently
they just may reach the top of the tower of

php

 -mysql-html-js code-babble.

You should find your knowledge here, more
importantly, wisdom.

A clever man finds a solution to a problem;
a wise man avoids it - Einstein.

After you get a basic understanding of

php

 
flow, http://us3.

php

 

.net

 / is an excellent source and is
available in many languages.