Hacker Newsnew | past | comments | ask | show | jobs | submit | bloobloobloo's commentslogin

Communists are still okay though, right?

We still all agree that Communism's little "quirk" of killing millions every time it's tried is user error or whatever? Right?


The out-of-Africa theory is junky agenda-driven science. It was debunked a decade ago.

https://www.scientificamerican.com/article/is-the-out-of-afr...


Still out of Africa.


Yes, the wikipedia article (https://en.wikipedia.org/wiki/Human_evolution#Dispersal_of_m...) has more information than the article linked by the GP.


Most North American scientists agree that Asia isn't really in Africa per se. Perhaps this news hasn't reached your corner of the world.


Africa -> Asia -> Europe

Africa -> ... -> Europe

Africa is still where it started.


No, the ocean is where it started.

If we're going to speak meaningfully about where Europeans come from, we need to include wherever they picked up Neanderthal DNA (hint: not in Africa; no African population has it).


> So all you can really do is try to convince the majority about what is 'right' and what is 'wrong'.

Unless the people who own all the infrastructure disagree with you, and refuse to accept your money.


> the slippery slope that is always brought up never materialized.

Very true. Well, except maybe for that one time when Germany became an open-air rape camp under the noses of police who did nothing for fear of being accused of racism. That kind of sucked.

https://en.wikipedia.org/wiki/New_Year%27s_Eve_sexual_assaul...

And, oh yeah, there was that time they threw a lawyer in jail for defending a Holocaust denier.

http://www.dw.com/en/german-neo-nazi-lawyer-sentenced-for-de...

But otherwise, sure, unqualified success. Great example.


> And, oh yeah, there was that time they threw a lawyer in jail for defending a Holocaust denier.

That's not an honest reading of the article you linked. From the article, "[the lawyer] also signed a motion during Zündel's trial with "Heil Hitler" and shouted that the lay judges deserved the death penalty for "offering succour to the enemy" -- leading the court to dismiss her." She was a neo-Nazi herself.



In other words, she didn't defend him the way you feel that she should have.

We'll just make a list of all the arguments that are okay to advance in court, so then lawyers know which ones are forbidden.

That seems like a good concept with no far-reaching implications.


You are generalizing well beyond the scope of the action.


A lawyer went to prison, for statements she made, in court, in defense of her client.

The action doesn't need embellishment from me.


Do details no longer matter?

"A man was arrested for walking." and "A man was arrested for walking and aiming a rifle at a woman." are clearly different actions.

A lawyer went to prison, for illegal statements she made, in court, in defense of her client. These illegal statements that would be illegal even outside the context of being a federal court lawyer.

I can't understand this fetish of generalizing to the point of total vagueness. Case-by-case analysis is just as important now as ever.


> for illegal statements she made

Oh it was ILLEGAL. Why didn't you say so? That makes it totally palatable that a lawyer might be imprisoned for doing his job, and doesn't AT ALL impeach the entire concept of a "trial."

> would be illegal even outside the context of being a federal court lawyer.

You have it backwards, friend. The inside of a courtroom needs MORE protections for speech, not fewer, than the outside. Laws like libel simply don't apply there (disclaimer: in the US. Can't speak for how they do it in failed states like Germany), and for very good reason.


Let's put the issue of Nazi speech being illegal in Germany aside for a moment.

If my lawyer yelled "Heil Hitler" and claimed the judge in my case should be murdered, while ostensibly defending me, I'd want them at the very least disbarred and wouldn't mind a bit of jail time.

BTW, I highly doubt a judge exhibiting this behavior in the USA would keep their law license, and they'd probably end up slapped with a contempt charge as well.

> The inside of a courtroom needs MORE protections for speech, not fewer

Perhaps for the defendant. But actually, in every country -- including the USA -- lawyers have extremely strong and often vague constraints on their speech.

And even then, what you're saying just isn't true, even in the USA. There are far more constraints on your speech during a trial than in the public square. Judges in the USA have extremely wide latitude in determining what can and cannot be said, how those things should be said, etc. Those are constraints that judges can enforce in their courtroom but cannot enforce in the public square.

Also, FWIW, knowingly committing libel during a trial is probably a bad idea. Even in the USA.

> disclaimer: in the US. Can't speak for how they do it in failed states like Germany

Well, if you consider Germany a failed state then I'm not really sure what to say. They have their problems, but then so does the USA. No place is perfect.

E.g., using your metric, the USA has THREE TIMES more rape than Germany. So if you put your identity politics aside for a second and look at the data, you come to a far different conclusion.

