If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Which language to study next?

So
HTML, CSS, Javascript, XML, PHP and MySQL are cool to study.
Having HTML as the main markup language.
CSS to style mine pages.
Javascript to give mine website a little extra of effect.
XML to gather up data and let it easier to refresh on the page it self.
PHP for the prepossessing of pages that you can make.
MySQL for the User database information.

However, all of those languages have it's limit.
For example on Javascript you can Perform a function only once or let it loop trough an array.

So for some extra effect, maybe something for game based language I'm looking up for a new language which is even more dynamic.

I have been looking into Java but I'm not sure if I should study that language as it's being used less in the days.

Java is an extremely common language used all over the place, both for the web and applications. Many games are written using C# and C++, however, game development will involve much more complex topics, such as game engines, collision detection, etc... .

While you learn more languages, try to combine the ones you already know and build something increasingly complex. You'll find there are plenty of things about each language you probably don't know but once you learn it, you can perhaps apply it to other languages. One of the things I got involved in was making simple games, starting at with text-only cheesy games in Java. Eventually, I made other games, such as Snake, started to work on Tetris (got too busy so never finished it) but then decided whether I could make games in other languages, such as JavaScript, HTML and CSS. Another thing is if you see a nice site, game or whatever else, try to create it by yourself. It doesn't have to be perfect, you don't need to show it to anyone but it's to see whether you can do it and improve your coding abilities. Later, you can return to things you previously made and improve their performance, especially for SQL and PHP (i.e. I often run timers to see which scripts will return the correct results as fast as possible, which is critical if you're dealing with 400K+ rows).