they want to push a lot of buttons on those controls
LOL
Even with a lot of buttons available, good videogame controls are simple and narrow. Natural combinations add depth without overcomplicating things.
they want to push a lot of buttons on those controls
LOL
Even with a lot of buttons available, good videogame controls are simple and narrow. Natural combinations add depth without overcomplicating things.
OS stands for “Oh Shit!”
Notably for CPU only. And on other platforms they already did.
Broadcom would like to clarify that while using KVM for the CPU virtualization, they will continue to rely on all of the existing VMware virtual devices for graphics and other functionality. Also on both macOS and Windows they have migrated to the native CPU virtualization frameworks.
The follow-up quotes
In your specific case, the problem is your employer is on that list [of sanctioned entities]. If there’s been a mistake and your employer isn’t on the list, that’s the documentation Greg is looking for.
we should just write the code how it should be
Notably, that’s not what he says. He didn’t say in general. He said “for once, [after this already long discussion], let’s push back here”. (Literally “this time we push back”)
who need a secure OS (all of them) will opt to not use Linux if it doesn’t plug these holes
I’m not so sure about that. He’s making a fair assessment. These are very intricate attack vectors. Security assessment is risk assessment either way. Whether you’re weighing a significant performance loss against low risk potentially high impact attack vectors or assess the risk directly doesn’t make that much of a difference.
These are so intricate and unlikely to occur, with other firmware patches in line, or alternative hardware, that there’s alternative options and acceptable risk.
Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.
I wasn’t aware the GitHub terms of service explicitly grant / require you to grant permission to fork [within GitHub].
GitHub ToS section License Grant to Other Users
By setting your repositories to be viewed publicly, you agree to allow others to view and “fork” your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).
If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub’s functionality (for example, through forking). […] If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.
oh, that’s a cool website
adds it to bookmarks and search bookmarks
But did it reach test or production environment yet? Or will it die in development environment.
Even C# has something that few people use, but it has something.
Huh? Are you claiming few people use NuGet?
Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave.
What is Tails?
and Tails, a portable operating system that uses Tor
Formatted, so I can read it
Exception in thread "main" java.lang.NullPointerException:
Cannot invoke "String.toLowerCase()" because the return value of
"com.baeldung.java14.npe.HelpfulNullPointerException$PersonalDetails.getEmailAddress()" is null
at com.baeldung.java14.npe.HelpfulNullPointerException.main(HelpfulNullPointerException.java:10)
I think using display: grid;
as your default is the better default, so you’re all set. :)
You are going to get lots of downvotes, and this comment will too.
👀
Hahahahahahahahahahaha
(Pause for breath)
Hahahahahahahahahahaha
Was that tone really necessary? I would have liked your comment more without this part.
It baffles me when people use flex layout when it’s clearly visually a grid layout. Nothing here is flexing with varying element sizes and auto-fill-wrap-break of items.
A colleague of mine prefers flex too. But to me, grid is so much more intuitive and simple.
https://css-tricks.com/quick-whats-the-difference-between-flexbox-and-grid/
For me that’s the wrong way around.
I want to be able to fix the issues I see. I hate it when I can’t.
I’m thankful I am full stack and can do my stuff across borders. I hate the interfaces, waiting for stuff, or being hindered by dissatisfactory (to me anyway) stuff from them. So I’m glad when I have control over the entire stack - from talking to the customer to running production.
Anything I don’t have control over - most if it doesn’t get done, the rest can be okay or bothersome.
I hate that I don’t see what the admin set up and does on the infrastructure. It makes it harder to assess issues and potential issues and how they could correlate with infrastructure changes and activities…
one steering wheel to steer left, and one to steer to the right