Programming language?

[crazyhunter36]

Hi, What programming language need to I learn for creating 2D web based games?

 

[Negata]

Javascript.

 

[nevS]

JavaScript.
And depending which technology you want to use, there is other stuff to be learned (CSS, WebGL...).

I think three.js (contains renderer for WebGL, Canvas) is a good framework to start, and it's even capable of 3D

 

[crazyhunter36]

it is sufficient?
-WebGL
-CSS
-Javascript
-PHP
-SQL

 

[AnonymousHacker]

I adore the list you made on your own.
Javascript
PHP
SQL
CSS

They all have their own use.

CSS - You would like a good design correct?
SQL - Where will you store the accouts / game information
Javascript - It's all about functionality
PHP - How will the server side data , Registration / ETC work withot

 

[Negata]

You don't even need WebGL, PHP or SQL. Especially you can do without the last two and make a perfectly good browser game without any server at all.

 

[V for Vendetta]

Ne

Since i previously noticed that you are exactly knowing what you are talking about, have i decided to point my question at you. And nobody else.

What coding languages do you need to hold to make such client-game and where people can register and go to the client and play, and that the home has such things as profile settings et cetera that all connect with the server that you are also going to code.

 

[Negata]

Well most people could answer that question adequately.

For me, I'd pick the following mumbo-jumbo: Jade (html), Stylus (css), Coffeescript (javascript) for client side and node.js + mongodb for server and NOT develop on windows. Basically you do need all those components but I don't know if they're necessarily the most newbie friendly. So probably html+css+javascript+php+sql is just fine although I have an aversion towards doing anything at all with PHP. But it's probably easiest to get started with from level 0 and as you won't need a thick backend it's fine.

edit:
Still pondering... is node.js totally mainstream among newbies already?

 

[V for Vendetta]

Here's another question then.

I don't know if you have any knowledge related to Habbo hotel, But I've always wondered what they use to create that because for the basics i know that they are using: PHP, HTML, CSS , JQUERY. But what would they use for the in-client. I most recently noticed SWF files which i don't know **** about.

Anyway how am i suppose to create such game as Habbo such virtual game? - But nothing related to Habbo....

 

[Negata]

.swf indicates an applet run on the Flash player. As I see it, along with HTML5 features taking over the Flash technology is becoming obsolete. Most definitely it's not something that you should worry about at all if you're not already familiar with it.

So how to create such a game...? Well in most simplicity: a game is a collection of graphical objects, some of which respond to a set of input events and/or passage of time. Those graphical objects can be as simple as images displayed on HTML elements which you control via Javascript. Basically you'll write a server script that outputs the site HTML and include your Javascript file and there's your game. You'll also use Javascript (possibly the JQuery library) to access the server when you need to do something like login.

It's really a lot less complex than it might seem at a first glance if you don't know what kind of pieces it's made of.

 

[s-p-n]

I recently found playcraftlabs and I'm trying out their engine. The server is in Node.JS and their client library is prototypal JavaScript but utilizes closures as well. Their library seems to be one of the better HTML5 gaming libraries. They like to boast about working on multiple devices.
Home - Playcraft

 

[Negata]

Thanks for the link, s-p-n, I'll definitely check it out later! I've been periodically checking out for new and developing browser game engines/frameworks but nothing impressed me so far.

 

[crazyhunter36]

Now I get the best answer Thanks for you all..

 

[crazyhunter36]

web game legend of mir.flv - YouTube

you all things this games use what progamming lang?

 

[danse]

Well most people could answer that question adequately.

For me, I'd pick the following mumbo-jumbo: Jade (html), Stylus (css), Coffeescript (javascript) for client side and node.js + mongodb for server and NOT develop on windows. Basically you do need all those components but I don't know if they're necessarily the most newbie friendly. So probably html+css+javascript+php+sql is just fine although I have an aversion towards doing anything at all with PHP. But it's probably easiest to get started with from level 0 and as you won't need a thick backend it's fine.

edit:
Still pondering... is node.js totally mainstream among newbies already?

I'm it's kinda offtopic as we are argumenting over possible technologies which in this case are close to unlimited, yet I'm sorry Negata I really god damn sceptial of node.js - it's like forcing JavaScript to be a back-end language, I know i should be open to new technologies so I do enjoy stuff like Bootstrap, less.css or other, but JavaScript on back-end is something that does not speak to me, could you like thow few arguments from your experience that could at least convince me to give it a try, like biggest advantages of it in a pill, something that other languages are incapable of or that can be done blastly fast in node.js which would take me ages in PHP.

Thanks in advance.

 

[Negata]

