Re: Letter of marque
Dead on, except it wont be the Trump government ... I'd guess a superpac.
893 publicly visible posts • joined 10 Mar 2015
As an exercise to demonstrate that the specified ops model is broken, I guess it makes a point.
But that point is that humans are necessary, and that the entire loop has to be designed to produce quality results.
The "as fast as possible" part is especially significant in producing bad processes.
Confluence has 1% of the useability of word (and this is from a wordperfect fan).
It's the minimum effort they had to put in to avoid word attachements in their db.
Although the potential to migrate away from word is there, trading off word for another non-portable and functionally crippled embedded doc utility isn't going to cut it.
"The majority of what didn't happen in the second quarter was large capex deals at large clients,"
IBM doesn't have anythinh except
Large clients with
large
Capex deals
I'm pretty sure they've outsourced most of their "services" business, leaving them reliant on customer Capex projects.
was to install a supported linux, then distrobox, then the container Linux of choice, and operate out of that.
I did this specifically to avoid relying on windows specific VM management.
This windows API is interesting, but I'm inclined to avoid the MS devstack like I would a vaccine truther.
"It absolutely won't if the drive isn't also disconnected or the throttle closed, neither of which a conventional mechanical brake will do."
This is a flat out lie that contradicts not only decades of global auto design regulation, but decades of people stopping cars on their own, and your own internal logic.
" Arranging content in columns on a desktop browser makes little sense. "
It makes a lot of sense. The old square grid layout from maybe 5+ years ago was the best for visual scanning.
The first, single page was the stories for that day.
The next page was historical, and IIRC both pages were presented in columns sorted horizontally by recency.
Even harder to scan than the uneven-verticals grid format that was instituted a few years ago.
I mostly scan to see the new stories, and I have had no problem finding thematically linked articles from the links in the story (Authors, related stories, related topics, recent stories).
Moving all of that up to the main page is not helping with navigation or readability.
What'r the layout principles and goals with this design ?
No it's not a kill switch, it's a frontal cortex snip.
And it's far far below the sysadmin level. Show me the reverse dependency graph showing how kernel api X is propogated up through Libraries Y1 and Y2 to applications Z1 and Z2 which are running as daemons for app Z3.
Since all core functionality is protected by root, tell me again why we need a kernal api kill switch ?
I guess this could have some uses, but there are signficant manageability problems.
It's not really enough to just kill some apis. You need to know how system behaviour is changed, as well as capability. Otherwise you don't know what you're providing or supporting.
Is the kernel team going to be issuing security advisories with impact statements ?
If it was Windows, you'd simply expect more BSODs. Easy to detect and communicate to end users.
But there's a good chance that Linux will log some complaints somewhere and soldier on in a fashion.
And how do you secure that killswitch against abuse ?