Live data from Hacker News

OpenD, a D language fork that is open to your contributions

dpldocs.info

301–310 of 322 posts

Re: OpenD, a D language fork that is open to your contributions

#301

Earlier quoted context omitted.

> intuitive and Pythonic "Pythonic" hasn't been "intuitive" for 15 years now. Even old-school Perl is more cohesive and coherent than modern Python.

Yeah that is why Python popularity is on the downward trend and Perl is the opposite /s

Or perhaps "intuitive" and "pythonic" was never Python's biggest selling point.

Re: OpenD, a D language fork that is open to your contributions

#302
post #248

Earlier quoted context omitted.

> I could see it occurring someday "Someday" is on the order of decades here. By that time Rust will be a hoary legacy language with a list of warts longer than an ISO standard.

Nonsense, WG21 is committed to ensuring C++ has more warts and sharp edges than any other language on the planet.

I don't agree. Rust very much wants to be a C++ alternative in all (I mean all) respects.

Re: OpenD, a D language fork that is open to your contributions

#303
post #297

Earlier quoted context omitted.

Thanks for calling my attention to that. I'll have to keep an eye on it.

Take it from me: I disagree with the BDFL of Nim about a lot, but him banning some of the people who are behind this fork was one of the best decisions he’s made. Stay far away.

Why?

Re: OpenD, a D language fork that is open to your contributions

#304

Earlier quoted context omitted.

> C# is not more safe than Rust By design, Rust requires unsafe code to implement any non-trivial data structures (except trivial POD types). This applies to both Rust standard library, and third-party crates. The issue is not a theory, security bugs actually happened in reality. Here’s an example about the Rust standard library: https://shnatsel.medium.com/how-rusts-standard-library-was-v... By contrast, thanks to t…

> Rust requires unsafe code to implement any non-trivial data structures That seems like a gross overstatement. https://github.com/rust-lang/rust/blob/master/library/std/sr... CTRL-F: unsafe Only one result, an optional utility function: "pub unsafe fn get_many_unchecked_mut"

That's a wrapper around the actual implementation (which lives in an external package). Notice "use hashbrown::hash_map as base;" at the top.

There's far more unsafe there: https://github.com/rust-lang/hashbrown/blob/f2e62124cd947b5e...

Re: OpenD, a D language fork that is open to your contributions

#305
post #297

Earlier quoted context omitted.

Take it from me: I disagree with the BDFL of Nim about a lot, but him banning some of the people who are behind this fork was one of the best decisions he’s made. Stay far away.

Why?

Because of experience I’ve had with the abusive behaviour of that community towards me and others.

Re: OpenD, a D language fork that is open to your contributions

#306
post #300

Earlier quoted context omitted.

Some context: dom96 here was the BDFL-in-2nd-command of Nim for quite some time. There is personal beef between dom96 and some of the primary nimskull contributors, which mostly involved a lot of name-calling, personal insults, and critiques of leadership and leadership effectiveness, that eventually lead to dom96 banning one of the aforementioned contributors, stalling quite a lot of interesting compiler work and pa…

It's no big reveal that I was involved and optimistic about Nim for a long time, though "BDFL-in-2nd-command" is a stretch for someone who couldn't even get the community to instate a Code of Conduct. That's one of the many many reasons I left. My many years of involvement with Nim is what I believe qualifies me to speak on the individuals in the forked project. That being said, I am no longer involved with Nim. I do…

Ah, I was referring to disruptek. I don't know why you two hated each other's guts, mostly due to being less active back then indeed. For what it's worth I didn't think the banning was undeserved: but the interactions you two had always struck me as strangely animus, and not anything like anything I've ever seen between him and anybody else, and certainly not between any other nimskull developers and anyone, ever.

It is perhaps notable that the nimskull project has a Code of Conduct (and a rather good one at that). I think it is indicative of serious intention to make a welcoming community, and I don't think that contributing members having had in the past what really struck me as personal grievances turning into open-air malice undermines that: particularly, such behavior would fall under the Code of Conduct itself. But again, I have not seen such behavior - quite the opposite! - outside of what happened between you two.

Re: OpenD, a D language fork that is open to your contributions

#308
post #300

Earlier quoted context omitted.

It's no big reveal that I was involved and optimistic about Nim for a long time, though "BDFL-in-2nd-command" is a stretch for someone who couldn't even get the community to instate a Code of Conduct. That's one of the many many reasons I left. My many years of involvement with Nim is what I believe qualifies me to speak on the individuals in the forked project. That being said, I am no longer involved with Nim. I do…

Ah, I was referring to disruptek. I don't know why you two hated each other's guts, mostly due to being less active back then indeed. For what it's worth I didn't think the banning was undeserved: but the interactions you two had always struck me as strangely animus, and not anything like anything I've ever seen between him and anybody else, and certainly not between any other nimskull developers and anyone, ever. It…

I don't hate anybody's guts and never have. There was a time when I could not post in the Nim community without an aggressive response from the person you mention - and would often enter the space to find many unprompted aggressive messages about me from him in what amounted to a harassment campaign. Contrary to your experiences, I have seen him frequently interact with others in the same way (and some have left the community because of it).

I'm glad that their community has a code of conduct. It is unfortunate that members there have never applied those rules to their interactions with and about me, nor with many others they targeted in the Nim community.

For your clarity going forward: I did not ban him, though I was one of the people who advised and agreed with that course of action. All decisions on whether to ban someone or not were taken by Araq (at the time at least).

It surprises me to hear you say you have never seen him engage that way with anybody else, given that you acknowledge that his banning was deserved. If I recall he was banned for aggressive behaviour towards _multiple_ members of the community.

Re: OpenD, a D language fork that is open to your contributions

#309
post #78

Earlier quoted context omitted.

I'm not sure the distinction is that clean, but isn't ubuntu still based off debian. As in, not a fork that went its own way, but a (big) collection of modifications on top of current debian?

Sounds like a fork with extra steps.

Derivative, it's less distinct than "fork" would have one believe

Re: OpenD, a D language fork that is open to your contributions

#310

Earlier quoted context omitted.

He pretty much derailed the D forum forking thread into remotely related tech discussion. This was weird to observe tbo, in the end my take is that he doesn't seem to bother much and would rather continue living in his version of the story.

It's worth pointing out that Walter is one of two co-maintainers of the language. The other has not said anything at all. On the other hand, I'm not sure what there is to say if they're not going to make any changes in the process. I'm far more concerned about community development of libraries, IDE support, and the beginner experience (especially on Windows) than I am about changes to the language, which is already…

I just posted on the forum about it, I didn't do it before because of surgery (I'm still nowhere near 100%).

What changes would you like to see happen?

Post reply on HN