NickPavlov

A software developer with passion for cloud and native (read desktop) technologies, and a professor in computer sciences in Plovdiv, Bulgaria.

[NickPavlov @dotPavlov]

@zacbowden Why? Does it have touch? A pen? Or something interesting like Dial?
Why on earth should I pay for this, unless I want to train and run some local models?

[NickPavlov @dotPavlov]

@zacbowden Actually, I see no reason to watch it. There is nothing revolutionary going on here, just a new ARM laptop, but without any UX innovations...

[NickPavlov @dotPavlov]

@konradkokosa Great news! Please don't put too much LLMs into GC :-)

[NickPavlov @dotPavlov]

@zacbowden Not impressed. No touch. No pen. No wow form factor. Why would one prefer this to a Mac already, or to a way more-reasonably priced laptop? I absolutely fail to see the winning points.

[NickPavlov @dotPavlov]

@WithinRafael I only hope he is leaving WinUI in good hands, and he is not leaving because WASDK is dead even before arrival.

[NickPavlov @dotPavlov]

@XAMLLlama Good luck! Thanks for all the work for the community and plese tell me you are leaving WinUI in good hands!

[NickPavlov @dotPavlov]

@pavandavuluri It is high time to come up with some innovative device!
And, consider threading into mobile again.

[NickPavlov @dotPavlov]

@levie Let's be honest. Software companies, with their demand for skills in specific frameworks, destroyed a lot of the demand for fundamental skills, bringing up a generation of developers who think knowing React is all they need. This must change.

[NickPavlov @dotPavlov]

@levie We cannot just throw the ball over to colleges. Businesses must cooperate with colleges and restore the importance of theoretical and fundamental knowledge.

[NickPavlov @dotPavlov]

@WindowsLatest Well, that was to be expected when you kill your mobile platform and then neglect your customers platform (Windows) for years.

[NickPavlov @dotPavlov]

@Erinthul_ The Witcher 3, I think Johnny.

[NickPavlov @dotPavlov]

@WindowsLatest Killing Live Tiles was the saddest mistake MS made in regard to Widgets. A native and perfectly working solution was replaced again with some web based misconception.

[.Morten 🪁🗺💻 @dotMorten]

#WinUI source code now includes the unit tests, so it is easier for us to verify our PRs doesn't break anything: https://t.co/OO3sF03c4k

[ClarkeZone @ClarkeZone]

WinUI3 perf update:

https://t.co/B2cRpMYwiy

[NickPavlov @dotPavlov]

@WindowsLatest Well, this has been around since ages. It is called priority boost. Windows has been using it in many cases, including when a thread (app) receives user input. I really don't understand the noise.

[NickPavlov @dotPavlov]

@shanselman This overreaction puzzles me, too. Priority boost has been in Windows for many, many, many years. Including boosting the priority of the thread receiving the user input. This is just a fine tuning of the priority boost technique.

[NickPavlov @dotPavlov]

@Eirenarch Just looking at DirectWrite Api gives me terrible headaches. I can even phantom the complexity of the implementation.

[NickPavlov @dotPavlov]

@WindowsLatest Fine-tuning priority boost, nothing else.

[NickPavlov @dotPavlov]

@davidfowl Hope you are cooking native. ;-)

[NickPavlov @dotPavlov]

@lauriewired This is non-sense. Compilers rely on strict rules to generate code, all optimizations include. LLMs rely on "guess the next word from a large db of dubious code", sprinkled with randomness, and doomed to ultimately fail by the inherent hallucination.