skysight-inc/HackerNews huggingface dataset:
I don't want to disdain the success of Go, and I think the whole building of the community from the ground up is an achievement that few can say they were able to do.

However, what I dislike about all this is the generalization issues (like I saw on "Moving from Scala to Go"), which misses the point of history, and what to expect next.

First, saying "look how Go simplified our code by not allowing anything too complex" and using that example is very biased against someone that usually programs using applicative functors and don't really see anything overly complex in that code - besides some overly compacted structure which makes reading a bit hard. And that comes from someone that is not a Scala programmer, BTW.

In fact, from the "applicative functor" guys, most OO code would be deemed overly complex - and TBH with some sound arguments - but the "improved Java" camp would think that reasoning about shared mutable state is easier...

Second, the article tries to reason that it's a matter of being opinated, but it's not a matter of just being opinated: it's a matter of having that particular opinion, which means using simplified concepts without any ways to really elaborate them further, and having a more lax approach about exact semantics, types, etc. Very nice for beginners, as you don't really have much to learn, but most programmers that like it now would start hitting that expressivity ceiling soon.

Which brings me to the history part: it's funny to think that Java was born in a very similar way: no generics, tried to follow the most popular paradigm of the time as closely as possible and stay simple.. then people started using it, requesting improvements, and it became more and more complex after each release - until everyone realized that the very same thing that got everyone using it (simplicity) was not really there, as the complexity moved from the language to your code. Boilerplate over boilerplate, ever-increasing tightly-coupled frameworks, and there you go.

If I had to guess, I'd say 10 or 20 years in the future we may see the same happening with Go (if it tries to become more expressive) or it being put aside as a niche language (if it stays the same). But only time will tell it's fate.
Fix paxtest output on OpenBSD 6.0?
Someone who really wants to savor the steak.

Smaller bites and more chewing is so underrated. And you won't eat as much, either, which is great if you're trying to control your weight.

It's hard to remember to do when you're hungry, though.
I didn't read the article? Sorry, I didn't notice you standing over my shoulder as I scrolled through a waste of time.
Go for it. Will be fine for javascript.
AllergyPoster.com gives out Free Posters
That "remnant" is much larger than the handset division they sold. 114k employees after acquiring Alcatel-Lucent. Seems to be doing well. (I just learned that Bell Labs is now "Nokia Bell Labs".)
You seem to have misread the comment you responded to. The author cited external stimulation as a key factor, and you've somehow ended up redefining "alone" to mean "mentally still."
For fun, or for profit? Building IaaS to support your own company is hard enough; building it with the level of isolation and security required to be multitenant is harder still.
I would worry about this about as much as your employer worries about ensuring they have a well thought out career development plan for you that includes a fully funded pension.
Maybe they're trying to complete one of those 64 oz steak challenges.
The former FTC Commissioner, Joshua Wright, had previously been paid to write "independent studies" defending Google's antitrust position while teaching at George Mason U, which Google then used as expert material. Unsurprisingly, the antitrust investigation against Google was buried during his tenure, despite the FTC staff wanting to go forward with a formal complaint. Then add in that the Obama administration has placed Google employees in almost every high level tech position...

Suffice to say, I've yet to see anything that indicates the FTC intends to do anything about Google yet. Until international cases and public opinion support action against Google so strongly that our government can no longer bury it, we're not going to see anything done here.
How does it handle building from LaTeX sources where you need to "rebuild" the document multiple times to get page numbers and references right?
AARON RUSSO RIP you should listen,it won't save you,but you will know why t
Four Things I’ve Learned as a Startup Advisor
It is the average size of a new UK house I believe, just under 1000 sq ft, 3 bedrooms.
Four Insights from 51 Articles on Breaking into VC Industry
A lot of recent research uses RL to "fine-tune" NLP models. A practical example would be Google's recently announced Machine Translation System (https://arxiv.org/abs/1609.08144). It uses RL to directly optimize BLEU scores on translated sentences.

