The goal of my question was about what are the differences between the two solutions: I know HN is a place where I can read technical arguments based on actual experience.
Perfect anwser. I have used DI for years, and the common DI abstraction is a great features: it allows people to start using DI and allow MS to use it internally, then, if you find it too limited or like some custom features, then start using a custom one, which is a breeze.
I shared the same frustration, but I finally gave up, and guess what, I was able to fulfill my projects and have a good insight about what my layout will be even with ~5cm difference. I learned to relax about absolute measures and think more about feeling and subjective dimensions.
Still, to switch back to the previous point, it seems it's more a divergence between using markup or code to design a document. Both have valid usage and benefits depending on your case.
In my case and my apps, I often need to handle complex conditions that fits better imo in procedural code (complex invoices and agreements). On other cases (reports), I prefer to use a markup language.
Webpages and pdf (paged documents) are fundamentally different, you won't be able to support easily headers and footers, page-breaks and orphans on a webpage. You can create basic invoices on webpages, but anything more complex (and by that I mean any serious word document) will require you to twist HTML. Try to have column headers to repeat on each printed page on a HTML page.
This keyboard layout, also known as AFNOR Azerty NF Z 71-300, has since be standardized. Drivers[0] are available and keyboards[1] can be purchased.
I am using this layout for more than 1 year for programming and writing in french, and it's really good. I find it even better that the international keyboard layout or qwerty.
The fact that they have considered both the programming language approach AND the natural language typing is a real pleasure.
No particular advice here, I just want to point to the fact that bing allows users to search their organization documents (office 365 files) when using bing [1] when connected with their org account.
This feature is named "Microsoft Search in Microsoft 365". It's not mentionned in the article.
See original ms doc article for details [2].
So it's not just a way to force users to use bing, it's also a way to push this feature in front of them.
> By making Bing the default search engine, users in your organization with Google Chrome will be able to take advantage of Microsoft Search, including being able to access relevant workplace information directly from the browser address bar. Microsoft Search is part of Microsoft 365 and is turned on by default for all Microsoft apps that support it.
> The restrictions are based on place of residence and location, not on nationality or heritage. If someone was flagged in error, they can fill out a form to get the restrictions lifted on their account within hours.