/tech/ - Technology★

you mean like we've already been doing forever in golang, with closures?

>>800858

>golang

>zero cost futures

wtf do closures have to do with futures???????

also golang is garbage collected garbage without generics. kill yourself

>>800862

https://medium.com/strava-engineering/futures-promises-in-the-land-of-golang-1453f4807945

http://www.golangpatterns.info/concurrency/futures

etc.

On generics -

Golang doesn't need generics. Generics suck.

Rust has an absolute shit package manager, is still unstable and on top of that is managed by a bunch of retarded leftists.

It's safe to say that C++ will stay the best language.

does rust have any GUI frameworks yet?

>I think one of the best ways to get comfortable with using a library is to look at how it works internally: often API design can seem bizarre or impenetrable and it's only when you put yourself in the shoes of the library author that you can really understand why it was designed that way.

lol

>>800863

this is not zero cost though

>Golang doesn't need generics. Generics suck.

stockholm syndrome

>>800864

thanks for the salt, m8

>>800865

http://gtk-rs.org/

>>800867

not an argument

You know, when you insult people and call the things they like shit, they're more than likely going to hunker down and not budge.

Whether you're getting paid for this or just trolling I don't care, I'm tired of seeing these fucking threads.

>>800893

>waaah dont hurt my feefees!

lol. you sure you belong here?

>>800842 (OP)

wtf i love rust now!

check it memory (un)safe fags

https://play.rust-lang.org/?gist=11b8cb9088b0f8c36048a54ee293f537

>>800842 (OP)

I'm going to keep using C++ because it's good enough and my name isn't Rusty Chucklefuck.

>>800915

>reposting my oc

i feel honored. here, have a segfault in safe rust:

https://play.rust-lang.org/?gist=50e18bbb0512dfc13cf3c9edaeade188&version=stable

Comparing Rust to C is retarded, C is a much simpler (as in tinier) langage. Its obvious adversary is C++.

>>800925

>Comparing Rust to C is retarded

why?

>>800931

because rust at first need to follow his own assumptions

after that they can think about competing with c/c++

>>800915

>>800920

>>800935

it's just a bug bro. this will be fixed soon(tm).

>>800937

maybe it's a new unannounced feature

>>800935

So, basically, safety is FIRST, and you should KYS for not putting it first, but they're using a meme language that is barely a few years old, filled with "bugs" and "trivial errors" that never get solved because the progressive stack gives them less priority.

I think no one would be using this mess if it wasn't for sjw evangelizing.

>>800980

This kinda shows that for Rust users there's something more important than safety, just as everyone else was telling them. For rust users its politics.

>>800993

Top kek

>>800896

>"criticism of my techniques means you're butthurt"

Alright, now I know for sure.

>>800931

Comparing Rust and C is like comparing C++ and C: stupid.

>>800901

explain this one rustfags

>>800993

lel

>>800993

my sides

>>800863

Go isn't even a competitor to Rust, but it's still total shit. Go has zero metaprogramming facilities at all. Why would you bother with it when there are so many better languages that have surfaced in the last decade? As if Ken Thompson didn't do enough damage by creating C and Unix, he puts the capstone on his career with this turdlang. Go is destined to be the next Pajeet language. If Go has one saving feature, however, it's that Go is slightly preferable to Java, and that's not saying much.

Also, its mascot looks stupid.

>>800842 (OP)

shit syntax.

SJW infestation and a CoC.

NOT memory-safe. re-use after implicit destruction.

> Inline macro assembly. Memory safe. Oh you adorable, naive, ivory-tower-meets-reality head trauma victims.

Never change faggots. Endless source of fun.

>>801034

>As if Ken Thompson didn't do enough damage by creating C and Unix

LARPer detected.

>>800869

You are right, they aren't particularly zero-cost. I do wonder how they compare upon execution, and how they compare in readability.

Generics aren't that important though.

Just learn to use state machines you fucking babbies. How many abstractions-of-the-month are you going to go through before you just git gud.

>>800980

