Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

C++ in Linux or Windows

Name: Anonymous 2012-01-11 1:20

>inb4 Google, I looked and couldn't find what I'm asking about

Is it better to code C++ programs in Linux or Windows? I'm new to this. I'm just learning and don't want to start off on the wrong track. I'm using Linux btw.

Couldn't you just take the same code written on Linux and compile it on Windows? The only difference would be certain OS-specific differences like window managers, etc., which could somewhat easily be fixed, right? If so, what's the big deal about porting programs to and from Linux and Windows? What am I missing?

If you also have some brotips on better languages than C++, please share them. I want to be able to make all sorts of programs; efficiency is important. My ideal language is one that can do "anything" so that I can specialize in a master race language. Tl;dr Please confirm whether C++ is god tier.

Name: 5 2012-01-11 11:55

Let's put it another way...

Why should we have to provide arguments for you guys to not use C++? >>4,5 just provides arguments on why it should not be considered `god tier'.

A lot of other languages compile to fast code, have C++'s features and none its shortcomings. Some provide truly powerful abstractions that are absolute headaches to emulate in C++. Many languages also satisfy this and have truly safe typing, some of them are used in industry...

The `feature' of being able to mix C and C++ is a subjective matter, it could be seen in the same lens that mixing HTML and PHP is good. Static and dynamic linking and FFI models have been created for a reason. This may mean that there has been a lack of separation of concerns, and now theres low level and "high level" jizzed all over the place in a 50KLOC app. What if one wants to, or worse, HAS TO (by contract, etc) port to a platform that does not have (complete) C++ compilers but obviously has support for ANSI C? Even a Lisp + C project would have been easier to retrofit, as the C is fine, and the Lisp will need to macro'd to an intermediate form and then compiled from there. How are you going to transform the same sugared up UI "layer" (if its been layered to begin with) source code written in C++, write your own translator parser? on the probably most difficult to parse syntax after PL/I?

People latch onto C++ by peer consensus only. The academic concensus OTOH for C++ is particularly dim, even C hasn't gotten this much scorn.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List