Hi everyone,
Have you guys already had any cool projects and want to share with us?
I just quickly made a site here where I would love to showcase your Rust project. http://builtwithrust.com/.
Thanks all,
Announcing Rust 1.0 Alpha
241–250 of 255 posts
Re: Announcing Rust 1.0 Alpha
#242Hi everyone,
Have you guys already had any cool projects and want to share with us?
I just quickly made a site here where I would love to showcase your Rust project. http://builtwithrust.com/.
Thanks all,
Re: Announcing Rust 1.0 Alpha
#243Earlier quoted context omitted.
> I think the stdlib is not the way to go. Give me an example of any ecosystem where the standard library is the defacto best solution? Python, Go, C++'s STL, Java SDK, to name a few. They might not be 100% perfect, but they are good and reliable, and always there for you. Hunting the latest "best" library that gets abandoned after a year (like in Javascript and Ruby often happens, and also Go too) gets old quickly.…
> Java SDK Hardly. See Joda Time (it only took 10 years for java.time to catch up) and Apache Commons (the situation is much better now, but who hasn't turned to Apache Commons due to shortcomings in Java's standard library?). In any case, I definitely agree with the frustrations of trying to find libraries for Ruby.
Again, people have seem to miss the point I was making.
I wrote that those batteries "might not be 100% perfect" -- and as a Java programmer back in the '00s, I know the specific problem points with Java time that Joda tried to solve (btw, it has inspired the time lib in the latest SDKs IIRC).
The thing is, the JDK APIs, with all their issues have been a genuine force in Java adoption, and something every Java programmer relies on. Of course there'll be some pain points, but it's nothing like having to hunt for a Collections or DB abstraction or String manipulation or XML etc lib each and every time you start a project.
Having an official batteries API doesn't preclude you from using external libs (like Joda) when they are better -- whereas not having one is a genuine loss.
If I have turned to Apache Commons that was overwhelmingly for things MISSING from the SDK, not for things the SDK already did.
And don't get me started on the Commons code quality, with BS reinventions of the wheel, lame FactoryFactoryProxyFactorySingletonFlyweightFacades and the like, and code that was blisfully ignorant of enconding issues...
Re: Announcing Rust 1.0 Alpha
#244Earlier quoted context omitted.
let (x, var y) = ... can easily express the intention. Also, communication is in the ear of the beholder. Var: variable, that varies. 'Let' would be immutable by default. Thanks for the response anyway.
Well then it would be: let var x = ... the `mut` or `var` is part of the pattern match.
No.
let x = 100 // constant
var y = 200 // variable
x = x + 1 // error
y = y + 1 // 201Re: Announcing Rust 1.0 Alpha
#245Does anyone know of the Rust Book is available in epub format? Or, if not, but if it's still possible to build one from source, what are the required dependencies I have to install to be able to build the epub?
It would be more useful in a format which works on Kindle, since that's by far the most common. It wouldn't hurt to support both and also pdf. If there was a single page view of the book it would be quite trivial to export it to a single ebook file.
Open source tooling for creating mobi's are nowhere near epub's and Calibre does a good job of converting epub to mobi, so I don't mind when projects offer only epub, although I'm a heavy mobi user.
Re: Announcing Rust 1.0 Alpha
#246Earlier quoted context omitted.
We absolutely want one, but we've been actually developing the conventions first. You have to know what you want to format to!
Please tell me those discussions are on the mailing list.
I was on the rust mailing list for a little while about a year ago. Around that time there was discussion of this exact subject. Most of the discussion was around exactly how to break parameters beyond a certain length and so forth, but it was there.
Re: Announcing Rust 1.0 Alpha
#247Earlier quoted context omitted.
Solution: Don't inherit from GameObject. Make GameObject "final" and simply be a container of components. Move all object-specific behaviour into the components.
But, I still need inheritance. DuckComponent would need to inherit from Component in order for my GameObject to add that to the list of components attached. Am I wrong?
This sounds like the exact case where you'd use a trait.
Re: Announcing Rust 1.0 Alpha
#248Stupid question, but how can a web developer relate to Rust? I had to look up 'systems programming' and Wikipedia basically told me it is writing software for certain hardware components. Will I ever be writing a web application in Rust?
My background is primarily web development, however I've been writing a text editor in rust for a few months now. Prior to that, I had never written any software outside of the web. Honestly, its not such a big change once you get into it. I'd encourage you to just give it a go, build something just for fun with it. Be it a command line tool, game, whatever. My experience has shown me that just because you've only be…
To me it's more like s/he asked if they could build web apps with it, not about their chance to like it considering they come from web apps.
Re: Announcing Rust 1.0 Alpha
#249Quick poll: what's your favourite features in Rust? What's the core reasons for you are going to use it soon?
Re: Announcing Rust 1.0 Alpha
#250Earlier quoted context omitted.
But, I still need inheritance. DuckComponent would need to inherit from Component in order for my GameObject to add that to the list of components attached. Am I wrong?
This sounds like the exact case where you'd use a trait.
Yes, I think you're right!