366 karma · joined July 21, 2016
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/161 https://gitlab.gnome.org/GNOME/mutter/-/issues/2166 https://www.reddit.com/r/kde/comments/vgqyv2/wayland_nvidia_... https://gitlab.gnome.org/GNOME/mutter/-/issues/1891 https://forums.developer.nvidia.com/t/external-monitor-doesn...
I have learned my lesson, and will NEVER buy another nvidia product, not worth the trouble.
In short, the 4,500 year old date is based on very, very thin evidence, and much other evidence of longer timeline is simply ignored because "it's not possible".
Could not agree more. I was using mac's for a decade prior to buying thinkpad X1E a couple years ago. It's been an absolute disaster and I now loath them. Multiple years after purchase, the only distro I could find that even half works is Fedora.
Docking is worse, even under windows. So the dock was working under linux for a while but as a last week it's completely non-functional, no usb, no display. Under windows, probably 25% of the time the USB devices don't function on startup, and have to be unplugged and plugged back in. I was trying to run a monitor with hdmi and it would half the time not wake up. Switched to display port and it's a little better but still problematic. And if your computer goes to sleep, it's 5-10 minutes of trying to wake and often requires hard power cycle to come back. I had to set the computer to sleep only after 2 hour or so. This is with all firmware and os updates applied.
In the future, will be be selling these hot messes, and moving to a framework laptop. Doubtful I every buy another thinkpad, I have many fond memories of my first couple of IBM based thinkpads those were awesome machines.
Yes would agree and see them as platform related. It's just too large a task to create from scratch. Like say on JVM you can compile to bytecode and have strings already built into platform, and java.time, and ability to access an ecosystem of libraries.
With zig could one could use c or rust libraries?
How suitable is zig for such a task compared to say rust?
Tokenization. Exchange the data for tokens, and store the sensitive data someplace very secure separate from the main operational system. To process a delete, delete the token. Ideally this is handled via proxy, so it's a completely separate system from primary app.
Having used this method, I feel it ought to be used for every app storing sensitive data.
edit: I forgot to mention the biggest issue I have with crypto shredding (encryption per record) is that you can't correlate data between records as you can with tokens.
I have to agree. Are there any open source package managers similar to cargo?
I can't tell you how many times over the years I've seen tens of millions of rows of sensitive data(e.g. ssn) sitting in databases unencrypted. Software devs as an industry really needs to take this more seriously, but often businesses simply will not allocate the funds to do this right because of minimal risks to the corporation. At least with PCI the companies are forced to take card data security seriously.. but for instance nacha data, not nearly as much.
Absolutely the way to handle sensitive data in every app, so much so that I'm working on an open source version.
Absolutely agree, it's just a core technology, which enables new model of operation, on which all that is necessary to run. Right now there is almost nothing.
> If you want to start faster than containers, you already can — by not using containers.
Only if don't care about security/isolation. WASM is strongly sandboxed. It's appropriate for multi-tenant systems, where containers/jvm/etc have to be run inside of virtual machines(e.g. firecracker) to get acceptable isolation.
> I suppose that's too slow for serverless cold start
Yep, half a second is way too slow for new instance per request. I think wasm startup time around 35 μs for lucet.
WASM has near instant startup, making a cold start for each request feasible. I think this could be a key property/advantage that makes it preferable and more economically efficient in the long run.
WASM I think has a stronger sandbox as well. Containers in a multi-tenant environment need to run inside a virtual machine. WASM can be run in multi-tenant without the need to isolate each tenant in a virtual machine, again making it more efficient in long run.
edit: also recalled a relevant tweet from creator of docker https://twitter.com/solomonstre/status/1111004913222324225
Native AOT is on the roadmap for net7 which is good but very minimal support. For instance asp.net mvc is a non-goal (https://github.com/dotnet/runtime/issues/61231), so probably another 3 or 4 years before it's well supported.