skysight-inc/HackerNews huggingface dataset:
> By four days in of exploring Go I had mastered most of the language, had a working program and tests, and was adding features to taste.

I felt this way too but then realized the advanced topics of Go really take time to get right. Writing correct concurrent code is non-trivial as you need to tailor your solution to the problem at hand. There is no one size fits all way to write concurrent code. In some cases a mutex makes sense whereas channels work better in others.

Programmers must be diligent when using these tools as well because of deadlocks, data races, or go routine leaks. I think this is an area Rust excels in with its ownership model that eliminates these problems.
If you read the bill [1] (it's quite short), there are a couple of gotchas, but not too many.

1 - Don't go work for your brother's startup. As a family member of certain C-level employees, you're ineligible. Some C-level employees are also excluded.
2 - Early employees that get more than 1% of the company are excluded.

I'm usually among the first to complain when I see the Republicans advocating policy that I find foolish, but it's certainly not the case here. This is sensible policy that corrects a decades-old problem in Silicon Valley and, for that, I support them in this legislation.

[1] https://www.congress.gov/bill/114th-congress/house-bill/5719
Is Rust harder to write than safe, readable C++ code?

EDIT: Reworded it to be more specific
A friend of mine put it into good words: Go and Rust are two big conclusions, to big follow-ups to the C and C++ world.

Go is an easy, fast, and very parallel language. Go is exactly what google needs, in all regards. It makes sense why Go exists, it makes sense why google is creating a way to migrate from python2 to go. Go is easier than hard C and Go is fast.

Rust is the safe follow-up of C, but more familiar than Haskell, Caml and such. It's a pain to get working, it sucks to program in, it requires so much thought, it's just a bloody fucking fuck. But once rust runs, it works and there's a very very good chance it won't break.

And that's also the reason why we'll probably build firewalls and hardened OS in derivatives of Haskell and Rust, and we'll build Google 2 and Facebook 2 in Go. And in my book, that's a good thing.
Solid gold bars. That or top quality stainless steel bars properly passivated and polished. The correct question is what material is near worthless and not usable as a construction brick that is none the less durable and laser engravable. Its going to be hard to beat clay bricks.
Quick iteration on concepts is actually helped by not having to do extensive testing & maintenance work to keep your system from 500ing, which a static type system can help you do. The fact that dynamic languages don't care about your bugs is actually a hindrance.

What dynamic languages have as an advantage is that they allow you to more readily change your system as your understanding of the requirements change. This is where static type systems have traditionally been very weak - they create roadblocks for evolutionary change.

What would be great is a type system which catches your bugs but doesn't block you from evolving. I actually think Rust's use of type class polymorphism ("traits") goes a long way toward that goal, once you learn it.
Accusations are cheap and easy. Facts and evidence are hard.
This isn't anything different from the other two articles he wrote. What's the point of writing a third one saying the same things?
The medical scientists / professors I know have gone through several revolutions in medical science (statins, diabetes treatments, resuscitation procedures, surgical procedures, dialysis, etc.). I wouldn't call them unable to change their habits. In fact, they are few of the smartest people I know.

I don't know about the margins of food, but I consider preparing food from the basic ingredients somewhat time-wasting and costly (when I actually order or buy and prepare them myself). As they can have fine nutritional values, I don't think processed foods can be generalized to be bad per se.
No, not that easy especially when you get to the functional programming stuff. But I find FP hard to understand since I don't use it much.

> this function signature must be EXACTLY like what I wrote or it won't work

This can be seen as a feature in the sense that you can't program by luck: well, this incantation seems about right and the compiler nods its head that it understands and that means something, so it must be right.
If you read why ESR is a Python fan, it turns out to be similar to the reasons he liked Go in this article: ease of learning and a simplicity that led to writing working code on the first run.

http://www.linuxjournal.com/article/3882
Anyone know how / why they're able to send this much data over the controller ports? That seems like a sample rate that's way into the "insane" realm, irrationally beyond what any human could produce.
Proof-of-concept experiments extract true requirements
> the lot of them are closed source

That's wrong. See OpenSPARC, where you can get the Verilog code for the T1 and T2 (Niagara-based) processors. (IIRC this was only one year after their commercial release).

SPARC in general is perhaps not a bad example, since the ISA is open and royalty-free and there are actually independent implementations (well, today only Fujitsu and ofc. Oracle).

It's quite interesting to see RISC raising again after it died rather harshly in the late 90s -- were literally every year a major manufacturer announced the end of an architecture -- and early 2000s (and remained dead rather firmly throughout the 2000s).
The France has a multi-layered tax system.

The 41% is one of the layers.

Before it there is a 20-25% layer that doesn't depend on your income ;)

And it goes on...
but why do you care if luajit is faster than python if everything that matters is computed on the GPU anyways?
dunno- just copying what was in the original article :)
I have found opposite to be more true.
Maybe Japan will become more open to people from other countries living in Japan; I'm probably moving there soon and if you have contracts with Japanese businesses you can self sponsor a visa. Seems fairly progressive to me.
If sequencing a DNA sample became as cheap and common as taking a selfie, then I could see that happening, yes. I also think that would be a very strange world to live in, but recent events have shown that strange worlds are hard to rule out.
You can exercise your options the day they're granted, even if they're not vested.

