lately · contact · live · newsletter · talks · workshops · licensing · writing · rss feed · notes · radar · thanks · support · about ·


what's next

If you have been keeping a careful eye on GitHub commits you might have already guessed that after a long break from .NET - I’m back.

I’m still a super huge fan of functional programming (and Haskell) but due to multiple waves of redundancies (and judging off their careers page - a departure of the CFO) at a previous employer I’ve had to pause previous engineering leadership ambitions to help bring haskell to the masses. There definitely is a huge pool of people out there wanting to do Haskell as their day job and use it to build real products that make money. Haskell is definitely a way companies can solve their talent acquisition problems.

Anyway, Jérôme Laban upon hearing the news that my previous employer had left me stranded in Seattle hinted that I should work with him on the Uno Platform. To be honest - at first I wasn’t sure as I’ve previously done quite a-lot in the Xamarin ecosystem and was half-way through a ecosystem transition. I distinctly remember asking Jérôme “What makes Uno special?”:

  1. Until recently, all Windows 10 XAML platform controls were tightly-coupled to the version of the OS run by the user. This meant fixing any bugs related to platform controls would require an update to the user’s entire OS. WinUI changes everything.

  2. Uno took the correct approach and implements the Windows 10 windows.ui.xaml.dll contracts which means your existing Windows 10 XAML should just work on all platforms - AS-IS. If it doesn’t please raise a GitHub feedback issue. This translates into the ability to share styles, layouts, and data-bindings while retaining the ability to mix XAML-style and native layouts on a per-platform basis.

  3. With Uno, all views inherit from the native base view type. On Android this means View. On iOS this means UIView. Since Uno couldn’t change the design of the iOS or Android frameworks, Uno made DependencyObject a interface with a implementation that is automatically supplied by code generation. This design decision allows an Uno FrameworkElement to be a View or UIView and at the same time to be a DependencyObject.

  4. WebAssembly, WebAssembly changes everything. Most folks think WebAssembly is about the “web” but that’s missing the big picture - wasm is so much more than that. I kinda wish I had of listened more to Jay Phelps, sooner.

  5. Project Umbrella. Right now, Uno is a cross-platform UI framework but there’s more to come.

and that won me over. For the last couple of months I’ve been shipping features along side the engineering team, crafting code examples, supporting + pair programming with community contributors, documenting knowledge, and acting as an internal advocate and feedback-getter.

Even though I’m in love with Montréal, I’m not going to be moving here. I’ll be shipping commits remotely from my office back home — Sydney, Australia.

My remote office

Speaking of Montréal, Québec. I’m here for UnoConf and will be staying around for the next couple weeks so if you want to catch up for a cup of ☕ just ask.

UnoConf is tomorrow and we are releasing some cool stuff ™ that I’ve been working on. If this is your first time here in Montréal here’s a list of ideas to help you fall in love with one of my favourite cities.

If you can’t make it, stay tuned to the livestream to learn more.