Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dinglejungle
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
dinglejungle
3y ago
This might be more of an indictment on 'readable' being a meaningful concept (beyond simple personal preference) than it is of Zig's syntax.
2.
▲
by
dinglejungle
4y ago
> Cookie Monster (includes Black Metal) But what about Pterodactyl-fronted Black Metal: https://youtu.be/UZlZuYp1fZc?t=164
3.
▲
by
dinglejungle
5y ago
https://www.youtube.com/watch?v=a-WXzLKv_rc
4.
▲
by
dinglejungle
5y ago
> Why would operator overloading allocate memory? What if I wanted to overload the + operator to concatenate strings?
5.
▲
by
dinglejungle
5y ago
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.
6.
▲
by
dinglejungle
5y ago
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 holder
7.
▲
by
dinglejungle
5y ago
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:&
8.
▲
by
dinglejungle
5y ago
The comments on the original announcement here were pretty positive: https://news.ycombinator.com/item?id=27676266
9.
▲
by
dinglejungle
5y ago
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
10.
▲
by
dinglejungle
6y ago
The company Elastic was created 2 years after the release of ElasticSearch.
11.
▲
by
dinglejungle
6y ago
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 constan
12.
▲
by
dinglejungle
6y ago
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 th
13.
▲
by
dinglejungle
6y ago
> Paying the artists you actually listen to This is what Bandcamp is.
14.
▲
by
dinglejungle
6y ago
Are you saying that the given example should be disallowed?
15.
▲
by
dinglejungle
6y ago
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.
16.
▲
by
dinglejungle
6y ago
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...
17.
▲
by
dinglejungle
6y ago
Bandcamp?
18.
▲
by
dinglejungle
6y ago
Archive link to the referenced post: https://web.archive.org/web/20200415084132/https://slatestar...
19.
▲
by
dinglejungle
6y ago
https://www.google.com/search?q=site:reddit.com+ianal+-intit...
20.
▲
by
dinglejungle
7y ago
Being less vague about which nutrients you're talking about would be a good start.
21.
▲
by
dinglejungle
7y ago
> 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% e
22.
▲
by
dinglejungle
7y ago
> 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 20
23.
▲
by
dinglejungle
7y ago
> 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
24.
▲
by
dinglejungle
7y ago
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.
25.
▲
by
dinglejungle
7y ago
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-
26.
▲
by
dinglejungle
7y ago
> 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.
27.
▲
by
dinglejungle
7y ago
Yeah, seems to be back up. That link (along with https://github.com/jasonrohrer ) was 404ing when this was submitted.
28.
▲
by
dinglejungle
7y ago
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
29.
▲
by
dinglejungle
7y ago
https://github.com/ziglang/zig/wiki/Why-Zig-When-There-is-Al...
30.
▲
by
dinglejungle
7y ago
It's 100% manual[1]; that "safety" you're quoting is not referring to memory safety. [1] https://ziglang.org/#Manual-memory-management
More ›