You'll find similar applications in state-of-the art models for chatbots for example. Though I agree, "widely used" may be somewhat of an overstatement. But it's becoming more common.

On a side note, I actually think RL makes a lot of sense for many NLP problems and it would be super interesting to build a pure RL approach to language modeling or translation. Nobody has managed to do that quite yet.
Actually, I think the problem for Google is that the market is already pretty fragmented, depending on how you slice it, and shows no signs of vendor consolidation. In this particular case, Google's pushing hard on the flat side of the boulder; they are trying to strongarm audio technology companies (who, unlike software and media companies, don't have any preëxisting entanglements with most software and service platforms) over a set of Google services that don't hold a particularly commanding position in the market vis a vis Amazon. I just don't get why they think they're in a strong negotiating position here, except that they must assume that the Google brand is powerful enough to create its own Kool-Aid-based distortion field.
The article you quote in [1] is not a good article. See the comment by perseids.
Everything is good enough at low-to-moderate scale.
Platinum Hide IP Serial Number 3.5.2.8 and Crack Free Download
Google is the Microsoft that wants to cripple competitors and stamp over its users to make a quick buck. Nothing to see here.
> discounting that, in the real world, if you're in a team but don't actually do the work, you're going to get screwed.

Ha. I used to think that, then had two separate experiences with completely different management chains where the incompetent guy did just fine.
> Unfortunately, that doesn't leave me a good term for the people like the ones that murdered most of my grandmother's family because of their race.

This is what you said.

Nukes are just a convenient way to eliminate an entire race these days. If you don't think right wingers calling for the middle east to be nuked is in any way related we're probably done here.
"But if they can position the market as voice-based home automation, they are almost definitely safe. Amazon and Samsung probably have the majority of that market and Google is the "little guy" coming into the fight."

That's a good point. Defining the relevant market is the name of the game in antitrust. Google could argue that they are a minor player in home appliances. If Samsung tried a lock-in contract, they'd probably be hammered in court. Google can argue they're a minor player in online retailing. If Amazon tried this, they'd probably lose.
Receptionist bullies my wife after throwing my parents out at 4AM
Using Giant Mirrors to Light Up Dark Valleys
I think I didn't explain my problem well. What I really need is a book (or a set of papers) that describes and compares for example LSM Trees or ISAM or other techniques (Which I'm not aware of many of them). I'm not a basic developer in database world. I want to dig into it and understand how actually it works (This is where I am basic).
Don't let your bad opinions hit you on the way out.
Oh, I didn't know it was unrestricted before. (Re-read your comment) Yeah, not good of them to remove such a major feature if it was there before.

Why did you lose email for domain? It seems like I still have this option for the domain on DreamCloud (although I also still use their shared hosting).
>>> I don't see why clicking the ad makes you less web savvy.

Web Savyy people have AdBlockers. It's the first thing to install right after the operating system itself.

Clicking the ad means you don't have an AdBlocker, therefore you are not web savyy.
It's impossible for us to know why Google decided to do this. But both issues could both be considered antitrust issues. Amazon's staggering market share in shopping puts them at risk by them not selling a competitor's products in another market segment. And Google's attempts to strongarm manufacturers into blocking out a competitor is obviously problematic.

The argument could be made (and I think Amazon technically claimed it) that Amazon blocked Chromecast from their store for incompatibility with their products, because Google won't allow forks of Android to have Google apps on them. Which is also anticompetitive.

So, if we want to suggest both companies are petty as all get out, it's plausible Google was anticompetitive, Amazon was anticompetitive in response, and then Google was anticompetitive again in reaction to that. What's next? Maybe Amazon will remove Chromebooks?
"Altogether, 18,000 people from 134 countries made time to take part in what was quite a lengthy survey devised by Hubbub - an international group of academics, artists, poets, and mental health experts - showing perhaps what a pressing issue rest is in the modern world."