The thing is, once Rust starts to get really adopted by dumbass corporations, a fuckton of bugs will pop up in the safety checks like mushrooms after rain. Literally nobody has ever used this in a big project (I'm talking BIG. do not come at me with redox OS, it's 5M lines of code whereas LibreOffice is 7M. It's not mature enough.) and when they do they're gonna drop it like it's hot.

>>801048

>muh state machines

>>800993

>C/C++

>C/C++

>C/C++

C++ is shit. C is not shit, except for its compilers, which are only shit due to pressures from C++. They are two different languages. One of them popped fully-formed out of the forehead of Zeus and has grown but a little over time; the other is a shambling horror created from sewn-together animated corpses.

Fuck this. I'd rather use Forth, but I'm going to learn Rust just so that I can deliver something relatively manager-friendly that people won't try to hack on with their fucking C++ editor modes.

>>801084

rust lang pro/con

>very low runtime overhead

<slow compiler. can't use source as binary. and they promote this as a web language? I'll take never being able to distinguish malware from legitimate site files for $200, Alex. And they promote this as a systems language? Not for admins: Perl may be slower but at least I can always tell what it does

>uses Serbia's .rs TLD, /pol/ approved

<docs written by fucking commies

-has memory something-or-other

>not Go

<not stable yet

>steampunk is cool

<will contract at least nine STDs from act of scheduling attendance at any Rust conference

all in all... nevermind. People saying "C/C++" is no reason to go to a gaybar. How about Lua for a normie alternative? https://www.activestate.com has a cool howling-wolf icon for it.

>>801084

>the other is a shambling horror created from sewn-together animated corpses.

Which is which?

>The earlier compiler does not know about structures at all: the string "struct" does not appear anywhere. The second tape has a compiler that does implement structures in a way that begins to approach their current meaning. Their declaration syntax seems to use () instead of {}, but . and -> for specifying members of a structure itself and members of a pointed-to structure are both there.

>Neither compiler yet handled the general declaration syntax of today or even K&R I, with its compound declarators like the one in int **ipp; . The compilers have not yet evolved the notion of compounding of type constructors ("array of pointers to functions", for example). These would appear, though, by 5th or 6th edition Unix (say 1975), as described (in Postscript) in the C manual a couple of years after these versions.

>Instead, pointer declarations were written in the style int ip[];. A fossil from this era survives even in modern C, where the notation can be used in declarations of arguments. On the other hand, the later of the two does accept the * notation, even though it doesn't use it. (Evolving compilers written in their own language are careful not to take advantage of their own latest features.)

> It's interesting to note that the earlier compiler has a commented-out preparation for a "long" keyword; the later one takes over its slot for "struct." Implementation of long was a few years away.

>Aside from their small size, perhaps the most striking thing about these programs is their primitive construction, particularly the many constants strewn throughout; they are used for names of tokens, for example. This is because the preprocessor didn't exist at the time.

>harder than C++, more billable hours

>takes forever to compile even small projects, more billable hours

<faggy SV companies like it

>faggy SV companies have a lot of money and don't care if you bill them for doing nothing all day

>>800993

Holy shit this is great. Fukken saved.

>>801001

>reddit spacing

Alright, now I know for sure.

>>801002

>comparing C++ and C is stupid

why?

>>801043

>Generics aren't that important though

stockholm syndrome

>>801048

rust futures are state machines. it's like you didn't even read the links and still posted

>>801068

>5M LOC isn't big

ok

>>801092

>slow compiler

the upcoming incremental compilation will be fucking rad. way better designed than anything else

>they promote this as a web language

they dont

>not stable yet

??????????

>>800993

>using -Wall and -pedantic will make c/c++ memory and thread safe

lel. thanks for this amazing product of butthurt

>>801136

It's like you can't even grasp I'm telling you to not use the abstraction. If you write everything as a bare state machine it's compatible with everything and works the same in every language. If you ever have to work on the glue of a polyglot project you'll learn the hard way why what I'm saying is important.

>>801143

>larping

btw rust futures are bare state machines

>>801147

epic. im a #cmissile now. who needs a package manager anyways? just use single header libraries.

>>801151

>HAHAHA NPM IS RETARDED

wow. much insight. many amazing

here is the thing though: this wouldn't have happend with cargo

>>801152

Oh so you're a smart Rust shill.

Can you explain why people hate Java and Perl for their shitty syntax but when Rust does it it's okay?

>>801156

no i cant explain other peoples retardations

>>801160

Then explain your own.

>>801162

i dont know which. please specify

>>800842 (OP)

If it's so great why do people feel the urge to write a tl;dr infomercial thread every 24 hours?

>>800842 (OP)

Rust is useless to me until they renounce current CoC and implement sane rules.

As religious person I cannot agree to their current CoC because it implies that gender exists. Because I cannot agree to their CoC I am not allowed to join any official Rust places like (IRC) chats, code repositories and forums.

Can someone recommend me good book (or website) about writing safe C code?

>>801160

So if you say Rust syntax is fine then you also are okay with Perl/Java syntax?

>>801172

no im not okay with perl syntax. it is an abomination. but that is not the reason why i dont use it.

>>801174

>MUH SYNTAX

you are just as retarded as anti rust shills, cya

>>801176

lol

>>801149

>futures are bare state machines

That's pretty dumb even for /tech/.

>>801189

rust futures are zero cost/overhead abstractions around bare state machines. that is what makes it superior to everything else.

there is literally nothing dumb about this

>>801191

To help you stop being dumb, consider what would happen should you mix rust and C where rust uses futures and C uses state machines. How easy would it be to tie the two together.

>but it's zero cost!

Literally irrelevant and missing the point entirely.

>rust thread

>no steve klabnik LARPer appeared yet

something is going wrong here…

>>801036

>NOT memory-safe. re-use after implicit destruction.

this is only an implementation bug which will be solved. the language is just fine.

>>801195

>mixing rust and c

wtf????? rust completely replaces c. ther is literally no need.

>>801196

i stopped tripfagging

>>801196

I gave him such epic shit he said he would stop and did. I was surprised when it worked. If he starts back up, I'll start making his life hell again. I'm a NEET with plenty of time to kill and nothing better to do.

>>801198

>ther is literally no need

You're going to love the real world where integration is the vast majority of the work programmers do.

>>801199

i stopped because i became bored of tripfagging as an antifa cuck. i am still shitting up this board with rust threads though :^)

