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

List of failed C replacements

Name: Anonymous 2016-07-21 6:16

1.Rust
2.D
3.C++
4.C#
5.Java
Its 2016, why C is still so popular and used in mainstream project?

Name: Anonymous 2016-07-21 7:32

6.Go
7.Vala
8.Javascript
9.Alef
A.Cyclone
B.PHP
C.Objective-C

Why are all C-based languages failures?

Name: Anonymous 2016-07-21 7:42

>>1
C is good for low-level systems programming so it's used for that a lot. it also allows for optimizations for vidya. for eveyrything else it's just momentum - people use it because they know it and they know it because everyone uses it.
>>2
how is javascript or php a 'C replacement'? their syntax is C-like (kind of) but their purpose is much different: client-side (js) and server-side (php) scripting for web. also, they're shit.

Name: Anonymous 2016-07-21 10:07

>>2
The Jews want C and Lisp. JavaScript is a Lisp that looks like C. It is the ultimate Jew.

Name: Anonymous 2016-07-21 16:34

Node.js makes Javascript the "acceptable C"

Name: Anonymous 2016-07-21 17:37

why doesn't anyone try just improving C a little bit (like the boring c idea), rather than 'fixing' it by making it into a childrens toy

Name: Anonymous 2016-07-21 19:24

>>3
Javascript is getting to be a C replacement if you want that level of single-threaded speed, but it's certainly not a systems-level programming language.

Name: Anonymous 2016-07-22 6:36

>>6
C, like many other things, is a legacy system. they keep fixing it but those fixes are never enough, and because they want to keep backwards compatibility they don't remove the bad shit (or, if they do, it takes them years to do so) - they just give you a better alternative and nicely ask you not to use the old shit. it's appealing to try to design something with the same power, familiar syntax and more elegance but as it turns out it's easier said than done.

Name: Anonymous 2016-07-22 7:18

1.C replacement that could replace C in Linux kernel.
basically allowing some unsafe low-level memory operations and inline assembler.
2.Shill it everywhere, like Rust/Go. Crucial.
3.Tons of "Dumb troglodyte guide to C+ functoid-lambda-closures in 30 minutes". Purge academic speak and use simplest terms for everything(so don't actually call it "functoid-lambda-closures", it would be something like import Sparkles to do Jingleloop). It has to appeal to masses.
4.Replace all major C/C++ libraries(Libraries are like "muh videogames require Windows" for programmers)
5.Win high-profile benchmarks. Haskell has dedicated autists that write code and patch the compiler to win benchmarks.

Name: Anonymous 2016-07-22 7:29

>>9
Forgot the common mistake is "FFI to C code will reduce the need to write libs/code/programs" is gesture of obsolescence.
The "C replacement" must replace all of C.
If (C ecosystem can survive without X) and (X ecosystem can't survive without C FFI), programmers will choose the safer option with the larger ecosystem. However when X ecosystem can compete with C ecosystem with its own libraries/OSes/programs, people will start switching due C many flaws(which X fixes in some way).
This means alot of code needs to be ported.
C FFI is a tempting because it seems to be easy way out: in reality its only a temporary crutch that cannot be relied on.
Every piece of C code that is relied on is contributing to C survival and ecosystemic dominance.

Name: Anonymous 2016-07-22 7:50

(this space left intentionally blank)

Name: Anonymous 2016-07-22 10:05

The reason all of these meme languages fail is because they try to force you into the cuck shed of "safe" programming. But it's all a big lie as you are still able to write shitty terrible software, with bloat, memory leaks and unhandled exceptions leaving data in inconsistent state.

Enough with the cuckoldery. The future comes in four parts:

- Updated version of C. Think C with lambdas (based off of Obj-C Blocks), task-oriented threading library, OpenCL vector/simd and half-float types and a few other minor additions. These are considered for the next version of C to be standardized in 2020 or 2021, if you look at the ISO JTC1/SC22/WG14 website.
- Static code analyzers, validation checkers and proofers separate from the core language that ensure all of the shit that "safe" programming languages claim, without you being stuck out in the cuck shed.
- DSLs with Scheme/Lisp-like syntax for higher-level or special-purpose programming. S-expressions for human readable structured data.
- Machine Learning. Simpler programs that discover the optimal solutions to more complex programming problems are able to scale way beyond what a human mind is capable of handling in a single lifetime.

Name: Anonymous 2016-07-22 10:32

Name: Anonymous 2016-07-22 10:37

>>13
Clang also supports Obj-C blocks in regular C. That's the reason they're standardizing it.

Name: Anonymous 2016-07-22 15:14

>>12
Look mom, I said cuck again!

Name: Anonymous 2016-07-22 15:41

>>15
cuck

Name: Mom 2016-07-22 15:42

>>15
Please don't talk about your father like that.

Name: Anonymous 2016-07-22 21:43

>>14
Wow, I didn't know about that.

That seems like it would make C a lot more bearable.

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