We've completely revamped ✨
Developer environments should be as simple as toggling options.
Especially if you're exploring Nix, give it a try ✨
• languages
• processes
• services
• scripts/git-hooks
• tests
• containers
• poly/mono repo support
My twitter feed:
- oh crap, Python2 is going to be legacy in 2020, 12 years after first release of Python 3, what to do?
- companies updating to GHC 8.8.1, which was released 3 weeks ago
Static typing has won, just need to open your eyes.
After months of hard work by
@ValentinGagari4
, we have the most comprehensive Nix language tutorial:
Please, share it with your peers and report any kind of issues following the tutorial 😊
A new chapter.
I'm quite excited be part of
@earnestcapital
and to be able to focus full-time on building infrastructure for Nix and taking us one step further to mainstream adoption.
It's going to take another few years before developers recognize that Haskell folks have built an amazing technology built upon foundations of math. And yes, it's also easier to use for humans. Go, etc will be remembered as Java. Good ideas take time.
My favorite part of IOHK gathering last week was dr. Phillip Wadler and dr. Duncan Coutts faces when CryptoKitties appear on screen as an example of smart contract application during a very serious project planning meeting.
I've been handling commit access to nixpkgs for years and once I stopped that process only one person thanked me for it and a dozen of people full of hateful messages.
I didn't do it for anything else than to help Nix, but this culture will have to change by people stepping up
It's been a year without income. Every few weeks or so I'd get slight panic attacks that it's all going to fail.
I remind myself that the only failure is not trying.
This book aims to be the comprehensive manual for type-level programming. It's about getting you from here to there---from a competent Haskell programmer to one who convinces the compiler to do their work for them.
by
With HashiCorp and Red Hat giving the middle finger to the OSS communities:
I'm grateful we went over all the obstacles we had to to set up a vendor agnostic NixOS foundation.
Thrilled to announce our Series A fundraise today🎉.
We look fwd to continue making GraphQL & data-access instant & painless, bring the Hasura experience to other databases & keep investing in our users & community, we ❤️ you!
More from
@tanmaigo
here:
To learn Nix, I think we have a three step journey:
- it's JSON datatypes + functions, just copy the snippets
- read the 2-3h tutorial on the language
- look up functions you need at
That's it folks.
So many people are wondering what's there to be done about all the drama in Nix.
Absolutely nothing needs to be done, wait for the dust to settle.
Take time to chill, go to nature, and do whatever means living meaningful for you.
Everything will be fine.
Going to spend next few weeks writing Nix tutorials.
What kind of tutorial would you like to read?
Would you screen-share with me so we can go through it together?
We're $1300 away from funding Nix improvement for replacing all current error/warnings to use the new output format.
This is going to change the experience for newcomers and reduce feedback loop for experienced users of Nix tooling.
Educating about Haskell starts with the fact that one needs no background in math in order to program in Haskell. If you want to dwell on prejudice, do it, but it's going to be hard to be educated.
Linux when? Linux now. 🎉🐧
For the last 6 months, our team and our open source community have been working hard to bring Zed to Linux.
As of today, we've released our first, official, stable build of Zed on Linux!
Looking back before learning Haskell, I remember so many people say: good luck, we'll see what you can do in a few years.
Two years later I discover the ecosystem and it's so much better than Python but so underused and underdocumented. But it's built on a solid foundation.
I finally did it 🤯🙇♂️
After 2+ years of therapy, I started microdosing psilocybin two weeks ago using the fadiman protocol.
On Friday I closed my childhood trauma during therapy!
My brain hurts and have some symptoms of derealization, but the feeling of internal state is 👌
As promised a year ago, we transferred all the content copyright and to the NixOS foundation.
Nix deserves to have good documentation owned by the community.
Who do we need to talk to help fund to preserve the whole history of software for the last 10+ years?
Storage and bandwidth costs are reaching 15k USD per month.
Please RT for reach 🙏
@JustAnkurBagchi
@agoda
I had the same with and they didn't grant me a refund because the owner refused.
It's so sad to see they are protecting businesses like that at such obvious scams.
I'm so amazed how far we've come with nixpkgs.
It used to be a work of ~50 people to bump packages, doing a lot of monkey work.
Nowadays there are automatic PRs of package bumps on github, already built by CI and with binaries available.
Go team :)
Today is my last day at IOHK. I'm thankful for being part of the story and was given a chance to bring together a team of 6 engineers to bring cryptocurrency using Nix and Haskell into production. Wish everyone the best going forward! 🎉
We’re thrilled to announce Zero to Nix, a new learning resource for Nix 👍! It's built to be beginner friendly 🧑🔬 and to generate those shining "a-ha!" moments that make technology stick ✅.
Read more in our announcement post:
Today is two years since
@cachix_org
was announced.
It has since saved compilation times to multiple thousands of developers and shortened their CI completion times.
I'm happy to announce we're finally restructuring the NixOS Foundation and I'm going to be a board member!
There's a lot of work to be done for the better future of the Nix project.
To ensure a balanced future for
@nixos_org
, my stance is that we should restructure NixOS Foundation to be represented by board members from active members of our community.
This is no small or simple restructuring, but it makes sure that all interests are challenged equally.
😍 Nix has hit feature parity with Bazel :)
- recursive Nix (incremental builds)
- content-addressable paths (early cut-off)
And all the other things that Bazel can't do.
Would you like to work with me in 4 SRE team using Nix / AWS / Haskell and challenging growth? Remote position, preferably in EU timezones.
Everything we do is open source.
What you're observing on the surface of the Nix community is internal fighting.
The actual game is classic divide and conquer, splitting the community on topics like flakes and military funding.
The next step is to conquer, where we'll see gaslighting and power-grabbing.
If there's one world I wish we banned in our profession it's:
Easy.
It's relative by each person, time, assumptions and information you don't know yet.
It misses the whole point of productivity management:
It's not about if you can do this, it's about the opportunity costs.
If you're using Nix for an Open Source project and would benefit from a larger binary cache:
Write me at domen
@cachix
.org with a few sentences about the project and I'll sponsor it.
Big productivity hack for OSS projects it to avoid the temptation for reviewing PRs as a way to sneak in perfection, but rather to ask if this already improves the status quo and can be merged.
I've observed that Nix adoption often leads to teams abandoning it after a while.
The primary cause for this is due to numerous instances where Nix was covertly introduced into the workspace.
That's why was created, to present the Nix layer in the most
Upcoming GHC 8.10.3 + non-moving GC early results on
@cachix_org
:
Worst case GC pause 115ms (previously 1.5s), with normal case being around 1-5ms (previously 20-50ms).
So far it works without a hitch, looking forward to confirm that on Monday's load!
Had a long draft of why I moved away from Python into compiled languages with safety guarantees, but I deleted it as it's hard to write a perspective without starting language wars, will just keep quiet and keep doing what works. Might write how Haskell is production friendly.
Early cut-off optimization is coming to Nix 3.0!
With that last one filled from build systems a la carte paper, it's the most complete build system out there.
I'm really excited to announce that Nix RFC 49 - Flakes has been unanimously accepted:
If you wish to read more about why and how flakes will shape the future of Nix:
Now think twice please, Elm 0.19 takes 2s to compile 50k lines of code to assure you won't have runtime exceptions. How long was your last debugging session? 1h?
I think to the outside world it seems like I'm making a ton with
@cachix_org
, but frankly for the last two years I've been paying myself barely a junior eng. salary.
If I freelanced I'd make a fortune, so I'm not in this for the money.
And yes, I turn down VCs almost weekly.