srakadoor.blogg.se

You don't want notifications for your communication services? (Zoom, Meet, Slack, Teams, Discord, Messenger, etc.) It also reflects the difference in their revenue being services vs software. Microsoft's Open Source policy reflects that they now need to attract new customers in a diverse technical landscape, vs try to lock in existing customers to a Microsoft-created ecosystem. The explosion of new platforms and of mobile devices meant it was easier for them to sell SaaS products like Office 365, and to treat Azure as their new platform play. My opinion however this wound up being overall healthy for them, because they have always mostly sold to companies and strived for more recurring revenue via support contracts and the like. Their emphasis on backwards compatibility (and general developer distrust of Microsoft's long-term support of new API) wound up making it very difficult to get support for newer platforms, especially on new architectures like ARM. Google capitalized on the technology gap for most non-smartphone third parties in releasing a quasi-open-source mobile platform, seizing the market that Microsoft would normally sell their platform into. Most likely, it came from them realizing they had lost their platform monopoly due to floundering so badly with consumer mobile.Īpple invested tons of resources to accelerate their initial iPhone OS efforts, and had a polished experience you couldn't get from third party integrators. Personally I think Microsoft's change mostly came from realizing that being a government contractor is much more profitable than serving consumers directly and playing nice with open source is really important for attracting talent. > I don't think you have to be a dumb optimist to buy into this. I'm not going to give Apple a pat on the back for trying to catch back up to web standards only after lawmakers start eyeing up Apple's monopolistic and destructive web and app store practices. > Say what you will about Apple, but I think the team behind Safari has been doing some fantastic work to make up for its reputation If 10% of it works we consider it a success." attitude.

It's more reliable for web developers than Safari's often maligned: "Hey we released this feature and don't care that it's broken. Personally I'm fine with this delayed approach to make sure it all works. Microsoft and Agalia have both been working on the Subgrid implementation for the chromium core to push it forwards faster. Subgrid support is/was easier to implement and maintain on the grid component of their new layout engine (GridNG), so they didn't bother making an implementation for their older layout engine. Google has/had been working on a new layout engine (LayoutNG) for chromium for quite a while. Going further, a search over the ~2k comments shows 47 responses using the word "color" and 168 using the word "nest". Color spaces didn't even appear in the list. Nesting was the third most requested feature.

In fact, I just had a look at the last state of css survey. I'd argue that nesting is much more desired than expanded color support. But scss won't be going anywhere until css nesting has broad browser support. It's more for designers who want to remove the scss build step out of their build stack while still being able to make hue changes (using css' custom properties instead of scss' variables). It's not something that web developers in particular are crying out for just yet. Easy enough to implement, it's just some matrix math in the graphics stack. There's only two things that Chrome is noticeably behind Safari on (Interop-2022-wise). Fun fact: even with the latest release of Chrome, Safari is surpassing Chrome in Interop 2022