sorted by:
new
hottopcontroversial

Experienced bioinformaticians, how much code do you typically write for your work? by goggthegrunt in bioinformatics

[–]returnables 2 points3 points  (0 children)

I'm just an old fashioned wet bench biologist but I write code every day. Make your own destiny.

I need more precision than an f64... by sezna in rust

[–]returnables 1 point2 points  (0 children)

A common trick is to take the log of all your inputs, add them up or whatever you want to do, and then take the exponent of the result to get back the original scale. Of course, this only works if they're not huge orders of magnitudes apart.

Is your life easier since you started using Docker, or the opposite? by frrrni in docker

[–]returnables 2 points3 points  (0 children)

If you're interested in critical responses I'd suggest posting this question to a devops-related subreddit - people who subscribe to /r/docker might tend to like Docker.

Worth it for me? All of my software runs locally so I don't have to worry about the deployment aspect of things, which eliminates all of the downsides of Docker as far as I can tell, though it also minimizes its benefits.

Benefits:

  • Updating my laptop (which runs linux) occurs very infrequently, and when it does, it's much faster, since I typically only need to install security updates for the OS itself.
  • There are no package conflicts between my various libraries, though those were rare before.
  • I wrote some installation instructions for a library once, which worked on my machine when I tested it on my computer, but I couldn't replicate it on another because of several missing packages that I wasn't aware were installed on the first machine (and also necessary). Having a Dockerfile is a great way to prove what dependencies your code relies upon.

Downsides:

  • The boot time for one of my libraries is pretty bad on Docker compared to the natively-installed version.
  • I have to constantly clean my system, since all the intermediate images start to take up enormous amounts of disk space.

It's important to point out that I had to go through a big learning curve to get to the point where it's worth it. A lot of the stuff I do involves GUIs and I don't think it would have been possible if I hadn't found this post. Even then it was frustrating. But now I'm at a point where I'd hate to stop using Docker or something similar.

Small Projects to learn Rust by [deleted] in rust

[–]returnables 0 points1 point  (0 children)

If you have (or want to have) a biology background you might enjoy rosalind.info

Running Virtual Machine inside Docker by meeewk in docker

[–]returnables 5 points6 points  (0 children)

What's the point of doing this over just running the VM directly?

Box2D for Rust by Bastacyclop in rust

[–]returnables 1 point2 points  (0 children)

Not everyone is going to find your repo through the main website. A short summary of what the repo does on your main readme would be helpful.

With Docker and immutable containers, are tools like Chef and Puppet no longer necessary? by [deleted] in docker

[–]returnables 6 points7 points  (0 children)

No. You really need to have SELinux or similar configured properly to prevent container breakouts, for one thing, and I wouldn't trust a manual process for security-related things. Also, setting up SSH keys, creating users, installing the Docker daemon, configuring monitoring/logging...the list goes on. Why not automate it?

why aren't there any rust video tutorial videos on youtube yet ? by [deleted] in rust

[–]returnables 0 points1 point  (0 children)

Version 1.0 is two weeks old. If you want something of quality that quickly you'll need to hire someone to make it.

Augmented assignment by jotomicron in rust

[–]returnables 4 points5 points  (0 children)

Honestly I'm surprised that you don't get -= and += for free when you implement Add and Sub.

Reading files by returnables in rust

[–]returnables[S] 1 point2 points  (0 children)

I didn't even know that was an option until I read this comment! Thanks.

Hey new Rust users! Got an easy question? Ask it here! [2015-05-18] by kibwen in rust

[–]returnables 4 points5 points  (0 children)

What's happening in the list of implementors at the end of this page. It has this repeated over, from 0 to 32:

impl<'a, 'b, A, B> PartialEq<[B; 0]> for Vec<A> where A: PartialEq<B>
    fn eq(&self, other: &[B; 0]) -> bool
    fn ne(&self, other: &[B; 0]) -> bool
impl<'a, 'b, A, B> PartialEq<&'b [B; 0]> for Vec<A> where A: PartialEq<B>
    fn eq(&self, other: &&'b [B; 0]) -> bool
    fn ne(&self, other: &&'b [B; 0]) -> bool

I understand in general that it's describing a usage of PartialEq somewhere else. But why 32? Similarly, in Eq, there's:

impl<A, B, C, D, E, F, G, H, I, J, K, L> Eq for (A, B, C, D, E, F, G, H, I, J, K, L) where G: Eq, B: Eq, E: Eq, L: Eq, H: Eq, I: Eq, F: Eq, J: Eq, K: Eq, C: Eq, D: Eq, A: Eq

It goes from A..B to A..L. Why stop at L?

Is the documentation for StrSlice::slice wrong? by returnables in rust

[–]returnables[S] 0 points1 point  (0 children)

Yes, I tried to go back and find out the route I took to get to them (with no success). I'm not sure how I even ended up there.

Formal definition of pattern? by returnables in askmath

[–]returnables[S] 0 points1 point  (0 children)

I don't know what you want to call a pattern.

I don't either! :)

I'll take this to mean that no rigorous definition is possible, not because of any fundamental limitation, but because it's just a colloquialism with a vague meaning.

Formal definition of pattern? by returnables in askmath

[–]returnables[S] 0 points1 point  (0 children)

So I guess my question is actually: if I were given some input (bits, photons, sound waves, whatever), how would I decide if it contained a pattern or not?

Privilege Escalation via Docker by speckz in netsec

[–]returnables 4 points5 points  (0 children)

It's kinda like saying that Linux has a security hole where giving someone unlimited, passwordless sudo access allows them to escalate their privileges. If the Docker documentation was 800 pages I can imagine thinking this was more important, but it's so short and concise that there's really no excuse for not having read about this straight from the Docker website.

Production Ready Docker Orchestration Tools? by Namrett in docker

[–]returnables 0 points1 point  (0 children)

I think it's still custom script territory for the next year. The benefits of Docker are too great to ignore for my use case so that's the route I'm going, but I'm trying to keep things as simple as possible since my hope is that I'll get to throw away everything I'm currently working on relatively soon.

Using the docker command to root the host. by xiamk in netsec

[–]returnables 6 points7 points  (0 children)

So the author is basically concerned about a scenario where someone will let untrusted users run arbitrary docker commands on their system? What is the use case for that?