Also, IMO German citizens have a lot more practically useful freedoms than US citizens, even speech-related freedoms. "Don't be a Nazi" is something the Germans are pretty serious about, but they're a lot more lax about a lot of other speech that is de facto prohibited in many parts of the US. Eg, I seriously doubt Damore would've lost his job in Germany. And the Germans I talk to claim it'd be unambiguously illegal. And cultural self-censorship matters as well -- I'm much more comfortable discussing Christianity in Bavaria than in Alabama.

Germany draws their lines differently from the USA, but we're talking more about delineations at the fuzzy edges than actual differences in kind.

So again, if Germany is a failed state, I'm not really sure what a non-failed state looks like. At this point it's kind of hard for me to take you seriously.


> what you're saying just isn't true

Except that it is.

https://www.casamo.com/can-you-sue-for-defamation-during-tri...


The full quote is:

>> what you're saying just isn't true. There are far more constraints on your speech during a trial than in the public square.

Which, OBVIOUSLY, is responding to:

> The inside of a courtroom needs MORE protections for speech, not fewer, than the outside.

and NOT responding to:

> Laws like libel simply don't apply there

The object-level claim is that even with exceptions like that one you link to, speech is MORE LIMITED in court rooms than in the public square everywhere -- including the USA.

And yes, yelling that a judge should be murdered in open court would land a US lawyer in jail.

You're nit-picking (and what's more, nit-picking over a willful misinterpretation of the argument I'm making), not responding to the substantive object-level claim.


