High Level Languages that aren't shit

Do any exist? I've been looking for something like a high level C. The closest thing is probably Lua, but that's obviously unacceptable. Plus Lua is more C++ and less C. I liked Perl, but Perl 6 is not so good and has left a bad taste in my mouth.

IronPython maybe?
Just becouse python has OOP capabilities you don't need to use it.
With the module system you can use it as an excellent procedural language. And python is the language that hates modern syntax the most so it will probably fit you.

>>41
Python is a horrible language.

>>1
Learn Common Lisp. It's not very much like C but you won't regret it I guarantee.

>>42
Python is crap, Lisp is shit, but Common Lisp is truly diarrhoea.

>>34
There's more to life than programming. It is fun, but I don't think I would program if I had a week left to live. I'd probably walk around, and climb stuff or something.
You must be joking friend.

>>44
Go fuck an autistic nigger, faggot.

>>43
Haskell, OCaml and their ilk are part of a 45-year-old static-typing movement within academia to try to force people to model everything. Programmers hate that. These languages will never, ever enjoy any substantial commercial success, for the exact same reason the Semantic Web is a failure. You can't force people to provide metadata for everything they do. They'll hate you.

An important theoretical idea behind type systems is "soundness". Researchers love to go on about whether a type system is "sound" or not, and "unsound" type systems are considered bad. C++ and Java have "unsound" type systems. To date, the more "sound" a type system is, the more often it's wrong when you try to use it. This is half the reason that C++ and Java are so successful: they let you stop using the type system whenever it gets in your way. The other half of their success stems from the ability to create user-defined static types. The reason C++ and Java (particularly Java) have been so successful is that their type systems form a "let's not get any work done" playground for n00bs to spend time modeling things and telling themselves stories. You can't actually model everything; it's formally impossible and pragmatically a dead-end. But they try. And they tell their peers that you have to model everything or you're a Bad Citizen.

One very real technical problem with the forced-modeling approaches that static type systems are often "wrong". It may be hard to imagine, because by a certain definition they can't be "wrong": the code (or data) is programmatically checked to conform to whatever constraints are imposed by the type system. So the code or data always matches the type model. But the type system is "wrong" whenever it cannot match the intended computational model. Every time want to use multiple inheritance or mixins in Java's type system, Java is "wrong", because it can't do what you want. You have to take the most natural design and corrupt it to fit Java's view of the world.

Have you considered Pike?

It's basically just C with garbage collection, anonymous functions, and classes.

http://pike.ida.liu.se/

>>46
Sounds like a load of bull, not sure if troll. I haven't met a type system I couldn't subvert, and I only rarely provide type information to the MLs. I don't feel compelled or obligated to "model everything" either.

Personally I benefit from static typing. I don't demand soundness but I'm not a pussy about it either. I certainly don't cry about it when the compiler tells me my program is incorrect.

>>48
"correctness" is a buzzword.

>>49
"buzzword" is not jewish.

>>50
"jewish" is not correct.

OP, try Symta.

SYMTA> ($eval "ls {$@Data units} | map 'rhd")
_construction_site _corpse _destroyed_site alleria altar_of_storms armor2 armor3 arrow attack attack2 attack3 axe ballista ballista_bolt battleship berserker blizzard bloodlust boar board build build_advanced build_basic building cancel cannon cannon2 cannon3 cannon_big cannon_impact cannon_land castle catapult catapult_rock `cho'gall` church circle_of_power cross_green cross_red daemon daemon_attack danath dark_portal death_and_decay death_coil death_knight deathwing demolish dentarg die dragon dragon_breath dragon_roost dwarven_demolition_squad elven_archer elven_destroyer elven_lumber_mill exorcism explosion explosion_small eye_of_kilrogg eye_of_kilrogg_spell farm fire fire_big fire_small fireball fist flame_shield footman fortress giant_turtle gnomish_flying_machine gnomish_inventor gnomish_submarine goblin_alchemist goblin_sappers goblin_zeppelin gold_mine great_hall grom_hellscream grunt gryphon_aviary gryphon_hammer gryphon_rider `gul'dan` harvest haste haul_oil healing hellhog human_barracks human_blacksmith human_cannon_tower human_foundry human_guard_tower human_oil_platform human_refinery human_shipyard human_tanker human_transport human_watch_tower invisibility keep khadgar knight korgath_bladefist `kurdan_and_sky'ree` lightning lightning_impact lothar mage mage_tower missile morph move move_ship nil ogre ogre_juggernaught ogre_mage ogre_mound oil_patch orc_barracks orc_blacksmith orc_cannon_tower orc_foundry orc_guard_tower orc_oil_platform orc_refinery orc_shipyard orc_tanker orc_transport orc_watch_tower paladin peasant peasant_attack peasant_rebel peon peon_rebel pig_farm player polymorph producing raise_dead ranged2 ranged3 ranger remove repair ...

