[ 3 / biz / cgl / ck / diy / fa / g / ic / jp / lit / sci / tg / vr ] [ index / top / reports / report a bug ] [ 4plebs / archived.moe / rbt ]

Maintenance is complete! We got more disk space.
Become a Patron!

/g/ - Technology

View post   

[ Toggle deleted replies ]
File: 32 KB, 400x416, 1555362531908.jpg [View same] [iqdb] [saucenao] [google] [report]
70747722 No.70747722 [Reply] [Original] [archived.moe] [rbt]

the destruction of C is guaranteed, its a matter of when, not if

>> No.70747779

that gets the yikes from me

>> No.70747794

Sadly, C is not going to die. It's very much the perfect virus, never to be extinct.

>> No.70747818
File: 8 KB, 261x193, team rustlets.jpg [View same] [iqdb] [saucenao] [google] [report]

Imagine designing your logo after a bunch of eternal losers.

>> No.70747833

our war is holy

>> No.70748381

>confusing a bohr rutherford diagram with a gypsy cat and 2 lesbians
you'd be better suited on reddit

>> No.70748755

Until Rust compiles to .o object files that seamlessly allows an interface with C libraries, C will not die.

>> No.70748796

not memory safe

>> No.70750305

You know what else isn't memory safe??? Rawing your mom

>> No.70751401

it's easy to make a better C
it's hard to make a good language
Rust didn't

>> No.70751438

>it's easy to make a better C
Then why hasn't anyone done it yet?

>> No.70751461

Haha you sure got him bro XD XD

>> No.70751465

it has been, several times. but that doesn't guarantee adoption

>> No.70752270
File: 308 KB, 1156x1848, WHITE MALE POWA.jpg [View same] [iqdb] [saucenao] [google] [report]

white male programming = get job done

>> No.70752294

C will be destroyed eventually, at least in the sense that very little new code will be written in C compared to today. However, it will be at the hands of Zig or V or one of those other languages that are actually C replacements rather than C++ replacements.

>> No.70752303

It is memory safe if you take an amnestic beforehand,

>> No.70752314

Rust can't replace C. C is dead simple and blazing fucking fast, compiles within seconds. The only other language that can achieve that is Zig.

>> No.70752354

>dead simple
>blazing fast
>compiles within seconds
that's slow

>> No.70752367

C is not simple


maybe you're a fucking pro and you can guess all of these, but as someone who doesn't know C I don't understand why half of these are the way they are

What the fuck are you on? Last time I tried compiling a C project it took 45 minutes

>> No.70752377
File: 296 KB, 900x2648, rust.png [View same] [iqdb] [saucenao] [google] [report]

Fresh from yesterday's thread. Rust is unusable.

>> No.70752395



>> No.70752410

Zig is the most promising right now and I love the name, but there are others: V, Muon, D -betterC and others I can't remember right now. Maybe some day Mr. Blow will release Jai.

>> No.70752415

Thank you for making a screenshot that is now insanely wide.

>> No.70752424


>> No.70752433

Rust will be remembered as an important language that helped popularize linear types. But there are already new languages that have learned from Rust, https://github.com/carp-lang/Carp.

>> No.70752439

>a literal lisp

>> No.70752458

A lively linear Lisp.

>> No.70752460

anyday now....

>> No.70752465

It's still a lisp.

>> No.70752469

kek, try comparing the compile times of a 100kLOC Rust project to a 100kLOC C project.

>> No.70752471


>> No.70752475

>inb4 brainlet

>> No.70752482

I don't like it.

>> No.70752486

What do you dislike about it? I doubt you've read the paper.

>> No.70752496

Well, the paper is not about lisp in general. I did not read. I dislike the syntax of lisp. Those parens all over the place. Why are you even asking, surely you should know by now that the majority of programmer population dislikes that shit.

>> No.70752514

I'm just curious if there is anything thinking behind it or only a gut reaction to the parens. I am not a big fan, personally, but I don't see why people react to them like they're allergic.

>> No.70752520

of course you can't write that style of code in Rust

why would you try to fit a square peg in a round hole? Rust programming is a different style, you don't make a World struct and try to do everything with it. That's closer to OOP programming.

