Hello peeps I want to make websites, so I'm going to learn php,sql, and Javascript. However I have some confusion on if I should learn one of these languages before another so I can have the most smoothest learning experience as possible.. So like if learn SQL and know how to build databases, but not php will it be useless by itself? Like say I had my own website already could I just add my sql database to it without understanding what the php code does. And again same with with Javascript could I add it easily to my website without knowing how the website is built? I know there's more languages like css, html but those I think are fairly easy to learn so I'm not worried about them atm... Any help will be appreciated!!!

MySQL/MariaDB and PHP are separate things. You can learn them separately and you can learn one without learning the other.

They intersect with phpMyAdmin, which is a tool for managing *SQL databases written in PHP (and, to some extent, in *.php webpages, which can call information from *SQL databases), but you can use the phpMyAdmin interface without knowing how to code PHP. You can also manipulate SQL without using phpMyAdmin, but phpMyAdmin makes it quite a bit easier.

Thanks for the tip I'll definitely consider it!

You could learn those languages while creating a simple projet. Like a html page that uses JQuery to request a php script that collects infos from a mySQL database

Take a look at W3Schools - a good site for learning all this.

... (koff, koff) ...

It's too bad that you missed both BYTE and Creative Computing, having been born too late to have actually "been there, done that" ... ... but ...

... "quite honestly, 'learning an entire new language'" is something that you are quite expected(!) to be able to do over a single weekend.

"The learning experience" is actually never "smooth." (One author of the day referred to it as "taking a sip from a fire-hose.")

You should also be very-frankly prepared for the realization that "Rome wasn't built in a day." I've been practicing "this crazy hobby profession of mine" for more than thirty-five years now, and I'm still not convinced that I am any good at it. But, "this one thing I do know": that it is considerably more difficult than it looks.

"Yeah, yeah, maybe you'll get that gold buckle. But, right now, you have a bull by the horns ..."

Thanks for all the great advice I think I think I'll just learn PHP first cause I have a feeling it'll be easier to know about the plugins (if I can call it that) for the other languages first.. And I'm in no rush to make a website so all will be easy peezy!!

Strange as it may seem ... or not ... I find myself "a student of programming languages." I actually enjoy finding new ones and kicking their tires, especially since nearly all of them have Unix/Linux open-source implementations.

The vast majority of them are "ALGOL-derivative languages," using the traditional "procedural" approach to problem-solving (such as all of the languages most-commonly discussed here), but some are not.

SQL, for instance, is a (semi-)declarative language: you describe the solution that you want, but don't tell the underlying system how to do it – as you would have had to do with a predecessor like IDMS, or that you do(!) have to do, today, in a throwback-language like MongoDB. SQL is not fully declarative, however ...

Languages such as Prolog (almost-)purely describe the problem to be solved, giving (almost) no hint as to how to arrive at the solution. Great way to solve Sudoku puzzles or logic-problems. ("The man with the red hat is not sitting on the blue chair.")

I have more-or-less made my living by dealing with legacy software: right now, I'm unraveling a big, phat, PHP system ... 11 years old at this writing ... which by-the-way earns over $1.1 million dollars a month. Dozens of people over these years have turned up their noses at it and promised to "re-write" it. I did not. Neither do I challenge the author – my boss on the project – nor will I ever. Having a very broad(!) technical perspective from which to work, honed by more than three decades now of experience, have certainly served me well in this niche. But, it all comes, I think, from my genuine fascination with computer programming languages and techniques. (Yes, it still amazes that we can make machines(!) do these wonderful things for people. And, across all these many years now, "the details are continuously changing, but the principles do not."

Ahh, we do live in interesting times.