is there anything unusual about the giraffe?
It appears to be a baby
I actually view this as a reasonable response. I don't know anything about giraffes so to me it's entirely plausible that they get their spots later in life.
HN user
is there anything unusual about the giraffe?
It appears to be a baby
I actually view this as a reasonable response. I don't know anything about giraffes so to me it's entirely plausible that they get their spots later in life.
Yeah, I study* that way too.
*procrastinate
Can someone explain how it's ethical to be working on multiple things like this at the same time (e.g. OpenAI, AI chips, that eye orb crypto thing), but the benefits of each not accruing to the other investors, only to that individual?
I've always had similar questions about folks like Musk and Dorsey. Is it simply lack of proper governance? Is it something written into their contacts? Is this just a Silicon Valley thing? I can only imagine that a lot of people would like to work on many side projects, but their employment agreements forbid it.
I love this positive way of looking at it. I wish more people had this as the default - "I did a thing and it was bad/hard, here's my experience so you don't have to do the same."
This is a great explanation of the technical differences between the available options. What are the practical differences - is one option better from a maintenance and usability standpoint for creating systems that are reproducible?
I've lived in the Red Hat ecosystem for work recently. How does this compare to something like... Fedora Silverblue? Ansible? Fedora Silverblue + Ansible?
Alright, I'll bite... What led you to leaving the Linux world entirely? What can "the community" learn from your experience to make it better for others?
Let's put aside the technology not working for a second...
Isn't it ultimately leadership's responsibility to prevent these situations from occurring in the first place? Shouldn't they have been testing/auditing this system beforehand, addressing risks, and ensuring there were adequate operational plans ready in the event of an issue?
It's easy to blame software (even easier when that software clearly doesn't work), but blame ultimately should be on the people making the decisions along the way that led to this outcome.
So other than less battery performance, what other notable differences should I expect from Fedora on M2 vs the native MacOS. (I'm not being snarky, just trying to get a feel for how similar I should expect the performance and peripheral support to be; not focused on differences between gnome and the MacOS UI)
Yes, but what if the one skill you are lacking is the ability to identify what only you can do?
What does this realistically mean for these open source tools and models?
This kind of appropriate skepticism is why I love the HN community. This may be a perfectly innocent project, in which case I hope the author notices these comments and adjusts. But this comment highlights the possibility that it might not be so innocent.
I don't think this can be overstated enough. The incentives for vc-backed companies these days don't align with this model, hence the reason it's not more widely in use.
I do not believe this is the first PR made by a LLM, is it? If not, why is this notable?
I suspect you meant 'Ask HN'.
I've used Mozilla SOPS on many projects and I highly recommend it. I'm not quite sure why, but it just doesn't feel like it gets the recognition that it deserves, which is why I'm happy to see it here on HN.
The question asks why the all 0 public key in SR25519 and ED25519 has a known private key and what users should be aware of when using these curves. The answer explains that this is due to the mathematical properties of the Edwards curve models used in these curves and suggests using hash-to-curve to generate unspendable funds instead of the all zero public key.
First time I'm learning about this. Is it possible to take content that falls into this category and then reformulate it so that it produces more responses?
Unsub-squirrel
Wow, thank you for that link. Now I have a new bookmarklet...
javascript:location.href='https://labs.kagi.com/ai/sum?url='+encodeURIComponent(locati...
Thank you for sharing. This many years later, can you clearly identify how being a programmer has impacted your life (for better or worse)?
I wrote a few children's books when these tools first came out, but ultimately I decided against publishing them due to ethical concerns. I couldn't quite put my finger on it, but something felt dirty with the act of publishing and profiting off this work as my own.
That said, it was a very fun exercise and I look forward to the stories that are created in the future where the authors don't have the same hang up I did. Even if you don't publish, I would recommend going through the creation process at least once to familiarize yourself with how simple it actually is (tedious, but simple) to create this type of work.
They have a dedicated chat bot for their docs that might be able to help you find answers to your questions...
I was that other student - the one who was being berated. My PI acted terribly towards his subordinates just because he had it badly during his years as a student. That is not an excuse to act this way to another human being IMO.
I went to a U.S. PhD program during the '08 recreation out of necessity. It was a terrible experience and ultimately I ended up quitting. I've never quit anything before in my life so this was an especially jarring experience.
I left, got a job in tech (my original true passion if I'm honest), and never looked back. I learned a few things from that experience.
I learned that if you don't know what you want to do, then just try a lot of different things so you can compare. I learned that you shouldn't do something solely because of external expectations. I learned how important it is to treat people like humans no matter what their job is. I also learned how warm, interesting, and inviting the tech community is.
I'm appreciative every day for that last one as that's why I'm here with you right now.
The common misunderstanding of the word `factoid` to mean "a small fact" is itself a factoid.
In your opinion, why was overcoming the hardware-software hurdle that you described not enough?
What is it about the nature of data that makes this different (and harder to overcome) from a typical software problem for businesses?
Off-topic, but I wonder how much traffic is lost on PG's site due to not having a valid TLS certificate for his domain.
Hang in there buddy, it gets better.
It sounds like you're getting frustrated with the process (working with other people on an open source project), but you should really just let the process work _for_ you, not against you.
Work with your community (which might just be this single developer at this point) to collaboratively create a style guide or a set of standards for all future code submissions. This will be an outlet for you to professionally air your grievances and allow them to see where you're coming from. Simultaneously, this might provide you with some additional context that could help you better support them.
Best of luck!