Programmers out here?

I find that the best way to learn (for me), it to just start working on an app that you want to make. If you don't know how to do something, you go on google and start searching around until you can figure out how to do it.
This. Works best for me, too.

I might paraphrase this incorrectly, but PHP, SQL, Perl, etc are Scripting languages, not programming languages. The argument is that a programming language can compile and send directly to the processor, whereas Perl, SQL, PHP, Batch, Bash, etc cannot.
It honestly sounds like you just made that argument up. PHP and Perl are programming languages, period.

Am I the only one here who knows Lua?
Nope!
 
well anyone here developing games ? I am really interested but i just can't find a spot to start . Other then that i am really good with C++ and Java , and have worked in C# , Actionscript3.0 , ASM , Python , C , PHP

If you're good with C++, I suggest you go from there. When I started writing games I used SDL which is pretty simple to use and made some nice 2D games. You could just start learning OpenGL/Direct3D or something but it can be a bit overwhelming when you're just getting started.
 
If you do some researching, you'll see that some people get real technical about what is a programming language or not. I might paraphrase this incorrectly, but PHP, SQL, Perl, etc are Scripting languages, not programming languages. The argument is that a programming language can compile and send directly to the processor, whereas Perl, SQL, PHP, Batch, Bash, etc cannot. They send messages to an interpreter which then sends messages to the processor. Again, I might have paraphrased this wrong, but do some googling on it, and you'll it's basically a huge nerd war and that with some languages it really is a technicality (such as PHP, since you can still build desktop applications for it. Asterisk VOIP uses PHP for it's phone menus, or at least did at one point in time if it does not anymore).

Perl has a compile and runtime phase. And I have no idea who uses the type of applications a language can make in arguing whether or not it's a programming language.
 
Perl has a compile and runtime phase. And I have no idea who uses the type of applications a language can make in arguing whether or not it's a programming language.

This was me not understanding Perl :/. Would you also say Java is flat out a programming language by the same definition? Java still has an interpreter which is one of those criteria people rule it against. Java also have a compile and runtime phase though. That's why I said depending on technicalities.

It honestly sounds like you just made that argument up. PHP and Perl are programming languages, period.

Did you bother googling this? I have a few friends who are big into programming (as well with PHP) and the discussion comes up quite often.

http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=is+php+a+scripting+or+programming+language

http://www.google.com/search?source...=1&bav=on.2,or.r_gc.r_pw.&fp=91f35080109ff7ec
 
is this some gaming engine made in flash? and if you have made any game in it then can you show it to me please :)

It's a 2D library for AS3 that lets you use raster graphics instead of vector ones, it's really good if you have a history using Game Maker, but it's easy to use regardless. This is one I made for a game jam a while back, and this I got sponsored.

The first one took 48 hours to make, and the second took about a week, although if I was dedicated I could have finished it way quicker.
 
Re: Programing vs. Scripting Languages

There are both compiled and interpreted programming languages. And in fact some, like C#, are both at the same time. It's compiled into an intermediate language, which is then interpreted at run-time.

Really, the thing that determines whether or not a language is a programming language is whether or not it can be used for writing programs.

For instance, one thing that keeps a language from being a programming language is lack of flow control. If the language doesn't have a facility for conditionally branching logic, then you can't use it for programming. Hence a mark-up language (HTML, XML, etc.) is not a programming language because there's no way to write a program with it.

Another thing that keeps some languages from being programming languages is that they are only used to control the behavior of other programs. Some scripting languages have many of the features of programming languages, but they can't be used to to make programs, simply because there exists no stand-alone compiler or interpreter for doing so, and they have no input/output features apart from interacting with the program they are designed to control.

And there's plenty of gray area. JavaScript, for instance, is an object oriented language with flow control that can be used to write applications that interact with users in arbitrary ways.

It's called a script because it works within the context of a web browser, and can be seen as purely controlling the features of the browser. But from another point of view, a web-browser is a general enough environment, which is ubiquitous enough amongst end-users, that web-applications can certainly be considered programs/applications in their own right, and not just browser scripts.

So in some instances, the distinction is about the language lacking programming capabilities by nature, and in others its more of a technicality of the situations in which the language can actually be used.
 

My first response was that w3schools isn't any good for advanced programming, but that seems to have changed a bit. I still wouldn't recommend it for advanced programming though as it is clearly aiming only at the web and mostly at beginners

The more advanced programs I wrote aren't actually using any code that is more difficult. They DO have a much better structure so they are easier to change, extend, maintain, test, and work on with multiple people.

(I also see some irony in this url: http://www.w3schools.com/php/default.asp)
 
It's a 2D library for AS3 that lets you use raster graphics instead of vector ones, it's really good if you have a history using Game Maker, but it's easy to use regardless. This is one I made for a game jam a while back, and this I got sponsored.

The first one took 48 hours to make, and the second took about a week, although if I was dedicated I could have finished it way quicker.

nice games . How did you start making the game . Saw any tutorials ? if yes then can you give me some links please
 
Ok, I know it's pointless to complain about at this point, but since I'm among programmers, it has to be said...

Is anyone else driven just a little bit crazy by the cubing community's misuse of the term "algorithm"?
 
Ok, I know it's pointless to complain about at this point, but since I'm among programmers, it has to be said...

Is anyone else driven just a little bit crazy by the cubing community's misuse of the term "algorithm"?

A precise step-by-step plan for a computational procedure that begins with an input value and yields an output value in a finite number of steps.
Computational: calculating or reckoning.
Procedure: a particular method for performing a task.
Input value: the state of a cube.
Output value: another state.
Finite number: obviously.
Steps: which sides to turn and how much to turn them by.

Before reading this, what would you have suggested as a better term to use instead of algorithm?
 
Before reading this, what would you have suggested as a better term to use instead of algorithm?
"Sequence" seems perfectly adequate.

An algorithm is a "decision sequence".

Technically, you can decide at each point that the state is perfectly predictable so you just do the next move. And so technically, a prescribed sequence of moves, involving no decisions, is an algorithm, in that it meets the denotation of the term.

But it definitely violates the connotation that there are decisions being made at each point, which makes it misleading, since you would presumably have used any word like "sequence", which is both simpler and more accurately descriptive, if that's what you had meant.

"Methods", such as Fridrich, Petrus, Waterman, and Roux would be more appropriate to call algorithms. They involve a sequence of examination, evaluation, decision, and action, which is what "algorithm" is generally used to imply.
 
Is anyone else driven just a little bit crazy by the cubing community's misuse of the term "algorithm"?

...what would you have suggested as a better term to use instead of algorithm?

Move sequence? (At least that's what we use in Germany to avoid the term algorithm)

I take this as a "yes". I guess Germans don't like using the term "algorithm" to describe a sequence of moves involving no decisions.
 
Back
Top