I'm it's kinda offtopic as we are argumenting over possible technologies which in this case are close to unlimited, yet I'm sorry Negata I really god damn sceptial of node.js - it's like forcing JavaScript to be a back-end language, I know i should be open to new technologies so I do enjoy stuff like Bootstrap, less.css or other, but JavaScript on back-end is something that does not speak to me, could you like thow few arguments from your experience that could at least convince me to give it a try, like biggest advantages of it in a pill, something that other languages are incapable of or that can be done blastly fast in node.js which would take me ages in PHP.

Thanks in advance.

To me the best thing is the speed at which I can get a simple backend up and running from scratch. With npm (node package manager) downloading and managing 3rd party libraries which are plentiful is easy so typically when you need anything you'll just google for a library.

I'm fairly strong at using Coffeescript on the client side so when I switch to server code I don't need to make a context switch at all because the server is in the same language. It's easier on the brain. Sometimes you may require configuration variables both on client and server side, well when they're written in the same language you don't have to repeat your code but instead include the same configuration file on both sides.

Usually not a concern to me as I mostly deal with prototyping and software with small user bases, but in some cases you may appreciate node's quick response times to requests and ability to handle a great number of them at once. While neglible for full page loads, it's ace for ajax calls and websocket connections.

It feels good and I like writing in Coffeescript. I might not like it as much if I wrote plain JS though.

 

[danse]

To me the best thing is the speed at which I can get a simple backend up and running from scratch. With npm (node package manager) downloading and managing 3rd party libraries which are plentiful is easy so typically when you need anything you'll just google for a library.

I'm fairly strong at using Coffeescript on the client side so when I switch to server code I don't need to make a context switch at all because the server is in the same language. It's easier on the brain. Sometimes you may require configuration variables both on client and server side, well when they're written in the same language you don't have to repeat your code but instead include the same configuration file on both sides.

Usually not a concern to me as I mostly deal with prototyping and software with small user bases, but in some cases you may appreciate node's quick response times to requests and ability to handle a great number of them at once. While neglible for full page loads, it's ace for ajax calls and websocket connections.

It feels good and I like writing in Coffeescript. I might not like it as much if I wrote plain JS though.

Plain JS is not an option, abandoned it years ago in favor of jQuery. Having same language on both side ( front to back ) sounds tempting and scarry at same time.

Response time & heavy load can be dealt easily just by adding memcache and nginx as a reverse-proxy, in extreme cases load balancer is perfect solution.

Being able to prototype apps very fast is nice as well, but i'm using cakePHP as a framework, which in my opinion is one of the best when it comes to rapid development. Building app from scratch in no time is just combining cakePHP with Bootstrap from Twitter.

Also tempting is what you've mention about websockets, I had node.js has big advantage in this field.

 

[Negata]

Plain JS is not an option, abandoned it years ago in favor of jQuery. Having same language on both side ( front to back ) sounds tempting and scarry at same time.

Using just jQuery means still writing JS. If I had to type JS without Coffeescript now I'd kill myself. Too much noise in JS...

Response time & heavy load can be dealt easily just by adding memcache and nginx as a reverse-proxy, in extreme cases load balancer is perfect solution.

Not entirely true. In the context of thick client applications which I mostly deal with anyway majority of requests are passing JSON data back and forth as models get updated. That's something you can't cache.

If you're happy with PHP by all means stay at it. I've never had much exposure to PHP myself which I'm pretty happy about so I'm in no place to make a proper comparison. I just have the impression that PHP code is ugly while JS for example allows me to apply reactive and functional paradigms with ease. That suits me personally.

 

[danse]

Using just jQuery means still writing JS. If I had to type JS without Coffeescript now I'd kill myself. Too much noise in JS...
Not entirely true. In the context of thick client applications which I mostly deal with anyway majority of requests are passing JSON data back and forth as models get updated. That's something you can't cache.

Ok now you got with two points:
- I'm going to definetly check Coffeescript then, I'm really curious what it is.
- You told me when and in which case studies you apply those solutions, that's also tells me much usefull info.

thanks.

 

[jMerliN]

Using just jQuery means still writing JS. If I had to type JS without Coffeescript now I'd kill myself. Too much noise in JS...

Then you're doing it wrong. Coffeescript is horrible.

Not entirely true. In the context of thick client applications which I mostly deal with anyway majority of requests are passing JSON data back and forth as models get updated. That's something you can't cache.

The vast majority of load-heavy applications are read-intensive, so caching as close to the user as possible tends to scale better than anything else (hence why I refuse to use CDNs that don't have permanent caching for versioned files, because it's throwing away all layers of caching between the server and the client WRT latency, which is THE MOST IMPORTANT THING IN MODERN WEB APPLICATIONS).