i cant leave, as i am the only rust shill on /tech/

>>801199

>>801202

Are both of you NEETs?

Are both of you the same person?

>>801205

We are definitely not the same person

>>801202

So you went back to being a regular cuck?

>>801202

The very moment even a half-working Z compiler becomes available, Rust will stop being relevant forever.

>>801295

rust also isn't memory safe: https://8ch.net/tech/res/798797.html

>>801296

That's a compiler bug tho, that should not compile since foo was already moved into bar.

It's like saying C is not reliable since you found an ICE in GCC.

>>801329

https://github.com/rust-lang/rust/issues/29723

>Nov 9, 2015

RUSTSHILLS ON SUICIDE WATCH

>>801344

i was merely pretending to be reddit though :^)

>>801349

HAHAHA EPIC!!! LMAO M8

can you please post some more funny images?

please post funny cat images. you will get many upvotes good sir

>>801335

>Two years to solve a compiler error

Worrying yes, but does not refute my point.

>>801361

How about you leave and the meme stays?

>>801373

hi. i'm steve klabnik. by the rust core developers own admission, borrowck is a fatally flawed mess

>>801375

how about i continue shilling rust on this board and you choke to death on my tiny antifa cock???????

>>801198

rust doesn't replace c in use cases where performance primes over safety. C code is also faster to produce, so kinda you'll have to fight against the limits your language imposes you that might not always be the faster ones to produce "safe code" where safety isn't even a concern.

>Inb4 "But such scenario doesn't exist, durr durr"

It does.

>>801390

>what is assembly

Did anyone know they have official yt channel?

https://www.youtube.com/channel/UCaYhcUwRBNscFNUKTjgPFiA/videos

>>801417

>what is assembly

<C code is also faster to produce

Which still applies in comparison to assembly.

>>801417

If you don't need safety, and write 90% of your code in a buttfuck language with ugly sintax because safety, then you have a mental problem.

>>801570

>implying c is faster than rust

where is your proof though?

>>801575

>muh syntax

opinion discarded

>>801615

http://benchmarksgame.alioth.debian.org/u64q/rust.html

>>801617

>#include <emmintrin.h>

just wait until simd is added to rust's std

https://github.com/rust-lang-nursery/stdsimd

>>801623

I fucking hate SJWs but the way I thought about the name was: it's between hardware and the outside world; rust on the surface of hardware.

>>801623

>reddit spacing

>>801674

>>801623

This is why C++ will stay the superior language. It is not governed by a bunch of whiny faggots.

>>801376

Steve, does your mom know that you're using her laptop again? You better go back to your basement before she beats you with the belt again.

>>801623

> being too retarded to do a simple search

https://en.wikipedia.org/wiki/Rust_(programming_language)#History

