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.
kogasa
joined 2 years ago
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.
That soap says a lot of things.
No, this is insanity. Mod-tap has an inherent delay. Using it for anything but the most rare operations (like "shutdown") would drive me crazy. If you can't reach mod keys, unless you're arthritic or have otherwise reduced mobility, change your technique instead of doing this.
The only substitution I do is to replace Caps Lock with Super and Super with Escape, plus standard F key mappings when using a <75% and arrow key mappings on 60%.
You can clean cups with straws on the regular with antibacterial denture cleaning tablets
Of Mice and Men
The analytic continuation of KB(x) to the complex plane subject to a superconvexivity constraint is unique but doesn't necessarily have a straightforward geometric interpretation
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.
Not true at all, lots of wireless mice with durable optional cables.