treesprite82

> A code block is not the same as a paragraph. [...]

Right, but for Markdown they're a difference in output despite the input \n\n being just whitespace, and for the final text they have semantic effect despite being just a gap between text. I don't think the argument was whether the particular semantic meaning of paragraphs exactly matches the semantic meaning of code blocks, just that they do have semantic meaning.

> This has nothing to do with the lack of significant white space and everything to do with terrible language design

It's a problem that illustrates how indentation indicates intent, and would be fixed by semantic whitespace. I agree that if a language is going to disregard whitespace, then {...} should be consistently required to partially make up for it.

> I guess that most humans are used to just automatically write and type semantic white space

My experience has been the opposite: looking over huge blocks of completely unindented VBA/MATLAB code written by people with little prior programming knowledge, and being thankful that data science is moving more towards Python. Likely a different crowd than those being actively tutored in C++.

But yeah there are bigger, often harder to automatically fix, issues with beginner code. PyCharm has PEP 8 lints by default for things like variable name conventions, which help but are still commonly ignored.

I think diminishing returns applies regardless of whether it's improving itself through optimization or breakthrough new ideas. There's only so much firepower you can squeeze out if everything else were to remain stagnant.

Like if all modern breakthroughs and disruptive new ideas in machine learning were sent back to the 70s, I don't think it'd make a huge difference when they'd still be severely hamstrung by hardware capabilities.

I think the original article's chosen image plays well with unsettling/uncanny nature of current AI generated images, faces in particular.

Definitely disagree with claims of "it's never gonna look right" in the tweet chain - DALL-E 2/Imagen/Parti are already notably better than Midjourney in general. Visible flaws will continue to diminish and prices will drop.

> For these reasons, I don’t think I’ll be using Midjourney or any similar tool to illustrate my newsletter going forward

> [Header image from Getty]

Maybe I should complain about how multi-billion dollar companies utilizing aggressive intimidation tactics to collect fees, even for public domain images they have no claim over, are stealing work from developers at the independent Midjourney research lab.

> capable of constructing a slightly better version of itself

With just self-improvement I think you hit diminishing returns, rather than an exponential explosion.

Say on the first pass it cleans up a bunch of low-hanging inefficiencies and improves itself 30%. Then on the second pass it has slightly more capacity to think with, but it also already did everything that was possible with the first 100% capacity - maybe it squeezes out another 5% or so improvement of itself.

Similar is already the case with chip design. Algorithms to design chips can then be ran on those improved chips, but this on its own doesn't give exponential growth.

To get around diminishing returns there has to be progress on many fronts. That'd mean negotiating DRC mining contracts, expediting construction of chip production factories, making breakthroughs in nanophysics, etc.

We probably will increasingly rely on AI for optimizing tasks like those and it'll contribute heavily to continued technological progress, but I don't personally see any specific turning point or runaway reaction stemming from just a self-improving AGI.

> a couple of newlines

A couple of newlines to create a new paragraph is semantic whitespace, as one newline or a space would not do so. Markdown (although not HN's Markdownesque syntax) even has significant trailing whitespace, which I would object to in a programming language.

> it's much harder to tell the difference between " " and " ".

Can't think of any scenario where you'd need to.

If you do mix hard tabs with spaces for indentation, which would cause readability issues with other languages anyway, it'll fail to run and point out where.

I can empathize that significant whitespace sounds off-putting at first, but after biting the bullet I think it's definitely a net positive. Indentation indicates my intent yet most languages just ignore it. For example, consider this gotcha across multiple non-significant-whitespace C-like languages:

    for (i = 1; i < 11; ++i)
        printf("%d ", i);
        printf("%d ", i);

Or, alternatively, hunting down one misplaced closing bracket.

Also, with Python appealing to new programmers, there'd probably otherwise be plenty of beginner code with no indentation at all.

> Don’t force a kid to walk in front of your 4,000-pound metal box traveling at god knows what speed

Some consolation, according to the tweet chain, is that it'll be at 5MPH and the child wouldn't be in front of the car (just on the sidewalk approaching the road). Still not sure the need to put an actual child at any risk when the car stopping for a dummy would prove the same point if not stronger.

The distinction they're drawing is between ignorance of the law (e.g: you take someone's phone because you didn't know stealing was illegal) and lack of knowledge/criminal intent relating to the act you committed (e.g: you take someone's phone because someone sold you a stolen phone and you were unaware).

Former is what "ignorance of the law is not a valid defence" applies to. Latter can be valid, and particularly in this case I'd find it hard to imagine that those affected by the dusting attack would be found guilty of violating sanctions.

No knowledge/criminal intent relating to the act can be a defense (other than for strict liability crimes like statutory rape), ignorance of the law is not.

Cut and dry if the open-source contributors are "blocked persons", but are they?

They'd no longer be allowed to contribute to the project, but does someone having contributed in the past mean the sanction on the project extends to their person? Github themselves provided hosting to the project.

> ...your response to which is to liken me to a dog while crying bully

Dog whistles are blown by humans. Arguably it implies the people you're trying to reach are dogs, but I don't think the analogy is intended to be taken that far.

> I said nothing about the non-binary demographic-- you did that in trying to spin my comment into HR Thunderdome.

Following up "you used the wrong pronoun. Reddit posts identify as "they,"" with "As a wolf, I am deeply offended" doesn't exactly reassure me of honest intentions.

For convenience features advertised as requiring active driver supervision and not making the vehicle autonomous, I think it only really makes sense for the driver to be liable.

Similarly, if some airplane instrument is stated to require regular calibration to stay within acceptable error limits, I don't think the manufacturer would be liable if the instrument starts to drift when those calibrations are not carried out. Or if some crash-contributing decision is made based on assuming a higher accuracy than promised.

Something that just flies an aircraft straight and level is still an autopilot, so I don't think it's a totally inaccurate metaphor.

Ironically in these situations a more understated name would probably work better for PR. Headline of "Tesla on cruise control rear ends motorcycle on freeway, killing rider" gives a much stronger impression of it being the driver's fault.