you wouldn't really have world.get().x

You can't just write Java/C++ in Rust and expect it to work

FWIW I wrote a Go (Baduk) AI in Rust and only had to Arc the board cache so it can be shared between threads

I didn't have any issues after I understood how Arc works

>> No.70752521

s/anything thinking/any thinking/

>> No.70752522

A gut reaction to code that looks like unreadable mess.

>> No.70752527

Please explain it to all the brainlets that pollute C and C++ threads spamming their rust bullshit asking people to convert.

>> No.70752530

Weak. Spend three days with it, and your perception will change.

>> No.70752534

Maybe. But I do not want to spend three days with it.

>> No.70752554

>Last time I tried compiling a C project it took 45 minutes
The Linux kernel, one of the largest C programs you'll encounter, compiles significantly quicker than that on normal desktop hardware.

>> No.70752560

That doesn't make it fast. There is no reason for million loc projects should not compile in few milliseconds. Computers are fast enough to enable that.

>> No.70752569

wew lads, that's my daily dose of cringe.

>> No.70752577

Is there an idiomatic ECS implementation in Rust?

>> No.70752580

compare incremental builds and touch a header file

once you touch a header file in C, the changes can ripple through the entire codebase, which means you may need to recompile EVERYTHING

when you touch a file in Rust, the compiler only has to recompile things that can potentially be affected

Sure, the final --release build may be slower by like 50%, but you usually make a lot of incremental and debug builds just to check whether your shit is working correctly at all

>> No.70752593

>and touch a header file
I had so many issues with this because build tool was implemented by idiot who did not use dynamic dependencies generated by compiler.
Also: C linkage is not type-safe. One more point for name mangling.

>> No.70752609
File: 189 KB, 850x1188, D5W9ypzXkAAFLKv.jpg [View same] [iqdb] [saucenao] [google] [report]

>of course you can't write that style of code in Rust
I know you still have your penis attached, but your passive aggressive HRT induced psychosis is showing.
>you don't make a World struct and try to do everything with it. That's closer to OOP programming.
Which maps perfectly to game programming.
Kindly fuck yourself.

>> No.70752614

>by like 50%
No, it's WAY fucking longer than that. 1 to 2 magnitudes more than that.
Because don't forget: you're not simply compiling your program, but all of your dependencies and all of their dependencies too.

The header file "rebuild propagation" is hardly an issue because C builds so quickly to begin with. Maybe with fuckhueg programs, it's more of an issue, but for most real world programs, we're talking less than 2 seconds.

>> No.70752617

there's a shitload of them


>> No.70752624

>non-lexical lifetimes block your path
>cyclic data structures blocks your path

>> No.70752626

>Weak. Spend three days with it, and your perception will change.
Spend three days in the sewer and your perception will change.

>> No.70752629

Speaking from experience, not really.

>> No.70752632


>> No.70752634

>C linkage is not type-safe
Unless your build system is brain-dead retarded, this is never an issue. Most good build systems make this sort of shit impossible.

>> No.70752645
File: 534 KB, 763x719, 009.png [View same] [iqdb] [saucenao] [google] [report]

>tfw Rustfags have to defend sewers to justify using their language

>> No.70752648

woah nice, now let's wait for linus to rewrite his linux in rust

>> No.70752652

most but posix make and not-so-old versions of eclipse
also assumes programmer doesn't ignore implicit declarations warnings

>> No.70752655

actually that's the benefit of Rust, you can cache the builds of the dependencies, so every time you recompile the program, even in --release you only compile the crate you changed

Wine takes 45 minutes to build and NOTHING is cached, it's literal fucking autism

oh what's that? your program didn't work in Wine? MAKE ANOTHER CHANGE AND WAIT 45 MORE MINUTES

whereas a recompile (not fresh build) in Rust takes a minute since the dependencies are already built, you only need to build the project

of course a Wine project in Rust would be broken up into several crates for this exact reason: it makes sense to break up your project into some independent parts so you can recompile them separately when working on the codebase

Name (leave empty)
Comment (leave empty)
Password [?]Password used for file deletion.