The fact is that the language is really go for all sorts of fields and being infested with SJWs doesn't mean much. You don't have to interact with the community to use the product. You can't argue against Rust when it comes to it's technical merits and your political argument is useless because you can just not contact with people you disagree with.

If I'd told you to hang yourself you'd probably do it.

>>801674

If you take a look online there's nothing but praise for the community. You can adopt the language and just not interact with them. The CoC does not bind you unless you contribute.

>>801901

>>801900

antisaged

>>801034

>Go has zero metaprogramming facilities at all

What about the AST package and `go generate`?

>>801929

>go generate

>>801932

What about it?

>>801933

>lol no generics

>>801935

I don't know what you're getting at.

>>801940

>The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.

>It must be familiar, roughly C-like. Programmers working at Google are early in their careers and are most familiar with procedural languages, particularly from the C family. The need to get programmers productive quickly in a new language means that the language cannot be too radical.

>>801942

Go doesn't need generics, and neither do you. Generics aren't a go-like solution, there's a reason interfaces are brilliant.

>>801901

What do smart programmers use then?

>inb4 java/rust

>>801901

Rust is shit. C++ is shit

http://harmful.cat-v.org/software/c++/linus

>>801952

Compiled: C, Ada, Fortran

Interpreted: Perl, Lisps

>>801900

>If you take a look online there's nothing but praise for the community.

Yeah, but that doesn't change the fact that it's community rules go against my personal beliefs and morality. I'm a stickler for rules and regulations and follow them to the letter. When the rules exclude me I keep away.

>You can adopt the language and just not interact with them.

That's not really how things work. Do you use a programming language where you're not involved at some level with it's community? I sure don't. I'm very active in all communities in the languages I use. That's a huge benefit both for yourself and for others.

>The CoC does not bind you unless you contribute.

I like contributing though. It's one of the things that give me joy when it comes to programming. Not all of us are cubicle dungeon pajeets who just wants nose to grindstone. And it doesn't say the rules apply only to contributions. It's defined as interaction with the community at all.

>>801942

What does that have to do with metaprogramming?

>>801990

metaprogramming is too hard. gophers cant understand it

>>801900

>technical merits

Are you referring to the unscalable compile times, the shit syntax, the false promise of safety or the annoying effort-wasting borrow checker?

>>801901

>uses a language designed by hipsters and at the mercy of a bunch of social justice lunatics

>>801948

>there's a reason interfaces are brilliant

>>801942 already gave you the reason: "Googlers" (the audience for Go) are too dumb to understand generics, and therefore a half-baked type erasure solution ("interfaces") is the right thing to have.

>>801960

COMPILED/INTERPRETED IS NOT A PROPERTY OF A LANGUAGE, DUMBASS

>>801674

That's not how it works. The software license allows you to use it even if you constantly send them your shitposting, even shit like death threats, etc., it doesn't matter at all.

Using a language doesn't mean being involved in its development.

Even if you sometimes want to send them your pull requests, is it too hard to simply not speak too much irrelevant shit? And if you don't like someone in particular, it's easy to ignore them. If you want, you can go as far as filtering their output with userscript in your browser or something.

>>802446

Yeah, and? That doesn't change anything.

>>802453

try to turn on your brain before posting, please

>>802457

Try to think of something relevant before posting.

>>802049

>muh compile times

https://github.com/rust-lang/rust/pull/44901

just got merged

>muh syntax

that is an opinion not an argument

>false promise of safety

do you mean this? >>798797

it's just a bug bro. it will be fixed soon

>annoying effort-wasting borrow checker

lol. are you mad that rust rejected your buggy code? maybe you should program in python

>>802520

> it will be fixed soon

Wasn't that bug discovered about year ago?

>>802049

>interfaces

>half-baked

t. LARPer

>>802524

The first year they waited for MIR to land, then the second year they realized it's harder to fix than it looks.

They probably need this:

https://github.com/rust-lang/rfcs/blob/db66dd2039b10b759084079827d85aba1c26256c/active/0000-seme-regions.md

But seems like a neverever scenario

>>802552

soon

https://github.com/rust-lang/rust/issues/44928

D btfos rust anyday in terms of productivity and is as good in performance

>>802578

true but people hate gc

>>802584

No, autistic people hate gc. An experienced programmer knows when memory management needs to be done by hand, and when it's better to save development time by letting the gc handle it.

>>802612

You forgot about LARPers.

>>802584

GC is hated because awful languages like java use it.

>>802612