This is a poor conclusion. For one, 18,000 people isn't sufficient to draw any conclusions on a global level. It's a tiny sample of a relatively huge population.

Furthermore, I think the ~795 million people is much more so a pressing issue.

If we disregard the developing world, 18,000 people is not an adequately large sample to draw any such conclusions either. I'm glad that they are using the word "might" in the article and "may" in title, but I still regard the journalistic value of this piece as being really low.

"A full analysis of the data will be published within the next year. It's already clear that it holds lessons for doctors. Callard points out that when doctors prescribe rest, not every patient will interpret the word in the same way."

It doesn't hold factual lessons for anyone, it's too speculative. I'm hoping that people will be getting more rest either way.

Is there a journalist watch-dog for when poorly designed studies such as this one is covered by the media in a manner such as this that can be alerted? Especially since BBC themselves were involved in the study.
I don't see how that could work in tup or any deterministic build system. If there is any possible way to parameterize explicit filenames unique to the stages, that will map better to tup. It requires you to be explicit about every file generated, even temp files. I've searched the mailing list for a few scenarios and the response is often to wrap tup in a makefile.
It's so incorrect, in fact, it's worth banning whoever did it from ever editing anything else...
They are both bad in different ways. The first one is meant to listen all the time.
you beat me to the punch.
ElasticSearch has a very good introductory guide included in the documentation. Go through the first half of the Getting Started section and you should be well on your way, with most of the following sections being just for fine-tuning:

https://www.elastic.co/guide/en/elasticsearch/guide/2.x/gett...
It really needs TF-IDF or BM25
As always, the issue tracker: https://bugs.dolphin-emu.org/projects/emulator/issues?set_fi...

And we have an IRC channel for developers on Freenode.
Wife and I dine out as autarkies and have had no trouble with it so far. The author seems to imply that the only reasonable thing there is is sharing everything. I strongly disagree with that.
git checkout <file> // throw away all changes since the last commit (one file)

git reset --hard // throw away all changes since the last commit (all files)

This is a perfect illustration of why git needs a better UI. Two different commands to do exactly the same thing, with the only difference being that one is for one file and the other is for many files? If you tried to design a hard-to-use UI you could hardly do better than that.

