Can we discuss this shit? Apple’s fucking language for apps is becoming a serious contender to c

Can we discuss this shit? Appleā€™s fucking language for apps is becoming a serious contender to c

Attached: Swift vs C++ g++ - Which programs are f...r? | Computer Language Benchmarks Game.jpg (1275x3545, 446K)

>regex 75 seconds
jesus fucking christ

Jesus fucking christ how can a lang be so slow?

Attached: Screenshot from 2018-11-21 19-58-13.png (660x1670, 237K)

kek

>is becoming a serious contender to c
no it clearly isn't

>It takes 75 seconds to compute a Regex in Swift
top jej

Okay, from those numbers we can see that Swift:
a) usually uses more RAM
b) is usually slower
c) is sometimes slower while using more RAM

So, yeah, I guess it is a serious contender to C.

How quick is HolyC?

It is notoriously difficult to construct fair and representative language benchmarks.

this
language benchmarks are fucking retarded, it's not a linear measurement

>contender to C
>loses to C++ in all tests, except the first two
>74.94sec in the regex bench
(YOU)

There are some ways to try damage control without coming out as actual retards, you know.

I have no stake in this and don't use either language

Sure thing, Tim.

>Remove Arc memory manager and add pure pointer references as C.
Arc MM is slower than Java GC

>tfw aplel users have to wait half an hour for an average regex task which should only take 30 seconds

How show can a language be??

Attached: Screenshot_20181121-140633.png (1440x2560, 225K)

It's over. C is kill.

A MINUTE AND FIFTEEN SECONDS

>Double to triple the slowness sometimes
>37 times the slowness with regex

Swift is quite fast, but more in the Rust/Go/Java tier than directly comparable to C/C++.
The only built-in regex in swift is NSRegularExpression, which is based on the rather but very unicode savvy) ICU regex engine, and is further slowed further by Strings needing to be bridged to NSStrings to use it. Since C doesn't have a built-in regex engine, I suspect they're using PCRE, which is lightning fast and only optionally handles unicode to be even faster.
Now that swift Strings exclusively use UTF-8 buffers, they can be converted to C strings with (almost) no overhead. This means if you need a faster regex, you can include PCRE, and use it directly for basically equivalent performance.

That's finally it. C is done for.

> but more in the Rust
Nice try. Swift manages to 1-up C++ in one occasion but always gets beaten by Rust.

Attached: Screenshot_2018-11-22 Swift vs Rust - Which programs are faster Computer Language Benchmarks Game.pn (1478x4970, 385K)

>comparing rust to go and java

Quite. Rust should be in the trash on its own.

That's a pretty good sign this is a toy benchmarking site that rust shills have spent a lot of work gaming. Rust performance in general is nowhere near C/C++.

The funny shit is JavaScript and meme languages etc are faster than most languages in regex

Why do several of the faster runs use more memory too

Do you get paid to relentlessly spread fake news?

Attached: Screenshot_2018-11-22 Rust vs C gcc - Which programs are faster Computer Language Benchmarks Game.pn (1194x4776, 351K)

Almost all regex engines are written in C or C++, which is called into from the higher level language. So this is mostly just comparing a bunch of different C/C++ code + FFI overhead.

>applel shill BTFO
how does Rust vs C++ look?

Similar, with Rust winning in one more test.

>posts the exact same benchmarks gamified by the exact same shills

Attached: 1527676829786.png (500x475, 65K)

Attached: Screenshot from 2018-11-22 01-41-10.png (2264x1272, 434K)

kek

what the fuck is an nbody and a knucleotide anyway?

>framework benchmarks as a comparison of language speeds
Retard.

>mac screenshot
Well, that explains your retardation.

Attached: 1540569773155.png (1024x491, 288K)

>serious contender
>several seconds higher runtime than sepples and several times more memory

Rust, like most languages, is just on a different planet compared to C/C++. If you care about perf, you use a fast language, and Rust isn't it.

You tried this before, refer back to , and

Attached: Screenshot_2018-11-22 kostya benchmarks.png (758x3362, 213K)

Benchmarks are just lies and disinfo in a nice package with a bow on top. Only real programs can actually compare language speed, and Rust doesn't have any of those.

Sorry, honey facts don't care about your opinions.

Attached: 1538143303183.png (1578x1668, 187K)

>Only real programs can actually compare language speed, and Rust doesn't have any of those.
Basically every common unix utility has been rewritten in Rust by someone, and the Rust one is almost always faster

Attached: 48cad94ec45accea905360085551935c.png (1000x399, 49K)

Yeah it's usually much better, see ripgrep

I honestly thought it wasn't THAT bad.

Attached: 1539143915222.jpg (200x224, 9K)

Any improvement a Rust program makes over the equivalent C program can be ported to C, but not vice versa. Rust is incapable of expressing most of the control flow constructs that make C fast.

>parsing email with regex

Attached: 1520068266932.jpg (700x643, 63K)

Came here to post this

>get BTFO in every aspect with facts and proofs
>AnY ImPrOvEmEnT A RuSt pRoGrAm mAkEs oVeR ThE EqUiVaLeNt C pRoGrAm cAn bE PoRtEd tO C, bUt nOt vIcE VeRsA.
Sad and pathetic

go back to r*ddit, nigger

>except the first two
read the second one again

You should see python

lma0 look at this nigger

Attached: 1529043549735.png (769x733, 34K)

Hang yourself double digit IQ boomer

>name your poo language swift
>it's not actually swift
What did they mean by this?

Attached: ARCBTFO.png (818x986, 179K)

shortly about this site competence

Attached: cdcode.png (609x104, 9K)

>hasklel faggots can't even come up with a valid regex-redux output
kek

Haskellfags write dogshit code for get decent results in benchmark since start

That really isn't any more of a contender than say C#.

>C#
>contender
Go back to your 6 fps games

Why nothing matches the speed of C/C++ despite their old age? How comes nothing new beat them?

Rust

Attached: Screenshot_2018-11-22 kostya benchmarks.png (728x1486, 91K)

Heavy compiler optimizations for C/C++, most new languages choose GC,OOP,inmutable data,heavy concurrence,dynamic types,Virtual machine or interprete and other features instead of speed.

LLVM backend open new generation for high performance languages, Swift/Rust choose don't use GC or Manual memory just Zig begin same speed as C

Because they had decades and millions in funding to optimize compilers.

>LLVM backend open new generation for high performance languages, Swift/Rust choose don't use GC or Manual memory just Zig begin same speed as C
nigger wtf

Phoneposting

>sjwift

Attached: 1537988974829.jpg (2016x1210, 285K)