Recent submissions

Comment · 11 years ago
It has a clear purpose the public can get behind, but it will almost certainly be abused for persecuting domestic political rivals, software developers among them.

Here are some entertaining thought exercises:

A cyber 9/11 is linked to Bitcoin. Can Bitcoin developers be sanctioned?

A cyber 9/11 is linked to Tor. Can Tor developers be sanctioned?

You donate to Wikileaks, which is linked to a national security threat. Can you be sanctioned?

Section 1(ii)(B) applies to _any_ individual or entity, domestic or abroad, developing or facilitating development of pentesting or related software employed against vague and faceless "national security interests". But don't you worry, because this is only applicable to the "Chinese" threat which may actually be true for the first couple of years to build political support for the eventual, predictable abuses of power.

Comment · 11 years ago
How considerate. As if the legal system matters at all to the existence of the NSA. Wikimedia's case notwithstanding, it's abundantly clear the spy agencies can only be peacefully resisted with privacy enhancing technology. It's obvious why they've been degrading public cryptographic standards and pushing for back doors.
Comment · 11 years ago
The Stasi controlled every aspect of life in East Germany, including the postal service and communications industry. In the US, FOIA documents reveal a history of domestic political spying on civil-rights leaders such as MLK, and on a wide variety of legitimate organizations.

Throughout history, suspicionless surveillance has been carried out by mafioso to oppress and control.

Of your suspicionless surveillance, you assert "this time is different". The assertion fails.

The Nazis could use your arguments word for word on dissenters of the Gestapo.

Comment · 11 years ago
Comment · 11 years ago
The Nazis would say the same of the Gestapo to dissenters, albeit with a tinge less arrogance.
Comment · 11 years ago
Are you trying to play victim, or are you just using your holier than thou card?
Comment · 11 years ago
You can do worse than pip and virtualenv, yes, but I wouldn't call pip the cream of the crop by any means. NPM is way easier to use for starters, and Go, Rust and Nim go one step beyond NPM by compiling language dependencies down to a single binary file which can be shipped to users. It's very succinctly done.

Python really needs to step up the game to stay ahead of up and coming languages like Nim, which looks like this:

    import rdstdin, strutils

    let
      time24 = readLineFromStdin("Enter a 24-hour time: ").split(':').map(parseInt)
      hours24 = time24[0]
      minutes24 = time24[1]
      flights: array[8, tuple[since: int,
                              depart: string,
                              arrive: string]] = [(480, "8:00 a.m.", "10:16 a.m."),
                                                  (583, "9:43 a.m.", "11:52 a.m."),
                                                  (679, "11:19 a.m.", "1:31 p.m."),
                                                  (767, "12:47 p.m.", "3:00 p.m."),
                                                  (840, "2:00 p.m.", "4:08 p.m."),
                                                  (945, "3:45 p.m.", "5:55 p.m."),
                                                  (1140, "7:00 p.m.", "9:20 p.m."),
                                                  (1305, "9:45 p.m.", "11:58 p.m.")]

    proc minutesSinceMidnight(hours: int = hours24, minutes: int = minutes24): int =
      hours * 60 + minutes

    proc cmpFlights(m = minutesSinceMidnight()): seq[int] =
      result = newSeq[int](flights.len)
      for i in 0 .. <flights.len:
        result[i] = abs(m - flights[i].since)

    proc getClosest(): int =
      for k,v in cmpFlights():
        if v == cmpFlights().min: return k

    echo "Closest departure time is ", flights[getClosest()].depart,
      ", arriving at ", flights[getClosest()].arrive
And performs like this:

    Lang    Time [ms]  Memory [KB]  Compile Time [ms]  Compressed Code [B]
    Nim          1400         1460                893                  486
    C++          1478         2717                774                  728
    D            1518         2388               1614                  669
    Rust         1623         2632               6735                  934
    Java         1874        24428                812                  778
    OCaml        2384         4496                125                  782
    Go           3116         1664                596                  618
    Haskell      3329         5268               3002                 1091
    LuaJit       3857         2368                  -                  519
    Lisp         8219        15876               1043                 1007
    Racket       8503       130284              24793                  741
http://goran.krampe.se/2014/10/20/i-missed-nim/
Comment · 11 years ago
I see Go and OCaml recommended to people fed up with Python's lack of static typing, and I just cringe. I love experimenting with programming languages, and Go seems to be picking up momentum but unfortunately for both Go and OCaml, they have this ridiculously restrictive syntax to them respectively which it makes it deeply unattractive for prototyping anything.

If you're looking for a statically typed Python that can be grokked in a matter of minutes, and compiles down to a static binary like Go does, and runs as fast as C in benchmarks, you should definitely check out the Nim compiler [1].

