joseluisq

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.

Agree.

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.

And if someone wants to phone him the ringtone sounds like this https://www.youtube.com/watch?v=8zEQhhaJsU4

(bad joke I know, it's Friday anyway)

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".

Honestly I never have seen such piece of crap like "Notarization". One of the Apple's failures ever (if is not the most one).

A nightmare (and not cheap) to deal with it as a developer.

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?

May you elaborate why virtualization provides a layer of security and isolation that containers still haven't (and maybe never will)?

Already discussed at https://news.ycombinator.com/item?id=26332944

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.

That's great set of tips BTW.

Yes, this sh*t must stop infecting our children.

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.

https://news.ycombinator.com/item?id=25254737

Yeah, worth reading. Even not being me a systems-developer stricto sensu, but Rust dev BTW.

There are valuable sort of pro/cons standpoints about Rust RFC for the Kernel.

And honestly I have learned many things. Hours well spent :). Just recomendable even if you like Rust or not.

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?

Maybe because of this?

> 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.

https://lkml.org/lkml/2021/4/14/1131

I'm not a C++ dev BTW, so this could need more details by someone with background for it.

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.

https://lkml.org/lkml/2021/4/14/1131

Latest Miguel Ojeda reply to Linus concerns

https://lkml.org/lkml/2021/4/14/1130

Yep, BTW looking forward https://lkml.org/lkml/2021/4/14/1105 those kind of 'real piece of code' that pleases Linus :)

Yep, 8min late. However turns out that the Algolia Search https://hn.algolia.com/?q=https%3A%2F%2Flkml.org%2Flkml%2F20...

didn't list the link at the time.

Anyway it seems that this problem is recurrent in HN.

Yep, honestly running ArchLinux + KDE on my Acer TravelMateX since 4 years approx I never had hardware/drivers related issues. This laptop is not an ARM of course but works wonderful well. BTW it also came with a fingerprint reader but I never used it.

It looks like these guys have taken serious the copy/paste recurrence and now you can copy/paste on steroids.

Don't forget the extras `Esc` + `:` + `q` to exit the hell.

Changes between 1.1.1j and 1.1.1k [25 Mar 2021]

https://www.openssl.org/news/cl111.txt

- TeLOS Linux: https://sourceforge.net/projects/teloslinux/

- Video Review https://www.youtube.com/watch?v=IHR6hUVCpsQ

Wow! the above code is described by itself about what Torvalds means with: very odd header files that *pushes the boundary* of what can be called "C".

I'm not a C dev BTW.

Copied and pasted from the article:

> So what would our tech bro saviors have found out if they had actually bothered to talk to anyone black? Well, at least this black person would have told them that calling the branch master is not offensive. Furthermore, black people as a collective are not triggered by words like master wherever they appear in the wild. Context people, context. Banning a word because you think it’s offensive is basically telling us what we should and should not be offended by. There are bigger problems around inclusivity that deserve our time, let us put this drive for change into those.

It speaks by itself. I agree.

--

Honestly trying to connect vaguely the calamity of racism or the master/slave human abuse and then bringing them forcibly into the context of a software term "master" used as a naming convention to describe the root (default) repository's branch is just stupid and insane.

Simply because both contexts are completely different. So try to mix them is big mistake and confusion-prone. Even it can fracture your community (if maybe it's already).

It's sad see how devs/companies are supporting this stupid idea of the change or even worse they encourage you to do it so.

Fortunately there are humans (devs) who really understand the matter and don't buy this nonsense.

The research article "Near-Optimal Decremental SSSP in Dense Weighted Digraphs"

https://arxiv.org/abs/2004.04496

Don't get me wrong but I don't really understand why for server stuff do you could prefer Ubuntu in favor of a rock-solid operating system like Debian?

One number, Debian Buster for example is LTS until June 2024 + 2 yrs. Just to mention one strength, I don't tell you about the well-known ones such as large community, fully openness, among others.

But how about ugrep?

https://github.com/Genivia/ugrep