Paul Irwin
@paulirwin.bsky.social
CTO at feature[23]. Co-founder @codeonthebeach.com. Member @apache.org. Passionate open source software contributor, currently burning the midnight oil on Apache Lucene.NET.
Mississippi should have the burden of providing a service to their residents that i.e. digitally signs an anonymous token with a nonce and age range, which can be cryptographically validated against their public key. Uploading IDs to third parties is very bad for privacy.
August 22, 2025 at 9:35 PM
Mississippi should have the burden of providing a service to their residents that i.e. digitally signs an anonymous token with a nonce and age range, which can be cryptographically validated against their public key. Uploading IDs to third parties is very bad for privacy.
This is great! But the browser reconnect dialog almost never works for me when relaunching the app host, I have to refresh the page. Is that going to be improved?
June 12, 2025 at 6:40 PM
This is great! But the browser reconnect dialog almost never works for me when relaunching the app host, I have to refresh the page. Is that going to be improved?
Lest anyone think this is empty complaining, there are real, good IDEs to compare it to. IDEs that build simple apps in seconds, and don't turn on my laptop fan. IDEs that have great keyboard a11y, package management, and coherent project settings.
Those IDEs are created by @jetbrains.com.
Those IDEs are created by @jetbrains.com.
April 11, 2025 at 2:01 PM
Lest anyone think this is empty complaining, there are real, good IDEs to compare it to. IDEs that build simple apps in seconds, and don't turn on my laptop fan. IDEs that have great keyboard a11y, package management, and coherent project settings.
Those IDEs are created by @jetbrains.com.
Those IDEs are created by @jetbrains.com.
And don’t get me started on how comically bad the Swift package management is. Even ChatGPT, without my prompting, said the UI can be “silly” and suggested removing packages and re-adding them to upgrade.
All in all, just a terrible IDE in 2025, and I regret every time I have to open it.
All in all, just a terrible IDE in 2025, and I regret every time I have to open it.
April 11, 2025 at 1:47 PM
And don’t get me started on how comically bad the Swift package management is. Even ChatGPT, without my prompting, said the UI can be “silly” and suggested removing packages and re-adding them to upgrade.
All in all, just a terrible IDE in 2025, and I regret every time I have to open it.
All in all, just a terrible IDE in 2025, and I regret every time I have to open it.
The quick help dialog almost never works, and fails at the worst times, like when your project can’t build… which is when you need it the most!
And small rough edges like how selecting text then cmd+shift+F doesn’t put that text in the find pane, all add up to a terrible development experience.
And small rough edges like how selecting text then cmd+shift+F doesn’t put that text in the find pane, all add up to a terrible development experience.
April 11, 2025 at 1:45 PM
The quick help dialog almost never works, and fails at the worst times, like when your project can’t build… which is when you need it the most!
And small rough edges like how selecting text then cmd+shift+F doesn’t put that text in the find pane, all add up to a terrible development experience.
And small rough edges like how selecting text then cmd+shift+F doesn’t put that text in the find pane, all add up to a terrible development experience.
Xcode is the prettiest IDE out there, but also the most infuriating.
On top of the insane build times that require full power from my laptop, the worst part is the terrible keyboard accessibility. There’s no way to create a shortcut for switching to your most recently used tab, for example.
On top of the insane build times that require full power from my laptop, the worst part is the terrible keyboard accessibility. There’s no way to create a shortcut for switching to your most recently used tab, for example.
April 11, 2025 at 1:43 PM
Xcode is the prettiest IDE out there, but also the most infuriating.
On top of the insane build times that require full power from my laptop, the worst part is the terrible keyboard accessibility. There’s no way to create a shortcut for switching to your most recently used tab, for example.
On top of the insane build times that require full power from my laptop, the worst part is the terrible keyboard accessibility. There’s no way to create a shortcut for switching to your most recently used tab, for example.
Reposted by Paul Irwin
Perception continues to be a problem for .NET. 10 years after we open sourced the platform.
February 20, 2025 at 5:22 AM
Perception continues to be a problem for .NET. 10 years after we open sourced the platform.
Note that I'm fine with FluentAssertions changing to a paid model. It's frustrating, but fine. Rent-seek all you want as long as it doesn't affect me. My problem is solely with now having to pin NuGet version numbers and be careful not to accidentally upgrade and face legal or financial harm.
January 15, 2025 at 5:45 PM
Note that I'm fine with FluentAssertions changing to a paid model. It's frustrating, but fine. Rent-seek all you want as long as it doesn't affect me. My problem is solely with now having to pin NuGet version numbers and be careful not to accidentally upgrade and face legal or financial harm.
Imagine that you're allergic to gluten, and always buy the same GF rice cereal. Then one day, they quietly add wheat to the ingredients and remove the GF label. You face the consequences. Shame on you for not reading the ingredients for a product you always buy? No, that's ridiculous. Shame on them.
January 15, 2025 at 5:40 PM
Imagine that you're allergic to gluten, and always buy the same GF rice cereal. Then one day, they quietly add wheat to the ingredients and remove the GF label. You face the consequences. Shame on you for not reading the ingredients for a product you always buy? No, that's ridiculous. Shame on them.
NuGet should require that packages that change to an incompatible license change their package ID. FluentAssertions could leave v7 frozen in time as Apache-licensed. The idea of having to review licenses for every single *version upgrade* is an unreasonable burden that constitutes harm to users.
January 15, 2025 at 5:34 PM
NuGet should require that packages that change to an incompatible license change their package ID. FluentAssertions could leave v7 frozen in time as Apache-licensed. The idea of having to review licenses for every single *version upgrade* is an unreasonable burden that constitutes harm to users.
Update: we're now 47% done, and will be 52% once we get my current PRs merged. Only a couple high priority items remain. Will be going full steam ahead to knock those out. I'm feeling better about my goal of being dev complete with beta 18 by the end of the month/year.
December 5, 2024 at 6:58 PM
Update: we're now 47% done, and will be 52% once we get my current PRs merged. Only a couple high priority items remain. Will be going full steam ahead to knock those out. I'm feeling better about my goal of being dev complete with beta 18 by the end of the month/year.