Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dooglius
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
45 ms
·
571.
▲
by
dooglius
6y ago
Presumably, (1) he wants the software to run as within-container root and (2) since this is work-related, he has a limited degree of trust that it at least won't actively try malicious activity like trying to break out of the container
572.
▲
by
dooglius
6y ago
Couldn't repro. What's the censored part of your image? I don't see anything there, maybe it's relevant.
573.
▲
by
dooglius
6y ago
clickbait, the decision by the professor was overridden by the university as it says at the end
574.
▲
by
dooglius
6y ago
The articles defines its sense of commutation as "meaning that if the two changes could be written without knowledge of each other, they can be applied in any order" But, this seems to require semantic level understanding of the c
575.
▲
by
dooglius
6y ago
Except, of course, for ads officially purchased through it
576.
▲
by
dooglius
6y ago
Even in your heavily contrived example, I can think of cases where the optimization isn't what the programmer wants. For instance, I might have a special handler via userfaultfd(2) that detects if I'm doing an increment of the nul
577.
▲
by
dooglius
6y ago
The simple solution to me seems to be to just ban use of loops hierarchically between a defer statement and a guard block. The guard block should definitely be kept as using scope seems like it confuses and complicates the notion of scope;
578.
▲
by
dooglius
6y ago
Some commenters are claiming this issue can be worked around by using by-reference capture, but the following code still requires dynamic allocation: void reverse_bitstream(void * read_ctx, void * write_ctx) { guard { while(ha
579.
▲
by
dooglius
6y ago
I just noticed the difference between what the manufacturer advertised and what the BIOS provided. Maybe I'll do a write-up of what I did at some point, but it's highly non-portable, and somewhat unsafe. Generally, the BIOS is sup
580.
▲
by
dooglius
6y ago
Actual physical memory. I actually have a hack in order to reclaim and use some of this on my laptop.
581.
▲
by
dooglius
6y ago
Are you sure it's dmidecode that's wrong, and not the DMI itself? dmidecode just parses what's given to it by the BIOS.
582.
▲
by
dooglius
6y ago
If you have certain GPUs, it can be multiple gigs stolen as that's set aside for video memory
583.
▲
by
dooglius
6y ago
What's the desktop equivalent of Uber?
584.
▲
by
dooglius
6y ago
For "TFA", see e.g. https://news.ycombinator.com/item?id=19781756 > so could torrent clients, not sure what's different really This is precisely why the developers' attitudes do matter. The differen
585.
▲
by
dooglius
6y ago
It's more that just the protocol though. TFA links directly to the IPFS Desktop Client, which certainly can have an attitude e.g. if a future update blocks this project. That risk doesn't really exist for any mainstream torrent cl
586.
▲
by
dooglius
6y ago
That's fair, BitTorrent v2 does solve this problem, but I can't say I've seen any v2 torrents around (not that I'm specifically looking)
587.
▲
by
dooglius
6y ago
A strange choice given that distributing copyrighted materials violates the IPFS Code of Conduct [0]. Why not use BitTorrent whose attitude toward copyright is much more in sync with libgen's? [0] https://github.com/ipf
588.
▲
by
dooglius
6y ago
You seem to be implying it didn't work, but how do you know? Sure, the other person didn't go "I admit defeat", but the ideas can sit and percolate. Also, your messages may have had an effect on lurkers.
589.
▲
by
dooglius
6y ago
It says >Instead, we strongly encourage you to use one of the very good software licenses which are already available But as far as I am aware, there are no comparable software licenses that prohibit commercial use. So, the CC NC license
590.
▲
by
dooglius
6y ago
Universal Instantiation
591.
▲
by
dooglius
6y ago
https://rosettacode.org/wiki/Ackermann_function#Stackless_it...
592.
▲
by
dooglius
6y ago
> we try to piece together the truth from all the sources and from what isn't said I'm skeptical that this can be done effectively
593.
▲
by
dooglius
6y ago
Sounds like the two of you may be "harbinger customers", the interesting economic phenomenon of people who tend to like products that flop.
594.
▲
by
dooglius
6y ago
Roughly, what you shouldn't be able to do is distribute a product with that requires a contract in order to build upon it or extend it. You'd have to tease out the nuance of this more in legalese for sure, but that's the gist
595.
▲
by
dooglius
6y ago
> The bios allowed me set up my own keys which I use to sign the kernel Not all manufacturers allow this, and even then, it adds considerable user complexity to have to do this to install Linux, as opposed to a normal liveUSB GUI flow, n
596.
▲
by
dooglius
6y ago
What about procedural issues such as the bundles of documents in the morning?
597.
▲
by
dooglius
6y ago
I think you are taking an overly strong reading, I highly doubt the author would say that writing to stack memory is reasonable unless the address has explicitly been taken with &x
598.
▲
by
dooglius
6y ago
You can "obtain the address", whatever that means, but that does not mean it's well-defined behavior to change the data in said address.
599.
▲
by
dooglius
6y ago
You're either coming up with a huge strawman, or you're confused about what the post means. Pointers being integers does not mean that writing garbage to any random integer you come up with has well-defined semantics. In any case,
600.
▲
by
dooglius
6y ago
IIRC most of the nVidia codebase is platform-agnostic with small bits that shim to the underlying OS, rather than developing two entirely separate codebases.
More ›