WinUI made sense when windows actually had a proper design guideline, and touch was also the focus. So using WinUI was just easier as the controls were all following the guidelines, and if you wanted to offer a native experience, that was the best choice.
But it's been long gone that time where Windows had a minimum cohesive guideline.
I am sure this was posted so many times before but someone should reverse engineer the windows 8 era windows phones. Those were ridiculously smooth compared to android and ios with just 512mb of ram.
WP was incredibly smooth and they were willing to reinvent UX from first principles in ways that'll to this day make me reach for Sailfish OS if I didn't need physical buttons, but I must bring up the desktop version of Windows from that day.
I'll never forget the Asus Netbook proudly boasting about its 1024MB of memory via a colorful sticker that'd be considered excessively large on a 17.3" workstation, somehow running Gimp with multiple layers on Windows 8 alongside a few Chrome tabs without a care in the world. UX of 8 and 8.1 was awful, but it was optimized and stable in ways that made me hopeful for what MSFT would deliver in the future. 1gig of memory, a spinning hard drive and a single low powered x86 core were enough to get some image editing for a then school course done with some wiki pages in the background. I'd hardly believe it, had I not lived it. 10 and 11 have been regressions in my book.
The UX of Windows 8 was amazing on tablets, to the point where it's still my favourite touchscreen UI. The keyboard+mouse UX wasn't very good though, which is all that >99% of users ever used.
> 1gig of memory, a spinning hard drive and a single low powered x86 core were enough to get some image editing for a then school course done with some wiki pages in the background. I'd hardly believe it, had I not lived it. 10 and 11 have been regressions in my book.
I had a similar experience with the earlier releases of Windows 10 also [0]. I'm not really sure when Windows's performance got worse, but it was definitely some time after that.
I’d argue they started doing that a bit earlier. My hard drive from 2011 made using Windows a miserable experience any time the search indexing or windows defender scans kicked on, no later than 2016-2017.
I never used 8 because I hate the UI. But I used 7 for a long time. I recall that 7 was blazingly fast on a 2GB notebook back in the early 2010x. But then that was already way beyond its minimum system requirement.
Contrary to Windows Phones, Android was still mostly JIT compiling, with Dalvik.
Windows Phone 8, used technology from Singularity, .NET Native apps were compiled on the cloud and what was downloaded was MDIL (Machine Dependent IL), on device only linking was performed.
Starting with Windows 10, everything was done on cloud and you got a binary targeted to device.
Android had to go through AOT compiler in version 5, 6, reintroduction of JIT with AOT on idle on 7, staring of PGO data across devices on 8, until it got into a similar kind of performance.
And to this day, NDK sucks compared with Windows Phone 8 C++/CX experience.
Windows 8 Inbox apps a lot of them where WinJS actually. But on Windows 8 even web tech was fine (speed-wise).
And WP 8.0 < didn't offer AOT for .NET apps. AoT only came as experimental on WP 8.1 with WinRT apps if I recall right. And on W10 and W10 Mobile, it comes as default for all UWP .NET apps.
.NET Native was experimental in WP 8.1 and W8. On 10, it becomes mandatory and you couldn't even publish a JIT .NET app to Store.
WP 8.0 didn't even had WinRT, only Silverlight apps, and all JIT. If you wanted native in 8.0, had to go with C++.
About Desktop, C++ was rarely used. Most apps were either .NET C# (JIT) or WinJS. JIT WinRT .NET was super slow, WinJS apps were even faster, which is why many apps were all WinJS, including inbox Windows apps, like the MSN apps.
Some people really have very selective reading capabilities.
"When you build your app in Visual Studio, the code is not compiled into a native image, but into a machine-independent Common Intermediate Language (CIL) binary file. (CIL was formerly known as Microsoft Intermediate Language, or MSIL.) This CIL file is what you submit to the Store when you’re ready to sell your app. At that time, the binary file is converted from CIL to optimized Machine Dependent Intermediate Language, or MDIL. Finally, when the user downloads your app to a device, the MDIL file is linked to produce a native image. These steps are repeated in your development environment whenever you deploy your app to a Windows Phone 8 device.
Pity that the Channel 9 videos on MDIL for Windows Phone 8 are no longer around.
I think android apps bundle pretty heavy batteries, so it's like Electron, but in java, windows can make it faster by just pushing the GUI into the system as it always did.
I don’t even understand what you mean by “banks had to talk to each other” and why you are referring to TED in the past tense when it’s still the largest settlement method by BRL amount
Because TED is not the only way to send money now...? It's basically legacy, although yes, still used.
Very rare you'll see Person to person/business using TED. Basically business to person...
And yes, literally banks had to "talk" with each other. Which is why it was paid and slower in first place and didn't worked 24/7.
I suggest you go read the SFN messaging manuals from BCB if you truly want to understand how interbank communication works. It is very well documented.
You clearly don’t know what you are talking about since you are conflating the STR (transfer reserve system) with TED (one of the many settlement methods in STR)
The goal with Pix was not to increase the total amount of value tranfered, but the amount of small micro-transactions, increasing fluidity and bypassing unecessary bureacratic processes.
TED still wins by raw value, but that amount is irrelevant. It is what is left after the small-fry micro-transactions were liberated from complicated, archaic systems. Those small-fry transactions provided a lot of fluidity to the market, which is the realm in which Visa and Mastercard were supposed to act (incresing consumption) but were unable to compete due to their own legacy devices. They really need to catch up with the competition: those systems and their culture are ancient relics.
tbh even cashback these days might be worthless. It need to be a considerable amount. Because most things you buy, you have a discount when buying with Pix or money...
What still make credit cards strong in Brazil it's installments though...
The government already have card transaction access though. If you are in the banking system - you are being tracked. Doesn't matter if is Pix or a card.
Doesn't mean they will automatically expose you, as it requires justice approval technically...