[NOTE: these two commands actually don't do quite the same thing, which is part of the problem.]
This is how you cheat democracy. You can play people with ease using media and the truth is that it is always for power and money however you wrap it. At least dictatorship is honest.
The problem is better solved with good tutorials. Cutting corners is a bad idea here so encouraging newbies to do that is more hurting than helping them.
I hate how entrenched MySQL is.

We had 6 months of testing a high-throughput database trying to get it to do the consistency and latency required for peak load to no avail. (Even to the point of replacing the kernel with a custom one, and using a faster memory allocator)

PostgreSQL could do it with only minor configuration tweaks.

It still took a further 1.5 years to get the central IT body of my company to allow us to use it, and we wouldn't have had that if our software didn't 100% require it.. I hate to imagine how other software that actually needs conversion is right now.

sidenote: I've had many corruption issues from using MySQL, so I'm double-baffled.
Pity. I'm morbidly curious to see what other silly things you're willing to say.
iwStack fits the bill too
I looked up holoprosencephaly, the rare congenital defect mentioned in the article. Stuff of nightmares.
While in theory I appreciate what pijul is trying to do, I'm not going to plug it until it at the very least self-hosts. Two years in, still not there.
And your ad agency will be fired when that happens. It is therefore a must buy.
You absolutely did not read the article based on your comment. I feel confident stating that, despite not looking over your shoulder.
New York monument honors victims of giant octopus attack that never occurred
What if you did one year on two years off?
The whole advantage of stash, the way I see it, is that you don't need to type out a whole bunch of commands to stick something into another branch and deal with remembering where you put it and what you called it and so on.

I started out using secondary branches since that was the intuitive way of doing things, and I had issues with stash before, but after a while I went back to using stash again because it's just so much faster to stash my config differences, do all the necessary merges or pulls or switches, and then just stash pop. A large part of the advantage is that stash is a bit orthogonal to the usual workflow, so it goes in a specially defined place in my brain vs being yet another branch, especially if I already have work/dev/backup branches for other purposes.

I agree that I wouldn't recommend using the stash to beginners, though, it does really odd things at times if you are not clean with it. First time I used stash, I lost all my code and nobody could figure out how to get it back. :P

But that the thing - I never stash crucial code, just things like settings that are special to me and not other developers, so they'll probably never be pushed.
That's only 200 bytes per document.

Can they be really considered 'documents' or are they actually database fields?
And how do you get back in sync if the client that did the LISTEN, crashes and has to be restarted?
Corporate Accounting Dissertations
Checkout ninja-build. Generate ninja build files automatically using CMake. Ninja is really fast.
No wonder wealthy Chinese go out of their way to buy not-made-in-China food and medicine.
British scientists a step away from finding HIV cure
As a kid, I seem to recall never having enough alone time. So your daughter may appreciate that you're not hanging out with her every waking minute (but it depends on the particular kid of course).
> All that said, avoiding an entire state because of the perception or political demo breakdown of said state is a mistake.

It's avoiding states because of their laws, which is a result of the political demographics. It's not the demographics themselves. Those laws have very real consequences for the people living in those states, and I would not want to be one of those people.
I love fabricate---even helped with the OSX port. I had to give up on it when El Cap came out; I just didn't have time to work around SIP. The other problem with fabricate/tup/not-Make is they store the structure of the dependency graph. This leads to ugly build ... worries when you have subtle dependency changes caused by, e.g., updates to system headers, or interactions in large rule-bases. I just never had confidence the builds were correct.

However, using Make + ccache + a custom ar wrapper (port the deterministic flags from Linux to BSD), I got all the speed up of tup/fabricate, using off-the-shelf open source tooling. I've never looked back.
No. Nobody thinks that open offices are better for work.

They just think that the cost in productivity is less then the cost of the extra real estate required.

Your estimates of cost are totally incorrect.

When it comes to a difference of 200k vs 300k per fully loaded employee, most managers are going to doubt they are going to get 50% more work out of each employee.
> (Git has a consistency-of-naming problem.)

I wonder how many git usability issues could be solved just by addressing this and this alone.
Then use `git checkout -f` if it so pleases you. There's more than one way to skin a cat.
regarding "out of tree": I'm not quite sure about your explanation here (just looks like a list of source files), but presuming you mean "creates output files in a seperate directory from source", it doesn't really have complete support for that. You can use "variants" to place output files in a subdirectory of the source tree, though.

> "some way for tup to manage discovering the files to build"

Well, no. It's not a "convention" build tool like rust's `cargo` where you just place things in the default locations and it figures it out.

You can use the `run ./script args` mechanism in tup to run your own script that emits tup rules, though.

The manual has details: http://gittup.org/tup/manual.html
For me it was

sudo apt-get install elastic-search

pip install django-haystack

add haystack to installed_apps, add the elastic search backend and set the end point.

use a haystack index class that is prebuilt to hook into all model change signals.

done. No weird configurations, everything was vanilla.

Maybe I am missing a step but it took me less than an hour to get everything going and it hasn't had to have any maintenance.

When you are adding ngram support and all the indexes and views in postgres to replicate the behavior, ES looks to be less complicated. At the very least I don't see a reduction in complexity doing the postgres way just that you have 1 less dependency to worry about.
A few things:

1) Did you mean deadlift instead of squat in your first few sentences? Squat has the bar on your back, so distance off the ground is not an issue...

2) Speaking honestly, if this is the kind of thing that is going to keep somebody from getting stronger, then they're not gonna accomplish much in life. Working from first principles, there are two ways to get a less-than-135lb loaded bar at the right height for deadlifting:

