Age verification just requires that one be able to provide an age when setting up an account. Like, for example, when you setup an account for your child on the device. This doesn't seem to require any sort of online account requirement as far as I understand it.
It doesn't really matter anymore. When .NET 10 is done, there will be .NET 12 and all your apps will run just fine on it.
.NET framework used to get new versions as well; it's just that it's not anymore. After moving on to newer versions, .NET framework feels clunky now. Also you end up missing out on a decade of new libraries.
> Why wouldn't you program a GUI with a GUI if one is available? Avoiding the use of WYSIWYG editors when making GUIs is like avoiding the use of musical instruments when writing songs.
I've been a developer for a long time; I've built pretty large applications in all sorts of technologies and I now just prefer defining GUIs using text. Having a live GUI preview is great but actually dragging and dropping stuff is not more efficient to me.
To fit your analogy, using source code is like writing a song using musical notation. I'll write the song, then play it, and then go back to notation to fix it or expand on it.
I have also configured my Windows 11 to look and act like Windows 7. I like my taskbar to be a list of open windows with labels. The tray area and the start menu is replicated across all my monitors.
I also have set the classic right-click menus.
There are some things about Windows 11 I like but a lot of it seems to be designed by people who use Mac OS (graphic designers).
"This means reading light data requires zero locks. No mutex, no spinlock, nothing." threw up red flags, and by the time I got to "But here’s the insight" I couldn't go any further.
Maybe the metaverse is a viable concept or maybe it isn't. But Meta doesn't care about the metaverse or the potential users of it -- they simply want their own platform similar to how Google has Android, and Apple has iOS, and Microsoft has Windows. Apple, in particular, is a thorn in their side.
Not caring about what the user's want is the first problem. The second is that they wanted this done yesterday. So rather than evolving the technology and seeing where the market was going, they tried to build the whole thing at once immediately.
They didn't know what they were building, how to build it, and they threw it together as quickly as possible. The result was, unsurprisingly, pretty lame.
Then to justify the expenditure, they then forced it into every aspect of their Quest devices trying to force adoption. Unsurprisingly again, this failed and also pissed off all their Quest customers and damaged the viability of that platform.
Meta thought they could simply spend their billions and that would be enough to succeed.
reply