Programming Language
- Thread starter Munzy
- Start date
wlanboy
Content Contributer
There are different routes:
Take one and search for the proper client side framework.
- .Net environment
All about C# and ASP.NET. Looks similar but you need a new (and pricy) environment: Windows Server, IIS, MSSQL (or Azure) and Visual Studio. - Java environment
Opensource like PHP. Similar language and you can scale from JBoss. JSF and JEE are the starters. - Ruby
Good for webpages, REST services, message driven apps (my homepage is written in Ruby too). The mayor static generators are written in Ruby too: Jekyll, Octopress and Middleman. - Phyton
Same as Ruby. There is one static generator too: Pelican. Well the discussion for Ruby or Phyton is allready
- JavaScript
Don't underestimate the new drive of client side JS. Forget about the node.js hype.
More and more devs and corps cutting server and client side with the help of the MVVM or MVW patterns.
Backends in Java/Ruby/Phyton/PHP and frontends on Angular.js or Backbone.js
It is an eye opener to see how crafted those webapps can look like.
Your PHP code is just for data sending and data receiving. The whole (and nasty) HTML stuff is done with JS.
Databinding, controllers ... basically
- MVC - Model-View-Controller
- MVP - Model-View-Presenter
- MVVM - Model-View-ViewModel
- MVW / MV* - Model-View-Whatever
Take one and search for the proper client side framework.
RobertYank
New Member
just take a look
wlanboy
Content Contributer
If you want language that is useful in itself: Python. See my comment here: https://vpsboard.com/topic/7387-python-any-interest-in-group-learning/?do=findComment&comment=99913
If you want to stretch your mind: Haskell. I am learning it at the moment. Definitely hard to learn, but you learn a lot. It may not be something you will use, but I think it would make you a better programmer, and it is the most functional language that has any traction (you did mention functional). It is also as different from PHP as you can get (functional and strongly typed)
Scala, Clojure, and F# may be interesting. Erlang is probably too niche (good for extremely high reliability and uptime and scalability). Ocaml looks like its fading away slowly (but some people love it, and it is a gentler transition than Haskell to strongly typed functional languages).
If you want to stretch your mind: Haskell. I am learning it at the moment. Definitely hard to learn, but you learn a lot. It may not be something you will use, but I think it would make you a better programmer, and it is the most functional language that has any traction (you did mention functional). It is also as different from PHP as you can get (functional and strongly typed)
Scala, Clojure, and F# may be interesting. Erlang is probably too niche (good for extremely high reliability and uptime and scalability). Ocaml looks like its fading away slowly (but some people love it, and it is a gentler transition than Haskell to strongly typed functional languages).
Last edited by a moderator:
As someone who hasn't dedicated himself to studying a programming language but can limp around blindly on fools errands in most of them, I am really starting to dislike PHP. Wasted so much time last night searching for a simple workaround to array_combine's refusal to parse 'duplicate' keys (conflating two different arrays into one for the x and y axes on a graph where the keys were unpredictable and may have turned out similar at times). I don't see the absolute need for the key to be 'unique' in a situation where two arrays with unpredictable variables (market data) will merge, just let me combine the god damn key/value pairs!
Kind of hilarious responses here: http://stackoverflow.com/questions/9078770/php-merge-two-arrays-similar-to-array-combine-but-with-duplicate-keys
Kind of hilarious responses here: http://stackoverflow.com/questions/9078770/php-merge-two-arrays-similar-to-array-combine-but-with-duplicate-keys
Last edited by a moderator:
Munzy
Active Member
There are a lot of those in php, but there is also a ton of amazing things you can do with it. Personally I <3 php. I like more verbose syntaxs, unlike python.
Verbose is not good in itself. Overly terse languages can be difficult to read (like APL), but readability is good, and being concise is good if it improves readability. That is why I like Python.
IN this particular case a
As for PHP, this expresses my opinion of it better than I could: http://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/.
I'd very much recommend Node.js. Very easy to pick up (especially if you already know JS), generally decent documentation all around the ecosystem, package management that doesn't get in your way. Especially when wanting to learn something new (and gain a different perspective to solving problems), JS being half-functional is a very relevant thing. A bit more about that here and here.
Mind the inheritance model - Javascript is object-oriented, but not classically-inherited. There are no classes in JS (just a few things that pretend to be classes, with mixed results). Closures are great, and a lot more intuitive (and useful) than their PHP counterpart. Execution model for web stuff is considerably different - long-running process, rather than CGI-style like PHP does. Useful for many non-web things, though not for CPU-bound tasks, things that require extremely low latency (eg. HFT), or things that require arbitrary precision numbers (scientific, financial, ...).
Package management is a big one - nested local dependencies, so no version conflicts. As a result, you have many modular frameworks and libraries, and not so many monolithic ones. This is a good thing, but may be a little unusual when coming from PHP. Generally, you want to be looking for small modules that do one thing only, and just string them together. Definitely use promises.
Avoid MongoDB, though. It's unfortunately picked up a lot of traction in the Node.js community, but it's utter crap. Similar for Meteor, which relies on MongoDB, and Sails.
Plenty to learn, either way
Mind the inheritance model - Javascript is object-oriented, but not classically-inherited. There are no classes in JS (just a few things that pretend to be classes, with mixed results). Closures are great, and a lot more intuitive (and useful) than their PHP counterpart. Execution model for web stuff is considerably different - long-running process, rather than CGI-style like PHP does. Useful for many non-web things, though not for CPU-bound tasks, things that require extremely low latency (eg. HFT), or things that require arbitrary precision numbers (scientific, financial, ...).
Package management is a big one - nested local dependencies, so no version conflicts. As a result, you have many modular frameworks and libraries, and not so many monolithic ones. This is a good thing, but may be a little unusual when coming from PHP. Generally, you want to be looking for small modules that do one thing only, and just string them together. Definitely use promises.
Avoid MongoDB, though. It's unfortunately picked up a lot of traction in the Node.js community, but it's utter crap. Similar for Meteor, which relies on MongoDB, and Sails.
Plenty to learn, either way
Last edited by a moderator:
You are good in PHP. You could learn any CMS like Wordpress, Joomla, Magneto. You can speed up your rate of development by using these CMS. Learn any MVC framework like CakePHP. Frameworks are used in managing big projects.
If you want to learn more, you could learn J2EE. Some topic of J2EE are Core Java, JSP, Servlets, Java Beans. Some framework designed in JAVA are:
1. Struts 2 - Front end development.
2. Spring - Remove dependencies injection ( Removing the new operator for making objects)
3. Hibernate - IT manages your database using objects.
If you want to learn more, you could learn J2EE. Some topic of J2EE are Core Java, JSP, Servlets, Java Beans. Some framework designed in JAVA are:
1. Struts 2 - Front end development.
2. Spring - Remove dependencies injection ( Removing the new operator for making objects)
3. Hibernate - IT manages your database using objects.
risharde
Member
At university, they taught java and at the time, I was like... java?? Why java??? Ughhhh. In best case scenario, I would have chosen c++. Nevertheless, java is used for web apps... or you could make your own http server altogether. But you aren't limited there. You can code for android apps and even for other java enabled devices which are out there. Down to certain blu ray supports java. Its also 'supported' on a wide range of operating systems from windows to linux etc so you can easily port or not even have to port your programs.
Last edited by a moderator:
You don't need Java for any of those things, except for perhaps Blu-ray.
risharde
Member
Please elaborate... I code android apps in java so I am wondering what you mean
Go with C. Write a few simple programs and compare its performance to other languages. You'll learn to hate everything else. On a more practical level, it's good to have a grip of it before trying C++ no doubt.
Go for lower level if you're after deeper understanding, higher level if you're looking to monetise your learning, IMO. It seems all the cool kids use nodeJS nowadays, if you wish to script.
On a more practical level, it's good to have a grip of it before trying C++ no doubt.Go for lower level if you're after deeper understanding, higher level if you're looking to monetise your learning, IMO. It seems all the cool kids use nodeJS nowadays, if you wish to script.
Last edited by a moderator:
Nearly every modern language works cross-platform, many of them out of the box. Qt is a cross-platform solution for building graphical interfaces that has bindings for just about every language.
There are JS runtimes for mobile platforms as well - Cordova and PhoneGap come to mind. There's also TideKit, but they're evil. I've also seen some mobile runtimes for other languages in the past (eg. Python), but can't recall where to find them.
Building web application servers can be done in many modern languages, almost every one of them in a simpler manner than Java. Think Node.js, Go, Python, Ruby, and so on.
Games in C/C++/C# almost consistently perform better than their Java counterparts, with significantly lower system requirements. "Cross-platform" is a farce there, anyway - even if you didn't have to think about the OS you're going to be running on, you're still going to have to dig deep into GPU-specific implementations of OpenGL (as well as proprietary APIs) to reach anything near acceptable performance.
The idea of "Java-enabled devices" is more or less a pipedream nowadays. (Non-Android) Java phones are almost dead, IoT products generally run C or PHP, and the only "Java-enabled device" that most people will own nowadays is a Blu-ray player.
Frankly, the era of Java is over. And it just doesn't have any reason to make a comeback. The only reasons it's still in wide use, are that 1) it remains part of school curriculums, and 2) there is a large amount of legacy code running on it.
Last edited by a moderator:
Java is two different things:
1) Java the language. I do not like it much, personally
2) The platform: the JVM and the libraries.
There are a lot of JVM languages other than Java, some are JVM specific (Scala, Clojure, Ceylon...) while some are JVM implementations of languages that are well known for their non-JVM implementations (there are JVM implementations of almost every language we have discussed so far).
Other JVM languages give you access to Java's huge libraries and many be deployed just as though they were Java.
Java is mostly absent on consumer devices, but it is widely used on servers. The new JVM languages are a very good reason to use it as, unlike most new languages, they have huge libraries. Look at things like Hadoop, Spark, Cassandra, Lucene (Solr and Elasticsearch and others) - those are major applications in growth areas.
1) Java the language. I do not like it much, personally
2) The platform: the JVM and the libraries.
There are a lot of JVM languages other than Java, some are JVM specific (Scala, Clojure, Ceylon...) while some are JVM implementations of languages that are well known for their non-JVM implementations (there are JVM implementations of almost every language we have discussed so far).
Other JVM languages give you access to Java's huge libraries and many be deployed just as though they were Java.
Java is mostly absent on consumer devices, but it is widely used on servers. The new JVM languages are a very good reason to use it as, unlike most new languages, they have huge libraries. Look at things like Hadoop, Spark, Cassandra, Lucene (Solr and Elasticsearch and others) - those are major applications in growth areas.
wlanboy
Content Contributer
Don't forget Android.