Earlier quoted context omitted.
Ada users are called ... Ada users are never called :/
Lacelovers?
In France, they are called adaistes which seems to translate to adaist in english.
Fun facts about Rust's growing popularity
61–70 of 136 posts
Re: Fun facts about Rust's growing popularity
#62Well, a fun fact: there is nothing funny about that list :). It should have been called "Some facts about Rust's growing popularity". Now, my predicament: I love Rust's type system and tooling, but it's really hard to justify to myself the pain of writing correct Rust code (borrowing, lifetimes, etc.) when I know I can get almost the same effect by using a GC language + immutable messages. And I don't need that last…
You're overlooking that Rusts "solution"(borrowing, livetimes, etc. ) is not only solving the same problem that garbage collection tries to solve. Garbage collection is "only" solving the "memory resource problem". Rusts solution is a more general solution to the "general resource problem" .. like file handles, sockets and of course memory and besides that gives you tools to never get bitten by data races. Nothing (besides memory) garbage collection is helping you with. You have to mitigate those problems still in garbage collected languages like Swift, Go, Java, Python (to name a few) and various other solutions to help with this (try with resource, with statement, immutable message passing etc.) Rust tries to give you one solution "to rule them all". Is this better, worse? Idk – nobody does, the Rust people are trying to figure this out :) Nothing is carved in stone. And if you're more productive in another language you should use it! But you can only know by figuring this out for yourself. Rust works well for me – that's no guarantee that you have the same experience. Rust is still hard to learn and one needs to question himself if the effort in learning pays out at the end – it has for me, i guess/hope ;)
Re: Fun facts about Rust's growing popularity
#63Earlier quoted context omitted.
Please please please can we stop with the Rustacean/Gopher/etc crap? You don't need a cutesy label to identify that you use a tool. I enjoy Doctor Who (though it's been getting worse for the last 5 or so years) but I do NOT want to be called a Whovian. What's the first image that pops into your head when I say "Trekkie"? It's probably not someone with good health and hygiene, is it?
People like to label shit and themselves. No reason to fight it.
Sure there is a reason: it stops me from using Rust and Go.
I don't want to be part of a "movement".
Re: Fun facts about Rust's growing popularity
#64Well, a fun fact: there is nothing funny about that list :). It should have been called "Some facts about Rust's growing popularity". Now, my predicament: I love Rust's type system and tooling, but it's really hard to justify to myself the pain of writing correct Rust code (borrowing, lifetimes, etc.) when I know I can get almost the same effect by using a GC language + immutable messages. And I don't need that last…
I suggest taking a look at D[0] optional GC if you need to get that low level. A bit older than Rust.
[0]: https://dlang.org/
Re: Fun facts about Rust's growing popularity
#65Well, a fun fact: there is nothing funny about that list :). It should have been called "Some facts about Rust's growing popularity". Now, my predicament: I love Rust's type system and tooling, but it's really hard to justify to myself the pain of writing correct Rust code (borrowing, lifetimes, etc.) when I know I can get almost the same effect by using a GC language + immutable messages. And I don't need that last…
To me, Swift feels very similar to Rust only a lot simpler. Arc is also (imho) a nicer solution than a GC (though people have different opinions on that). Even better, with future versions, some of the features of Rust (i.e. lifetimes) will also come to Swift in an opt-in way. It is still a young language but fun to code in.
What's coding in Swift like outside of being on macOS? Is the tooling decent on Ubuntu / *NIX or Windows?
Re: Fun facts about Rust's growing popularity
#66Best fact: Rust users are apparently called Rustaceans. I did not know this, and have never seen this wonderful term before.
Please please please can we stop with the Rustacean/Gopher/etc crap? You don't need a cutesy label to identify that you use a tool. I enjoy Doctor Who (though it's been getting worse for the last 5 or so years) but I do NOT want to be called a Whovian. What's the first image that pops into your head when I say "Trekkie"? It's probably not someone with good health and hygiene, is it?
Check your hangups at the door man. I love being a gopher and a rustacean. I like being cute and having a cute name for myself and fellow community members. It's attitudes like this that created the massive gender divide in CS and it needs to end.
Re: Fun facts about Rust's growing popularity
#67Earlier quoted context omitted.
Pythonista makes me think of a leftist guerilla in a jungle with a beret and a machine gun.
This is fairly accurate bc they have a Chairman-for-life, and a schism between two groups, one of which denounces the other as revisionist.
Holy cow that is way too funny.
Re: Fun facts about Rust's growing popularity
#68Earlier quoted context omitted.
To me, Swift feels very similar to Rust only a lot simpler. Arc is also (imho) a nicer solution than a GC (though people have different opinions on that). Even better, with future versions, some of the features of Rust (i.e. lifetimes) will also come to Swift in an opt-in way. It is still a young language but fun to code in.
What's coding in Swift like outside of being on macOS? Is the tooling decent on Ubuntu / *NIX or Windows?
Tooling is all right, not as good as the cross platform tooling for something like Java, but still pretty good, especially given how recently Swift has had any non-hobbyist presence on non-Mac platforms.
The core language "just works" pretty pleasantly on other *nixes, I don't know about windows.
You end up missing Apple-specific libraries a lot, though. There are some packages making progress on that problem, but a comprehensive replacement for e.g. audio or graphics surfaces is a ways off, I think, if only because of the fragmentation that exists in those spaces on other platforms. Of course, Swift has that problem only a little worse than any other language that ships without an OS.
Re: Fun facts about Rust's growing popularity
#69Well, a fun fact: there is nothing funny about that list :). It should have been called "Some facts about Rust's growing popularity". Now, my predicament: I love Rust's type system and tooling, but it's really hard to justify to myself the pain of writing correct Rust code (borrowing, lifetimes, etc.) when I know I can get almost the same effect by using a GC language + immutable messages. And I don't need that last…
> So if you just want a native language with a good type system and a growing ecosystem, where do you go? Still Rust or something else?
Haskell?
Or on today's HN: https://news.ycombinator.com/item?id=15582429
Re: Fun facts about Rust's growing popularity
#70Well, a fun fact: there is nothing funny about that list :). It should have been called "Some facts about Rust's growing popularity". Now, my predicament: I love Rust's type system and tooling, but it's really hard to justify to myself the pain of writing correct Rust code (borrowing, lifetimes, etc.) when I know I can get almost the same effect by using a GC language + immutable messages. And I don't need that last…
You're overlooking that Rusts "solution"(borrowing, livetimes, etc. ) is not only solving the same problem that garbage collection tries to solve. Garbage collection is "only" solving the "memory resource problem". Rusts solution is a more general solution to the "general resource problem" .. like file handles, sockets and of course memory and besides that gives you tools to never get bitten by data races. Nothing (b…
>Rusts solution is a more general solution to the "general resource problem"
It's true. Ever since I got familiar with the ownership concept, I've taken to writing C# IDisposables with disposable member variables like this:
public MyObject(){
this.myResource = new DisposableResource();
this.ownsMyResource = true;
}
public MyObject(DisposableResource resourceToUseThatIDontOwn){
this.myResource = resourceToUseThatIDontOwn;
this.ownsMyResource = false;
}
public void Dispose(){
//not pictured: .NET's boilerplate dispose code
if(ownsMyResource) myResource.Dispose();
}