|
I thought you could fix anything with a hammer and/or some duct tape... 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
Naaahh! Hammer and duct tape only fix 87.3% of problems. Throw in chewing gum and beer (NOT at the same time!) to get the other 24.7%. Ooops, too much beer.
|
|
|
|
|
Member 12502619 wrote: how many programming languages do i have to know in order to make an effective app,like lets say a game or a social media app
Two different things, I'll pick the latter.
Web front-end:
Javascript
HTML (not a language, but you have to know it)
Web back-end:
The blue pill: C#
The red pill (poison): Python / Ruby / Javascript, et al.
But more importantly, for both front and back ends, you are going to have to choose from a variety of frameworks. Almost always jQuery for the front end, plus whatever you want to do with making it look better than plain vanilla HTML controls. Then there's a variety of MVC frameworks to choose from, like Angular, Backbone, etc.
On the back-end, you have the same nightmare. Do you roll your own web server, use ASP.NET, Razor, or if you chose the red pill, buy into the framework, like Django, Ruby on Rails, node.js, respectively.
It's a mess.
As to combining different types of languages together, sure, you can call C++ with C#, you can call C with Python/Ruby/Javascript extensions, if you want a desktop app that runs a web app, you can use CefSharp to write stuff in C# and talk to Javascript, and vice-versa.
It's a mess.
Marc
|
|
|
|
|
wow,well detailed,thanks man 
|
|
|
|
|
Marc Clifton wrote: The red pill (poison)
... but but ... it allows to escape the Matrix[^] !
|
|
|
|
|
Compared to pure desktop development, web development is an ugly beast. If your main goal is to learn programming and not to develop some web app then I'd suggest to start with desktop development and then work your way from there.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
to be honest, you're VERY far from serious application development if you ask these type of questions.
Of course, nothing prevents you from learning. There's much more to "programming" than you would think.
my article[^] explains this to some extend. Rarely is a large application a one man job. Asking how many languages you need to know is irrelevant. You´ll need to understand the concepts, you'll need to build up experience and you'll need to learn how to design systems properly. And when you have all that knowledge and know-how, you'll need time to do it.
So basically you'll need to learn to crawl before you walk. Start with hello world and move on to more difficult algorithms, IO systems, web services, database design, patterns, best practices. When you get more experienced the languages will come as needed: C#, C++, java, python, javascript and "secundary" languages like HTML, XML and SQL. (and more)
You'll also learn the best tools to use for each of these.
Grab a book, follow courses and get your hands dirty from basic towards advanced and things will become clear quickly.
hope this helps.
|
|
|
|
|
Learn 1 programming language and the theory. This will allow you to write in any language without learning them. Eventually you'll learn all languages you need from using them.
P.S. Learn to use google and to read reference manuals.
P.P.S. Learn English before any programming language.
|
|
|
|
|
If you want to make a game I would recommend C# language with the Unity engine which are easy and very strong.Imagine some of the best selling games are made with this combo.For an android application I would recommend java which is very similar to C# .
|
|
|
|
|
How many programming languages do you need to know to make an effective app?
One.
Why? Because developing a piece of software that is "effective" and "intuitive" for the user(s) isn't a result of the language used, but rather how well you have communicated with your user(s) as to what their needs are, and how to implement and accomplish those needs. You can make a great application using for instance 10 different languages and frameworks, and still end up with something that the user(s) hate, because it doesn't do what they need it to do.
That said - most modern applications use more than a single language in their development. For instance, web applications typically require the developer to know at least one core language (like python, php, ruby, etc), and then stuff like javascript, css, html, and a whole host of other bits and pieces.
Whereas native mobile application development typically only require one to know a single language, plus the OS of the platform (Java and Android, ObjectiveC or Swift and iOS) - but of course, if you want to target both Android and iOS - you need to know all of that. Or - go another route with a framework that works on both (I personally like Ansca Corona - which uses Lua for the coding part).
Application development for other scenarios might use multiple languages - for instance, game development will typically have a "core language" for the main game engine (usually C++), but then for other pieces (game logic and such) will be developed using a "scripting language" (which may be compiled in to the final game, or exist outside of it as modules) - which could also be the same as the core language, but is generally something like Lua or some other simpler language. This allows for a team to be broken up into those handling the hard-core underbelly of the game (graphics and such), versus the game logic, which is higher level (and so can be done in a simpler to use language). This kind of structure also improves workflow and other issues that can arise during a project.
Now - as far as your question on "combining two different languages together" - to an extent, that's possible - depending on the language and the compiler. For instance, many C/C++ compilers support the ability to add "inline assembler" to the code - this used to be something widely used; today, while I am certain it is still used, it probably isn't done as heavily as it once was. In theory, something like this could be done for any language, and allow you to combine different languages all in a single source code file - but generally it isn't done, as it would be a complete mess. Instead, what is more typical is a "separation of concerns" - where one part of the application is coded and compiled in one language, but if it needs to access something coded in another language, an API is involved (which may mean a wrapper around a library is created for the language calling the API - or some other method is used to invoke methods within the targeted API - like RESTful or JSON API calling conventions for remote web services).
There's also another possibility - rarely used, and is more a curiosity currently under research (and may stay that way - but the possibilities are intriguing): It's called Domain Specific Language (DSL).
Essentially, at the core - it's a programming language specifically crafted to solve a particular problem domain, typically for the application needed by the user. So - for instance - if you were making an application for use in a bakery, you would first craft a programming language specifically for the tasks and domain of baking (whatever that would ultimately mean). In one way, it "silos" software development - so now it is possible for there to be a multitude of programming languages (as well as highly proprietary ones - only known to a single business entity) - this can be bad from a maintenance and hiring standpoint.
But on the other side, by having a language tightly coupled to the needs of the user (and the problem domain), that language can be crafted so that problems within that domain are easier to solve, among other possible advantages. There isn't many "real-world" examples I can think of - the closest I can think of off the top of my head would be stuff like MATLAB, Octave, Mathematica, R (all for stats and mathematics) - as well as certain graphical programming languages like LABview. To an extent, there are also a few industrial process "languages"; ones for industrial robot programming, as well as things like g-code (CNC) and "ladder-logic" (for programmable logic controllers - though today, ladder-logic is mostly old-school, and instead other languages are used, but some are still compiled to a ladder-logic format).
One interesting example of a DSL system (which I've wanted to find time to play with) is JetBrains Meta Programming System (MPS) [^]
Essentially, it's an IDE and programming system that allows you to create (and mix) custom DSLs while you code. In other words, you can create your DSL as your write your code (!) - and create specific DSLs for each area of your code (need a particular DSL just for 3D graphics - go for it - but you need something else for your business logic? Again - create it right there). At least, that's how I understand it from a high level (I may be wrong). I personally like the concept of a DSL - but I like the concept of creating your own programming language on the fly as you code much more intriguing (I can also see it being fraught with pitfalls, too).
Anyhow - JetBrains MPS is something you and others might find interesting, if you haven't seen it before. It's also open source [^] which makes it just that much more intriguing to look into.
|
|
|
|
|
How many programming languages do you need to know to make an effective app?
One.
Why? Because developing a piece of software that is "effective" and "intuitive" for the user(s) isn't a result of the language used, but rather how well you have communicated with your user(s) as to what their needs are, and how to implement and accomplish those needs. You can make a great application using for instance 10 different languages and frameworks, and still end up with something that the user(s) hate, because it doesn't do what they need it to do.
That said - most modern applications use more than a single language in their development. For instance, web applications typically require the developer to know at least one core language (like python, php, ruby, etc), and then stuff like javascript, css, html, and a whole host of other bits and pieces.
Whereas native mobile application development typically only require one to know a single language, plus the OS of the platform (Java and Android, ObjectiveC or Swift and iOS) - but of course, if you want to target both Android and iOS - you need to know all of that. Or - go another route with a framework that works on both (I personally like Ansca Corona - which uses Lua for the coding part).
Application development for other scenarios might use multiple languages - for instance, game development will typically have a "core language" for the main game engine (usually C++), but then for other pieces (game logic and such) will be developed using a "scripting language" (which may be compiled in to the final game, or exist outside of it as modules) - which could also be the same as the core language, but is generally something like Lua or some other simpler language. This allows for a team to be broken up into those handling the hard-core underbelly of the game (graphics and such), versus the game logic, which is higher level (and so can be done in a simpler to use language). This kind of structure also improves workflow and other issues that can arise during a project.
Now - as far as your question on "combining two different languages together" - to an extent, that's possible - depending on the language and the compiler. For instance, many C/C++ compilers support the ability to add "inline assembler" to the code - this used to be something widely used; today, while I am certain it is still used, it probably isn't done as heavily as it once was. In theory, something like this could be done for any language, and allow you to combine different languages all in a single source code file - but generally it isn't done, as it would be a complete mess. Instead, what is more typical is a "separation of concerns" - where one part of the application is coded and compiled in one language, but if it needs to access something coded in another language, an API is involved (which may mean a wrapper around a library is created for the language calling the API - or some other method is used to invoke methods within the targeted API - like RESTful or JSON API calling conventions for remote web services).
There's also another possibility - rarely used, and is more a curiosity currently under research (and may stay that way - but the possibilities are intriguing): It's called Domain Specific Language (DSL).
Essentially, at the core - it's a programming language specifically crafted to solve a particular problem domain, typically for the application needed by the user. So - for instance - if you were making an application for use in a bakery, you would first craft a programming language specifically for the tasks and domain of baking (whatever that would ultimately mean). In one way, it "silos" software development - so now it is possible for there to be a multitude of programming languages (as well as highly proprietary ones - only known to a single business entity) - this can be bad from a maintenance and hiring standpoint.
But on the other side, by having a language tightly coupled to the needs of the user (and the problem domain), that language can be crafted so that problems within that domain are easier to solve, among other possible advantages. There isn't many "real-world" examples I can think of - the closest I can think of off the top of my head would be stuff like MATLAB, Octave, Mathematica, R (all for stats and mathematics) - as well as certain graphical programming languages like LABview. To an extent, there are also a few industrial process "languages"; ones for industrial robot programming, as well as things like g-code (CNC) and "ladder-logic" (for programmable logic controllers - though today, ladder-logic is mostly old-school, and instead other languages are used, but some are still compiled to a ladder-logic format).
One interesting example of a DSL system (which I've wanted to find time to play with) is JetBrains Meta Programming System (MPS) [^]
Essentially, it's an IDE and programming system that allows you to create (and mix) custom DSLs while you code. In other words, you can create your DSL as your write your code (!) - and create specific DSLs for each area of your code (need a particular DSL just for 3D graphics - go for it - but you need something else for your business logic? Again - create it right there). At least, that's how I understand it from a high level (I may be wrong). I personally like the concept of a DSL - but I like the concept of creating your own programming language on the fly as you code much more intriguing (I can also see it being fraught with pitfalls, too).
Anyhow - JetBrains MPS is something you and others might find interesting, if you haven't seen it before. It's also open source [^] which makes it just that much more intriguing to look into.
|
|
|
|
|
Thanks to everyone who helped out with last Friday's QA kerfuffle[^]. Particularly to @Dave-Kreskowiak for spotting the obvious problem!
Based on a comment from the OP, it sounds like he's still got ransomware. Unfortunately, I can't reply, because he's deleted all of his questions. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Did you go to the May Day Fayre this year?
|
|
|
|
|
Yes. Camped out in the beer tent next to the jazz band as always.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I will try to get down there for a jar with you one day!
|
|
|
|
|
Thank you. He's probably off to SO now to piss everyone off over there by telling them his machine isn't infected.
|
|
|
|
|
|
...I use to hate it when my Mum would tell me I had to get off the computer. Now most days I'm at work I wish she would come in and say it again.
|
|
|
|
|
So? Stop wanking and get out there and mow the lawn, you lazy, no-good asshat! Or there'll be no dessert for you tonight!
How's that? Close enough?
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
|
Bro?
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
|
|
|
|
|
...and then I would go to bed and read a book, and then she came back to say I have to turn off the light...
...and then I would not, and then my father would remove the fuse for the upstairs lights...
...and then I would crawl under the sheets and go on reading using a flashlight...
Eh !
|
|
|
|
|
... we didn't have computers.
I would stay up programming an HP-65[^]
I still have it somewhere in a box in the storage shed.
Marc
|
|
|
|
|
£€₡ $₭ლ₡₹ ৳¥£ (3,5,3)
modified 4-May-16 6:02am.
|
|
|
|
|
Groundhog Day?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
