turminal

This sounds like a great way to lose data when the machine dies unexpectedly.

For lots of software projects, a release tarball is not just a gzipped repo checked out at a specific commit. So this would only work for some packages.

In other words, for the user, it's not a step forward. It doesn't matter if the spec is perfect.

But most software that would need to care about that already needs to care about timezones, and those already need to be regularly updated, sometimes with not much more than a month's notice.

As I'm sure many of the customers can tell you, the company and the products are very real. And they come in very real milled aluminum cases, the case in the images is 3d printed because it's a prototype.

I don't understand the initial motivation for converting regular dynamic library dependencies to dlopen dependencies. How does that help with reducing the footprint?

Except for the users.

If char is signed and ' ' * 13 is bigger than CHAR_MAX, you get UB by signed overflow.

That would imply WAF gets to see unhashed passwords, so not good at all.

The funniest part of this is that they don't even check for all of the banned strings.

Source: I'm a student there and tried it out of curiosity.

> The first 4 are implementation defined rather than undefined.

Third and fourth are only defined in some implementations.

Oh, this is about last names, that makes more sense. Should have read it more carefully.

Did I read this correctly, there is a mandatory suffix to names of all female Lithuanians, required by law?

Also probably going to speed up language extinction :(

"Code" refers to whatever software written in C. "Implementations" refers to implementations of the language - C compilers and runtimes.

Yeah and they're both hostile to the user.

Unless Google Alert gets shut down by then.

A similar thing exists for Plan 9: https://orib.dev/git9.html

Wow, I didn't know about this correlation, where can I read more about that?

The "task" changes from time to time as well. Creating crazy new things, then figuring out they're too complex and then reinventing them simpler is another endless cycle, much older than software development itself.

I think this is on some level very much like deciding which programming language to use. It really depends on what problems you're trying to solve and there isn't a single one that is the best.

The difference is that type theories are much less of a "solved" problem and a lot of the variations are subject to ongoing research. As a consequence we're still at the stage where we're trying to figure out the "deciding how to decide", as opposed to programming languages, where decision criteria are relatively well understood.

This is not just a Windows thing. Plenty of Unix software struggles with long paths as well.

Most likely the motherboard has 8GB soldered on, they do that with a lot of laptops these days unfortunately.

> (but I don't know whether C already had the "const" keyword at that time)

It did, "const" exists since C89.

Related, one of my favorite in-depth stack overflow answers: https://stackoverflow.com/a/33206814

I have a hard time believing this is about blocking malware. Discord doesn't want to be a free file hosting platform anymore, and that's fine, but they shouldn't pretend this is about something else.

People will trust their connections regardless of this.

That specification is a monster. "quite easy to support" is not a good description of the situation.

Fringe and fastest-growing are not mutually exclusive: https://xkcd.com/1102/

No more Python parsing for those germans then...