In response, I expect the open-source community to make an optimal square packing window manager. https://en.wikipedia.org/wiki/Square_packing

Is this the Stephen Dolan of "mov is Turing Complete" fame?

Is this the Stephen Dolan creator of jq?

https://jqlang.org/

Yes, its exactly that Stephen Dolan.

I believe so.

Are you suggesting we move to C++++?

It's already there. It's called C#

Well, C# also has its quirks already. Like the crippled finalizers which are never to be used. If the IDisposable interface had been correctly designed, finalizers could become be the "public void Dispose(void)". Or the manual passing of Task in case of async methods, which is... kinda smelly.

It's possible you didn't realise, but C# is sometimes said to be named that way because # is the symbol you get if you draw ++ small and then on the line below ++ again. Hence C++++

All languages have some spikier edges, there are no languages I know where I think "Well, even if we could start over I have no idea how to improve this". What's notable about C++ is just how rich that "could do better" seam is, so very many of their defaults are wrong, so many of their keywords are the wrong word, so many of their standard library features are allowed, sometimes even mandated to be crap.

I don’t know if that’s true or not, but while the thought never crossed my mind before your comment, it’s now canon in my mind. Yes, C# is spelled C++++ with a ligature.

The name is actually pretty clever (the fact that it was originally un-googlable notwithstanding). There are at least three interpretations:

* "C sharp" as in "C but higher",

* C with four pluses, and

* a homophone of "see sharp"

I think you meant to get that to the original poster, who seems to imply C# is the flawless, bestest incarnation of C\+\+(\+\+)+.

This is a fundamental problem with GC-ed languages. You can't get predictable finalization, so IDisposable can never be implemented reliably.

“#” is just two “+”. Count the lines.

Personally I like C+. Picking the nice parts of C++, but skipping all the nonsense. I just wish C++ hadn't deliberately screwed up designated initializers with mandatory ordering. The C version of it that allows out-of-order assignments is clearly superior.

Didn't you read the article? That form is deprecated. The recommended one is C,++,++

You clearly didn't read it either. Going forward, it will be C++...

I've never verified this, but it feels like scp starts a new TCP connection per file. If that's the case, then scp-ing a tarred directory would be faster because you only hit the slow start once. https://www.rfc-editor.org/rfc/rfc5681#section-3.1

Here's another for your collection.

- Putting the car in reverse sets off the neighbor's home security system. https://www.reddit.com/r/cars/comments/7k12fs/neighbors_hous...

Did this get solved? I think I read all the comments from OP but saw no confirmation as to what happened.

I don't think the OP ever returned with a conclusive answer, but I'm somewhat convinced by the commenters that it was either a low-frequency engine sound rattling the neighbor's windows or something to do with the car's rear-cross sensor.

There are yet more interesting docs in the parent directory :)

https://chromium.googlesource.com/chromium/src/+/main/styleg...

Oh no! I can run it on my phone, which is a few years old, so I figured it wouldn't lock anybody's computers up.

It's pretty CPU-heavy because it's constantly creating and updating SVG elements. I may attempt to rewrite sometime with WebGL and shaders :)

Check out Canvas 2D if you haven’t.

Hah, believe me, the flamethrower feature is first in line for the v2 milestone!

I'd like it but don't listen to me and please just stay in love with programming because this is such an awesome little project.

It would also be really nice if you could snip bits, pruning what is growing - with cuts causing something different to happen...

Oh, those are great ideas. On that note, I was also considering simulating nutrients and rewarding the roots that find them.