LambdaComplex

But apparently saying you'd get downvoted gets you downvoted just the same. Just like on Reddit!

None of us can

Alright, here's an example:

  touch 'file with spaces'
  for file in $(ls); do
    rm -- "$file"
  done

This will not work, because $(ls) will get expanded to three items, not one. rm will be called on the files "file", "with", and "spaces"...which is not what was intended.

Now do this:

  touch 'file with spaces'
  for file in *; do
    rm -- "$file"
  done

This works correctly.

Fruits are natural and have plenty of sugar

Let me quote that thing you linked to:

"As with many of the utilities that deal with filenames, the output of ls for multiple files or in one of the long listing formats must be used carefully on systems where filenames can contain embedded white space."

POSIX is such a system. If you try to parse the filenames output by ls, it will break when you encounter a filename with whitespace in it. Use a shell glob instead—it will actually work right.

There's plenty of ways to style a lambda. And plenty of colors to choose from.

That's the Half-Life logo, not a coincidence.

(And, just to prove how much I love Half-Life, my username is a Half-Life reference)

In your scenario, the door is a clear divider between "room" and "not room." What's the equivalent divider in the universe scenario?

I've recently (within the past week or so) begun learning LaTeX for the purpose of typesetting my resume. It's actually been easier than I expected, and the result already looks much better than the Google-Docs-Exported-to-PDF that I had before.

Sounds like Toyota's given you plenty of incentive to take it into one of their shops (and, thus, give them more money). The system is working as intended ;)

The point is, they were designed that way. And that's the problem.

No, it would be open source. There's the source code. It's open; anyone can go look at it. Whether or not you can modify it without violating a license has nothing to do with whether or not you can read it.

And this is exactly why Richard Stallman doesn't like the term. https://www.gnu.org/philosophy/open-source-misses-the-point....

Slightly off-topic: Why is JSON so popular for this sort of thing? I think it's fine for programs communicating with each other, but I really don't understand why anyone would want to have to match brackets when writing a configuration file

And appeal to tradition is a logical fallacy

If it's worth anything, that's apparently just pictures from someone else's article[0] with different (yet similar) captions on the pictures

0. https://dogbehaviorscience.wordpress.com/2012/09/29/100-year...

"It doesn't strike me as a very healthy relationship that one party controls the other's DNA"

Oh, it definitely isn't: http://healthypets.mercola.com/sites/healthypets/archive/201...

(And look up an x-ray of a pug's skull, while you're at it)

I used to do that, but I've started using a toaster oven (400 degrees Fahrenheit for 6 or 7 minutes) now that I have one.

The skillet (understandably) doesn't heat the top of the pizza that much. The toaster oven doesn't have that problem.

I feel like it's kinda impressive that he managed to keep that up for 8 months. What were the two jobs exactly?

BeOS wasn't UNIX-based

Well, there's always 4chan.

Interesting, but not all that surprising when you stop to think about it: give it invalid arguments and it fails, with a corresponding exit code.

As an aside/self-plug, I wrote a blog post[0] complaining about my least-favorite Bash gotchas.

0. https://lambda.complex.rocks/2017/03/why-i-dont-like-bash/

Hm, I actually hadn't considered that. I suppose that is a good solution, if you don't mind paying a few bucks to spin up a VPS.

You're right, there's no silver bullet. But it seems like some people have the mindset of "Since everything is bad and (to some extent), there's no point in trying to improve."

> Following the logic here, you seem to be implying that no-one except the irresponsible should use C.

There are some platforms (such as embedded systems) where C really is the only choice. But if you do have a choice? Then I don't think using C is a good idea.

I'm not sure if "irresponsible" is the right word, though. I think developers underestimate the risks of C's unsafety and/or overestimate their ability to properly deal with it. Hanlon's razor[0] applies.

0. https://en.wikipedia.org/wiki/Hanlon%27s_razor

The GitHub repo[0] says that the server takes about 20 minutes to load the data and requires about 30 GB of memory to run. It would be interesting to play around with this, but I don't think a lot of people have a spare 30 GB of RAM in their box. Would it be feasible to modify the program so that it just reads from the filesystem instead? Or would that slow it down to the point of the server being unusable?

0. https://github.com/andrewreed/codaspy2017

C is not a safe language. This sort of thing seems (to me, at least) like a jury-rigged workaround rather than an actual solution.

If you actually care about memory safety—which you should, as the CVE list shows—then why not use an actual memory-safe language?

I do, but it's mostly just "because I can."

I signed up for the GitHub education pack, which provides (among other things) $50 USD in DigitalOcean credit. I spun up one of the $5/month droplets, primarily to use as an IRC bouncer. But, since I now had my own Linux server with a static IP address, I said "Why the heck not?" and bought a domain name for $10.

So now I have an IRC bouncer and a personal blog. (And a Quake 3 server...because I can)

So why would someone want to use this over GNU Social?

Why ask? If you don't mind how it's used, just make it MIT, 2- or 3-Clause BSD, or Apache 2.0

Did you not read the article, did you miss the point, or are you saying it's incorrect?