Programming in the future.
- Thread starter Vishnoo
- Start date
- Views 3,796
- Replies 53
I don't think any "major" languages have really died, due to the adoption cycle. Hype kicks off, some languages get enough hype to be adopted by enough stakeholders to make that language matter (i.e. C++, Java), then they go through cycles of popularity where they're suddenly the hottest shit, and others where there's an oversaturation of people who can use that language matched against fading adoption of that language.
You can still find high-paying jobs for languages like Ada and Cobol.
It's a bit like a fucked up version of the food chain.
You can still find high-paying jobs for languages like Ada and Cobol.
It's a bit like a fucked up version of the food chain.
Can you please help me with the C++ cycle.
Each ebook example programs differ from the other ebook example programs.I know that each is from different years ,so old and new.Which is the latest.
Ex; Void
<iostream>
<iostream.h> etc.
Each ebook example programs differ from the other ebook example programs.I know that each is from different years ,so old and new.Which is the latest.
Ex; Void
<iostream>
<iostream.h> etc.
I know C++
what do you mean
--------------------- MERGED ---------------------------
if you mean what tutorial to use then here
http://www.learncpp.com/
the above tutorial pretty much covers the entire C++ core language
you can choose to learn about the STL using a seperate guide after, but it's not neccesary to becoming a good C++ programmer
what do you mean
--------------------- MERGED ---------------------------
if you mean what tutorial to use then here
http://www.learncpp.com/
the above tutorial pretty much covers the entire C++ core language
you can choose to learn about the STL using a seperate guide after, but it's not neccesary to becoming a good C++ programmer
that one is outdated, and learncpp.com isn't that hard. I'm up to chapter 14 on there, so I should know what I'm talking about
IMO, C++ is only preferable if you need low level access to memory. C is only preferable for microprocessors. In most other cases, managed languages (like .Net languages) are preferable.
This really depends on what direction you want to go in. As for languages never becoming outdated, there's really no way of predicting that accurately. I mean back in the day people thought fortran was king and would never die and look what happened? Most people nowadays are like wtf is fortran!?
If you already know what you want to be able to achieve by programming, I can point you in the right direction, but without that info, nobody can really guide you. Do you want to do app/game development? Hardware development? Scientific prototyping? the list goes on and on
according to wikipedia:
so yeah, if you don't have a specific goal (like me), then just stick to C++ unless you find another language which you think you would like more
https://en.wikipedia.org/wiki/Programming_language
so yeah, if you don't have a specific goal (like me), then just stick to C++ unless you find another language which you think you would like more
While you can use C++ for anything, I would recommend C# for PC development, since it handles memory management for you, while it's incredibly eady to write memory leaks and such in C++. It's still possible in C#, but only in some circumstances.
After reading the replies:
I really want a programming language for gamemaking.
I think C++ would do it with some plugins or add-ons(I searched it before a year).
I think its Allego or something.
I really want a programming language for gamemaking.
I think C++ would do it with some plugins or add-ons(I searched it before a year).
I think its Allego or something.
Nobody programs their own games anymore, they use an engine off the shelf like Unity, XNA, or the Unreal Engine...
C++ and opengl will do the job well (you'll need to look for a sound library aswell, I'm not that sure myself)
avoid microsofts shitty platform-specific languages like DirectX or .NET
avoid microsofts shitty platform-specific languages like DirectX or .NET
Any help with these.Can you give me a link which also contains what requirements for it.
I have heard about this before.
That means,Is Programming language useless in future
I will be asking too much of questions. Its because i want to know that is it useful in future or not.
Last edited by Vishnoo,
And it was "not" with mono before it. I am not seeing the thing that will change that though.
c# is not a bad language as far as languages go and you can certainly make programs of nearly all flavours in it, I doubt we will ever see it outshine web development stuff or go for embedded stuff or go for phones worth having if you want more than a baseline phone.
I am not sure that for most purposes I could even suggest C# over python.
Until I have a star trek style "computer solve this abstract problem for me" style programming/AI/interface then programming as a distinct concept from maths, logic and what have you will not be useless. I would be pretty stunned to see anything close to that in the next 30 years. Thus if you are contemplating it as a career or useful skill to have in life then yeah it will be. It will change but I don't think we will see universal computer literacy during that time either -- they had their chance, they taught everybody microsoft word instead.
What will happen is it will become stratified even more than it is now. Take a person that has just gone through Java school and they will happily be able to make something that converts formats, speaks to a database to return a nice graph for someone, make a program that calculates something from a bunch of input data, formats something in a certain way... which is what the vast majority of computing is concerned with nowadays and what most people in the real world want. All the really fun stuff I know about algorithms, low level electronics, video encoding, cryptogaphy*, assembly programming, systems architecture, low level operating system concepts and so forth matters far less for most purposes. There is still room for it but once where every actually computery type would have been able to hang there then now it is not the case.
Or if you prefer being able to communicate in a language is pretty vital, being able to succinctly describe what an adverb is would be of less importance to most things.
I doubt computer programmers will be able to carve out a niche like lawyers and accountants have today where you are almost legally mandated, if not outright legally mandated, to have one in certain countries for a lot of purposes. My impression of US business is if you have an idea on the toilet then if you don't have a lawyer involved before you have wiped your arse then screwed up royally. Back on programmers then that is probably more due to a massive opposition to any kind of mandated professional competence thing like the lawyers have the bar exam.
*not so skilled programmers trying their hand at cryptography is the cause of a lot of failures there, however few seem sufficiently motivated to bother trying to restrict/govern its use like they do for certain machines, chemicals, biological agents and similar such things.
With the new standard platform, .Net can compile directly into native code, as opposed to MSIL that's compiled by the framework or Mono at runtime. Unlike Mono, the standard platform is designed for cross-platform usage, as opposed to being an after thought by a third party.
C# can be used for web development on the server side, so it's not a competitor or anything.
Python is an interpreted scripting language with a major split across major versions. Personally I think they should just kill off 2.X already since nobody's getting with the times, developing new things on a clearly outdated version. While I think outdated libraries are to blame for this, that and many other things like the lack of type safety, whitespace passing for end statements (reducing code readability), and the way some things like classes feel like hacks*, I'll recommend most things over python any day.
*To elaborate on these "hacks", here's some examples:
- Class functions have the instance as a parameter.
- Variable prefixes determine public/protected/private
- Properties are awkward
Similar threads
