14 karma · joined May 10, 2019
I think it's more like building a brain from organic matter that's the real boon. Sooner or later we'll be discarding silicon and extracting neurons from mice just to watch YouTube IX in space with our Tesla corvette cruisers and our alien barmaids serving us Soylent Green in a martini glass!
Skarupke inaccurately defined this as 'mutex vs. spinlock' and an ongoing debate surrounding this as they are comparable, when in no way are they comparable as in userland you simply cannot use spinlocks.
The Windows scheduler apparently doesn't do this, and handles spinlocks better; whatever that means. But the way it works is that spinlocks should work poorly if you run them poorly. Full manual-control of when running a spinlock in userland, you will be scheduled by other things, and you should know that.
That's what Linux is really about. The ability to do something and not have the system "better-ize" it like Windows does by doing some black magic and running an unknown process alongside your spinlock to make it run better.
A spinlock run in userland SHOULD be scheduled by other things, as Linus says. As Linus implemented in the kernel.
It still calls home, it's still online. Lock down Microsoft and Google's IPs permanently, outbound, on all networks you use or this won't work.
It's only sheer force of keeping servers internal that we've had the expertise and knowhow to host our platform ourselves. Now that we're the size that we are, the platform is crazily reliant on hosting it ourselves for administration and liability, so we'd need to have migrated anyway.
Who gets the 'tickets', why are 'tickets' always ruling people, when will 'tickets' be more like working for your own company?
The fact is the tickets themselves are acting like a virtual currency of which only one person gets, exclusively.
If more than one person could work on a ticket this would solve the problem, but the fact that people are locked out and it's exclusive makes them an argumentative point and causes greed/habits to form.
Fix the tickets, not the people. All the credit and satisfaction comes from this one point.
>Less 'idiot-focused' UX
>Better company running it
>Better apps/less locked down 'app store'
>More freedom/choice in phone companies and customisation
>About the same locked-down OS
There's really no other choice
Automation and people trying to have everything 'cloud-based' and 'secure' will probably rely on services not just like this, but like time-saving and squared-away solutions like this.
Businesses had no idea of this back when HTML was invented, and now that we understand how that works and that has become such a task that we would benefit greatly from implementing something to get rid of it, who knows!
I think it's worth a shot to automate something like this, which is already tech focused and surrounded by talent, that automating other things will become closer in scope.
That's what it's all about really, time-saving and automation.