I had a professor who is responsible for a lot of the more "modern" MUMPS stuff (lets be real, MUMPS is OLD!). Guy was pretty unbearable too.

Truly seems that way currently. He said he'd really dig in starting next week and just checked his email on vacation and saw this whole mess.

It may be hard for him to re-establish trust. Maintaining xz for more than a decade then doing this would be quite a "long con" but if HN threads are any indication, many will still be suspicious.

His commits on these links look legit to me. It's a sad situation for him if he wasn't involved.

Honestly, he should call it quits and just drop xz utils and move on with life. He maintained it for 15 years and struggled to get anyone else to help until Jia showed up. Meanwhile the Linux ecosystem depended on it.

The Linux ecosystem will either figure shit out and maintain it or move into a different archive library.

The fact GitHub suspended his account too suggests that they might have info saying he is involved.

Personally, I doubt that. I would assume that GitHub just banned all accounts that were directly associated with the project as a precaution.

I think it was somewhat irresponsible to block everything. It hampers instigation of the repo's history. It's good that Lasse had another mirror.

Woops, too late to edit this comment and say *investigation

Or you know, they just reacted with a ban hammer on all accounts related to xz and to heck with innocence.

no. unlikely.

Hey Mitchell,

Best of luck in the future! I'm a nobody - but I was around in the packer days and wrote a post-processor and terraform provider for our vsphere back in the day. I don't think I'd be where I am now without those experiences. Thanks!

I can't imagine it wouldn't be easier to build something like early FaceBook today. There was no GCP / AWS / Azure / whatever back then. We were still racking servers, and we liked it.

> I can't imagine it wouldn't be

Whenever you have a double negative, flip both:

"I can imagine it would be"

If that changes the meaning too much, you can say:

"I can imagine it might be"

> > I can't imagine it wouldn't be

> I can imagine it would be

No. That means something completely different. They're saying (probably hyperbolically) that they cannot imagine the first of two possible situations, not that they can imagine the second.

Oh don't worry, I understand that just fine.

It's the speaker's or writer's task to iterate for a half second to find whatever non double negative sentence fits what they want to say.

English isn't code. You can't say double negatives in conversation or writing, and you have to find the closest thing without using a double negative.

> You can't say double negatives

It is in fact not the case that you can't say that. Double negatives, like sentences with a excessive number of conjuctions, are perfectly grammatical (when they don't violate some actual grammatical rule like the one "You do can say that." does); rather, they are in most cases stylistically bad, for much the same reasons that:

  stop = 0
  while(a() && !stop):
    b()
    if(!(c==d || !e())) stop = 1
    // should be `if(c!=d && e()) break`
    if(!stop) e()

is stylistically bad, namely excessive and more importantly needless complexity.

Thanks, we agree.

Oh. ... Okay, then. In that case I regret to inform you that your previous comment was extremely poorly phrased, to the point of seeming to mean almost the opposite of what you apparently intended. (Particularly in that double negatives are fine in conversation or writing, and can in fact be used, wherever they actually make sense - which is relatively rare in general, but occurs in the case we were originally discussing, since "can imagine it would be" means something different.)

Wow, you aren't not really tiring /s

Use double negatives less.

The end.

If you consider cost associated as an added difficulty, it’s possibly even more difficult now.

What has gone up in cost? The methods available 20 years ago are still available now.

We just have additional options now, which are actually cheaper to start, as you can get a lot of usage out of AWS' free tier.

Sure, once you get to "scale up" it's probably cheaper to do everything on-prem still, but that story is much better too with things like Golang, Docker, Elixir, k8s, etc, etc to make managing/building web-scale infrastructure much easier.

There were 1 billion people on the internet in 2005. Now there are more than 5 billion people on the internet.

There were no smartphones in 2005 and everyone used the web to access "social media". Now any social media is nonviable unless it has an app for both of the smartphone platforms.

Youtube and streaming video didn't exist in 2005. Now it's table stakes for social media to allow people to share videos.

The bar has been raised by at least an order of magnitude. Sure, it might be easier and/or cheaper now to do what Facebook did...in 2005. But that won't get you anywhere in 2023.

There are no more vc funds (currently) to pay your cloud bill though.

Did you add the words "generative AI" to your pitch?

As someone who works in banking - We don't show anything other than login and enrollment (and maybe a link for account opening, if the FI has it). Apple has yet to complain.

I fail to see how this is related at all to laravel.

Bro stop spamming your stuff on HN and figure out how to use fucking padding. All of our posts are slammed left and it looks like there's CSS missing.

This really seems like spam. None of these apps are real and your "product" is kind of sad really.

The university I went to still had a modem bank around 2007. Pretty wild.