> (disclaimer: in the US. Can't speak for how they do it in failed states like Germany)

While neither is much like a failed state, the US right now is a lot closer than Germany (and more clearly heading in the direction of getting closer yet.)


I have nothing to say really about your first point where you do nothing but speculate about police motives, but the second one doesn't prove anything either.

The second case is not a slippery slope because it does precisely what's codified in German law, nothing more and nothing less. The lawyer herself denied the holocaust and that's punishable in Germany. So the law was correctly applied. That has absolutely nothing to do with the slippery slope discussion.


> you do nothing but speculate about police motives

80 cops "failed to notice" over 1000 violent crimes taking place in a space about the size of a football field, over the course of several hours.

My "speculation" is, by far, the very kindest interpretation.

> So the law was correctly applied.

Let's hope so. Defending her is a crime so we'll never really know.


You can defend her if you can resist your urge to praise Hitler and deny the Holocaust yourself in court. Again, that's all transparent and clearly defined in German law, so it literally had nothing to do with the original slippery slope discussion.


And you can defend a black girl who won't move to the back of the bus if you can resist the urge to claim blacks are people.

Fair trials without all that pesky social change! What could possibly go wrong?


>Very true. Well, except maybe for that one time when Germany became an open-air rape camp under the noses of police who did nothing for fear of being accused of racism.

What an awful example and has nothing, what so ever to do with the laws against being a Nazi. Do you honestly believe the US has never avoided reporting something for fear of being labeled? Really?

The other example you gave was covered by others in the thread. Spoiler: it's a lie.


> nothing, what so ever to do with the laws against being a Nazi

You are very poorly informed. The laws against "being a Nazi" are generic "no bad speech" laws. Nazism is just their most well-known application. https://en.wikipedia.org/wiki/Volksverhetzung

> Spoiler: it's a lie.

A lawyer went to prison, for statements she made, in court, in defense of her client. That's not supposed to happen. It's not a feature.


Germany is a joke. The fact that it's even considered a country and not a US territory is beyond me.

If you have a US military base in your country you are objectively not a sovereign nation.


Neat. Curious to hear your position on waving Communist and Jewish flags.


Is Jewishness "an inherently violent ideology of ethnic cleansing"?

For that matter, is Communism? Marxist-Leninist governments don't have a great track record, but there are plenty of individual pacifist hippie commies; the ideology of common ownership of production is not inherently violent and racist like Nazism and the Klan are.


The bar at King's College Cambridge used to have a hammer-and-sicle on the wall for years. If the authorities removed it the students would repaint it. All good clean fun.

It eventually got taken down for good after increasing numbers of students from eastern Europe came to the college and pointed out that, to them, it was just as oppressive a symbol as the swastika.

Really this all should have got sorted out around the time of the Spanish Civil War; actual capital-C Communism is too tied up in Stalinism to be trusted any more.

Of course, plenty of people are happy to label their enemies as "communist" for supporting basic reasonable non-Stalinist things like universal healthcare. So the fact that someone is labelled a communist by their enemies, especially in America, means almost nothing.


I'm sure not all Jews condone the ethnic cleansing going on in the West Bank and Gaza. But I kinda think some people see the Israeli flag in the same light as Jews see the Nazi flag. And yes, I am speaking as a Jewish man.

You might want to check your Russian History, particularly Stalin's era, to examine the violence inherent to the ideology of common ownership, when applied Soviet style. Scholars debate on whether he killed 8 million or 60 million...


If anyone is after anything on the topic, please try The Court of the Red Czar or The Young Stalin. Both by Simon Sebag Montefiore. Ironically a Jew with interesting views on Zionism and an excellent history of Jerusalem. The Radio New Zealand interview with him below covers his views on Zionism briefly.

http://www.radionz.co.nz/national/programmes/saturday/audio/...


[flagged]


> Jewishness is a religion of ethnic nationalism. As in, there's a DNA test to join.

This is not true. Source: http://www.beingjewish.com/conversion/becomingjewish.html Also, you seem to have confused Judaism with Israel.

> count up the deaths from pogroms that Jews are responsible for and the toll far exceeds Hitler's.

Source, please.

> Hitler certainly never mentioned ethnic cleansing in any speech or writings.

This is a straight-up lie. Read his speeches yourself: http://www.worldfuturefund.org/wffmaster/Reading/Hitler%20Sp... Also Google the definition of "ethnic cleansing".


> 10 different ways of doing the same thing

Mostly an urban myth. Where it isn't, at least 8 of those ways are actually important.

Exercise: write a python program that prints Python's quoting documentation, without external files, without editing the documentation. Spoiler alert: it's impossible.


So, how exactly these different ways of getting sub arguments are useful?

    sub add1 {
        my ($arg1, $arg2) = @_;
        $arg1 + $arg2;
    }

    sub add2 {
        my $arg1 = shift;
        # possibly two screens of dense code here, then
        my $arg2 = shift;
        $arg1 + $arg2;
    }

    sub add3 {
        $_[0] + $_[1]
    }

    # There may be some other ways to extract arguments 
    #  that I am not aware of.
    # It's possible to combine any of the methods!
And this is just argument access, one of the core language primitives.


> So, how exactly these different ways of getting sub arguments are useful?

Because in the second (add2), you might do something interesting with the second (or third) arguments depending on the first. You might have optional arguments. Your arguments might be a list of items you don't know the size of. It allows you to develop what you need out of the extensible core mechanism. Modules can and have built on that.

> # There may be some other ways to extract arguments

There are. Now you can just do

    sub add( $arg1, $arg2 ) {
        $arg1 + $arg2;
    }
My personal favorite is to use Function::Parameters[1]

    fun add( Num $arg1, Num $arg2 ) {
        $arg1 + $arg2;
    }
which allows named params, type constraints (runtime), default params, etc.

1: https://metacpan.org/pod/Function::Parameters


I cannot imagine any way of practical (ab)using this flexibility that could not be covered in Python with its only way of handling arguments.


To be a bit pedantic, these are not different ways to get a sub arguments, but accessing an array in different ways ("default array" in this case). If I understand this correctly, your criticism is aimed at how the core language makes arguments available to a sub body, in the default array.

The first example uses the explicitly named default array @_. This is a common pattern, and easy to read.

The second one omits the "default". Note that whilst it is possible to write some dense code between the $arg1 and $arg2, it won't work as expected if the dense code bit has array access - ie., the default array can change in the code.

The third example uses the typical sigils for accessing individual elements within an array (default or otherwise).

I wish the core language had saner defaults, but over time, I've seen some reasonable uses for the different styles:

1. General subs, the same as you example

2. shift removes the first element of the array and returns it. This can make the code more readable in certain cases:

  use Params::Validate 'validate';
  sub add2 {
    my $self = shift;
    my $args = validate (@_, { ... } ); 
  }
3. Slightly less verbose code, for simple one-liners and/or anonymous functions:

  my $calc_functions = {
    'add' => sub { $_[0] + $_[1] },
    'subtract' => sub { $_[0] - $_[1] },
    ...
  };
  my $func = 'add';
  $calc_functions->{$func}->($args);


The significant part of argument handling in Perl5 is that @_ is a list of aliases to the arguments. You usually see add1 or add2 style argument processing because nice named arguments that are a copies of the function parameters.

add3 shows how to access the aliased arguments directly.

  # break the aliasing of @_ and make undef into 0.
  sub undef_to_zero { @_ = map { $_ // 0 } @_; }

  sub math_stuff {
    # call with identical @_
    &undef_to_zero;
    # Do math without undef warnings.
    my $sum = 0;
    $sum += $_ for @_;
  }

  # Alter all arguments in calls by repeating them
  sub fatten {
    $_ = "$_" x 2 for @_;
  }

  $foo = "abc";
  @bar = ( 1, 2, 4 );
  foo($foo, @bar);
  say $foo; # abcabc
  say for @bar # 11
               # 22
               # 44


You aren't really showing off different ways to get arguments in any of those examples. In all of them, you get the arguments in a list called @_; you're just showing off three different ways to get values out of a list, which Python has plenty of ways to do as well. Translating your examples into Python:

    def add1(*_):
        _ = list(_)

        arg1, arg2 = _
        return arg1 + arg2

    def add2(*_):
        _ = list(_)

        arg1 = _.pop(0)
        arg2 = _.pop(0)
        return arg1 + arg2

    def add3(*_):
        _ = list(_)

        return _[0] + _[1]


That does not change the fact that in Python everybody writes

    def add(x, y):
       return x + y
whereas the Perl codebase that I work with has every possible combination of these methods.


But people using Python do at different times use destructuring, pop, and indexing to get values out of a list, which are the different ways of doing the same thing that you demonstrated.

e: Just clarifying that your complaint here is that every sub in Perl 5 just receives a list of its arguments; this isn't a "more than one way to do it" issue.


Why does Python have other options if no one is using them? Are these other options cruft in the language design, the compiler, or just reasonable support for features intended for other, perhaps infrequent, usage?

The old P5 motto TIMTOWTDI was long ago updated to TIMTOWTDIBSCINABTE and P6 adopts the latter. While P6 supports most of the options shown for P5, most folk writing P6 will just write something like:

    sub add($x, $y) { $x + $y }


I don't mean to detract from your point, but I have a related question:

How much actual cognitive overhead is there associated with three of four different ways of unpacking args?

Speaking for myself (as a long-time Perl/Python/GoLang/etc programmer), when I jump into a language I don't know, it doesn't take me long to get 'muscle memory' for how such things work.


Come up with a style guide and stick to it. Failure to do that with any language, no matter how restrictive, leads to messy code.

It doesn't matter which way you unpack your args unless you are trying to do something fancy (the sub 1% cases). Just pick one.

Hell, it's easy enough to make a script to rewrite multiple shifts into destructured list assignment or vice versa.


The second example is just bad code. The third example one would rarely use in oneliners or very shorts subs, maybe in a dispatch table. You can write atrocious code in just about any language. Perl 5.20 finally has function signatures anyway.


you'll be happy to know that the sigils (@) don't change in perl6 for access.


I see no problem here.


I'm not sure I understand your exercise. What do you mean by "Python's quoting documentation", and what do you mean by "editing" it?


> What do you mean by "Python's quoting documentation"

String literals are described by the following lexical definitions:

   stringliteral:   shortstring | longstring
   shortstring:     "'" shortstringitem* "'" | '"' shortstringitem* '"'
   longstring:      "'''" longstringitem* "'''" | '"""' longstringitem* '"""'
   shortstringitem: shortstringchar | escapeseq
   longstringitem:  longstringchar | escapeseq
   shortstringchar: <any ASCII character except "\" or newline or the quote>
   longstringchar:  <any ASCII character except "\">
   escapeseq:       "\" <any ASCII character>

You can't paste that text into a file and write a Python program around it that outputs the same text. You need to encode the quote characters.

More generally, there is no way in (many languages including) Python to treat an arbitrary (yet known) block of data as data.


For those that don't know you can use `「` and `」` to quote anything that does not contain `」` and Perl 6 won't process it in any way other than storing it as a Str.

If you needed to have `」` in there you can fall back to `Q{{{{{{…}}}}}}` or `Q:to<END>;␤…␤END␤`


I was wondering about that, too. Unless `"Python's quoting documentation"` is an easter-egg in "help()" that recursively contains a quoted version of itself, it should be possible to just escape all problematic characters. But maybe that counts as `"editing"`? Not sure.


> maybe that counts as `"editing"`

how would it not


> PA is very much a family.

So when, under the rubric of "general office IT," I'm asked to purge malware or replenish toner, I can reply with a lmgtfy link and a jocular reminder that I'm way too busy to give a shit about their irrelevant self-inflicted problems, right?


Absofuckinglutely yes!

In fact, if you mentioned this in the interview it could help you get the job. They're not looking for someone to replenish toner.

Edit: to whomever downvoted me, this is not a joke, I'm being 100% serious here. If it seems unbelievable then go watch some episodes of PA TV or something, that's just how it is there.


Why even put "general office IT" in the ad? Any task that can be described as such is far beneath the abilities of anyone meeting the other requirements. Whatever it means--Installing Office? Stringing cable? Deskside support?--this stuff can get done for $20/hr or less.

It only makes sense to ask a rockstar do-it-all to do it when you already got 40 hours from him, aren't paying OT, don't give a shit about his mental health, and are wringing as many hours as possible out of him to reduce the effective hourly rate.

This is the thinking of a scumbag cheapskate turd. No one who is paying a fair price for talent like this would waste it on vague low-level chores.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: