skysight-inc/HackerNews huggingface dataset:
> [...] and Linux is much more user friendly on the desktop.

Actually, I am not sure if Linux is in fact user unfriendly. I mean, my grandpa (78) uses it every day since about a year now and hasn't complained once (email, banking, ebay, news, ...; he used vista before).

I mean it's not like you don't have to learn a lot of new stuff if you come from years of windows experience and want to reach the same level of proficiency on a new platform which is totally different. It most certainly doesn't feel good to be novice again just because you booted a different system. But I doubt that it is a usability problem with the Linux desktop as people who have no previous experience with windows tend to have an easier start with Linux.

My primary PC has Linux installed and my laptop has a dual boot with Linux and Windows 10. When I use Windows I feel often helpless. Some program tells you that you need to install the newest update but while the updater tells you that its updating, you can't see any progress. After waiting for hours without seeing any progress you conclude that something must be wrong. So you reboot a few times and start searching on the web. Eventually you find a page which tells you how you can reset the update cache and after that it takes only a few reboots to complete the update. I definitely prefer updaters which actually work and tell you straight away when something is wrong.

My problems are probably just the result of too much Windows absence, but somehow I don't expect that to become a real problem anytime soon.
> No it wasn't. This is something you heard from people who never really used it. It had its faults but it was never a pile of shit nor was it substantially worse than other databases.

This is FUD, I have used mongodb, I have a certification in mongodb even.

Unless you know precisely what you're doing it's very easy to burn yourself. And mongo markets itself as being "easy to use out of the box" this is not a good thing to do.

I consider MySQL defaults to be unsafe, (as in, it used to corrupt data silently) but it's a godsend compared to the data consistency in mongodb.

There are countless promises it fails to deliver on too, I will not, ever, recommend it for a project. However in recent months I've heard it got better- This means I will stop deriding developers who now use it. But it does not mean I will be realistically allowing its use in the environments I work in. I tend to care about the data consistency in those.
Because the point is mostly lost on the unrelated analogies most tutorial writers use. A monad is a mathematical construct. Trying to explain them in terms of what makes sense to you, because your analogy results from your understanding, isn't likely to be more helpful than outright accepting what they represent, mathematically speaking, then putting that to use in your code.
As someone who is prescribed colchine for life for 3x/day, I remain blown away that a generic drug I'd taken for a better part of my life went from costing pennies to costing ~$6 per pill.
Chromecast itself is locked down, you need to authenticate to a sender, so don't expect a software compatible version. You can use a capture device however.
Between failure, placebo effect, and the possibility of being less effective than other treatments... that isn't guaranteed. Studying these drugs may just prove they aren't worth using.

If it's so straight forward to prove, the government should just fund the studies itself. There's no reason to grant any private company anything in that case.
Coming without any graphical applications and coming with 3D or AR software is a big difference. 90% of users will be able to make use of a simple image editor. 0.1% of users will be able to make use of 3D and AR.
Not sure it ever was or is, but been told that when entering China the fine print of the foreign-local partnership pretty much grants the CCP rights to your IP, do when they take your IP and copy it, it's technically legal.

Hearsay, for all I know.
Not sure about this, but you may be able to run the 180-day trial as much as you want, as long as you're willing to reinstall every 180 days. I installed the 2008 and 2012 trials several times over the years and got the full trial each time, but I haven't tried it back-to-back after expiration.
Ive been following Fantasy Land since times immemorial, but I never knew thats where the name came from (even though I followed the legendary discussions around the spec back in the days). Only today when I reread it did I notice the fantasy land call, and told myself "Omg...THAT is where it came from!"
My father's last position before retirement was as a civil servant responsible for approving equipment for medical use.

One of his last cases concerned a businessman who insisted, that a vacuum cleaner produced by his company should be certified as a medical device - ostensibly its use was to deliver drugs(via reverse action and inhalation).

My father rejected this notion on the grounds that, among other things, it was impossible to control the dosage. Unfortunately once my father retired that man eventually found somebody who would give in to pressure.

What I'm trying to say is that there's a decent amount of "medical" devices on the market that serve no such purpose so, a non-conformant artificial hip joint is only the tip of the iceberg.
This is true

It hurts when the next requirement comes along something like...

"As a user I want to have a home, work, and mobile phone number"

Now you have 3 "versions" of your implicit "schema" to contend with

1) No phoneNumber
2) phoneNumber and mapping it into / out of one of the three phone numbers in the UI
3) objects with three properties homePhoneNumber, workPhoneNumber, mobilePhoneNumber etc

Then the business comes up with "As a user I want to have arbitrary phone numbers that I can label" now the developers start to squeal

RDBMS + SQL is no panacea but having DDL operations like the following (all probably syntactically invalid but you get the idea) out of the box is incredibly powerful.
ALTER TABLE user RENAME COLUMN phone_number TO home_phone_number;
ALTER TABLE user ADD COLUMN work_phone VARCHAR(32) NOT NULL;
CREATE TABLE phone_number (id BIGINT NOT NULL, user_id BIGINT NOT NULL, name VARCHAR(64) NOT NULL, phone_number VARCHAR(32) NOT NULL);

I have had reasonable success using MongoDB as a store of "things that happened" and will never change
If a company can't afford to give its employees humane leave, it can't afford to have employees. That's sad for the company, but it's how capitalism works.
How could anyone possibly consider this offensive?
I just moved to Spain, and just played around with the beginners Spanish course. This is badass. Thank you for making this.
> Compiler and debugger support is not at the level of Java or C.

WASM is more of a compiler target, not a language at the level of C or Java: its something you'd compile to from C.
Isn't this a bit of an oversimplification? It's not like if you knock out p53 and something else you instantly get a metastatic tumor. Granted if you remove key tumor suppressor genes your probability of mutations persisting skyrockets, but that in itself doesn't create a dangerous tumor. You need many more mutations than 2 to be able to acquire the functionality to grow, persist, escape the local environment, and establish a foot hold in a new environment.

Here is the classic review paper on tumor formation: http://www.cell.com/abstract/S0092-8674(11)00127-9
Feelings get in the way of changing minds. Ignoring your own or your opponents' feelings doesn't make them go away.

Take a look at the article. How is someone who is concerned about sex differences in representation going to feel when they read, "Many academics in the modern world seem obsessed with the sex difference..."?

The article shoots itself in the foot in the first sentence. It's not going to change minds because it doesn't consider feelings.

Writing in a way that gets the facts right, and uses good arguments, and is worded in a way that doesn't turn off your opponents is hard. But it can be done. I think slatestarcodex.com often does it (though not always).
What would that have gotten him?
Sure. You could leap to the best solution first. Probably, you lucked out in the gene pool and your future fate is not to write bad code. The rest of us, who did not acquire sufficiently complex frontal lobes, struggle with concepts and probably dive into stupider solutions first, like I did at uni in the 1980s allocating a fixed size buffer (big initial mistake)_ and maintaining a huge linked list of edits sequence events into it.

I passed the course, but future evidence suggests I didn't learn as much as I hoped!
he does? he's gonna measure it poorly then because lol at working for facebook.
Historically LL, CH, and RR have been considered separate Spanish letters, too. Since 1995, opinions diverge.
The Science of Winds Affecting the 2018 Winter Olympics in PyeongChang
For what it's worth, it's easy to generate the 12-tone equal tempered scale by starting with 440 and repeatedly multiplying by the 12th root of 2.

For a just scale, it's a bit more complicated because there are sometimes multiple options. For instance, a minor seventh might be 9/5, 16/9, 12/7, or 7/4 depending on context.

In general, a pretty good "default" 12-note chromatic scale if you want to use JI in a way that works with most normal western music is 1/1, 16/15, 9/8, 6/5, 5/4, 4/3, 45/32, 3/2, 8/5, 5/3, 9/5, and 15/8. (Just multiply the fraction by the frequency of the root note to get the frequency.) 2/1 would be an octave above the root.

Just major chords are three tones that make a 4:5:6 ratio, such as 4/3, 5/3, and 2/1. You can think of a major chord as the 4th, 5th, and 6th harmonic of a note two octaves below the root. (1:3:5 or other octave-equivalents are also major chords.)

If you add on the 7th harmonic to make a 4:5:6:7 chord (and for this you'll need at least one note not on the scale I provided above), you get a barbershop dominant seventh chord.

Just minor chords make a ratio of 10:12:15, which you could also think of as 4/4 : 4/5 : 4/6.

The advantages of just tuning are that it sounds very stable and allows precise distinctions between very similar notes. Equal temperament is an approximation of just intervals and has been dominant for the last few hundred years largely because it allows instruments with a moderate number of fixed pitch notes to play in any arbitrary key and with each other.
Who conceived of AMP Stories? Who conceived of AMP in Email? What do they even have to do with "Accelerated Mobile Pages"?

My irritation with AMP is also driven by the fact it's not usable for me. Reader mode is often broken in iOS which is a particularly egregious regression. URLs are obviously broken. And sometimes sites can't even get text-on-a-page right with their AMP versions: https://twitter.com/lukestevens/status/963910460796936192
>Aggregates carry with them a memory limit.

I think you are referring to the 100MB RAM limit, but that’s not a hard limit, it’s more of a bad default. The `allowDiskUse` option lets MongoDB write intermediate results to the disk (which is exactly what SQL databases are doing).

> But aggregate queries really do not give you the power of SQL. They are great for transforming stuff for a report, but I would avoid using them for anything else unless 1) it can be cached (and therefor properly invalidated) and 2) doesn't need to be "real time"

I really don’t see a difference between what you can do with MongoDB and SQL. I can’t say much more without knowing specifically what impediments you have in mind, but I would certainly like to hear more. For example, why do you cite results caching and lack of real-time requirements?

> Being a document, schema-less database,

I guess if you’re on 3.4 you can’t take advantage of JSON Schema yet, but keep that in mind as a part of your upgrade plans. In the meanwhile you can still use document validation?

> your "quality of life" as you scale with MongoDB is going to be heavily dependent on how you structure your documents and the types of their fields.

This is completely true, but couldn’t we say that just as much about any database? I’d put money on there being way more grief out there over bad tabular schema than over bad document schema. I mean, who’s worked on large-scale systems that hasn’t put off implementing great ideas, or had to hack up app code to compensate for a restrictive schema, because you can’t take the pain of ALTER TABLE?

> Are you treating your collections like SQL tables?

Ouch. Please don't!

> Have any many-to-many relationships in hot code paths? Welcome to hell.

That's probably fair, but if you're in hell to a vastly greater than you would be with Postgres, I'm pretty sure that's a modeling problem. Again, can you tell me more about the particular example?

> Its type system is also limited compared to modern SQL DBs. Storing IP addresses, and want to query them based on a given CIDR range? Postgres makes this eas, MongoDB has you writing code that does sub-queries

That's 100% legit. MongoDB needs to do a ton better with that... types rule.
> If we could compute with Real numbers, we would get much better predictions.

This is a paradox. The real numbers are in some technical sense not computable. I get what you mean though, analog computers. However, there are still limits to the precision.
At Olympics, robots are cleaning, painting, skiing
In that case, one thing we can do is that the under the hood promise is not forced at all if the wrapping promise's value isn't forced yet. Then we don't have any async behavior, unfortunately; no calculation begins until the promise is called in. We can do part of the calculation ahead of time, but then stop and don't complete it until there is an indication that the value is required. That is fudgy though: how far is far enough to reap the async benefit without the downsides.

How about this alternative: instead of .cancel() on promises have a .commit(). This is called if you're sure that you will eventually need that value. The calculation then proceeds full steam ahead: no going back.

You can ask for the value with or without .commit(); it is just a hint. But if you ask without .commit(), you may have to wait for a completion that was deliberately stalled due to your lack of commitment.

Without .commit(), async promises will still proceed on their own to some extent based on some fudge factor; we don't want programmers automatically calling .commit() on every promise they make to get the async benefit, which defeats the purpose.

Uncommitted promises could be identifiable to the garbage collector and subject to an internal cancelation protocol between GC and the promises. That protocol basically helps the promise's thread vacate the object so it can be reclaimed.

Promises could have some sort of hint about how far to proceed before requiring commitment. This would have to be well thought out: such hints tend to be too system and workload specific. Automatic tuning is better. The promise system could keep some statistics about how soon various kinds of promises are called in after being initiated, and how often they are called in at all, and then uncommitted promises could decide based on that how far to compute.
I sometimes wonder how much of the UK economy is actually built on this fraud. The vast majority of these accounts are with UK institutions, it should be rather trivial to track down. Just the sort code alone tells you the bank and very often the branch.

I've heard it claimed that often the money gets transferred internationally from the shell account. Even so, the KYC for anti-money-laundering purposes should cover who owns the account it first lands in.

The most benign sounding explanation I've heard that sounds plausible is that privacy is a key selling point for UK financial services (I hear Switzerland isn't so private any more) and that main parties that investigate organized fraud (typically City of London police -- distinct from the Metropolitan police) know where their money's coming from.

Viewed from this perspective, every article on a couple being blatantly defrauded of their life savings is more like an advert for those international customers that might want a bank within a country that allows the whole banking system to take "data protection" to ridiculous levels.
Not really, I can read at normal text sizes. But it is somewhat annoying (much like how tiny English can be readable but annoying to read) and used to have my default font size bumped up by one in my browser. I currently have it bumped up quite a bit for Chinese because I really have trouble with the "tiny little flicks" problem in Chinese.

The consonants of Devanagari are easy to tell apart; they are pretty different. In most cases the "similar" ones are basically with an extra line (प/ष, ब/व) or with a little loop (य/थ, ट/ढ) . (The line/loop has no semantic meaning, these letters are just random letters that look similar) . The only super annoying one is घ vs ध -- the thing up top is a loop in the second one, but depending on the font/handwriting can be rather unclear.

The vowels are also easy to tell apart. There are 12 main ones, and they're made up from some really basic components which are quite distinguishable.

So you can easily distinguish consonant+vowel combos.

Consonant clusters can get tricky, like I said there are a bunch of ambiguous ones. Fortunately you end up realizing which is which and then it's nbd. But like, द्म and ह्म can be infuriatingly similar and you just get it from context.

Bear in mind, at one stage you start sight-reading words, so the actual details of the word matter less.

> Another related question is, because Devanagari's information density seems higher, does that mean shorter text for the equivalent information?

Visually? Yeah. Words can be really small. But it ends up roughly being the same number of code points (and probably more bytes in UTF-8).
"Lead" and "leash" are used interchangeably in some (non-American) dialects of English.
The basement dream of the web is dying faster and faster. At the hand of large, scared companies. It's ironic that the more powerful you get the more scared you become.
I wouldn't post Rust benchmarks in here it's behind Java in every scenarios.
As already mentioned, they're a lot better than callbacks (well, for certain cases. There are still places where callbacks are better).

The problem is that this is a field that has been heavily studied, and there are great solutions to this problem that also solve countless other problems, and interop well with each other. The way promises work, they solve that ONE problem but throw away the rest.

If you have the choice between 2 mostly equivalent solutions to solve a problem, but one of the solutions also solve 10 other problems with essentially no drawback, why would you choose the former?

This is probably already linked in this thread somewhere and is also probably was prompted someone to post this old issue to Hacker news, but this is a good explanation of the problem:

https://staltz.com/promises-are-not-neutral-enough.html
One issue I've run into a few times though: I'll come back to a tab for it and hit enter, and it seems to try and reload. I then get this error:

more_vert
This is not a valid session ID. Note that this URL ist not valid across browser reloads.
While I don't disagree that 8GB isn't much for a developer machine these days I do also think your claim is a little exaggerated. I certainly don't have any issues running a couple of intelliJ instances + Chrome with at least a dozen tabs open (seriously; I'm terrible for leaving tabs open).

What I find kills my machine is trying to run Chrome and Firefox concurrently. Particularly if I still have IntelliJ open.
I'm excited about this project. A few questions about your tech stack:

How's Datomic? Are you using the community edition?

Also about databases, are you using or have you considered using a graph for Cassandra like Titan?

I guess also, if you do a mobile app will you use ClojureScript with React Native, like Re-natal?

Thanks.
It doesn’t pick quite the right movement for some of the subtler sounds. I’m still trying to quantify where it breaks down for me.
Every day we live for those things and face a small chance that some powerful government or entity will capture and torture us or our loved ones indefinitely, for scientific reasons, or perhaps for no reason at all. Escaping life is one solution, but bracing against fear and leaning onto hope seem like more appealing choices to me. Pessimism is a valid argument against Cryonics, but since it's as unfalsifiable as optimism, I'll gladly take the choice that makes me happier. Maybe that is a priveleged and rare choice these days, but all I can say is I hope you find optimism and hope someday in this life, regardless of the viability of some inconsequential technology.
Accessing the material is becoming less and less of a problem, for all the reasons already stated - piracy, international editions, OER, etc. The real issue is that the textbook publishers know this and are pushing more and more access codes so it doesn't matter where you get the book, you still have to shell out $100 to be able to submit homework. I still haven't seen a good solution for this issue.
Cancer Immunosurveillance: Immunoediting (2016)
Pipistrel’s Electric Airplane Earns Canadian Certification
I was talking about those pre-built VMs.
I used to work with the head of engineering at Monzo, smart guy.

I know he pushes a lot of their tertiary code open source.
They get relabeled, but they are everywhere.
How to Use Dynamic Member Lookup in Swift
No, the crashy Bengali sequences are reasonable to have; like I mentioned ZWNJ has semantic meaning with bengali vowels.
Why would you need a textbook code to submit homework? As long as I can read the text of the book (that I pirated), why can't I solve the homework and submit it to my school?
>You only need to look at the current state of India's government, which over the course of more than 50 years of affirmative action (and other varying factors) has managed to convert the government sector into a cesspool of corruption and bad management.

This seems to imply that India's government fifty years ago was NOT full of corruption and bad management. The Raj was definitely corrupt but I know little about the two decades after India got its independence - were things really that good fifty years ago? Or was it just that it was less obvious?
Simulator, not emulator. (There is a difference, and it is significant).
I own a small farm and work in tech. We are struggling with this issue right now as we look at the options for a new tractor vs an older serviceable model. While many of the larger corporate farms are content to buy new equipment every 10 years, those of us at the small end of the scale have begun a push to keep older equipment up and running.

My tractor is from 1996, my hay baler from the early 70s and my hay cutter is even older. These all work just fine even if a little slow. The challenge of not being able to work on my equipment currently outweighs the marginal speed gains I would see on a farm our size. The same goes for nearly all of my neighbors.

The last "new" tractor in the local area was bought a couple years ago by one of the older guys who was buying the last tractor he will ever own and he thought it would be nice to have a top of the line, new, tractor just once.