OP, try C++11

>>53
Ey said ey wants a language that isn't shit.

Fucking assembly better then c++, atleast no fucking types or nullpointer exception from hell, and no fucking inhertiance full retard chains.

>>35
Although I would like something with a nice plotting library if possible.
Python has a nice plotting library. But if you're all about the plotting and the matrices, try R or Matlab (/Octave).

Also,
Isn't it way better to get good at a few languages rather than learning dozens I don't really know well at all.
It's stupid to choose to specialize in a specific area before you even have an overview of the field. Having even very brief experience with different language designs should help you in your day-to-day programming in whatever language you choose. It also prevents some common types of tunnel vision.

>>26
http://www.youtube.com/watch?v=u4IdoBU1uKE watch this and cry, luafag

Python
http://img.0chan.ru/_python/src/13229608415879.png

>Dave Herman
>Grown mature person
>Starts to talk
>Furry avatar
>I heart JavaScript
IHBT

You want Go.

>>47
GC IS SHIT

>>57
Javascript
"the language it wants to be"
he menas Lua

ITT: retards think that high-level = high-level of abstraction

>>63
http://en.wikipedia.org/wiki/High-level_programming_language

>>64
To be fair wikipedia is talking about taking the machine details away while there are low-level languages that will give you powerful abstraction features. I have no idea which >>63 meant though.

check my high level dubs

>>56
Yeah, I'm already pretty good with MATLAB/Octave. Used it in college a lot. I worked with R a little bit, but again I was put off by some of the odd syntax.

I'll try out the suggestions in this thread (other than Python, I already tried it out). Also, why do you guys recommend Common Lisp? I was going to use Scheme so I could learn it with SICP.

>>63
implying high-level != high-level of abstraction

>>67
MATLAB!
Nice choice for girls.

>>69
u sure told em bro

Use C++, but not all the crazy and excessive features (which require crazy and excessive syntax).

>>71
IHBT!

>>69
Wasn't my choice, we used MATLAB in my college. Truth be told it's innate matrix math ability made a lot of our simulations really easy. That plus it had a lot of good visualization tools.

Bash (71 chars):

for f in *.png; do convert "$f" $(echo "$f" | sed 's/png$/jpg/'); done


Symta (53 chars):

fe (F:[@P [N {png}]] -> convert F [@P [N {jpg}]]) ls

C/C++/Java/C#

System.FileAccess.CDirectoryIterator System.FileAccess.openDirectory("./", "rw");
It.setFilterExpression("*.png");
while (It.notEnd()) {
  CString Src = It.getName();
  CString Dst = Src.copy();
  System.RegEx.replace(Dst, "$png", "jpg", System.RegEx.SingleOccurency);
  System.ImageLibrary.CImage Img;
  Img.loadPNG(Src);
  Img.saveJPG(Dst, System.ImageLibrary.Overwrite);
  It.advance();
}

>>74
Symta is shit.

>>71
What do you mean? “Write in C, compile with g++”?

>>77

He probably means, use classes, use one consistent version of inheritance, don't overdo it with multiple inheritance, and don't make template <template>  <template friend> Functor++ &*friend >>>>>>template< > << friends*&.

>>76
Doubt you're confident enough to judge.

>>78
This would be awesome if anyone managed to read.