I wish Microsoft would treat GitHub a little differently. Leave it alone and let it be it's own thing. Maybe if enough customers leave they will backtrack.
As a long term GitHub customer, I see many practical and personal reasons to move away from the platform. I've seen a handful of similar posts lately. A few years ago this would have felt totally fringe, but now all of a sudden it really doesn't. For now, for me and many others GitHub still works great, and is very convenient. But the alternatives are getting even easier to self implement all the time.
Microsoft did that for a lot longer than I expected honestly. Historically they would take a year or so before giving up on the "you're an independent company" bit and merge the team into MS orgs.
GitHub pulled it off for 5ish years before that began to change, and it was only last year when they stopped having their own "CEO".
The post does a great job at explaining some of the details consumers often overlook. Especially in regards to sensor size, light and accutance.
The best camera is the one you have with you. And this is why smartphones are so great, but the author also does a great job of expressing the limitations and problems.
I've worked as a professional photographer and videographer when between work. I've owned pro Nikon, canon and currently roll with some bonkers expensive leica gear. What makes smartphones so special as cameras is how easy they are taking unobtrusive photos of friends, family and kids. There are few things more frightening to me than a kid charging my way to rip the leica out of my hands because it looks so interesting. They don't do that with smartphones. Smartphones are especially stealthy because it's not clear what the user is doing with them. They could be just browsing the web or whatever. Are they taking video? Or a photo ect.
This is why I ended up picking up an (admittedly quite expensive) Ricoh GR IV. It's tiny enough to take with me everywhere, has a modern APS-C sensor and great IBIS.
In my experience as a web component library builder, writing and maintaining web components is the easy part.
Getting them to work well in various react and angular codebases is not easy. New versions of React work well with web components. Old version s of react need web component wrappers. Angular works out of the box with web components (aside from some quirks and sometimes encapsulation issues with the web components). However, web component form controls will not work with angular reactive form controls and require an implementation of the control value accessor interface. So if you're a web component form controls you need some kind of intermediary layer to play well with angular forms.
Problems tend to surface with testing infrastructure as well, especially in older codebases running Jest or other jsdom based testing frameworks that don't recognize the web component apis well (shadowDOM, elementInternals, ect). Upgrading to vitest with browser mode can solve these problems, or writing lots of mocks.
As a long term GitHub customer, I see many practical and personal reasons to move away from the platform. I've seen a handful of similar posts lately. A few years ago this would have felt totally fringe, but now all of a sudden it really doesn't. For now, for me and many others GitHub still works great, and is very convenient. But the alternatives are getting even easier to self implement all the time.
reply