Just go write your own Android then?
kogasa
joined 1 year ago
They’re not taken for granted, they are compensated by the corporations I’m purchasing the device from.
You're taking for granted the requirements that need to be met in order for the device you're purchasing to be technically and commercially viable. It needs to work, it needs to be safe, it needs to comply with privacy regulations and so on.
Again, these problems have already been solved on desktop for decades. They’re not breaking new ground here.
Managing complexity with containerization and sandboxing is occurring on desktops too. It's more mainstream in the mobile ecosystem because of essential differences in the ways users interact with phones versus desktops.
The people who build the device and software ecosystem you take for granted.
All of that interest is from people making computers,
like the people who make phones for other people to use
The desktop solution isn't feasible in the mobile context. Even for desktops, you see an increased interest in reproducible/containerized/sandboxed environments with docker, flatpak/snap, immutable operating systems, and so on. It's all about managing complexity.
The right design decision isn't necessarily the best for a specific use case. Making the system overall rigid and strict by default makes the whole thing more manageable. Adding features like "user initiated opt-in shared filesystem access for sandboxed apps" increases complexity, hence cost and maintenance burden and likelihood of bugs. Not to say this feature isn't worth it, but it's necessary to accept some rough edges in some use cases.
Sandboxing is a good thing. It makes it a lot easier and safer for billions of devices to run millions of apps.
Yes... But ASP.NET Core kept the branding. Thus "Core" still exists, concurrently with the regular ".NET."
I have no complaints about just calling it .NET. The distinction between .NET and .NET Framework isn't much of a problem. It's the fact that .NET and .NET Core aren't actually different that's odd. It underwent a name change without really being a different project, meanwhile the Framework -> Core change was actually a new project.
Not an intern, but this week I've unraveled some mysteries in ASP.NET MVC 5 (framework 4.8). Poked around the internals for a while, figured out how they work, and built some anti-spaghetti helpers to unravel a nested heap of intermingled C#, JavaScript, and handlebars that made my IDE puke. I emulated the Framework's design to add a Handlebars templating system that meshes with the MVC model binding, e.g.
@using (var obj = Html.HandlebarsTemplateFor(m => m.MyObject))
{
Name: obj.TemplateFor(o => o.Name)
}
and some more shit to implement variable-length collection editors. I just wish I could show all this to someone in 2008 who might actually find it useful.
The attention paper from Google introduced transformers, OpenAI introduced generative pretraining as a technique that allows transformers to achieve very good performance on downstream tasks with very little additional fine tuning. This paper and the subsequent release of the pretrained GPT models directly lead to the LLM boom.
Decentralized SSO on the other hand has the potential to be both convenient and privacy respecting.