

Embrace it. Teach these people how to use data URIs to “embed images into the HTML file”, then laugh when they burn even more tokens.


Embrace it. Teach these people how to use data URIs to “embed images into the HTML file”, then laugh when they burn even more tokens.
The compute part of Nvidia’s proprietary driver stack is fine. That is what they historically have been putting their resources and effort towards, since their big customers only care about compute.
The graphics part of the stack is where the problems are.
Their transparency and community involvement outside of the kernel mailing lists is also pretty poor. They read peoples’ bugs reports and feature requests on their forums, but they rarely acknowledge them or give status updates.


The Dunning-Cougar effect. I know this one and I’m never wrong.


Being baited into spending time replying to social media posts questioning the value of your time… you sure showed them, buddy.


Used used, or just used? File caches and memory-mapped files are technically “used” but are basically free since they can be evicted if that memory is needed elsewhere.


Why would they buy property they aren’t going to use? If their rockets did break people’s windows, it would be cheaper for them to settle a lawsuit for the repair costs.


I wonder what the value of an ad nauseum user is…


And even with the overhead of translating DirectX and Windows API calls.


There is ReactOS, which is an ABI-compatible kernel and operating system. That is as close as we are going to get unless pigs start flying.


Good point. I’m not keen on personally comitting fraud, but with the inevitable data breaches in mind, identity verification would do absolutely nothing to deter malicious actors.


Not if they use cryptographic signing.
Browser sends website the signed identity verification, then the website checks the signature against some key in a list of trusted identity verifiers. With the verification responsibility being pushed to the OS vendors, that will be a short list of tech megacorporations. And maybe Canonical or Red Hat, if we’re lucky.


They can’t make it illegal, but with a little frog-boiling, they can make it functionally useless for visiting websites you might need to use. No identity verification = no access, and Linux = no identity verification.


Almost perfect. You forgot to replace “community chest” with “shareholder portfolios”


this is a case where the problem isn’t the corporations: it is the government.
It can be both.
So… it actually makes perfect sense for the companies that dealt with this bullshit to get reimbursed by the christofacists.
If the company ate the cost, sure.
If the company raised the price on consumers to cover the tariffs, the consumers already made the company whole. If the company gets the reimbursement money on top of that, they’re double dipping.
Thanks for correcting me. Considering a long is also 32 bits, a “Long Pointer” being 32 bits makes sense.
Identifying the windows string types is fun. The letters are supposed to have a meaning. Without looking them up, my guess is:
LP_ - Length Prepended
C_STR - C string / null-terminated
WSTR - “Wide” string / utf-16
TSTR - I have no idea
The H in HGDIOBJ could mean “handle to” and if I’m remembering right, GDI is a Windows graphics drawing interface.
Popsicle = should take a seat over there
One-eyed monster = a fan of Austin Powers
The only thing worse than no security is a false sense of security. It’s better for someone to know they’re using an untrustworthy device than to find out the hard way.
If other phones can’t provide an acceptable baseline level of security, the GrapheneOS devs are correct to not support them. Yes, it sucks that the only phones supported are Google Pixels. They have a partnership with Motorola to create a non-Google alternative.
If you still don’t like it, fork it.