RAII is also good sometimes

>>802612

There is already shitload of languages with GC, without D. D doesn't cover any new use cases.

And having GC without memory safety is kinda odd, why would anyone pick D if there is Java (and Kotlin, Scala, etc.)?

>>801929

Still waiting for someone to address this.

>>802890

see >>801942

metaprogramming is too hard. gophers cant understand it

>>802912

>Context-free snippet of text

>some sort of insight into the ability of Go programmers

All your snippet says is "we need people to be using something that's c-like enough for anyone to just dive right in", not a commentary on the language and it's features

>>802912

That's not a valid argument, Go supports the means for metaprogramming, even if your statement was true it wouldn't change this. People have written about it publicly and there are projects that use it, so obviously someone can understand it enough to utilize it.

Metaprogramming is pure cancer. Did you learn nothing from the hell C++ developers went through?

>>802919

I'm not sure who you're directing this at but I'm only proving the ability is there, not that it's a good concept.

>>802917

>>802918

>text substitution and reflection is proper metaprogramming

>this is what gophers actually believe

go was made for retards like you. leave my rust thread immediately

>>802924

I don't think you have any real arguments, I don't see the point in any of your recent posts or your language.

>>802925

>gopher doesnt want to admit that his language sucks

>n-n-n-no argument!!!!!!!

lol

>make language without generics

>add special function to make generic lists and maps

BRUTALLY PRACTICAL

gophers are actually THIS retarded

>>802929

>google makes a language specifically for retards because you can pay them less

>retards go full gopher

>>802927

>>802926

Not sure what kind of response you're expecting but you're not doing a good job of selling me on Rust if that is your aim. This kind of behaviour seems typical amongst Rust advocates, it really does seem childish and/or fake, in either case it's negative, either the members are stunted mentally or they're trying to fit in with a certain demographic just to have more of a social appeal without having any merit on their own. This whole project seems like a mess at every level except concept. An actual shame.

>>802931

>MAXIMUM DAMAGE CONTROL

found the triggered gopher

>>802933

Besides repeating the same nickname what point are you trying to convey? What is your goal? If you don't word it clearly I'll never know, you can;t just be purely aggressive or foolish and expect me to understand what you mean.

A good starting point would be forming some argument convincing me that metaprogramming is a good concept and how Rust facilitates good metaprogramming, then we can disuses it.

Focusing on a seperate language and expressing your opinins on it don't really have any bearing towards Rust, even if we both agreed that Go is a bad langage it does not make Rust a good one, more importantly, showing that Go has a specific feature doesn't make it inherently good either.

If you can't talk about this kind of thing properly I'm going to ignore you from now on, I have no problem discussion it with you if you're this invested in the project.

>>802934

>moving the goalpost

>strawmanning

>hurr durr you stupid im going to ignore you. i won xdddddd

this isnt about rust, but about go. this isnt about whether metaprogramming is good or not. this is about go sucking at metaprogramming.

kys gopher

if err != nil {
    return err;
}

LOL

>>802936

What's the point in arguing that Go is bad? Why not make a thread devoted to Go, why post about it in the Rust thread?

You keep saying "gopher" as if it has any meaning, primarily I am a C++ user, people say Rust is competing with it, I'm here to hear their argument.

>>802937

>rust thread

please show me a single post in this thread that actually is about rust futures

protip: kys gopher

>>802937

Stop replying to him.

>>802936

Go does not suck at metaprogramming (which is demonstrably bad).

>>802940

>gopher cant handle that his favorite language sucks at everything

lol

>>802939

It's fun to make Rust advocates look like actual children. Have you been reading this garbage? most jej

>>802942

>i was merely pretending to be retarded

gophers are so pathetic tbh

>>802943

That's not what I'm implying, even if you're being insincere you should make your jokes work. At no point did I imply I wasne't being serious, just that your arguments are typical for Rust supporters, they all act like this, anonymous or otherwise. I know you think memes are the hip young thing but that kind of shit is only going to work on github and /g/, don't bring that shit here, faggot.

>>802944

>gopher gets dubs

fugg :DDDDDDDDDDDD

I tried learning haskell once but dropped it because of the syntax.

Rust is worse

>>802946

>in a ball pit

ohmyfuck.jpg

bump

>>803938

the bear suit is kiwikig

>>803938

Does anyone know the origin of this meme? When I found it I was told it was some kind of elder meme.

>>803977

