@JimSproch@anaisbetts@migueldeicaza For me, itโs the ability to use (almost) any 3rd party .net library in iOS, Mac, Android and Windows and the bindings provided for AppKit, UIKit, Android, etc...
@anaisbetts@migueldeicaza I tried moving to Swift and SwiftUI, but wasnโt ready to give up my legacy code base (yet). What I couldnโt give up after that experiment was declaritive UIโs though, which is why I wrote my own one over the native layer (and Blazor for web).
@anaisbetts@migueldeicaza 1000% this. As someone whoโs always used the native layer (unless a customer requested Maui/Forms), itโs frustrating to see as using the native layer can be both faster to develop with and more stable long term.
@decriptor No, much lower tech based on resources I already had provisioned. I use Azure Functions and Azure Queue Storage for injestion and transformation, and then it goes into Postgres. I was planning on moving to something like Promethus and Grafana, but this approach has worked, so๐คทโโ๏ธ
Today was my last day at GitHub (after deciding to leave 8+ weeks ago). Proud of everything my teams delivered and looking forward to what they do next! Top of my list now is to have some real time off for the first time in a long time, after which Iโll figure out what comes next
@praeclarum Iโd comment on that issue to share that additional bit of feedback (and also that the latest VS for Mac update also broke Riderโs ability to launch Mac and Maccatalyst apps), but the feedback site errors out when I try to post a comment. ๐คทโโ๏ธ
Iโm hiring! GitHub is looking for a Senior Docs Manager to help one of our three core teams of technical writers thrive in our friendly and well established crossfunctional org.
https://t.co/iMiSluA32j