That said, they're not really worth anything to you until they're vested, of course.
Kunze plans to distribute ceramic tokens around the world to everyone who either funds, contributes to, or advises on the project. Every 50 years, starting in 2070, he says, holders will meet to keep the memory of the capsule alive and to discuss if it needs to be reopened

The problem with this is that if there are enough people around that remember about this and have the spare time and means to go there an dig an opening again, then it's probably not needed because society still exists.

If a some global catastrophe happens that wipes out much of our our modern records and knowledge, then "Oh hey, there's some good books under a mountain in another continent" is going to be pretty low on the list of things that's preserved through oral lore.
>15 years programming here, from VB6 to JS including C(++/#), PHP, Java, Scala, many Lisps... I "get" what you mean, I just want to give my perspective:

When I tried Go I just didn't get what it had to offer. It felt like the wheel, reinvented. I was like "That's it?". I can see how that's appealing but, for me, Rust is a stepping stone on what we should expect from programming languages of the future.

A new language with a new paradigm is going to take longer to feel productive in, especially when the tooling and libraries aren't quite there yet. I can see how that's not good for someone who wants results now.

Rust's ecosystem is very much in its infancy. I expect 2017 to be a great year in terms of both language ergonomics (e.g. see Rust Language Server) as well as stabilization/standardization of very important things like how to do concurrent I/O. If your niche is distributed computing (e.g. I/O bound servers), yes, Rust is currently not going to satisfy you.

I think comparing Rust and Go is not fair for neither of them and, even if both are advertised as "systems languages" they are actually very different beasts filling their unique niches.
Very cool to see R playing nicely with Spark via sparklyr package. The new flex dashboarding feature out of knitr is awesome. The R/RStudio team definitely knows what they're doing and very excited to see what's next for the data science community.
Too early to call. Let the court decide. Point is, the outcome will be significant. If Oracle wins, the diversity initiative that some mainstream media are pressuring to tech companies will take a blow.

On the reverse side, an ethnic quota system is likely to be adapted by other large tech companies in order to avoid lawsuits.
Managers don't want waterfall. They want a process they can understand (waterfall is great here), that gives them a specific date they can point to as when everything is done and they can start making money. Waterfall says it gives you that.

Of course we all know that waterfall doesn't actually give you what it claims, but it says when it doesn't you failed to manage one of the early phases correctly which means it tells them how to fix things: work harder there.
> Note that most code today is written in C, JavaScript, PHP, Java (none of which would win any prizes for theoretical elegance)... rather than ALGOL, ML, Haskell, the various Wirth languages...

ALGOL wasn't actually that bad.
Glad to see this under a better umbrella. The Twitter developers kept blowing off everyones' requests for Crashlytics to support the gradle-experimental plugin (which was necessary to use the NDK within Android Studio for the longest time).
Having just spent the last two months writing Go code, exceptions are the thing I miss most (well, besides the ternary operator and map/reduce operations). Not only are errors painful to debug without stacktraces, but every single method call is followed by three lines of "if err != null {". I am amazed that folks tolerate the sheer amount of repetitive typing required by the language.
I'm not sure I'd call ESR a fan of either. The title clearly states it's a comparison for the needs of one particular project. Reading further makes it clear he nearly called Go disqualified from consideration. I think it's fair enough to make a comparison of any two languages in the context of a particular project. Horses for courses and all that, you know? Comparing them in a vacuum and trying to pick an overall winner is what should be avoided.
The Wirth languages saw fairly widespread use once.
I'm not trying to say that programmer can't take own decision after a week (or day, or hour) of learning new language. I'm trying to say that "teaching" others with such small experience as 1 week of knowledge is useless. It's not about this article, but in general.
... I'd agree. Put briefly, if you're trying to save the day, people first.

But when you stop needing to save the day and want to build something will particular properties , you may find that process has to come first.
Rust and Go are not readily comparable. Rust is a systems language aimed at the same domain as C++ and, to an extent, C. Go is more akin to Java and Python. ESR almost admits this:

"Latency and soft-realtime performance

"Again, zero-overhead abstractions and no stop-the-world GC pauses give Rust a clear +1.

"It is worth noting that Go came nearest disqualifying itself entirely here. If it were not possible to lock out Go’s GC in critical regions Rust would win by default. If NTP’s challenges tilted even a little more towards hard real time, or its critical regions were less confined, Rust would also win by default."

As an aside, if ESR couldn't get Rust's ownership model, I wonder how long it took him to internalize how not to write memory bugs in C?
Sorry, I wasn't clear, I meant trust-less consensus (proof of work).

Distributed transactions in an RDBMS requires trusting all the hosts it runs on.
Something to do with it? Yes. All of it? No.

http://thealternativehypothesis.org/index.php/2016/04/15/the...

http://www.telegraph.co.uk/news/science/science-news/1206178...

http://articles.latimes.com/2011/aug/10/news/la-heb-genetic-...
AWS SA Associate Practice Exam
The idea trade ties prevent war isn't at all credible. The main combatants of WW II had robust trade with each other, particularly Germany and France.
Also, we use JS for rendering - it's a key part of how Lyra works at the moment. We'd like to have a graceful fallback to text, but we need some more engineers first!
Wow. Just wow.

Being unfamiliar with this area I can't tell if this is ridiculously good or just above average. Nevertheless, for _me_ this was an amazing display of both hardware and software hacking.

This kind of falls into the same category of "out of the box" thinking that is used by NASA ground crews to squeeze more and new functionality out of old and distant hardware that far exceeds its original design parameters.

Loved it.
Probably my memory then. Your criticism is fair.

I'll try to mentally split iTunes into two epochs -- Before-iPhone and After-iPhone.

iTunes worked reasonably when it was simply a music library and store, with a simple integration to connect your iPod.

Since 2007, meh...
> It's a pain to get working, it sucks to program in, it requires so much thought, it's just a bloody fucking fuck.

I could not disagree more! Rust is a great joy to program in. I would rather program in Rust than any other language.

Rust is challenging for many people to learn. That is very different.
I don't know that good C++ has been standardized or is enforceable by the compiler. But Rust is hard to write and that's doubly especially the case coming from an anything goes language.
Building a scalable multiplayer game engine
I heard great things about Apteligent, especially from larger apps and teams. Was Twitter using the data from Crashlytics for ads? I am not sure if there's a clear answer, but they are an ad company at the end of the day.
They are owned by people though and your wife's underwear drawer is not a person either.
> Continuous integration is a good thing. Back in the bad old days you'd have three people working on parts of the system for 6 months and plan to snap them together in 2 weeks and it would take more like another 6 months.

Also extremely importantly is it brings you:

* Working tests. If you make changes and forget to or don't run all tests, the CI server will catch it and make you aware. You still have to write (useful) tests, of course, but that's a discrete problem.

* Entirely kills the excuse "Well, it builds on my machine". This means no undocumented dependencies, and the entire build is scripted.

* "Release builds" are a non-event. They just happen all the time, and your "release" is just the latest build that includes the changes you want and passes testing. This removes situations where there's only a limited set of people (eg: one) that can do a full release build.

Doing CI early on is much simpler. Aside from being beneficial from day 1, it is much easier to incrementally add to your build script/environment as needed than to try to create a script later based on a complicated manual process.

Not having CI is not nearly as bad as not using source control, but it's in the same ballpark.
I can't find the source atm, but there was an article on how it would take 300 years for schools in Paris to fill the admissions required for children of bankers.
I'm not sure what you mean by "20-25% layer", but there are other taxes besides income tax in the UK too : National Insurance contributions, Dividend Tax, Capital Gains Tax, etc.

Overall, it's definitely less in the UK, but not enough to warrant saying French taxes are "through the roof" compared to them.
Since you're an expert in the field: How does the insulin for a diabetic patient differ in its fat-storing capabilities from the normal insulin secretion of a healthy person? I agree that there are metabolic differences in people but rarely non-pathological and rarely not age or body mass related. Pathological cases where the difference in metabolism is indicable, we already know how to treat / be unable to treat them. Moreover: type I diabetics tend to be lean / normal weight. So the question is: what is the metabolical difference you are referring to?
AFAIK Azul is pauseless - it never "stops the world". Sure, it stops each thread (that's pretty much required for any synchronization mechanism, especially if you also need to determine the thread's roots), but it never stops all threads at once ("the world").
Systematic discrimination is not the same as literally having a process to explicitly pay non-white people less.
> It's a pain to get working, it sucks to program in, it requires so much though, it's just a bloody fucking fuck

What sucks about programming in Rust? What makes it a bloody fucking fuck? I disagree on both these points:

* Rust enums and move semantics make writing state machines a pure joy. Far nicer than in C++ or Go.
* Pattern matching (both fallible + infallible) is very developer friendly.
* Option<T> and Result<T,E> are totally brilliant.
* It's trivial to add and version-fix a dependency on an external library with Cargo.
* Rust's ownership and move semantics help you to write cleaner, easier to understand code.
"Specifically, OFCCP found gross disparities in pay even after controlling for job title, full-time status, exempt status, global career level, job specialty, estimated prior work experience, and company tenure." https://www.dol.gov/sites/default/files/newsroom/newsrelease...
This is one of the more reasoned differentiation I have seen between the two languages. Funnily enough, it's in both of their mission statements. It clearly shows too in the resulting languages.
Gochujang

I prefer a bit of sweetness in my sauce. Sour.. not so much.
How are blocks not required to be cryptographically verifiable?
in my experience either IO absorbs everything but the most trivial trinkets that I wouldn't ever mess up anyway

You mean you never mess up business logic? IO should only really be used when you need to be interacting with the world, IE, network calls, UI, etc.
> The title clearly states it's a comparison for the needs of one particular project

Hm.. Title is "Rust vs. Go" - looks like title of another one holywar flame article.
Mirai DDOS leak
Rust has had https://github.com/carllerche/mio for two years now, longer than Rust itself has been stable. tokio is just a higher-level, nicer, API.

ESR knows this. It was there in the comments of his previous issue. Yet he chooses to link to a two-year old issue with one comment that says that Rust doesn't have epoll as a source of truth.

Mio can't compare to the baked-in goroutine goodies (neither can epoll in C!), but this blog post is outright dishonest.
Neither of those situations is particularly difficult to handle. My mother has all of those things and to this day she still files a traditional paper 1040 like she has for the past decades. And she's not college educated or especially bright. She just does it because an hour of her time is worth more than the nearly $200 all-in costs of doing a state and federal return with TT.

The IRS could go towards a model where they assume a standard deduction and verified dependents, and issue a refund based on that. Then let people file an amended return with itemized deductions if they wish.

The tax code in the US can be very complicated, but the for the vast majority of wager earners, it's pretty straight forward. The complications come on the business end of things.
I've seen this scenario multiple times:

1. Company needs to raise money

2. Company issues new shares

3. Board realizes "oh shit, this is a lot of dilution"

4. Board decides "okay, who is important enough to keep around" and issues stock grants to those special people to undo their dilution.

Founders and VCs have seats at the board table, and so are always important enough to get grants. Employees do not, especially after exit.

So the two choices left are

a) employees have no protection against dilution, therefore no protection, therefore shares are worth zero, or

