281 karma · joined January 2, 2014
I agree, but journals should allow paying for reading the article X amount of money, where X is much much much lower than the usual amount Y they charge for a subscription. Example: X could be 0.10 USD, while Y is usually around 5-20USD.
And in this day and age there are ways to make this kind of micropayments work, example: lightning. Example of a website built around this idea: http://stacker.news
Not my experience at all. If companies care about mobile, they simply make a mobile app.
Ah interesting, I didn't know this.
> A mouse+keyboard design just doesn't fit a mobile screen well, you're going to need to redesign and reimplement large parts of your application regardless of what platform you pick.
I think you're understanding this backwards. I'm not aiming to port a desktop app to a mobile app, I'm aiming to choose a UI toolkit that works fine in mobile by default and requires tweaks in your app to make it work in desktop (rather than choosing a UI toolkit that works fine in desktop by default but requires tweaks in your app to make it work in mobile).
Why do I say this? Because the migration from Xamarin.Forms to MAUI was (actually, _is_, as it's not really 100% finished yet) a horrible PITA.
Let alone the migration from .NETFramework to .NETCore (now called "dotnet" since v5) which delayed us months if not years (but people that used Avalonia would be affected by this too; so the way to dodge all this would have been choosing Flutter or ReactNative, I guess).
That being said, the main reason why I chose Xamarin.Forms over Avalonia at the time is because the latter didn't have Mobile support. How's Avalonia's mobile support now? Even if the port is 100% complete, I always thought "well, XF/Maui are centered around mobile, making desktop just be an after-thought", which to me is an advantage because I prefer better UX for mobile by default, and require devs to spend extra effort for desktop support (instead of the other way around); given that desktop usage of apps is declining day by day.
This paragraph (which is the ending one) feels like it is contradicting the rest of the article. Because if those things really led to an awesome ROI, then Google would not be where it is now, but in a much better position than before. I guess?
Don't get me wrong, I'm not against valuing employees above everything else, but if this becomes too extreme maybe it's normal that the company creates too much fragmentation? For example, why did Google create both Go and Dart? Shouldn't they converge into one? (Shouldn't Flutter have been written in Go?) And I'm sure there are more examples like this (e.g. we can talk about Fucshia...).
FTFY
You keep fiat currency in a bank? HFSP