Majora320

You can pay for lower latency on your end.

What prevents a Sandbox mode program from just using a chain of `··`s to access the root?

Most Linux distributions provide torrents for disk images.

If he's into programming, he could try writing server-side mods with the Spigot framework.

You have to enable the SCHED_UTILEST flag when compiling the kernel. Most end-users don't compile their own kernels, as doing so requires a very large and time-consuming amount of configuration, but you can if you want (might want to start with your distribution's configuration as a base).

>Online multiplayer game developers figured this out decades ago. The primary way to prevent people from cheating is not by preventing them from hacking or cracking the client application code. It's keeping the game state — the data — only on the server.

At least, good online multiplayer game developers.

I don't own a company, but I'd like to try this out myself. Is there any possibility of having a "personal" trial mode instead of having to enter a company name?

What's wrong with D? I quite liked it when I used it (for a relatively small project). It's not really a C++ replacement (GC), but as a high-level language the only problem I found was lack of a large library ecosytem - the language itself was quite pleasant to work with (more so than C++ and even Rust, which I also like).

I might have stuck around to view your site, if it wasn't incredibly slow. This isn't an old laptop, either; I have a desktop with a recent, fast CPU and GPU, which should be way more than enough to run any modern website.

(Latest Firefox on Arch Linux)

I read that as "A Regrettable C Compiler"

Also: http://txti.es/

Why do you have to call `req.Body.Close()`? Does Go not have RAII?

Does Go have something analogous to Rust's `try!` or `?` operator, which would turn it into (pseudocode):

    contents, err := try!(ioutil.Readall(req.Body))

Or:

    contents, err := ioutil.Readall(req.Body)?

If not, why not?

(I don't know Go)

Sure, but usually you don't want to hire _all_ of the good applicants - the reason you get bad hires is the false positive rate, not because there aren't enough total good hires in the pile.

Except that isn't how statistics work. If you have 100 applications, 20% of which are good, and drop 50% of them, you get 50 applications, but you still have the 20% good application/bad application rate.

Of course, you still get 50% less total good applications, but ratios != total.

+1. The reason only 4 people submitted is that the challenge seems so, well, intimidating. Not hard intimidating, but "I wouldn't be able to think up & code a decent entry in a few minutes" intimidating. Nobody really wants to make a whole toy payment processing system like this, just to come up with one underhanded bug. It also comes with a lot of tooling: with underhanded rust, it is very clear that this is a project, with multiple files, cargo, dependencies, etc. All of the underhanded C contests are single-file, often single- or two-function solutions.

What about tup? http://gittup.org/tup/

What is the use case for this?

I type 60-70 WPM with 2-4 fingers lol

Try buying a spray canister of compressed air, works wonders for cleaning dusty electronics.

Looks somewhat interesting. Essentially, it just switches the primary index from "type of file" (e.g. binary, config file etc.) to "program this belongs to". That has some advantages, as humans are more likely to want to search by program. I do have some issues with the distro's execution of this idea, though - the path names are far too verbose, and I'd rather not have to use the shift key twice in every path. I'd take '/etc/foo.conf' over '/Programs/Foo/Config/Foo.conf' any day.

Sounds like a politician who dosen't know how e2e encryption works... And giving the government unfettered access to everyone's communications is a terrible idea anyway; the whole "you-shouldn't-have-anything-to-hide" mentality is BS.