skysight-inc/HackerNews huggingface dataset:
The novels have existed basically since the beginning, though tying them to a set may not have been there at the start. But if not, it was still very, very near the beginning, with the Weatherlight saga.

I both played and read Invasion through Fifth Dawn, and while the quotes never appeared verbatim, some of them could be pinned down to specific events. One of my favorite easter eggs was learning that the Blind Seer from Invasion [0] was actually Urza in disguise... which fits that flavor text perfectly.

[0] https://gatherer.wizards.com/pages/card/details.aspx?name=Bl...
>> OK so then does YAGNI apply to investment? Why not let existing firms handle it in the S&P?

Yes, don't rebuild your own balanced portfolio or pay someone to "beat the market" for you; just buy a COTS ETF, put it in the server closet and forget about it for a decade.
This seems to overstate the difficulty in implementing CQRS, and by that I assume you mean event sourcing. Kafka is definitely not needed, or even necessarily a good idea, nor is a PhD.

I'm not sure what you experience with CQRS has been but CQRS is not a solution for scale it is a solution for long-term maintenance costs of a growing codebase by enforcing the decoupling of services.
The disdain some developers tend to have for their data storage system is pretty unreal. It’s like they see it as a necessary evil instead of their friend.

They often react to FK’s as if they cramp their style, where their style is to just insert whatever into the database without regards for what And where it is.
OpenWrt community is proud to announce the first release candidate of 19.07
The OpenWrt community is proud to announce the release candidate
of the OpenWrt 19.07 stable version series. It incorporates
over 3700 commits since the previous OpenWrt 18.06 release.

In this release the OpenWrt project brings all supported targets back
to a single common kernel version and refines and broadens
existing device support. It also provides initial support for the new
ath79 target, the future device tree based successor of the popular
ar71xx target.

Selected highlights this release
* Updated toolchain:
* musl libc 1.1.24
* uClibc-ng 1.0.31
* glibc 2.27
* gcc 7.4.0
* binutils 2.31.1
* Updated Linux kernel
* 4.14.151 for all targets
* Flow offloading bugfixes
* Network userland:
* Fixes in network and wireless configuration handling
* Bugfixes in DHCPv6 client and server
* WPA3 configuration support
* System userland:
* Sysupgrade support for backup and upgrade capability checks
* Bugfixes in the process manager, system message bus, embedded web
server and the configuration management library
* Platform and Driver Support
* Dropped adm5120, adm8668, ar7, au1000, ixp4xx, mcs814x, omap24xx,
ppc40x, ppc44x and xburst targets
* Updates and new device support across all targets
* Web interface:
* Client side rendering of views for improved performance
* Security fixes

For a detailed list of changes see https://openwrt.org/releases/19.07/changelog-19.07.0

For latest information about the 19.07 series, https://openwrt.org/releases/19.07/

downloads
https://downloads.openwrt.org/releases/19.07.0-rc1/

Have fun!
The OpenWrt Community
It's definitely asking for trouble. Murphy's Law.
No problem!

The summary is basically this: if you say that a User has_many foos, then the foos table will have a user_id in it. When you ask for the foos a user has, the SQL will be emitted that has the "user_id=1" or whatever clause on it.

If you add a foreign key constraint, the database itself will verify that the foos have valid user_ids. If you don't, then it won't. You're basically giving up the ability for the database to verify the relationship for you. Like any kind of checks, this is more restrictive, but you get some value out of it. The question is, is the validation worth the restrictiveness. The OP comment argues no. Many would argue yes. It really just depends.
I think monopoly is a bit of a misnomer here. There's certain levels of market power at which you no longer need to cut corners to make a profit, and at that point the right thing to do is pay it forward. Start treating everyone better. Amazon obviously isn't doing this, and are instead taking a more parasitic route and I think monopoly or not, people are fucking tired of the whole "legally right but ethically wrong" thing.
Er, what? Foreign keys are not necessarily a net performance cost. Depending on the scale of the database, they can be essential for fast queries.
But I Had Always Wanted to Be a Dad
> Index usage: Go allows to loop over elements instead of indexes and also provides the correct range of indexes in for-loops. More functional expressions would mystify execution, while Go is more WYSIWYG of languages.

Indexes are the default though, you have to explicitly ignore them if you want to use the values directly.

More importantly, there are several simple operations that simply require indexes: most error prone is trying to create a pointer to an element in a slice. The natural, high level way of doing that would be

pointers := []*element{}
for _,value := rang elements {
pointers = append(pointers, &value)
}

Which looks very nice, but does the completely wrong thing. You absolutely must use the index version of you want to do this. Same would be true if you were to capture the value in a closure.
Sure, every little bit helps. But to avoid long-term catastrophe we have to get net carbon emissions down to pre-industrial levels. A 50% reduction sounds good on paper, but it's a trap. Suppose we achieved it. Then what? We're still increasing the overall CO2 concentration, just at a slower pace. That won't help us avoid catastrophe, it just delays it for a while, and probably not for very long. LNG is not a step towards a solution, it's a detour that leads back to catastrophe by slightly longer route.
You popped a shell, therefore it wasn't a true safety critical system.
> This is exactly backwards. A monad is not a design pattern - a design pattern is an awkward manual reimplementation of a monad (or another category).

This isn't correct either. Design patterns are simply cocategories.
Exactly. I always felt like the world of magic was bigger than my imagination of it, that the cards were a tiny window into an unfathomably strange world. "Eldritch" is maybe the best word I can think of to describe it.
Saw this comment on Reddit:

>I went searching for more reliable sources on this and found this story from AP: https://apnews.com/9ca1c29fc9554c1697a8729bba4dd93b

It's from 2018 but it does back up the idea that there is a program where China places party loyalists in the homes of Uighur Muslims in a program called "Pair Up and Become Family." It also briefly mentions bed sharing.
In RethinkDB, a table can be split into shards and each shard has at most one master and multiple replicas. With one master to perform all writes for a shard, there is no need for a co-ordinator. If the master of a shard goes down, a replica can be promoted as the master. For writes, RethinkDB prioritizes consistency over availability so a server failure may carry some downtime in terms of writes but reads can be configured to be highly available (though they could potentially be out of date).

But there is definitely a downside that if a RethinkDB master server fails immediately after a write (before it propagated to a replica) and does not recover, then there can be some data loss (but only the most recent writes on that shard).
You think an ordinary person's expectation is that It's A Wonderful Life is public domain? I think the opposite thing is true, and that most Americans generally assume that any major motion picture or television show is copyrighted no matter when it was produced.
I mean most of this in a devil's-advocate sense:

The proper economic arrangement for those who wish to make a living with creative works is patronage. Someone asks you to make something, you make it for them, then you get paid. You then don't get paid until you make another work.

Thus content creators shouldn't have an automatic entitlement to get paid each time someone reads/listens to/watches a work.

If you work once, it's only fair for you to get paid once. The idea of royalties that pay beyond the initial act of creation is unfair because you should not get paid to do nothing.

Copyright is meant to be temporary scheme to encourage creative works. It is not meant to establish ownership over non-physical goods like music, art, etc. though it is definitely currently abused to be that way.

I guess at some point in history we needed copyright to encourage more creativity, but honestly look around you - we are saturated with so much intellectual property. So many movies, software UIs, rehashes of rehashes. Does society really need/benefit from the incentive of copyright/royalty any longer? It seems only entrenched legacies are significantly benefiting currently.
Known issues:

* Sysupgrade from ar71xx to ath79 and vice versa is not officially
supported, a full manual reinstall is recommended to switch targets
for devices supported by both ar71xx and ath79
* Images for some device became too big to support a persistent
overlay, causing such models to lose configuration after a reboot.
If you experience this problem, please report the affected device
and consider downgrading to OpenWrt 18.06 or using the Image Builder
to pack a smaller custom image
* Some optional GUI packages crash with an error about missing
"cbi.lua", install the "luci-compat" package to fix these
* Any outstanding issues reported at https://bugs.openwrt.org/
$400/month and multiple cloud instances sounds like overkill though. The same could probably be achieved with a Raspberry Pi or Intel NUC on your home network. Maybe an RPi wouldn't be great for multiple reencodings, but I don't think that's really needed. How often do you really want to watch low resolution TV-series on your mobile data connection?

One feature I haven't seen on any commercial service is the ability to integrate with your IMDb watchlist, and automatically download "Linux ISOs" when they become available.
Technically all they really need is different UPCs. Appliance and electronics manufacturers have been doing this for decades so Walmart or Target can have "exclusive" items.
In theory but this would be a great way to see how many customers you can lose in a quarter.
Being able to view logs based on the name of the service instead of the name of the logfile. `journalctl -u <unit>` vs `less /var/log/service/something.log`

Being able to specify date ranges instead of grepping around multiple files. `journalctl -u <unit> -s <start> -e <end>` instead of horrid combinations of grep and gzcat.

"Okay," you say, "but that's all for logs on the host. Shouldn't you be using Splunk or an ELK stack?"

Journalctl can export logs in a json format that can be natively consumed by splunk for free metadata markup. I wrote some container sidecars to do exactly that, and it worked great.

The only thing I don't like about journalctl is that it doesn't line wrap by default.
>> “One of the underlying premises of the game,” he said, “is that there’s supposed to be a very simple set of rules and all the cards are exceptions. Every card allows you to break the rules at some point. That’s how I think of it.”

That's Garfield of course and it's his game, but I think it's more accurate to describe the game as an abstract machine and the text on the cards (the "ability text") as its inputs that change the machine's state. Seen another way, the ability text language is the scripting language of the game's rules engine.

The language itself is fascinating. Formally, it's a Controlled Natural Language, but I doubt there is any other CNL that has been in constant use by so many people, while undergoing so many changes to its syntax and vocabulary.

Consider for instance the ability text of the card, Stasis, discussed in the article:

Players do not get an untap step.
Pay {U} during upkeep or Stasis
is destroyed.

That was what was printed on the card in its original, Limited Edition Alpha printing. The same text is now listed as follows on The Gatherer, Wizards' of the Coast M:tG online card database:

Players skip their untap steps.
At the beginning of your upkeep
sacrifice Stasis unless you pay
{U}.

Note how the original card uses "destroyed" while the new text uses "sacrificed" to describe what happens if "you" (the player "controling" Stasis) does not pay {U} (one blue mana) during your upkeep step. In short, "destroy" and "sacrifice" now have different meanings. In particular, while both abilities ultimately move a permanent from its controller's Battlefield to its owner's Graveyard zone, "sacrificing" a permanent doesn't "destroy" it, so effects that replace destruction (like regeneration) cannot prevent a permanent from being moved to its owner's graveyard. Neither can "Indestructible", an ability that precludes destruction, prevent sacrifice.

So the ability text language started very loose and informal, a language aimed to help players understand how a card is meant to be played, but over time it has morphed into something else entirely, a precise formal language that leaves no room for ambiguity, given of course a good knowledge of the rules.
> I’m pretty confident that GitHub doesn’t use foreign keys because it was built as a Rails app

Maybe originally, but lack of foreign key usage is certainly not Rails specific today. Large MySQL shops generally don't use foreign keys, full stop, for the exact reasons Shlomi described in the original comment.

Facebook does not use foreign keys either. In my experience, same thing is true at all the other large MySQL-based companies. And those companies make up a majority of the largest sites on the net btw -- including most of the consumer-facing social networking and user-generated content products/apps out there.

This does not mean that, for example, Facebook is full of data that would violate constraints. There are other asynchronous processes that detect and handle such problems.

> If you get to a point where sharding is best for your company you hopefully have enough revenue coming in to fund a data transition.

Do you mean, stay with your current RDBMS of choice and shard while also removing the FKs? Or do you mean transition to some other system? (and if so, what?)

The former path is bad: sharding alone is very painful even without introducing a ton of new application-level constraint logic at the same time.

The latter path is also bad: only very recent NewSQL DBs have sharding built-in, and you probably don't want to bet your existing rocket ship startup on your ability to transition to one under pressure. Especially given much higher latency profiles of those DBs, meaning a very thorough caching system is also required, and now you have all the fun of figuring out multi-region read-after-write cache consistency while also transitioning to an entirely new DB :)
GateKeeper is becoming onerous for Mac developers who maintain free applications, who don't want to pay a yearly fee to Apple. Telling users a program is damaged because this fee is not paid and moving it into the trash is now the default.

This is a free prefpane that can hide the cursor anywhere via hotkey or idle timer. It's fairly popular. I've written and maintained it since 2007. Try running it in Catalina. http://doomlaser.com/cursorcerer
Please don't spam the app store with redundant Electron-hosted web applications. Just tell me the URL so I can load it in my (non-Google-compromised) web browser, or use the OS' native web frameworks so I don't have to waste hundreds of megabytes of disk space.
One of the greatest lies perpetuated in America is that billionaires should pay less taxes than the average person because one day, you too could be a billionaire, and you wouldn't want to become less of a billionaire because of taxes.
Safari doesn't use private APIs. WebKit does.

And WebKit is a fundamental OSX library used for many purposes.
If I pay for streaming service Z but don't like their streaming tech or the geofraphical restrictions they put on show Y that I was watching while traveling, I feel that there's no ethical harm happening if I obtain a copy of Y for private storage. It might not be legal or might be in violation of ToS, but personally I wouldn't call this theft. Would you agree?
While we’re at it: should databases handle transactions or should we let the application deal with it all?

IMHO The answer is the same for this as with foreign keys.
It wasn't "Google", but a handful of employees there. Secondly, they designed or with their perceptions of some of Google's use cases, which may or may have not aligned with the actual use cases. We can see this by how much golang is actually being used at Google for critical components, where C++ and Java still dominate
>but AFAIK there is no standard alternative way to calculate those "losses"

This isn't the problem at all. The problem is that they're calling them "losses", when they aren't losses at all. "Lose" is a plain English word with a very specific meaning: it means you no longer have something that you used to have. These companies never, ever "lost" anything at all due to "piracy". You can't use the word to describe "something you don't have, and never had at all, but which you should have"; it doesn't work that way.

If they used a different term, such as "unrealized revenue", then we probably wouldn't be having this discussion.
So now you have just created a many-to-many relationship. Due to a bug in software, a child could now be linked to multiple parents, or even no parents. Part of good database design is preventing corruption of these sorts of relationships.

> I think it's more about the expressivity of pointers and arrays compared to the "backwardness-feeling" of index lookups.

Greater expressivity in ways to store bad data is never a good thing.
> use their weight as "the most popular programming language" to get platforms to conform to whatever they want

I'd rather have an open committee tell a big corp what they have to do than the other way around.
Personally: Part of what I buy from Apple — the “job” I “hire” them to do — is curation.
The introduction alongside Mirrodin made sense IMO, but I really hoped they would revert after that. I also lost interest around the end of Mirrodin / start of Kamigawa.
Nothing Matters
My WireGuard server hosts my DNS server which NXDOMAINs all social media and ads for my machines.

If I really want to see what's up with some mess like this, I at least need to spend the 15 seconds it takes to turn WireGuard off.
>they simply don't have the resources to put up any kind of legal resistance to this type of judicial pressure

a very simple solution to this, don't keep the data once you've provided a service to the customer. Or anonymize it and scrub any association.

It's never a question of "we don't have the resources to protect your data". The conclusion should be, if you don't have the ability to protect your customers you don't get to harvest their information.
Foreign keys should definitely be used in most schema designs. While I can agree that they are problematic when doing a schema migration, a schema migration would only happen "very rarely" whereas inserts/deletes happen regularly. I believe this comment is more of a reflection of the specific database (MySQL) which has relatively poor FK performance and adjunct issues when compared to other SQL databases.

Also, from a process perspective of migrating a schema, the ideal mechanism would be to incrementally copy from the existing schema to the new schema (meaning there is no breakage in the interim). Granted (and somewhat obviously) for databases as large as what GitHub is likely using, this is not possible -- and so a "full migration" at once is their only option. However, part of that "full migration", to me, would be to _remove_ the original foreign keys from the schema, rename/delete/alter tables/fields/indices, and then after all of that is complete, as a final step, re-add referential integrity (ie, foreign keys).

I'd specifically like to point out the following:

1) This comment gives advice about all SQL databases based on the conclusion / operation of only one database (MySQL), whereas the same base facts do not apply to others (eg, PostgreSQL, Microsoft SQL Server, ...), and should not be used to evaluate whether using FKs makes sense for other databases or not.

2) Schema migrations should be done rarely, if ever. A better approach would have been to start with a schema design that was less prone to _needing_ change. Regardless, even if schema migrations are done with _regularity_, that frequency would still be orders of magnitude less regular than, eg, code changes or CRUD operations. As such, throwing away FKs simply to accommodate either a poor or non-thoroughly thought-out schema is tossing the baby with the bathwater, especially since the purpose of FKs is to reduce the ability of other tiers in the application from losing or otherwise corrupting the structured data storage.

3) FKs are useful when doing CRUD operations. They are not useful during schema changes. As such, the proper process in this case would be to temporarily remove FKs, perform the schema migration, and then re-institute the FKs. This may not always be possible, due to, eg, active business logic components or some such that can't allow the database to be taken offline to perform a migration (see point #2). In that instance, there are a number of other mitigations that can be put in place in the logic tiers, such as being able to recognize different schema revisions, and deploying that _prior_ to doing a schema change. As such, one would first migrate an active "smart" logic tier that can recognize different schema revisions, and allow for incremental migration of schemas without enacting a cluster-wide lock/disabling of reads/writes.
Exactly. I intentionally avoid GND because it can be quite wonky, and DerivingVia basically subsumes it. You do still have to have slightly more explicit declarations of instances, but IMO it's worth it for the control.
If you want completely FOSS setup, check out Jellyfin [0], it keeps steadily improving.

[0]: https://github.com/jellyfin/jellyfin
because they didn't have glass?
I've been eyeing Card Kingdom's battle decks. They're 60-card decks put together from inexpensive singles (most worth less than a quarter) around some theme, like goblin generation or enchanted creatures or recycling your graveyard or whatever.

Each deck is only $10 so you can pick up a handful of them and play them against each other with friends. They're not intended to conform to any particular format, but they are supposed to be relatively balanced against each other.
In my experience cartoons are hugely impactful but I only have anecdotes, I'm sure there are good studies out there to refute or support us both =)
> everyone who uses a database at scale has settled on MySQL

hmm?

I've only every seen people using MySQL at scale if they started with MySQL in prototype and never had the energy to migrate.
That reads like someone with specific inside knowledge IMO.
Aw man, this doesn't include the time Nikola Tesla literally made Mark Twain shit himself!

https://thoughtcatalog.com/zaron-burnett-iii/2014/02/how-nik...
The impact of negative interest rates on banks and firms
New ideas come and go.

Most of the "free love" generation came along thinking their parents were squares and that they were creating a new, better society. Drug overdoses and HIV turned that ship around quick.

Maybe it's more accurate to say that the better ideas resist change.
The Measure of Intelligence
Why would you willingly use such a garbage POS script? There's better services out there, or you could just roll your own.