colemickens has quit [Read error: Connection reset by peer]
colemickens has joined #nixos-azure
colemickens_irc has quit [Quit: Connection closed for inactivity]
colemickens has quit [Quit: killed]
colemickens has joined #nixos-azure
toraritte has joined #nixos-azure
<toraritte>
colemickens: Would you say that your project is ready to put a service into production? I need to do just that in about 2 weeks. I only know the bare minimum about flakes so I might be stuck with `azure-new` for now anyways, but if I suddenly have some extra time, I would love to try `flake-azure` out
<colemickens>
no, not really.
<colemickens>
But 'azure-new' isn't either.
<colemickens>
Azure-new is all pretty old, with an especially old Azure agent,
<colemickens>
the new project is better in many ways, but unfinished.
<colemickens>
neither have regular testing beyond me and maybe a couple other people using it very infrequently
<toraritte>
thanks! i'll use `azure-new` then but only because that's what I know and because I'll only have time to test `flake-azure` after this
<colemickens>
okay. I'm happy to answer any questions.
<colemickens>
Fundamentally flakes is just a bit of magic around nix and handling imports for you
<colemickens>
nixos-azure compared to "azure-new", the biggest differences have more to do with (1) module rewrite (2) new agent (3
<colemickens>
(3) it's a Gen2 EFI image, etc.
<toraritte>
I skimmed through the flake proposal and read Dolstra's tweag posts so definitely excited about it. As for the VMs, I have to get up to speed regarding gen1 and gen2 azure VMs - we are a small nonprofit so cutting edge is not a priority
<colemickens>
tbh there's no benefit other than the VM images are a bit easier in theory to create
<colemickens>
Azure Disk Encryption doesn't work with them (gen2) so ... yeah. it's weird.
<colemickens>
but I decided to aim for the future... and MS seems to want people to adopt gen2.
<colemickens>
To be perfectly frank, if I needed something to stay up, I would just use flake-azure.
<toraritte>
um, the disk encryption thing is truly weird as that would be my first thing to do for prod
<colemickens>
Like, if something is broken in one, it's likely going to be an issue in the other, and everyone's effort is better spent on the out-of-tree flake-azure (I'm probably going to rename it).
<toraritte>
you mean `azure-new` vs `flake-azure`? yeah, the latter is definitely the future, but having options never hurts (and thanks again for putting time and effort into both!)
<colemickens>
toraritte: for sure, I am reluctant to push too hard towards either, but wanted to make sure you had a rough understanding of how I thought about them so you can mash it up with your reqs :)
<colemickens>
toraritte: can I ask what the non-profit is?
<toraritte>
(thumbs up)
<toraritte>
sure, working for society for the blind, and we have a service called
<toraritte>
"access news" - 25 year old so replaced it with freeswith+erlang
<toraritte>
sacramento, ca
<colemickens>
very cool, even more happy to help out if I can. good luck! (all feedback is good at this point, I really have no sense of how many people try out this stuff and/or have successes or just give up quietly, etc)
<toraritte>
thanks! so as soon as the service is up properly in production, I'll start getting familiar with `flake-azure` - will probably have a lot of questions though...
<toraritte>
a bit of change of topic: how did you start rust and how long did it take you to become productive in it? (i know this is kind of subjective, just looking for a ballpark estimate)
<colemickens>
Even now, I'm not good or proficient, but I know enough to generally hack my way through docs and compiler errors, which is generally how I start out. I have a few projects that I generally re-implement in every new language I learn that help me build my mental map too.
<toraritte>
great start with Rust:) it took me way longer to submit a PR to anything