skysight-inc/HackerNews huggingface dataset:
> I don't have much experience with elixir, but that's because I like to stay employed.

While the previous commenter gave an objective and rational overview why he think Go gives him a hard time you can't resist to get polemic.
I was assuming OP was referring to custom-built projects. I too have a CGM (thanks to the recent Australian Federal subsidy) - a massive shame the technology isn't more open.
Why not do your furniture photography all by yourself, DIY
It seems the best thing is to be reasonable. For example, eat a variety of foods from different food groups. Try to expand your pallette. Eat a fair amount of fruit and veg. Ideally, whatever you eat will fit in your lifestyle.

For me, I found a few things (and I've actually lost weight and kept it off for years):

Mostly vegetarian works for me - I eat fish a couple times a month. I had gall bladder problems, though, and have had it taken out. This works well for my body and I like the food. I cook at home 95% of the time. I skip breakfast (I'm not hungry!). I use butter and cream. I also walk often.
How to Brand a Startup Like a Unicorn
> does anyone know why they chose Rust instead of Go for the Parity client?

Maybe ask them? According to their FAQ (https://github.com/paritytech/parity/wiki#our-priorities):

> Minimise Moving Parts: While Rust is multi-paradigm, we aim to write intra-function logic in as functional a manner as possible. Mutability is avoided except where necessary for the algorithm or efficiency.

> Minimum Footprint, Maximum Performance: Maximise references, minimise copying and holding copies. Rust makes it safe. When there are dynamic data structures, provide means for keeping them under control.

> Reliability: Through Rust's language-level memory and thread guarantees and a disciplined approach to exception-handling we can state with a high degree of certainty that our code cannot crash, hang or bomb-out unexpectedly.

But I can't tell you that's all of the story. In the original announcement thread on /r/ethereum, the main point of comparison was C++ rather than Go so ymmv.
Yes it is being used as a verb. It's at least common terminology among speedrunners.

Many games, including the one in question, have an in-game progress tracker. To "100%" the game is to complete everything necessary to make it reach 100%.

For games without such a tracker, the community usually reaches a consensus on what is considered to be 100%.
In my day to day work, I find Go very much in the league of efficiency of C, if, for robust and real programs, not beyond. Low level Go code compiles the same as C code does (yes, C compilers have better optimizers), you have sometimes to pay for some overhead (bounds checks, GC), but that often pales compared doing this by hand in C, when you need a reliable and robust application.
Rust bounds-checks indexes by default (there exist indexing methods which bypass that, they are unsafe).
Sounds like a Hoxton hipster being ironic.
Ink: React for interactive command-line apps
You can generally tell because of the distribution, which tends to show up after lots of data points.
It's not about being good, it's about doing your best and improving every day. Sometimes it's about doing what others would consider bad. Pretending to be perfect is the opposite of progress and evolution.
Strictly speaking you can use any noun as a verb in English. The grammar allows for it, though most nouns will not have a meaningful verb counterpart, semantically, or it will not have a usage that most people will understand (i.e. it won't be colloquial)

So in a speed running context, I would definitely say it is acceptable, but it might not be in the greater population. But the grammar nazi have nothing on this one.
Amazon is building another multibillion dollar business that you haven't heard
Sucrose is one part fructose and one part glucose. Our cells use glucose for energy directly, the liver metabolizes fructose. This similarity of fructose and alcohol is the basis of the whole sugar is a poison.
Fruit is fructose, which is probably why we are to be able to metabolize it, but fruit is generally very high in fibre and around the size of a serving or 2. Serving sizes of juice and additive sugars are extremely oversized.
> Sure enough, most of the scrapers chose to pay rather than babysit web crawlers once we pointed out that our price was lower than their time cost. If your data is valuable enough to scrape, it's valuable enough to sell.

Cool story, bro.

Some scrapers will buy your data if it's good enough, but most can't be identified (good luck with those Tor/AWS/dynamic IP users) and some will just resell your data at a lower price. So as a general strategy against scraping, this is useless.
Applications of machine learning for e-commerce
Go was explicitly designed to be a simple language, without a rich tapestry of data structures to suit every use case.

Languages are like tools. If you need a saw, use a saw, instead of complaining about the knife you are using.
Explanation and working example of convolutional neural networks with keras
I gave rational counter arguments and employment is pretty important too imo. It seems a lot of the anti-Go people tend to favor languages that no one gets paid to use.
Testing Certificate Chains in Go
A very significant part of the population in most 'third world' countries is actually trilingual.
Fir example, Pakistan is divided into 4 provinces, each with its own language and culture. So people there end up learning their local language and the national language Urdu. Most children who go through schools also learn English as a core subject in their curriculum which makes them trilingual. Well, now the government is also pushing Arabic language in schools as a core subject which would make most children in Pakistan tetra-lingual?
The first thing you will get for raising a issue, is a slap over the head for "bringing everybody down" and "not thinking positively".

Many managers view incursions of reality upon there vision as a personal attack.

You are right though, good communication is the best approach.
Side bar, if only Twitter would realize this and turn the firehose back on and charge $x per month for API access.

They'd be profitable in a month.
The war in cash intensifies: Visa offers restaurants $10,000 to go cashless
I appreciate the work that Daria Rose (Kevin's wife) has done with her book The Foodist and blog summer tomato. She had the same problem, but she is a Ph D and was looking for a project.
You do not need to go that drastic. One could consider significant reduction in numbers, even staying narrow to a small set of subspecies (e.g. deer ticks which are much more numerous this year), instead of full extermination.

This happens in nature, too. Predators and prey numbers can take big swings with no humans to blame.
For 10 years NASA has been Photoshopping its astronauts into posters
People with subscriptions are going to GIVE your data away for free.

Ever heard of KAZAA? Napster? BitTorrent?

All sites where people who have usually purchased data make it freely available to others.
Fractional reserve lending of bitcoin would happen in the same manner as fractional reserve lending of gold coins.

E.g. a bank attracts deposits of bitcoin (i.e. the bank gets the bitcoin, the customer gets an IOU/note in legal records saying that the bank owes them a bitcoin), lends these bitcoins out, some of the lent bitcoin get deposited in another bank and re-lent, etc. In this manner the on-chain bitcoins travel around faster, and the total money supply (bitcoin + all bitcoin-denominated IOU's) can easily grow.
Another thing I can think of - Go's interface mechanism overhead is usually significant, and I've also found that the networking stack is slow compared to raw C. When I brought this up on the user group a few years ago I was told that this is a fair price to pay for Go's safety and concurrency abstractions.

I pretty much agree actually. I won't be necessarily writing a database in Go, but for robust and fast application services it's very very good.
Nice project but why using REACT for this as REACT is designed for dom manipulation
What are you contradicting? You are supporting my point. You are sitting in NYC because you're not getting enough money in SF. High rents didn't make wages rise enough to make SF attractive even for you, a hot shot software developer. Now think about all the ordinary people that hail from SF...
This is becoming like 4chan, nightly china hate thread. Stop with it. Yes they kill dogs and hate muslims. deal with it.
Affordability of food is because food prices exclude most externalities (and subsidies). Food is one of the biggest global warming drivers. So we cannot afford more food consumption unless our diet composition changes.
I am not sure where the authors exact requirements fit in the greater picture of the desired application. But one important tool which works great in Go is functional representation. If you want e.g. an immutable map, make it a structure with private fields, and give access vial functions (methods). The first comment to the article describes a nice example of this approach.

I often read criticism of Go which is based on a missing "feature". In my experience, implementing these features is surprisingly easy in Go, as the building blocks are all there. In this respect, Go has some resemblance on Lego :).

My background contains a lot of Scheme/Lisp, so abstracting things with functions comes natural to me. It turns out that Go has basically the equivalent function concept (first class functions, closures, ..) so enables all the powerful abstractions coming from them.
ReadOnlyDictionary has been around for 5 years, and even before that you could implement this with generics in a way that is re-usable everywhere rather than having to constantly 're-write the wheel' as in Go as the author laments.
And java doesn't have them either. You need to use an external library, likely the google containers library.
I definitely agree with you that Go codebases has a high level of consistency. It's certainly one of the many good things Go offers and something I hope other languages look at to see if they can replicate.

But, that doesn't really have anything to do with it being a chore. We can just agree to disagree on that.

However, I think you misunderstood my point about errors (or maybe you're just working with very different types of systems). Empirically, looking at Java codebases, the C# team found that most errors weren't "handled" beyond an outer exception handler. Anecdotally, this has been my experience as well. I admit that this is a very 'web' point of view, where requests are isolated and most exceptional situations are best handled with logging + showing the user a friendly error message.

At this point, they should adopt the Elixir approach and consistently provide a ! alternative across the stdlib (Must* is inconsistently available and verbose). They thought Go would be used by C++ programmers, instead it's being used by Ruby programmers (1). The language paradigm doesn't fit how people are using it as well as it could.

I'm not sure what other languages you've been exposed to, but your last line is hard for me to believe. If you look at other languages, you'll find a lot of techniques aimed at quality and resilience that are nowhere in Go. Again, that doesn't make Go bad, but "resilient" ? Go has mutable, shared memory, nils, no thread isolation, no generics (so runtime casting), no pattern matching and so on. Even the error system which you like is reckless (??) compared to what you'll find in languages like Rust and Haskell (Result and Maybe).

(1) https://commandcenter.blogspot.com/2012/06/less-is-exponenti...
I would think having better safety guarantees is a big reason. Rustc can detect data races, which I'd say it's very useful with an Ethereum client.
"Calories in, calories out" is both true (in the thermodynamic sense) and accurate enough to be useful (in a practical sense). I've personally performed the experiment, using MyFitnessPal and a $14 digital scale, and it turns out that I can control my weight to within a few pounds.

There are a few caveats:

- Yes, your diet composition does have metabolic effects. Protein, sugar and fat all follow different metabolic pathways, and converting between them requires energy. Protein is supposedly easier to store as lean mass than as fat, for example. But unless you're already lean and training hard, these effects are relatively minor. If you want to lose 50 pounds of fat, calories are good approximation.

- Unless you're a hard-core distance athlete, the "calories out" side of the equation is mostly useless. Depending on your weight, walking a mile burns about 1 Oreo. Essentially, it takes a lot of energy to run your brain and your digestive system, but exercise is surprisingly energy efficient. So if you work at a desk job, and you don't run 5 miles a day, then use the "Sedentary" option when calculating your daily calories.

- If you want to be both lean and muscular, things get trickier, because you need to worry about your muscle:fat ratio. You can control this with resistance training. But weightlifting while losing fat can be pretty metabolically brutal. Conventional wisdom says that it helps to watch your protein:carbs:fat ratio, and to eat a nutrient-rich diet. (And my personal experience bears this out, especially once I've exhausted the easy gains in the weight room.)

- Most diets fail because most people stop dieting. If you revert to your old habits, you'll eventually revert to your old weight and body composition. As a general rule, few people stick with long-term lifestyle changes.

Losing weight and becoming muscular are both solved problems. The major challenge is sticking with the behaviors that produce the desired result.
This comes on the heels of banning beards: http://www.bbc.com/news/world-asia-china-39460538

and banning "extreme" Muslim names: https://www.hongkongfp.com/2017/04/25/china-bans-extreme-mus...

China's approach to its Muslim population couldn't be more different than western Europe's.
The OP suggests "some form of codegen" as a way of getting around the Go dev team's, shall we say ... unusual hostility toward generics. But that way lies C++ templates, which were originally meant to be implemented as macro-generation -- and which lead to the messiness and complexity of C++ builds which were one of their major reasons for doing a new language in the first place.
> The study was pre-registered (At ClinicalTrials.gov: NCT02211599), with a clear outline of the scope and methods (protocols) to be used. This avoids bias where only hypothesis-affirming data are reported and hypothesis-contradicting data are hidden or discarded.

This is good to see. I wonder if unregistered studies will ever be ignored like non-peer-reviewed studies are.
So... Go is excellent to write the software it was designed to write and it's no good at other things.
Twitter do charge for the firehose, and I hear it’s a reasonable amount of revenue. A person can’t go and buy it on a credit card, but there are authorised sellers, enterprise sales people, etc.

Bear in mind that it’s a large technical feat to be able to ingest the firehose effectively, so it’s not really suitable for consumers.
https://pbs.twimg.com/media/BzrbmiFCIAEE5HT.jpg
>> the entire error thing is absurd. Anders Hejlsberg got th is right many years ago: 9 out of 10 errors are "handled" by a central error handler

> This is almost always unacceptable in production, especially when it comes to mission critical hard/software. You need to be able to handle errors in production that you may not even be able to catch in testing and that means you need to catch all the errors and think critically about what should be done when that error is encountered.

Absolutely. My approach is usually that errors are always wrapped not just returned. The wrapping itself ends up looking almost like code documentation: "could not do X: <previous error>", "error while doing X: <previous error>". Every error string is then unique in the program, easy to grep.

"Could not perform the operation", maybe together with a 500 lines stacktrace in your logs (which are maybe line-by-line bacause that's the default)... you are up to a nice middle of the night debugging session :)
Key point near the end of the article:

> To Mr. Mandel, it’s not that e-commerce jobs are directly replacing traditional retail jobs. Rather, he describes a world in which some of what he calls “unpaid household labor” that we all do when we drive to the mall, park, shop and bring the goods home has been transferred into the labor market.

So sure, if you only look at the paid jobs, under an e-commerce regime we have fewer paid jobs than under big box retail. But if you factor the previously unpaid labor, we're netting more jobs.
Why isn't anyone protesting those TOS? Them having the apparently unqualified right to cancel the card you paid for is unacceptable.
Expert Exploited an Unrestricted File Upload Flaw in a PayPal Server
Indeed - Elliott waves come in mind too. As un-scientific as those ideas can be, not being expressed in any kind of mathematics, they seem to point at some possible reality in growth patterns. Notably, the fact that there's always a plunge after a first surge - where everybody think it's dead and where it starts a new uptrend - is something that makes me really curious.

Note that it's not just about people expectation either : humans actually went on the moon, they didn't just talk about it, and they didn't go any further in decades. So beside expectation, it doesn't seem far fetched to say there indeed was a plunge in achievements, at least if we consider distance traveled by humans (which should grow again when/if we go on Mars).
Refreshing and similar in sentiment to what the article expressed. Thanks for posting, even if meta. (And keep on increasing the HN SNR with information-heavy posts!)
The Node event loop (the control plane) is single threaded, but the data plane is multi-threaded, you can easily write C++ bindings to run in the thread pool to handle CPU intensive work.
You are right. I cant remember the link but there was an article I read that drinking fruit juice is not the same as eating fruits with fiber.
So it seems that for most of our past, this would actually have been beneficial.

The article says: "We found that drinking a sugar-sweetened drink with a meal significantly decreases fat use and diet-induced thermogenesis (heat production)."

So if food is relatively scarce then this is a good thing.

Feels a bit weird to optimize diets for couch potatoes. The article doesn't say how exercise was done, so I assume it was none.
Live streaming from ISS shows UFO in low earth orbit
To me a digital version is a shared google spreadsheet. Both work well.
In spoken French it's definitely on its way out, effectively leaving only "pas" as a single negative particle. It's a good example of what is called the Jespersen's Cycle

0: https://en.wikipedia.org/wiki/Jespersen%27s_Cycle
> Actually C++ doesn't have immutable data unless you count compile-time constants and literals. You can declare things 'const', but that only provides a read-only (1) view on mutable data.

const std::set<int>& s // This is a read-only view.
const std::set<int> s // This is immutable.

> Another approach is to just declare member variables 'const'. So you have a 'const map<int, int>' as a member variable. Except for that to work, you need to construct that member variable in the initializer list. The body of the constructor is too late. This likely means taking an already-initialized map as a constructor argument and copying it (probably exposing implementation details in the process) or writing a helper that returns the appropriate map type and copying it. Good optimizers will elide many or all of these copies, but relying on quality of optimizers isn't portable.

Foo() : s(helper()) {} // This is a move, not a copy.
Yes, but the discussion wasn't about the employment situation and if--your tone was slightly inappropriate. You could have also written: "I've no experience with Elixir but your words catch my interest. The inferior Elixir enployment situation (compared to Go) held me back from Elixir. But I should give it a try."

Same message and nobody loses his face.
I wonder if this means ending a meal with a dessert it's considered a "no no".
Spot faked photos using digital forensic techniques
I did enjoy the note about gatekeepers (insurance companies and the medical profession).

These scientifically conservative organizations are great for not letting terrible things happen to people, but not at all geared towards radical innovation. Viz the medical community just starting to realize that systemic outcome-tracking might be beneficial towards informing what procedures are more effective in the real world.
To know if you're good, compare your solution/methodology/speed to others better (or worse) than you for a certain task.

Also learning from someone better than you will help you get better at least 10x more than practicing yourself.
When you solve problems other people are incapable or unwilling to solve you may effectively label yourself as: good.

If the problem is a common one and nobody else is able to solve it people will use your code... even if the code isn't good.
No, languages are like toolboxes, they provide you with set of tools.
Go is nowhere near the speed of C.
But why not consider Rust?
You're not good at programming - you should embrace that. I suspect many others here hate the code they wrote 6 months ago. I find that's about the amount of time it takes for my craft to be elevated to a new level that makes the differences obvious.
relevant: https://www.amazon.com/product-reviews/B005MR3IVO/ref=cm_cr_...
> I can't remember having reached for an immutable ordered map in a long career.

Me neither. But I have reached for a fast single producer, multi consumer queue, futures/promises, concurrent safe maps, non-blocking queues, and even plain async queues with batch semantics, many many times.

So either the author, me and everyone else that is claiming this is a problem are doing it wrong or its actually a problem.
Java does have unmodifiable wrappers but they implement the same basic mutable Map/List/etc. interfaces, just throwing at runtime if mutating methods are called. Not exactly optimal but better than nothing.
But you can build and use generic immutable collections.