fulafel

18 ms·

481.
by fulafel 1y ago
Terminology nit: An exploit is a technique or automation to take advantage of ("exploit") a vulnerability. So fixing a vulnerability breaks an exploit.
482.
by fulafel 1y ago
Interesting to view this from the POV of the fossil fuel usage rampdown needed because to mitigate the climate catastrophe. It seems that the fact that a lot of people have utility gas over there, and low price of gas due to regulation (no
483.
by fulafel 1y ago
On the other hand the bill of materials of many gadgets is really low while having tight margins. If there are two $100 tablets on the market and the other can advertise a 30% longer runtime weighing 15% more at the same cost, it could be a
484.
by fulafel 1y ago
That's surprising. Do you know what your application memory access pattern is like, is it really this random and the single page io is working along its grain, or is the page clustering, io readahead etc just MIA?
485.
by fulafel 1y ago
Lots of laptops and tablet models could spare more volume and weight for batteries if there was a big cost advantage.
486.
by fulafel 1y ago
I'd argue it's a classic footgun and a flaw of CloudFront (they should at least warn about it much more).
487.
by fulafel 1y ago
> Note that when it’s really thrashing the swap the workload is 100% random 4KB reads and writes in equal quantities. The free memory won't go below a configurable percentage and the contiguous io algorithms of the swap code and i&#
488.
by fulafel 1y ago
This seems cool: > Hardware-enforced privacy > A core principle of Coral NPU is building user trust through hardware-enforced security. Our architecture is being designed to support emerging technologies like CHERI, which provides fi
489.
by fulafel 1y ago
I think you'd get a better reception if you started out talking about a digital forensics scenario, and not a vulnerability. There are a lot of ways to install backdoors and rootkits but the mechanisms used aren't called vulnerabi
490.
by fulafel 1y ago
Wait until you hear about $PATH, $LD_LIBRARY_PATH, $IFS, and so on - or the rest of the OS files in /etc and /lib aside from /etc/ld.preload.
491.
by fulafel 1y ago
Dropping everything is not necessary when porting to Rust, it can be done incrementally and starting with high-risk interfaces.
492.
by fulafel 1y ago
This sounds different from common refcounting semantics in other languages, is it really so in Swift? Usually access increases the reference count (to avoid the object getting GC'd while you use it) and weak pointers are the exception
493.
by fulafel 1y ago
Traditionally if you update the contents of a running binary in-place in Unix you're liable to get a SIGBUS. The way to do it is unlink the existing binary and create a new one with the same name. Which is eg what install(1) does.
494.
by fulafel 1y ago
It's practical enough that this is how it works now in many (most?) parts of Europe at least. Electricity at the wholesale level is priced hourly or quarter-hourly and households often elect to have a correspondingly hourly priced elet
495.
by fulafel 1y ago
If you want to run stuff in Docker as root, better enable uid remapping, since otherwise the in-container uid 0 is still the real uid 0 and weakens the security boundary of the containerization. (Because Docker doesn't do this as by de
496.
by fulafel 1y ago
At first blush it looks like it supports writing C in Python more than going along the grain of the managed nature: status_handle = ffi.new_handle(anari_status) #something needs to keep this handle alive (from https://gith
497.
by fulafel 1y ago
The comment I was responding to suggested Good C Code employes optimizations that, I opined, are more error prone wrt memory safety - so I was not attempting to define it, but challenging the offered characterisation.
498.
by fulafel 1y ago
This shared memory and pointer shuffling is of course fraught with requiring correct logic to avoid memory safety bugs. Good C code doesn't get you pwned, I'd argue.
499.
by fulafel 1y ago
A main reason to do new OpenGL releases was to roll developed extensions to required features of a new OpenGL version to give application programmers a cohesive target platform. The pace of API extensions has slowed down enough that it&#x27
500.
by fulafel 1y ago
That's OpenCL, not OpenGL.
501.
by fulafel 1y ago
.. but people ARE maintaining the implementations and tooling even if the spec might not be getting new features aside from extensions. There's a difference. Look at Mesa release notes for example, there's a steady stream of drive
502.
by fulafel 1y ago
Ok, I had the wrong idea (or out of date?) about Slang, thanks for the correction.
503.
by fulafel 1y ago
OpenGL in the form of WebGL is living its best life. It's the only way to ship portable 3D software across the desktop and mobile platforms without platform specific code paths, thanks to the API fragmentation and proprietary platform
504.
by fulafel 1y ago
That's not "OpenGL is officially deprecated".
505.
by fulafel 1y ago
The caveats: Slang is a transpiled language so you're putting in extra abstraction layers, and there's a difference between what people commonly use for GPU programming in games/graphics vs general compute apps. For example p
506.
by fulafel 1y ago
It has similar (but not identical) behaviour though: >>> for line in StringIO("foo\x85bar\vquux\u2028zoot"): print(line) ... foo bar quux zoot
507.
by fulafel 1y ago
SCTP had some other nails to its coffin too. For example it came from the telco world and so had no end user app buyin and poor dev experience.
508.
by fulafel 1y ago
Yep, this also reflects the design target of GPUs targeting much larger working sets, so have higher main memory bandwidth and rely less on caches. CPUs rather have few fast threads of execution working on hot cached data than many slow one
509.
by fulafel 1y ago
The high arithmetic bandwidth on GPUs is of course SIMD based as well. They just tend to have a ISPC style compilation model that doesn't expose the SIMD lanes in the source code. (Whereas SIMD even after decades is very lightly utiliz
510.
by fulafel 1y ago
> Google told 404 Media that it didn’t receive any warning from the DOJ, but that it “bans apps with a high risk of abuse” Seems to be something else in this case.

More ›