Unfortunately this is not clarifying my concerns about duplications in this particular case. I understand about the year of expiration and moderators can reach out submitters but for me is not clear what `significant discussion` means as well as `moderators could suggest submitters repost items which the mods felt were interesting but did not catch on`.
Essentially I still don't understand why some get label as duplicated and some others not.
Anyway, Unfortunately https://news.ycombinator.com/newsfaq.html is not clear at all for me and I think HN needs to make it more obvious to help members to understand without doubts or contradictions, which was the case for me.
So I will contact HN soon in order to request an account deletion.
Thanks for try to explain me about it.
PD. Sorry for the deviation of these comments from the main topic here.
But I think my concern is already expressed on previous comments.
If your affirmation is true, why many of HN users (me included) get [dupe] at first place? In general, Is not the HN intention to decrease number of duplicates? If not so then HN should provide a solution for prevent this, such prevention that is not happening today. Example search input.
Sorry but I'm seeing big contradictions in the so called rules.
Just one example:
> If a story has not had significant attention in the last year or so, a small number of reposts is ok. Otherwise we bury reposts as duplicates.
> "in the last year or so"
Not in the same month or even after some hours later.
> "a small number of reposts is ok"
Well, HN what to prevent duplications or not ?
> Dupes are not against the rules. You're likely getting downvoted by people aware of that.
With that premise in mind, let's continue making duplicate content. right?
So don't misunderstand me, since my intention here is just to put in evidence the same recurrent problem to improve HN. For instance I have also faced the same problem in the past so there is nothing agains rules or things like that, but instead is more a improvement for HN.
The reason because I'm interested on this is because I feel part of the community and this is a concern for me (I suppose for others too). Otherwise I could take the easy and dirty way to just say nothing and ignore the problem.
Probably no so related but your comment remembered me some friends sentence, something like: "end-users don't mind about the technical aspects they just want something that works".
This is an ad-hoc claim and not necessarily true, I know. But turns out that this sentence is trivial nowadays with this such of big impact of technology in people's lives. So users are not foolish, they are every day more aware about software in general. They know what they want and can give you the value that your software deserves so just let's start to tell them more about Linux.
FYI: The original title of the post is "The Gates to Hell: Apples Notarizing" evidencing the frustration involved with the notarization process and which now was relativised to just "Apple’s Notarizing".
If unikernel offers excellent performance, faster boot times, throughput and memory consumption. I'm curious what are the benefits of VMM (Firecracker) in contrast to unikernel?
Are not those two comparable?
I got stuck with exactly that use case today and trying to figure out how I can enter directly to my dir without typing it again. Bash is no so neat at completions like Fish for example. However !$ does the thing and keeps my fingers healthy.
But in current conditions, sadly this trash will continue to harm our children if parents as well as those big tech companies don't tackle the problem seriously. It's sad that even they promote or allow it directly or indirectly.
Fortunately there are parents aware about this flagellum and it's harmful impact in the society, specially in our young people. And they don't allow that this happens to their children.
Yeah, I see `Result<T, E>` more solid in Rust than on-purpose Go error approach as you already mentioned and even more concise than `Exceptions` in other languages.
BTW there are already interesting discussions around the topic if someone wants to have a look.
Yeah, same experience for me. Lots of fragile and bloated code bases. And I don't tell you about maintainability nightmare. Javascript in the server is another example.
So this is not the fact that PHP people can write useful things with it or that PHP can help them to put food on the table, etc.
Here some questions not only for PHP enthusiasts:
Are you using the right tool for the job? If so, Are you do it well? Are those programs that you write easy to maintain over the time? Is the language providing you the necessary mechanisms to help you to do so?
> I think that the standard Rust API may simply not be acceptable
inside the kernel, if it has similar behavior to the (completely
broken) C++ "new" operator.
Agree.
And yes, privilege just uncontroversial standpoints or promote indirect pressure over the members will result in community fragmentation. Therefore HN could turn into "one of many" monotone sites to just pass around.
Yeah!
Even he kind of appreciates one of my favorite Rust features.
> So "Result<T, E>" is basically the way to go, and if the standard Rust
library alloc() model is based on "panic!" then that kind of model
must simply not be used in the kernel.
Essentially I still don't understand why some get label as duplicated and some others not.
Anyway, Unfortunately https://news.ycombinator.com/newsfaq.html is not clear at all for me and I think HN needs to make it more obvious to help members to understand without doubts or contradictions, which was the case for me.
So I will contact HN soon in order to request an account deletion.
Thanks for try to explain me about it.
PD. Sorry for the deviation of these comments from the main topic here. But I think my concern is already expressed on previous comments.