ris

33 ms·

451.
by ris 7y ago
> I am not sure whether bookmarks or signed sections are "extremely useful". Well, they are. You try using a thousand page manual that doesn't have a section outline, or try sending around PDFs whose authenticity is legall
452.
by ris 7y ago
> calling back and forth between C and Python Yes - the trick really is to move your accelerated code away from python's object model, because then you can drop a lot of overhead and also release the GIL. Tricky, though. Out of inte
453.
by ris 7y ago
This isn't quite the same thing, but it is one of the articles that spurred my thoughts on this subject. In cpython, gc != refcounting. Instagram were talking about disabling gc, which would have stopped objects which they weren&#x2
454.
by ris 7y ago
There are myriad ways that PDFs could be re-written and re-rendered, but they would all be quite complicated and/or throw away a lot of extremely useful "meta" information (bookmarks, signed sections etc.) and almost certainl
455.
by ris 7y ago
It's nice that PDF security is getting a bit more attention, but there are a number of things that this approach will trash, for instance, I don't have high hopes for the accessibility of the resulting PDF. (edit: and needless to
456.
by ris 7y ago
> a Python monolith that has one route that is CPU-bound and would otherwise be an ideal use case for a language with real multithreading Sounds nasty. The classic python answer is to try rewriting the innermost loops in cython/c&#x
457.
by ris 7y ago
Thanks for this link - I had completely missed it (I think I was just expecting to disable gc entirely or perform some rudimentary surgery on its linked list)
458.
by ris 7y ago
I don't disagree with any of this but > "Why in the hell would you fork then load, instead of load then fork?" In python it often seems to make little difference. The continual refcount incrementing and decrementing sooner
459.
by ris 7y ago
> Probably better as each function can be in its own language. That sounds awful. How do you share any of your common logic? Do you have to write versions of your important routines once in each language, each with its own set of quirks
460.
by ris 7y ago
RFI. RFI Everywhere.
461.
by ris 7y ago
Search ebay for "used vhs" and start shopping.
462.
by ris 7y ago
Related: rescuing historic teletext pages from VHS recordings of broadcast TV: https://github.com/ali1234/vhs-teletext
463.
by ris 7y ago
> So, essentially he is saying: 1) go ahead and accept the risky thing from your users, and store it right there in your database Yes. It's hard to know what "risky" is when you're taking input. You don't have th
464.
by ris 7y ago
Brain exploded when I realized they're json objects to represent ordered sequences of actions ("quarks"). Good luck if you want to use the same action more than once.
465.
by ris 7y ago
Coincidentally I've actually spent the last couple of weekends putting together a little toolkit to allow fuzzing of cpython bytecode using AFL/AFL++: https://github.com/risicle/cpytraceafl
466.
by ris 7y ago
Similarly in need of mention: Nix/NixOS's `dockerTools` https://nixos.org/nixpkgs/manual/#sec-pkgs-dockerTools
467.
by ris 7y ago
Unless any of your users ever try and use a >72 character password.
468.
by ris 7y ago
Great article. The current state of the art for this sort of thing appears to be https://gnss-sdr.org/
469.
by ris 7y ago
What are we going to do with all these "AI coprocessors" once the AI bubble bursts? Are they at least well documented or flexible enough to be used for more general float crunching?
470.
by ris 7y ago
If it's for storage on optical disks I'm rather fond of dvdisaster ( https://en.wikipedia.org/wiki/Dvdisaster ) which will fill up spare space on a disk with redundant data, specifically distributing it across
471.
by ris 7y ago
The first step is to reject the fashionable "wild-west" style of package repositories and realize that maintained repositories came about for a reason. Then you can worry about rearchitecting your OS for sandboxes up the wazoo.
472.
by ris 7y ago
Sure - just let me take a fork first...
473.
by ris 7y ago
I used to do something a little like this with postgres advisory locks. Worker takes out a lock that signifies it's working on a task, if the worker fails or loses its connection in any way the lock gets dropped along with the transact
474.
by ris 7y ago
Well, enjoy it while it lasts because the GNU toolchain is in the process of deprecating & removing support for solaris 10.
475.
by ris 7y ago
Ok, where does this go when it needs to grow beyond a single machine? Is it time to set up replication? Partitioning?
476.
by ris 7y ago
As neat as this is, I'm not sure I'd recommend this - I'm not sure what the plan would be when it came to scaling.
477.
by ris 7y ago
> So a system like Android's? Not really, I'm essentially describing nix/guix.
478.
by ris 7y ago
I'm quite hopeful for the limited re-introduction of hypervisors to "containment", if only because I've become disappointed with the lack of power app authors have to specify fine-grained, strict security details. This i
479.
by ris 7y ago
> ...preventing devs/ops people to run tools like This is because docker makes the fundamental mistake of conflating packaging with isolation. "Packaging" is achieved in docker by using the OS to do an amount of sandboxing
480.
by ris 7y ago
Well this is the thing I'm confused about, having worked on some cloudfront stuff last month, documents like https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope... gave me the clear impression that e

More ›