Code example:

    import rdstdin, strutils

    let
      time24 = readLineFromStdin("Enter a 24-hour time: ").split(':').map(parseInt)
      hours24 = time24[0]
      minutes24 = time24[1]
      flights: array[8, tuple[since: int,
                              depart: string,
                              arrive: string]] = [(480, "8:00 a.m.", "10:16 a.m."),
                                                  (583, "9:43 a.m.", "11:52 a.m."),
                                                  (679, "11:19 a.m.", "1:31 p.m."),
                                                  (767, "12:47 p.m.", "3:00 p.m."),
                                                  (840, "2:00 p.m.", "4:08 p.m."),
                                                  (945, "3:45 p.m.", "5:55 p.m."),
                                                  (1140, "7:00 p.m.", "9:20 p.m."),
                                                  (1305, "9:45 p.m.", "11:58 p.m.")]

    proc minutesSinceMidnight(hours: int = hours24, minutes: int = minutes24): int =
      hours * 60 + minutes

    proc cmpFlights(m = minutesSinceMidnight()): seq[int] =
      result = newSeq[int](flights.len)
      for i in 0 .. <flights.len:
        result[i] = abs(m - flights[i].since)

    proc getClosest(): int =
      for k,v in cmpFlights():
        if v == cmpFlights().min: return k

    echo "Closest departure time is ", flights[getClosest()].depart,
      ", arriving at ", flights[getClosest()].arrive
Statistics (on an x86_64 Intel Core2Quad Q9300):

    Lang    Time [ms]  Memory [KB]  Compile Time [ms]  Compressed Code [B]
    Nim          1400         1460                893                  486
    C++          1478         2717                774                  728
    D            1518         2388               1614                  669
    Rust         1623         2632               6735                  934
    Java         1874        24428                812                  778
    OCaml        2384         4496                125                  782
    Go           3116         1664                596                  618
    Haskell      3329         5268               3002                 1091
    LuaJit       3857         2368                  -                  519
    Lisp         8219        15876               1043                 1007
    Racket       8503       130284              24793                  741
This language deserves your attention.

[1]: http://goran.krampe.se/2014/10/20/i-missed-nim/

[2]: https://github.com/Araq/Nim/wiki/Nim-for-C-programmers

Comment · 11 years ago
Gordon Duff is a Marine combat veteran of the Vietnam War. He is a disabled veteran and has worked on veterans and POW issues for decades [1].

> In a video published on Liveleak, a close range “execution style” shows no blast effect or blood, from a weapon capable of devastating effect. (See YouTube demonstration of AK47 effect [2])

> Ballistics experts consulted today describe videos of the French attack as “staged theatrical events.” Other than the suspicious HD video, experts have already noted that, without coming close to “conspiracy theory” dot-connecting, the weapons eject no shell casings, bullets supposedly hit concrete with no effect whatsoever, even from “point blank” range.

> You see, the AK47 round, 7.62×39 is not only very powerful but typically has a steel core for penetrating body armour. When hitting concrete, an AK round throws up large chunks of debris, unseen in this event.

> Preliminary analysis of the audio as well demonstrates a frequency indicating the subsonic report of a blank round. In an “urban canyon,” a supersonic round from an assault rifle creates a noticeable high frequency “crack” with a secondary “report” or echo, generally described as “crack-pop.”

> It has taken only a few hours for press outlets to question perfectly timed HD video from a seemingly fearless bystander who is witnessing actors firing blanks incapable of operating the ejection system of a weapon, imaginary bullets that leave concrete pristine and blood free.

1. http://www.veteranstoday.com/2015/01/15/neo-paris-terror-the...

2: https://www.youtube.com/watch?v=YLB36UxWD0M

Comment · 11 years ago
Comment · 11 years ago
Minimize casualties, maximize theatrical effect, is the norm for deep events.
Comment · 11 years ago
Paul was presenting the information in a politically correct format. The US would never carry out such a cowardly act of state sponsored terror.
Comment · 11 years ago
Comment · 11 years ago
Comment · 11 years ago
I may not be active duty military and a ballistics expert but I implore you to watch this quick video of the shooting: http://www.liveleak.com/view?i=bc6_1420632668

Here it is again in slow motion, zoomed in: https://www.youtube.com/watch?v=v_c4IUO6h7w

Kalashnikov rifles chambered at 7.62mm exhibit greater than zero recoil under the best of circumstances.

It simply isn't credible to state that a Kalashnikov rifle will not exhibit _any_ recoil.

And to pretend as if a 7.62mm round fired at point blank range into a human target would cause _no_ amount of blood splatter or blowback in the target is highly suspect.

There is no visual of a bullet hitting this police officer and I will not apologize for my statements inciting controversy. Watch the video. In less than a minute you will see I am accurately describing the events as they unfold on video.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton