skysight-inc/HackerNews huggingface dataset:
This points to some interesting research but the title is clickbait. First, "artificial intelligence" is actually agent-based simulation. Second, the article barely mentions atheism, but if ones digs into the sources you find that given their models in these simulations "people tend to secularize when four factors are present: existential security (you have enough money and food), personal freedom (you’re free to choose whether to believe or not), pluralism (you have a welcoming attitude to diversity), and education (you’ve got some training in the sciences and humanities). If even one of these factors is absent, the whole secularization process slows down."
> I decided to try and build a fairly standard To Do App that allows a user to add and delete items from the list.

Isn't it enough of such really? These (micro)apps which are actually single extracted screens of anything seriously larger can't help to decide about a stack.

What about other aspects of real apps: user auth, undo, back-button action, rich forms, client-side error logging, permalinks, rendering/filtering user markup, uploading/attaching content, drag&drop, notifications, SEO, integration with other useful libs (e.g. bootstrap, highcharts, d3), app extensibility with customer views/plugins?
Edit session divorces the session from its underlying profile so you can make local changes to it only
What if the computer is somehow compromised, before or after manufacture?
""We're no longer in the days of a master cylinder responding to pressure from a driver's foot by simply sending hydraulic fluid to drum brakes.""

At some point of actuation the Tesla car should have a mechanical backup when depressing the brake pedal, right? I really don't think it's pure brake by wire.
Wife and I were just talking about this and how this is a great example of how decisions made in one generation can have consequences that span multiple generations (eg. Eggs, where one’s family immigrated to, etc)
There are some legal complexities. See, for example, the discussion of TechCrunch's use of corporate logos in the following article:

http://www.dmlp.org/legal-guide/using-trademarks-others

"Although the practice is widespread, it is beginning to draw fire from trademark owners. As noted above, late last year a representative of Avis requested that law blogger Eric Turkewitz cease-and-desist from using its logo in a post about a lawsuit involving the company (see Turkewitz's post). The law is not entirely clear on this point. The nominative fair use defense may not apply because using the logo is not strictly necessary for describing the trademark owner or its products or services. Nevertheless, courts would probably find that use of a logo in the process of news reporting is not likely to confuse consumers."

In the context you describe, there could be more potential confusion than in news reporting, since there may be doubt about whether using a company's logo on your site implies some kind of endorsement by that company (even if you don't explicitly claim that it does).

The easiest thing, of course, is not to use those companies' logos (just refer to the company names in text). If you want to do use the logos, you'd be much safer if you either got permission or consulted a lawyer.
The daughter has some genes from the mother, and some from the father. Which genes are selected from which progenitor is random.

To have a big pool for recombinations, inbreeding is to be avoided and populations must be big enough.
Great summary!
> maybe wait a few hours before downvoting next time? at least give me the opportunity to not see it as being likely to be you

A user cannot downvote a reply to their own comment. (And complaining about downvoting is never productive.)
Keras implementation of Image OutPainting
Incorrect, long term support is actually required because of the insane prices they want to charge and market saturation.

Like with cars, the used market supports the selling of new devices. This is something Android manufacturers need to figure out.
It's not just relational features that matter but the decades of work on reliability, performance, flexibility, security, and general usability of these databases that makes them so great.

ElasticSearch doesn't have ACID or very good OLTP manners. More importantly, it still continues to have data loss issues so it's not a good fit as a primary datastore.
The ~ in "Año" is never optional. Removing it leads to some incredibly inappropriate readings.

Año = year. Ano = anus.
I bet being able to work with the plotting data to aid novel postproduction work would be a blast.
I see this happening in the US now.

For example with homes, when grandparents died in the 80s/90s a home was sold at a modest value and split among 3-5 heirs. Which amounted to very little per family after taxes.

Nowadays you have millennials set to inherit homes that are overvalued in the $1MM+ range and split among 1-2 heirs. Which can be a life changing sum of money. I personally know of people who feel little pressure in their lives because they know they stand to inherit a $1.5MM home plus whatever else their parents have at some point in their life.
As far as I can tell, Vue doesn't introduce anything new over other front end technologies. It's ironic developers who complain about React being the "new hotness" turn to Vue. It's the same core concepts as Backbone, Knockout, Angular, Ember, and the countless private frameworks we've home-grown on top of jQuery in our front end jobs. This is highly stateful, object oriented, mutate-by-defualt, class based, imperative programming, with imperative DOM manual wirings, separate templates from view logic (probably the biggest sin), and programming by non-transferable conventions (v-model="todo", this.$parent.$emit). I don't even want to know the implicit magic that makes list.push() update the view (notice how the author of the article doesn't know either!), but this is again the same as all of the above.

While I don't personally prefer any of the above style, the point is not a criticism, but to point out that fundamentally Vue doesn't seem to offer any different core concepts than other frameworks. I think it just hit a sweet spot timing of being a React competitor, when developers who didn't like (or, I suspect, don't fully understand) React's fundamentally paradigm and convention shift. As a biased pattern match, most times I see people comparing React to Vue, they're new to both, and don't get React.

I'm biased, but I'm biased through experience. Building Backbone apps where you glue events to DOMs written in strings with magic stateful data classes, and then scaling and debugging those apps, _sucked_. We didn't know any better back then, though, because we didn't have React to compare it too.

React can introduce problems (like any framework), but instead of trying to jump through hoops of convention, custom data binding and HTML tags, now my problems are my own. They're problems of composing functions or structuring my data flow. React is so thin that it's rare to have a "React" problem, now I have vanilla "Javascript" or even "function" problems, and it's such a breath of fresh air. Even when I'm debugging performance problems, I don't feel like I'm dealing with React, I'm dealing with comparing Javascript objects.
Interesting article about how multiple faults can be handled.

Name should probably be "Double Faults", the website is "Writing an OS in Rust ", but the post is about double faults.
In both cases, the party establishment tried to prevent a candidate on the left from gaining power through deceitful means. They tried to rig things against Bernie and Sanders.

That’s the comparison being drawn here. Does that make sense?

(Yes, the details are different as the mechanics of these party systems are very different.)
I used the Firefox extension "Scrapbook", until the switch to web extensions killed support for it.

It was quick. And it saved a local copy; no worry about stuff "going away". I might get back to it sooner, or I might a considerable time later. Regardless, it would be there.

Things like this differentiated Firefox and promoted much support of it from its user base.

In short, it's my god-damned client/user-agent, and it should do what I want.

(And I thank all the developers who helped enable that. It is, was their creation.)

I welcome progress. But, taking away useful features like this, does not feel like progress.

P.S. Yes, my thanks and all that, don't really suffice.

However all the credit and blame shakes out, we've got a composite medium that seems, in important aspects, to be becoming more transitory. Things disappear. It's harder to "keep up with the flow". Noise and rank-gaming and all.

And (thinking of another recent round of comments on Google search results), I guess search isn't "sexy" anymore. Not for Web content, at least.
I'm not sure about obsessed but at the very least Lambda can be much cheaper than a full host for occasional, but heavy tasks, and it takes care of the associated administration for you.

Basically, in some situations, serverless can be more efficient with everyone's hardware and money, which seems like a win.
https://github.com/gothinkster/realworld/blob/master/README....

That is what you want, maybe. Lots of different frameworks, building the same working application.
A close friend of mine also got multiple emails from sales telling that he is using too much bandwidth on the Pro plan and asking to upgrade to $2000/month+ or "else". But they were not able to define what would happen otherwise.
Now I guess its just a scare tactic?
> ...but never forget that what we gain is the tremendous ability to copy perfectly.

Yeah, all except the first one. I'm not gonna argue with the gushing passion for all things digital in the rest of your comment, but I will first of all, point out that putting your photos, music, and videos in the cloud is absolutely not an exact copy--cloud providers don't have ToS that cover the compression that they apply to your media. There's no telling how badly they'll compress it to make room for the newest stuff years from now.

Since you offered such an untempered view of digital media as the ultimate achievement of human civilization, I'd like to offer an alternative viewpoint that recognizes that digital copies reduce very deep, meaningful experiences down to very meaningless bits. That's great for newspaper articles, but it's no way to live life. Just yesterday I was sitting in the park under a tree. The winds were blowing, thousands of leaves dancing above, and distantly a church bell began tolling, it's bang-clang rolling and washing through and around the boughs, being buffeted by the wind itself. The boughs are laden with leaves and seeds, and the sound waves are muffled at a turn, coming through at a turn, as this branch shakes and wags between the bells and me. The sun is filtered and flickered, I see the veins of leaves through. The insects buzz. One shield-like bug, as thin as a blade and about the size of a fingernail, lands and waddles around my blanket, its six legs hyper-optimized by evolution. There are perhaps 10,000 such creatures in this field. A trillion generations to produce it. It starts, its wings buzzing a thousand times a second. The hundreds of thousands of blades of grass wag in waves like grain, like carpet, like kelp in a fishtank, and they too, rustle. Could digital media capture this? I move my head to the side, angle it up, cup my ears, and I sense this field...I am absolutely surrounded by information. The amount information is incredible. I could hear the scrapes of the leaves against each other and the audio shadows of them as they blow around in front of this bell! I can hear the bells harmonics, and in my mind I see the sound waves racing round its circumference, overlaid with other harmonics making it jiggle like a waterballoon. The information there is 10^30...10^40. We can't even imagine.

And yet, we are told that VR and digital media will usher us into a wonderful world of entertainment. Pah! Lossless copies. Pah! We cannot even capture a millionth of something like that.
all ads should just die
This might work in Europe but not in the states where the summertime temperature might be around +25 and the wintertime temperature might sometimes reach -25. The lake where my parents live freezes thick enough to drive a pickup truck on it.
What is was like to be in the acute psych ward
Zave – Save your favourite and most visited websites
http://flatbedsutra.com/flatbedsutrazenblogger/?p=1714
> It's not a browser. It's a browser design. (plus a bunch of not-really-functional prototypes).

Oh, sorry!
>I interpreted your statement of "just to have plenty of backup" as having plenty of storage space rather than multiple copies / redundant backup.

Yeah, plenty of backup copies. One can always die on you, and even just 2 is stretching it. And the working ones should be verified and copied to new copies every 3-4 years (but in overall, it's not a big deal).

>The problem I have had is that when one is trying to duplicate/copy > 1 Tb of data across tens, if not thousands of files, that the bitrot is not always easy to find

Yes, but for the order of 100s or 1000s of images (equivalent to those one would be able to print) this shouldn't be a problem though. Tiny HDs, SSDs, and USB drives + MD5 (or better) hashes/CRC codes should do.
Tradition? Family tree? History? More women want to take the husband's name than vice versa? Because kids traditionally get the father's surname?

Isn't there real journalism that theatlantic can do rather than silly nonsense like this. I expect this from reddit's ELI5 rather than a supposedly respectable magazine. Also is every other headline from theatlantic going to be a question?
Can you name an example?

I've never built something that did not need a relational database to model the domain, and search is such a common UX element that it's taken for granted in everything you use.

I can't even think of something that could use search that's not relational. Can you?
Such a suffix based on the father's name is called a patronymic, and is not just Icelandic, but seen throughout the world, mostly Europe.

https://en.wikipedia.org/wiki/Patronymic

In Russia and other Slavic nations, the -ich patronymic is used:

>> a man named Ivan with a father named Nikolay would be known as Ivan Nikolayevich or "Ivan, son of Nikolay"
This reminds me of the famous mistake of "referer" being spelled with only 1 'r' in the HTTP standard.
On the other hand do you want people who move around / don't want to pay $300 for a bedside table .... to just use cardboard boxes or something?

Ikea fits a need, I'm also not really sure more expensive furniture wouldn't also end up in the dump too...
And the early versions of the PLATO educational computing system used a computer-controlled microfiche reader to display graphics beyond what was possible at the time.

https://en.wikipedia.org/wiki/PLATO_(computer_system)
you're either severely underestimating how easy it is to insert a backdoor or overestimating how competent apple's code review practices are. remember that time you could bypass the root password prompt by putting in nothing?
For those looking to get into Racket macros, the Racket School [0] from this year is now also an excellent place to start.

0. https://summer-school.racket-lang.org/2018/plan/
Jacobson signed a plea deal for 15 years but only got 37 months?
To the extent that the comparison is so absurdly simplistic that it doesn't do justice to either of the situations it's trying to describe, sure, it makes sense.

Staff within the Labour Party running ads to deceive their party leader into believing they were running a more progressive message than they actually were is literally nothing like anything that happened to Bernie Sanders in 2016.
Java's Magic Sauce
If you are using Vue for anything other than the most basic use case and are not using Vuex you are not doing things the "best practice" way.

Same goes for React without Redux.

The frameworks have a strong architecture the moment you introduce the flux architecture (vuex for vue, redux for react). Writing vue/react code w/o flux is like putting your entire application code into the view layer of an MVC app.
>but with digital storage it's often a step function where it's like "whoops, a few bits flipped, can't read at all anymore"

That's not inherent in digital copies though. It depends on how much redundancy one adds. We've had self-correction codes that sacrifice size for redundancy and reliability since forever, even in simple formats like ZIP and RAR archives.

And with digital one can always make like 10 copies in the same disk too. If one is unreadable due to single bit flipped or a whole sector, some of the others will still be fine.
I would argue that he is more commonly known as Monopoly Guy - as this is the first I've heard "Rich Uncle Pennybags", and I first played Monopoly ~30 years ago.
I want to see something like https://web.hypothes.is made native in browsers, so you can have community overlays on websites and commenting based on a group you subscribe to, automate common operations teams perform on web pages and leave notes for them etc. with out the websites itself being entirely in control of the entire ux and functionality.
If long term support were “required” then why don’t the high end Android phones that cost just as much as iPhones get the same number of updates?

But either way, that Apple updates phones for years contradicts the statement that Apple wants you to replace your phone every two years.
Show HN: A CLI tool to run network tests from 200+ locations
Classical music interpretation is awfully anti-intellectual sometimes.

Example:

Tchaikovsky composed a theme for the second movement of his B-flat minor piano concerto which moves along at a given tempo, then gets repeated in the piano solo where it is typically played at greater than twice the original speed.

I've never read a serious criticism of that piece on the grounds that the laws of music dictate that the same unadorned theme cannot possibly hold together at such disparate tempi. I've also never heard an audience member say, "I liked it when it was slow, but when it sped up to be twice as fast it wasn't tasteful," nor, "I liked it when it sped up but it was like molasses at the beginning of the 2nd mvt." Instead, most people take as gospel the score that Tchaikovsky wrote and make a good faith effort to make sense of what he wrote.

Why are we willing to do that for dead composers but not for live classical performers?

Are we to really believe that in the 21st century, with thousands of profession recordings of Brahms, Beethoven, etc., there is so little leeway wrt tempo that a performance like Gould's could be unworthy of a good-faith listen? Especially given how contrapuntal Brahms' writing is...

Here's an even more glaring example: how fast should one play the final appearance of the main theme in Chopin's Pollonaise-Fantasie Op.61? If you take it slow you can illuminate the beautiful chorale-like Back-inspired voicing that Chopin was so fond of, at the expense of the main theme. If you take it fast enough to let the main lyrical theme ring out, you go too fast for the listener to hear those same intricate inner voicings. Both are valid interpretations, and they are mutually exclusive.

How about one professional recording of Beethoven's Appasionata Sonata that transposes everything up by a minor third so those low blocky voicings don't sound so muddy on the thick metal strings of a Steinway grand which did not exist when Beethoven wrote it?

Hell, how about one professional recording of Appassionata in F-sharp minor because, "It makes the fingering in a particularly nasty passage a little easier that way." Would an audience give it a fair hearing, or would they all spontaneously develop perfect pitch and suddenly care deeply about 19th century key associations that they vaguely remember hearing a sentence about from a music appreciation course 15 years prior?
For Non-SSD drive: https://dban.org/

Veracrypt for encryption. It's not complicated at all. You will have little to no other options except creating an ISO on a USB drive (or burning?).
> I still don't get as much money as I do with donations. But if it's noble purpose we're talking about, my latter choice seems more noble than the former to me.

It's still the same incentive structure. If you review iPhones then you get visitors from Manhattan and make $11. If you review $10 phones you get visitors with no money that advertisers won't pay anything for.

If they have nothing to donate to you then they have nothing to buy the advertiser's product with.

Doing work for people with no money is charity. And charity is great, but if you're expecting it to maximize profits, you're doing it wrong.
Seeing those quasi-JS expressions in HTML attributes is enough to put me off Vue.

I understand why people feel overwhelmed with the whole React/Redux/Router/Saga stack but you really don't need most of that when you're just getting started and React itself is quite simple and elegant.
You haven’t articulated why those other technology categories are important to your company’s technical strategy outside of “don’t wanna miss the boat” (which in itself is rather dogmatic). Start there.
>If you’re not already aware, a CLI (short for Command Line Interface) is basically a thing that you can install via npm that allows you to terminal/command line commands that will quickly build a general Vue/React file structure for you

No, not really... Good work for doing this comparison though.
Unexpected Kindnesses
I'm 34. I learned 5 new words in Hebrew via Anki this morning at 6:30am. I do this every morning as I increase my ability and go towards C1.

This doesn't include everything that I learned yesterday evening, per the requirements of the question.
> More seriously, she worries that low-cost Chinese-manufactured goods are starting to offer real competition to secondhand goods in developing markets.

And this is what I worry too. Not just in developing markets, but everywhere. I buy a very large amount of used tools and electronics, but recently new tools and electronics have gotten so cheap it usually makes much more sense to buy new.

You can get a slightly older phone used for about $200 or so, but there are plenty of great brand new options around $200 as well. You can get someone's old angle grinder used for $10, but you can buy a new one with a warranty for $14.

I personally don't care about scratches or heavy visual damage on my stuff, so buying used usually makes sense for me. But nobody wants to sell their old stuff for as cheap as Chinese new products these days. Even if they do, the Chinese stuff comes with a warranty and a promise of support and refunds.

That's what worries me: at some point, manufacturing new stuff just gets so cheap that it outweighs buying used even for the most hardcore thrift shopper like me. I recently bought a nice looking pocketknife with a pretty wood handle for $3.49; in a thrift store you'd see a used one for maybe $10. I recently got a used angle grinder for $10, but it broke, leaving me wishing I had bought a new one from a local store for $14 (including disks and a 2-year warranty!)

The worst thing is that because of lower-quality manufacturing for decades, many used things have very little inherent value. When every particleboard table cost $25, a used one was worth maybe $7. But now that you can get a new particleboard table for $5, the same used one is worthless. The same goes for a billion other things, from calculators to drills to speakers. In the past, when cheap new things weren't available, the used low- and mid- quality versions of those things held value. Now, anything that's not high quality does not hold value. When you can buy a used calculator for $3 or a brand new one with a warranty for $4, nearly everyone will pick the new one.

TLDR: When cheap Chinese products are available, used low & mid quality products become worthless and only used high quality products hold value. This will cause enormous amounts of unnecessary waste to be produced.