a. Plates which are less dense than steel. You can buy or fabricate wooden starter plates which are the same diameter as a 45lb plate.

b. Rely on something other than the plates to get the bar in the correct starting position. Blocks, books, Tupperware bins, or (if you have one) the safety bars on a power rack all would work.

3) In Starting Strength, the starting weight for each lift is whatever you can lift on day one. If that is below the weight of an empty 45lb barbell, then you get a woman's (35lb), junior (25lb), or PVC (perhaps less than 2 lbs?) barbell. Your starting weight is not the important part, it's adding weight to the bar each workout.

The SS community believes pretty strongly that strength is for everyone. They train lots of people (women and older people) who don't fall into the traditional strength training target audience (men 16-40).
> running git-am on the isolated commit

Huh? That command just turns the working copy into a commit, and mark it as the unique descendent as the commit currently pointed to by HEAD. Worst case, you just created another branch (happens if HEAD happens to point to something other than the last commit of an existing branch).

You wouldn't happen to try and save the state of one branch in the working copy, then using that working copy to update another branch, right? That's just asking for trouble: done naively, it'd cancel all changes made in that another branch.

If you know anyone who did this kind of mistake, do them a favour and explain the difference between a commit and a patch.
Impossible? Try breathing meditation. You shut your mind down in an amazing way.
I don't know if this is not wholly rational, but over time, I became more and more cautious of using any tool for git that wasn't the pure git command line itself. I don't like how the command line was designed, but at least I know what's going on. With other tools (the latest culprit is Visual Studio sync), I often have a reaction of: "You did WHAT?"
Google has all the exact same offerings as AWS.

The IaaS part is called GCE (Google Compute Engine): https://cloud.google.com/compute/pricing

Given all your comments in this thread. You seem to struggle quite a lot to understand the market and you didn't clarify what you want to achieve (how many servers do you have now? how many applications do you run? how many dev? how big is your company?)

So forgive me for thinking you are either a hobbyist or a newcomer, with rather simple needs. If that's the case, GCE and AWS are overkill. You should stick to Digital Ocean or Linode. It's wayyy simpler and cheaper.
that's why mine is next to a tv that sits on broadcast tv all day -- confuse em
Yes! You made me realise that I was applying my own limited view of tv shows (what I see on English TV) and appying that to the whole world.
> I always wondered why MySQL gained more popularity.

very simple

1. LAMP , you got everything packaged, and the database was MySQL
2. soon a lot of cheap hosting options had MySQL as the shared database options
3. phpmyadmin to administrate your website database from a website

I may be missing some history on the PostgreSQL side, but at least ~10 years ago, MySQL was the de-facto option for the wannabe web developer.
Pure JavaScript OCR for 62 Languages
>> the Google brand is powerful enough to create its own Kool-Aid-based distortion field.

Google is slowly building their brand position as 'invasion of privacy' despite their Kool-Aid colored logo.

Huge market opportunities for companies that can sell privacy by positioning themselves as the opposite of Google.
That's fascinating! I noticed your US tab just multiplies the MN output by 50. Can you do a detailed analysis of planting trees along roads all throughout US (or at least the 48 states)? Or is there missing data needed to do that calculation?
TBH if you're looking to do something serious & consumer facing you may want to look into paying for Google's Custom Search API, or if your data set differs dramatically in shape from webpages, hiring a really good data scientist and rolling your own:

https://developers.google.com/custom-search/

I'm an ex-Googler who's now working fairly extensively with ElasticSearch. While I've been impressed at how easy it is to get started, all the published academic ranking algorithms are utter crap compared to what Google has. Okapi BM25 is mentioned as the state-of-the-art up-thread; it was developed in the 80s, long before Google was born, and most of the advances in search since the 90s have happened behind closed corporate doors inside Google, Yahoo, and Bing.