It's just a music video for Still Life by Oneohtrix Point Never, the video is done by someone named "betamax" I think.

>>802932

Using your logic Java should be less popular than C#, and it isn't by a wide margin.

Face it, MS doesn't have the influence it did 20 years ago.

>>804130

C# is way more popular than Java in new fields. Java's basically a legacy language now, like what COBOL was in the late '80s. All those Unity games for example are C#.

>>803938

It's distressing that I only recognize three hentai pics from the quickly flashing sequence.

I don't see what the point of golang is. It can't do systems work because of the GC, the binaries are too bloated to replace python in embedded, it can't easily work as a replacement for scripting languages like lua due to the only JIT being a hack, and it's not got the wide support of Java. I can't think of a single niche where it's the best tech. Do you know of one? And no, "muh syntax" is irrelevant.

>>804143

Don't you think that whoever would have to deal with me would suffer psychological trauma? It's like you normalfags have no concept of compassion whatsoever.

>>804151

I think you misunderstood me.

I meant, go look at more hentai until you can identify it all.

>>804152

Ah, apologies. Yes, I'm sort of in process of catching up.

>>804142

>Do you know of one?

Yes, it's the perfect language for dumb subhuman "Googlers" (>>801942), just like how Rust exists to provide a safe-space for insecure Mozillafags who want to play systems programmer. Overall, and similarly to Java, these hipster languages exist to allow bad programmers to program without fucking everything up.

>>804139

Anon I'm all for /v/ but who the fuck cares about vidya usage seriously.

>Java is legacy language now

>Literally the only way to do anything in android

>There are more android phones than desktop/notebook computers

Yeah nah, Google pulls the strings now, Microsoft is just living of contracts and office to make money.

>>804142

Instead of shitposting about a langauge you've never tried - try writing some Go.

>It can't do systems work because of the GC

All operating systems have garbage collection, however they are more like services than subroutines or automatic like in golang. It could be done anyhow, Go's GC is not like the GC of old.

>the binaries are too bloated to replace python in embedded

You say that, but embedded python is dying anyway. It's already bloated and slow, and requires an interpreter installed on the system. A good Go program designed for an embedded context would perform better than an equivalent python program - I do not have an idea on how size would compare.

>it can't easily work as a replacement for scripting languages like lua due to the only JIT being a hack

Coming from an embedded Lua developer, it very much can (except for filesize) but it's not designed to do that. JIT is not a hack.

>it's not got the wide support of Java

Not a real argument.