b) employees are given protection against dilution.

You can say "b" is never going to happen. That's okay. It means that "a" and it's obvious conclusion happen.
That was my first thought, but if it gets spun as "The Trump administration went easy on a company giving US jobs to foreigners" it could get sticky.
I'm far from an expert on these things, but is this a mischaracterization in your opinion?

https://www.theguardian.com/us-news/2016/feb/24/obama-guanta...

Just one example: "The day before the Archives speech, the Democratic-held Senate dealt Obama’s plans an even harsher blow. By a blowout bipartisan margin of 90-9, the Senate rejected financing the closure. A Senate leadership aide at the time, stunned by what she considered White House lassitude, explained why even people inclined to help Obama would vote against the measure: Obama had decreed Guantánamo be closed without presenting lawmakers with a specific plan they could defend to skeptical constituents."

To be fair though, there's a lot in that article to justify getting angry at both Democrats and Republicans. For example:

"As implied by the term, Graham spent the summer of 2009 looking beyond Guantánamo. His basic proposition to the White House, reported in detail in Charlie Savage’s 2015 book Power Wars, was to deliver the votes in the Senate for shuttering Guantánamo and opening a replacement facility. In exchange, Graham wanted a broader wartime detentions policy than Obama was willing to embrace. It would allow the US military to continue making captures far beyond the declared battlefields of Iraq and Afghanistan, sending them to the alternative site. When trial was an option, it would occur in the military commissions."

Dirty politics, absolutely unacceptable (to me).

These things are extremely complicated. I really dislike this simplistic recurring narrative (not you specifically, I'm speaking in general) that everything is the Republican's fault. I have no problem believing this is usually true, it is the implicit assertion that it is always true that bothers me.

Although, the Republicans now have a historic opportunity to show their true colors with no excuses....I am ready to be extremely disappointed.
More often than not you will find opposite to be true.
I have two favorites. There's the basic sriracha (and various gourmet knock-offs). I also really like the smoked chipotle version of Tabasco. It's cheap, not super-hot, and has a terrific flavor.
GC must also reallocate used memory to avoid fragmentation of free memory. Do you know a true fully pauseless algorithm for that?
That's a pretty complete list of false equivalences.
It doesn't matter.

He's either "protected" in Russia or dead. I seriously doubt he could return to the US without suffering some horrible traumatic body-and-evidence-destroying "accident" ...