8,399 karma · joined September 4, 2016
> We are also reading Little House on the Prairie which I consider a little more “high brow”, and the girls really like that, too. But kids are easy to please and it has been interesting.
Yeah, that's kind of my point :) do you think an AI could write Little House on the Prairie? I don't. Sooner or later the vapid and nonsensical plots from LLMs stop being that amusing, and you need to feel real human connections to the things you're reading. That's the reason you read books, after all.
I don't know who these people are that are reading books so bad that an LLM could plausibly replicate the work, but if that market is killed by a swarm of AI-written nonsense, honestly: who cares?
> Now that AI books exist, the probability that I will ever blind purchase another eBook on Amazon from an unknown author drops to zero.
This is a thing people do? Like... before AI? Not even reading extract or anything? You just see a cover and a title and go like "sure, I'll spend my hard-earned cash to make a 30 hour investment in this thing I know nothing about"?
The best version of this argument you can make is that it's about the treadmill: great writers aren't born great writers, they have to write a lot of crap first to become great writers, and this market is how you do that. Take that away, you don't get any more great writers. But I don't particularly buy that either: there are very few writers I love that were able to successfully make a living selling self-published Amazon eBook garbage until they got good enough to actually be picked up by a publisher.
Journalism, however, is a different story: plenty of great writers (fiction or non-fiction) got their starts as journalists and honed their craft writing small pieces there, and that is a market that is under total threat from AI. That's maybe a cause for concern. But I don't think it's an existential threat to literature as an art form. I don't think that's ever going to go away.
One of my friends loathes everything Apple does (on principle, basically) and has tried several times to convince me that the ThinkPad X-series is just as good (or better) than an M-series MacBook Pro. Testing it out for a bit, there’s just no comparison. Even leaving the software aside, the hardware is just leaps and bounds better from Apple.
Still a cool argument though.
Maybe you can customize it and make it look great, but the "out of the box" experience is just... oof.
"When <card name> enters the battlefield, return target non-land card from your graveyard to your hand".
Both parts of that sentence is always worded the same, so it's probably quite straight-forward to make a parser for this: just have a parse rule for "When <card name> enters the battlefield, <triggered ability X>", with a database of triggered abilities (and their implementation) that include all the ones that have already been printed.
html { filter: invert(100%); }However, in general, I basically agree: for MOST tasks where you need a random number generator, a CSPRNG is probably the right choice and it's a reasonable "default" choice if you don't have good reasons why it shouldn't be. It's a continual annoyance to me that PRNG libraries usually don't include any solid CSPRNGs (looking at you, C++ header <random>) when it's often the right choice.
That's a very silly objection: CSPRNGs can be seeded just like a PRNG. The "P" in both abbreviations is the key, it stands for "pseudo".
Even if that wasn't an issue: this is a bug in C as well! You should absolutely be able to use setenv/getenv safely in multi-threaded C, it's insanity that you can't.
> or if the GIL is removed does the interpreter segfault (I'm pretty sure this latter will not be the case for GIL removal but I don't understand the gil remove plan very much yet).
I haven't looked into the plan in detail either, but presumably not, that would be nuts. My understanding is that they're going to replace the GIL with locks on the objects themselves (your list `l` in this case). This is why in all the tests single-threaded performance suffer, you have to take and release more locks if you don't have a GIL, and the objects themselves grow larger as well.
If you're on Linux, you make .tar.gz or .tar.bz2 or something. Or .zip, I guess you see sometimes. But RAR? That's a windows people thing, in my experience.
Bowyer-Watson (which is described in this article) seems very simple to implement when you start: just start with a "big triangle" and then add points iteratively to it, and perform the flips you need to do. To do it performant, you have to build up a tree structure as you go, but it's not very tricky.
However: almost every description (including on Wikipedia) and implementation of Bowyer-Watson I could find was wrong. There's an incredibly subtle and hard to deal with issue with the algorithm, which is the initial "big triangle". Most people who implement it (and indeed I did the same initally) just make the triangle big enough to contain all the points, but that's not enough: it needs to be big enough to contain all the points in all the circumcircles of the triangles. These circumcircles can get ENORMOUS: in the limit of three points on a line, it's an infinite half-plane. Even if they aren't literally collinear, just close, the triangle becomes way to huge to deal with.
The answer is that you have to put the points "at infinity", which is a very weird concept. Basically, you have to have special rules for these points when doing comparisons, it's really tricky and very hard to get right.
If I were doing this again, I wouldn't use Bowyer-Watson, this subtlety is too tricky and hard to get right. Fortune's sweep-line is more complex on the surface, but that's the one I would go with. Or the 3D convex hull technique (which I also wrote a library for, by the way [3]).
[1]: https://github.com/OskarSigvardsson/unity-delaunay
sqlite> create table x(c1, c2);
sqlite> insert into x values ("a", 1);
sqlite> insert into x values ("b", 2);
sqlite> insert into x values ("c", 3);
sqlite> select c1, max(c2) from x;
c|3
sqlite> select c1, max(c2), min(c2) from x;
a|3|1
sqlite> select c1, min(c2), max(c2) from x;
c|1|3
(note: since SQLite is dynamically typed, no need to specify column types for simple examples like this).Yes you did:
> You must specify the offset from where it should continue
No, you mustn't, you can specify - and it does exactly what you want. The docs are very clear and even provide examples. At some point you should stop blaming curl for your inability to read a man page and admit that you were simply mistaken.