The problem I think you have is you forget, "systems programming" is not normal development. C is great. Go is like C, except everything works the way you expect it to, and everything's a lot more evolved - multiple returns, interfaces, methods, the := operator... Go is an improvement to C in every way, unless you're writing some serious low-level kernel code (and you're aiming for pure performance and 100% godlike control).

“I like a lot of the design decisions they made in the [Go] language. Basically, I like all of them.” -- Martin Odersky, creator of Scala

“I think it goes back to the Unix C traditions back to basics and other compiled languages and it remedies other deficiencies in C, I don’t think C++ was an improvement but I do think Go is a definite improvement on C and we’ve got Kernighan and things in the background there and obviously they’ve got wonderful experience on building languages. It’s very nicely engineered and actually when it even came out impressive documentation, and all this stuff that you need. Even when it first came out it has a level of maturity that you would think would actually have been there for many years, so it is very impressive actually.” -- Joe Armstrong, co-inventor of Erlang

“[Go] just works. I don’t have any problems, which is the reason I am writing this post. I have used C++, C, and script languages for many years, but started to use Go at about a year ago. I am surprised how efficient and effective it is for me. When I design a new algorithm, it just works at the first attempt surprisingly often. Suddenly, programming is much more fun. I can’t say for sure why, but I think it is a combination of many factors.” -- Lars Pensjö creator of LPMud and the LPC programming language.

“Go is an awesome language and, as this talk illustrates, we aren’t competing with Go; Go and Rust have totally different goals and Rob Pike’s languages were quite the influence on Rust.” -- pcwalton of the Rust Mozilla team

“The complexity of C++ (even more complexity has been added in the new C++), and the resulting impact on productivity, is no longer justified. All the hoops that the C++ programmer had to jump through in order to use a C-compatible language make no sense anymore -- they’re just a waste of time and effort. Now, Go makes much more sense for the class of problems that C++ was originally intended to solve.” – Bruce Eckel, author and founding member of the ANSI/ISO C++ standard committee.

>>804235

>make new languages to replace c++

>both of them have worse syntax than c++

BRAVO

>>804390

This is a real issue for me, and the main reason I reject Rust. It replaces a bad syntax with a worse one.

>>804155

>muh bad programmers

t. LARPer

>>804235

>go

lol no generics. why would i use go over literally any other gc'ed language?

>>804401

>muh syntax

thanks for shitting up my rust thread. i will just have to make a new thread soon

>>804390

Go has the second nicest syntax out of any language I've used. C++ somehow made C's syntax worse, why would they change literally anything?

>>804409

>thanks for shitting up my rust thread. i will just have to make a new thread soon

I'll see you there bb.

>>804446

>That's not a fault of NPM

it was a fault of npm. "the cloud" has nothing to do with it.

>Commit your damn dependencies

are you saying that one should add the source of all dependencies to the git repo?

this will kill your repo: http://npm.anvaka.com/#/view/2d/browserify

>>804450

http://npm.anvaka.com/#/view/2d/angular.js-server

this is a good browser benchmark.

>>804446

>unironically defending npm

https://www.bleepingcomputer.com/news/security/52-percent-of-all-javascript-npm-packages-could-have-been-hacked-via-weak-credentials/

kys javashit monkey

>>804409

>>muh bad programmers

>t. LARPer

What's the matter? Are you insecure about something?

>N..No one is a bad programmer!!! Everyone is equal, everyone gets a gold star sticker!

t. delusional rust shitcoder

>>804489

>>N..No one is a bad programmer!!! Everyone is equal, everyone gets a gold star sticker!

thats not even close to what i was saying. but there is no point in arguing with a LARPer

>>801623

>Not to mention Rust is filled with SJWs. It's filled with SJWs who can't code, but "contribute" to the project by shilling for it and writing bullshit like CoC.

Meanwhile they leave other projects alone. Genius!

>>804235

Arguing that Go is better than C is like arguing that grasshoppers taste better than tree bark.

I started reading through Rust's documentation.

>The Character Type

>So far we’ve only worked with numbers, but Rust supports letters too. Rust’s char type is the language’s most primitive alphabetic type, and the following code shows one way to use it:

>Filename: src/main.rs

fn main() {
   let c = 'z';
   let z = 'ℤ';
   let heart_eyed_cat = '😻';
}

I am not convinced.

>>805117

>reddit spacing

>>805118

>his only retort is misapplied accusations of leddit spacing

I thought about squashing things a bit, but that's how it was laid out in the docs.

>>805120

>retort

to what??????

>I thought about squashing things a bit, but that's how it was laid out in the docs.

that's not an excuse. at least you didn't use reddit spacing this time.

>>805121

t.phone fag

>>805122

>no argument

???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

https://blog.rust-lang.org/2017/10/12/Rust-1.21.html

>>804493

>successfully extract the essence of the delusional rust shitcoder

<n..no that's not what I was saying you big meanie!!!!! you're just a LARPer! LARPerLARPerLARPerLARPermuhsafetyLARPerLARPerLARPer

>>805167

tasty salt

bump XDDDDDD

>>803986

betamax is the title of the artwork

>>802446

Yes it is; don't pretend that every language is equally easy to interpret at run time.

Ummm.... C++ has had futures since 2011...

>>805709

what a retard

>where is my cat, ls, ...

https://github.com/uutils/coreutils

https://github.com/redox-os/coreutils

>where is my grep

https://github.com/BurntSushi/ripgrep/

>where is my kernel

https://github.com/redox-os

>>805895

are they zero cost though?

>>805898

of courshe, everything in c++ is zero cost

>>805898

>magic perfect compiler

>memesafety trumps safety-by-design

>netscape lusers vs theo

>>806103

i dont understand what you are trying to say.

try rewriting your comment in english.

>>805898

how you are defining "zero cost"?

is rust(including futures) "zero cost"?

>>806816

Yes, any rust code takes up zero CPU cycles.

Anti-Rust shills BTFO

>>806816

how about you read the op of the thread that literally is about rust futures??????????

Rust CoC is a deal breaker for anybody with a functioning ethical system.

>>806849

>>>/4gag/

>>806861

>>/rebbit/

>>806825

As we know rust is working differently than docs describe it, so I'm asking

Take "memory safety" as example

>>807104

>rustc having a bug means the docs are lying

lol. you anti-rust shills are really grasping at straws.

>>807118

>main target of this "programming language" is memory safety

>lack of memory safety for 2 years(probably more) and nobody cares

yes, docs are definitely lying

>>807247

>screeching autistically because of a bug

t. LARPer

>>807263

>no rational arguments

>random insults

>>807275

>no rational arguments

>>800901

But I like Perl.

>>800842 (OP)

how is this new?

lazy evaluation is old af

>>807324

nice strawman. i never said anything about it being new

>Starting from version 1.20.0+dfsg1-1 (i.e. the previous version) the Debian packages of rustc no longer fail their build if any tests fail. In other words, some tests might have failed when building this and future versions of the package. This due to lack of maintainer time to investigate failures.

>Many previous test failures were reported to upstream and did not receive a timely response, suggesting the failures were not important. I was then forced to patch out the test to make the build proceed, so several tests were being ignored in practise anyway.

>This brings the Debian package in line with the Fedora package which also ignores all test failures. (Many other distributions don't run tests at all.)

>>808862

>rust is literally Compiled Ruby

>>808862

what tests is he talking about and why does he thinks ignoring failures is ok?

>>809067

Rust's automated tests often fail but Team Rust doesn't give a shit. SJW activism is more important to them than things like test failures in their 'safe' language, or memory corruption bugs going ignored in their bugtracker.

Debian is better engineered and runs package-provided automated tests as part of the deb build process by policy and failures prevent the packages from getting built. The maintainer does care and is obviously pretty pissed about it and is calling out the Rust devs and the sorry state of things where they're just leaving distros like Debian and Fedora to deal with their buggy software with no support. Since no one is helping but everyone is whining for the package, he's taken the same course as Fedora and just issued a 'buyer beware' and let it be built with failed tests

>>809067

>why does he thinks ignoring failures is ok?

He obviously doesn't think that, the rust devs think that, since they published a release version of their compiler that has failing tests.

It's not a package maintainers responsibility to fix broken code, that's what upstream is supposed to do. So he reported it to them and they obviously didn't care.

You can take a look at all the failing tests here:

https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=amd64&ver=1.20.0%2Bdfsg1-2&stamp=1508596936&raw=0

They all end with "... ignored"

>>809071

>Team Rust doesn't give a shit

i dont believe you tbh. can you give me a link to where >>808862 is from?

https://brson.github.io/2017/07/10/how-rust-is-tested

>>809076

https://packages.debian.org/sid/main/rustc

It's in the README.Debian in the debian.tar.xz source package.

>>809075

>>809079

well after looking around a bit i cant find any evidence for their claims. maybe if they included links to some of the bugreports i could verify their claims, but all i see is "hurr durr ignoring test failures is okay because we cant be bothered to do anything about it and fedora is doing the same LOL".

i looked at the rust packaging git repo and only found a few references to test failures due to outdated build dependencies.

>>809086

These are all the issues opened by the package maintainer:

https://github.com/rust-lang/rust/issues/created_by/infinity0

>14 open

>23 closed

>>809086

You type like a retarded child and have to be spoonfed the most basic info like where to find build logs (https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=amd64&ver=1.20.0%2Bdfsg1-2&stamp=1508596936&raw=0 faggot) to see the tests that have to be ignored yet are sure Rust is perfect. You're a fine example of the cult of Rust.

>>809094

>Many previous test failures were reported to upstream and did not receive a timely response

>only two dont have replies

thanks for proving me right. seems like the debian rust packaging team just doesnt care.

>>809095

i was no asking for the build log. i was asking for the bugreports that "did not receive a timely response".

>>809099

Devs generally contact each other's camps directly, not via filing bugs.

>>809099

>did not receive a timely response

>open for several months

>>809104

so what you are saying is that they didnt file bug reports and then got butthurt because nobody responded?

>>809105

yes????? they did receive responses.

>>809106

You're adorably naive about development.

>>809109

>not an argument

ok

>>809108

You know, a useless response might as well be no response at all.

Or do you consider "Works on my machine xD" a valid response when asking for help?

>>809112

>"Works on my machine xD"

source?

>requires you to use their dumb package manager (step aside emacs, now languages are operating systems) to be productive

>muh "safety" (restrictions)

>takes half a second to a whole second to compile a "hello world" program

>IO is retarded

>STD::LIB::IO::BBQ:::::: FUCK I LOVE COLONS

>pritnln!

>!

shit language, sticking with C