orf

10 ms·

151.
by orf 7mo ago
> Obviously you can't just put hardcore porn on Isn’t the thing that actually stops you from doing this just an ad-hoc, informally specified and bug-ridden implementation of Clearcast?
152.
by orf 7mo ago
The first 3 “hardening” points are not great. Essentially it’s just: remove .py files an execute del os.environ[“SESSION_TOKEN“]? This doesn’t really sound very secure, there are a number of ways to bypass both of these. It’s just security
153.
by orf 8mo ago
That’s still over-general to the point of being useless. What you wrote would apply to a human approaching this task as well, sans the “many trillion lines of code”.
154.
by orf 8mo ago
Like life, things should default to being safe. Unsafe, unexpected behaviours should be exception and thus require an exceptional name. Legacy and backwards compatibility hampers this, but going forward…
155.
by orf 8mo ago
So we shouldn’t mark anything as unsafe then? And give no indication whatsoever? The issue isn’t that the word “safe” doesn’t appear in safe variants, it’s that “unsafe” makes your intentions clear: “I know this is unsafe, but it’s fine bec
156.
by orf 8mo ago
yes, and bugs shouldn't exist because everyone should be familiar with everything.
157.
by orf 8mo ago
because the "unsafe" suffix conveys information to the reader, whereas `innherHTML` does not?
158.
by orf 8mo ago
Name. And. Shame.
159.
by orf 8mo ago
How does this work with more complex authentication schemes, like AWS?
160.
by orf 9mo ago
the query is just to highlight that relevance is a complex topic. few people would consider "perl blog posts from 2016 that have the stack overflow tag" as the most relevant result for that query.
161.
by orf 9mo ago
Sure, but the point is results are not relevant at all? It’s cool though, and really fast
162.
by orf 9mo ago
Number of docs isn’t the limiting factor. I just searched for “stackoverflow” and the first result was this: https://www.perl.com/tags/stackoverflow/ The actual Stackoverflow site was ranked way down, below some w
163.
by orf 9mo ago
Agreed, but not relevant to my comment.
164.
by orf 9mo ago
None of which is relevant to the point I was making. Try to focus your thoughts, they are obviously pretty scattered.
165.
by orf 9mo ago
When was the vote on deciding if murder is good or bad? “Society” doesn’t vote on things. Your viewpoint may differ, but a large enough majority of other people feel differently. In other words, it’s a you problem.
166.
by orf 9mo ago
> StageExecution(ref_id="t3", requisite_stage_ref_ids={"start"}, > … Your UX is important in a tool like this: using “needs” instead of “ requisite_stage_ref_ids” would be a pretty big improvement.
167.
by orf 9mo ago
You can look at the authors LinkedIn page and see that he’s never worked for a startup. The only job he’s had for more than 14 months was at Huawei. I’m pretty sure this is all completely fabricated LLM slop, created as a vehicle for the “h
168.
by orf 9mo ago
Sure, and this is completely sensible to do in a library. But that’s not the point: what can most applications do when SQLite tells them that it encountered a memory error and couldn’t complete the transaction? Abort and report an error t
169.
by orf 9mo ago
You need to apply backpressure before you hit memory limits, not after. If you’re OOM your application is in a pretty unrecoverable state. Theoretically possible, practically not.
170.
by orf 9mo ago
None of that matters: what is your application going to do if it tries to allocate 3mb of data from your 2mb allocator? This is the far more meaningful part of the original comment: > and furthermore most code is not in a position to do
171.
by orf 10mo ago
In the world of confusing landing pages, this project is a piece of art: what the fuck does any of this mean > EXCITABLE. EXACTABLE. EXECUTABLE. A shared universe of destinations and memory. > Space is a SaaS platform presented by P
172.
by orf 1y ago
Interesting read, but I feel like they should have also benchmarked using COPY with Postgres. This should be far faster than a bulk insert, and it’s more in line with what they are benchmarking. The omission feels… odd.
173.
Fedora SIG changes Python packaging strategy(lwn.net)
4 points by orf 1y ago|0 comments
174.
by orf 2y ago
I maintain a project that publishes a SQLite file containing all package metadata, if you don’t want to use BigQuery or the API to do this kind of analysis https://github.com/pypi-data/pypi-json-data
175.
by orf 2y ago
What giant hoops? I’m interested in reading more
176.
by orf 2y ago
Christoph Hellwig seems fun to interact with. He drive-by posts the same, repeated points and seemingly refuses to engage with any replies.
177.
PMF or Die(pmfordie.com)
3 points by orf 2y ago|1 comments
178.
Biases in Apple's Image Playground(giete.ma)
43 points by orf 2y ago|19 comments
179.
by orf 2y ago
> Crash a wedding. You are not a nuisance; you are the celebrity guest! Urgh. Really?
180.
by orf 2y ago
It sends the output of “git ls-files” to the telemetry server?!?! Who thought this is appropriate.

More ›