dinglejungle

This might be more of an indictment on 'readable' being a meaningful concept (beyond simple personal preference) than it is of Zig's syntax.

> Cookie Monster (includes Black Metal)

But what about Pterodactyl-fronted Black Metal: https://youtu.be/UZlZuYp1fZc?t=164

> Why would operator overloading allocate memory?

What if I wanted to overload the + operator to concatenate strings?

defer in Zig is per-scope, so

    {
        var file = try std.fs.cwd().openFile(path, .{});
        defer file.close();

        // ... code ...
        // file.close() is executed here
    }

would work just fine.

That doesn't excuse the behaviour from MuseGroup. They essentially were trying to do same thing that rights holders tried to do to youtube-dl, with (somehow) even less standing, since MuseGroup does not even represent the rights holders in this case.

Fraudulent DMCA claims and scare tactics ("Information about users who use this extension on musescore.com will be shared with local police"[1]) are inexcusable regardless of how they are justified.

[1] https://github.com/Xmader/musescore-downloader/issues/42#iss...

Yeah, judging from the MuseScore owners' behavior towards musescore-downloader, the situation with Audacity will only get worse from here.

https://github.com/Xmader/musescore-downloader/issues/5

https://github.com/Xmader/musescore-downloader/issues/42#iss...

The comments on the original announcement here were pretty positive: https://news.ycombinator.com/item?id=27676266

The TortoiseGit client basically has this feature[1]. In the commit GUI, you can right click a file and select "Restore after commit", then you can edit the file to remove all the changes you don't want to commit (which means you can also test it, etc, and that your edits can be as granular as you want). Then, after you commit, it resets it to have all the changes you left out.

I like it a lot.

[1] https://stackoverflow.com/a/48788906

The company Elastic was created 2 years after the release of ElasticSearch.

From https://www.elastic.co/about/press/elastic-n-v-reports-stron...

> First Quarter Fiscal 2020 Financial Highlights

> Total revenue was $89.7 million, an increase of 58% year-over-year, or 62% on a constant currency basis.

Yes, but it's much more likely your money is going to record labels rather than artists with something like Spotify. With Bandcamp, you are typically directly paying the artists, and you can always pay above the minimum price set by the artist if you wish.

> Paying the artists you actually listen to

This is what Bandcamp is.

Are you saying that the given example should be disallowed?

Your analogies ignore the advertisement part of what you are quoting. Selling an OS doesn't require any particular scale at all, selling ads to display within an OS would.

An example of this in the Zig math tests, where it tests calling the same function at both comptime and runtime: https://github.com/ziglang/zig/blob/33c4ad7f3a79aad5d7ea481a...

Bandcamp?

Archive link to the referenced post: https://web.archive.org/web/20200415084132/https://slatestar...

Being less vague about which nutrients you're talking about would be a good start.

> I am slowly coming to the realization that a quarter to a half of a percent of people who are alive on Earth today may not be in one year.

More than that percentage of the world's population die every year regardless (about 0.8% each year it seems like[1]).

[1] https://en.wikipedia.org/wiki/Mortality_rate

> These [wip] labels were there before this vaporware article :)

Only a day or two at most according to archive.org. No WIP labels on 2019-06-21 (the closest snapshot available before the article was published)[1]. WIP labels exist on 2019-06-24 (the closest snapshot to the articles date)[2].

[1] https://web.archive.org/web/20190621013937/https://vlang.io/

[2] https://web.archive.org/web/20190624052507/https://vlang.io/

> many empty promises by the creator which V simply wasn't able to deliver on.

Seems like this trend will probably continue with regards to the "1.0 release in December 2019" claim advertised in the Github description[1][a], since things like memory management are not implemented yet[2] and the December 2019 deadline would mean going from "first public alpha"[3] to 1.0 in less than a year.

[1] https://github.com/vlang/v

[a] depending on what 1.0 means, I guess

[2] https://news.ycombinator.com/item?id=21296992

[3] https://news.ycombinator.com/item?id=21297051

Ah, I see. It would help if the article made that argument a bit more explicitly, as I totally missed that interpretation the first time through.

The title of this submission ("Fuzzing makes memory-unsafe languages untenable") makes no sense[1] and is not found anywhere in the linked article.

[1] perhaps the intended meaning of the title was "fuzzing shows that memory-unsafe languages are untenable", but that's certainly not the meaning of the current title

> We can download the thing, try it and see for ourselves.

You couldn't two days ago, and nothing was marked as WIP two days ago, either. Hopefully things can cool down now that it's available.

Yeah, seems to be back up. That link (along with https://github.com/jasonrohrer) was 404ing when this was submitted.

Judging from the earliest Github issues, it's been there since late 2018.

edit: As pointed out below, it looks like the title refers to recent source code commits, not the creation of the repo.

Relevant links:

https://github.com/dotnet/wpf/pull/720

https://github.com/dotnet/wpf/pull/727

It's 100% manual[1]; that "safety" you're quoting is not referring to memory safety.

[1] https://ziglang.org/#Manual-memory-management