The old Nest is available as https://old-nest.pijul.com, but the HTTPS certificates are broken (I will try to fix that as soon as I can).
Looking forward to trying this out soon! But right now, anu.dev and nest.anu.dev are inaccessible. HTTP Strict Transport Security is active and the certificate seems to be invalid?
1 Like
@pmeunier can I suggest switching xxhash to pure rust implementation? This additional C dependency is probably unnecessary.
1 Like
You can suggest it, but it’s actually a dependency of C code in zstd-seekable, so it is not possible at the moment. If you want to work on a pure-rust version of zstd-seekable, go ahead!
Regarding information on the blog, is it possible to add an rss or atom feed?
It’s already there:
1 Like
Thank you. Sorry for trouble, I some how have not noticed it.
Eheh got it, seems worthwhile.
Hi,
Looks like things have been quiet for a while. Any chance that I can get an update on the project? Sorry if there actually has been other activity around the site, I’m new to using Discourse. I noticed that there is also a Zulip and a Reddit, but I am most familiar with Discord. Any chance that one exists?
I signed up just to upvote and support this effort.
The Git experience in version control feels like the C++ experience in programming languages—gotten so messy with all the various options and features that it is a pain to learn and debug.
The Pijul experience in version control feels like the Go experience in programming languages… a breath of fresh air… and a bliss of using an elegant and user-friendly piece of software/solution that just works rather than being a Frankenstein monster that you need to constantly fight in a 100 different ways.
I feel Pijul deserves the chance to prove itself in a real-world production environment so that the world can really take notice of what it is capable of. This would let the world see what Pijul can do for projects. It could be the boost that can bring Pijul to mainstream.
I understand that there maybe high costs to changing a core part of existing tech stack for most large teams but it feels like the world is missing out a lot. I feel holding on to legacy like its the ultimate truth, neglecting its pitfalls… would make the world miss out on the joy of programming and the effectiveness of being efficient. A good version control system should stay out of the way of the programmer, so that the the programmer can focus on what they are here to do… programming. I feel that the world should try out emerging technology like Pijul so that there can be a transition from high-friction legacy software to productivity enabling software that stays out of the way of the user.
I am just a beginner, would love to know what you all think.
I have good news about this, I’ll start to use Pijul more, and with others, and on a larger project (my own company) soon. I still noticed a few minor quirks in the tests which still need some fixing, but hopefully this will give me more opportunities to experience the pain points (many are “only” communication, i.e. people assuming wrong things because they are poorly explained).
6 Likes
Thank you for developing Pijul and for your efforts to make it robust! I would love to hear your experience once you use it on your larger project. Meanwhile, I hope to use it in more of my personal projects and gather an experience myself.