skysight-inc/HackerNews huggingface dataset:
> Changing the size of int shouldn't be a breaking change in Go since pointer arithmetic isn't allowed and everyone should use fixed-size variables when you're relying on this behavior.

All of the "breaking changes" in Rust have been of this form.

We're very up front about any possible breakage. When we talk about "breaking changes", we mean "a change that shouldn't be breaking, but could be breaking if code was relying on this bug/implementation-specific behavior". Those types of changes—changes that might cause breakage in practice but do not change the language definition—are often not considered "breaking changes" in Go. But in Rust we often call them "breaking changes", because we are concerned first and foremost about the practical considerations of changes we make, not just whether we are technically allowed to make them per the letter of the law.
Haha, asking a barber if you need a haircut! I like it. Especially since I am clipped bald. I think I'll go to a barber and see if he recommends a straight razor shave
I'll definitely second this one, I'm still getting comfortable with Clojure Spec and the hooks into test.check (it's brand new, and I'm unfortunately no longer doing Clojure for my day job) but it's already great and I'm only at the beginner/intermediate stage.
Some background about Protocol Buffers:

http://blog.codeclimate.com/blog/2014/06/05/choose-protocol-...

https://developers.google.com/protocol-buffers/docs/overview
It doesn't need to be open source, no. It will host anything in the repo as static content, even if the repo is private.
Seafile now accepts Bitcoin via BitPay
That answers my questions.

I thought I was on a phishing site!!
Haven't played it, but testing an app without any significant load would seem to be pretty different from scaling up the backend to twitter-scale in a couple of days.
Though, I always feel kind of bad about the whole torch-and-pitchforks almost certainly resulting in some poor sap(s) working 24/7 to fix the issue ASAP when it really could have been fixed, oh, Thursday. (assuming the absence of malice, it's just important it get fixed reasonably soon) Especially considering they doubtless have all kinds of other major issues on their plate- like the server load problems.
Am I the only one that would prefer that politics and lazy bureaucrats didn't have the ability to get in the way of my well being in the first place?
Figure 6. Medicare 30-Day, All-Condition Hospital Readmission Rate, is plotted with Y-Axis not starting from zero, which makes it look like there was a dramatic decrease.

Having studied readmission rates, I was amazed, only to be disappointed as I looked at the Y-axis.
I set up a general purpose Docker image for go-rust-swift on Linux platform

https://github.com/ontouchstart/grs

Hope it will make it easier for people to write CLI tutorials.
Angular Utils
This appears to be JAMA's in-house style.

See http://jama.jamanetwork.com/article.aspx?articleid=2533068, http://jama.jamanetwork.com/article.aspx?articleid=2533066, etc.
Great high-level feedback, thanks. I'll add a cost/estimates component to Requirements.
Isn't this a bit: "Accidentally left open gate to castle. Now closed. No fix in place to make sure other people working closely with Alphabet/Google won't leave door open again. Share and enjoy." ?

On another note, from the "privacy policy":

1. REVISIONS TO THIS PRIVACY POLICY

Any information that is collected via our services is covered by the privacy policy in effect at the time such information is collected we may revise this privacy policy from time to time if we make any material changes to this privacy policy, including any change that we propose that will have retroactive effect, we’ll notify you of those changes by posting them on the services or by sending you an email or other notification, and we’ll update the “last updated date” above to indicate when those changes were made

So, they'll let you know if they apply retroactive changes to the policy? How is that any different from "lol, you give data, we do what we want, ok?"
There is a 30 seconds video based on 90 minutes of a collaborative experiment by 22 fuzzing practitioners. Aim was to write down couple of points about fuzzing state of the art.

Video: https://www.youtube.com/watch?v=UrhRUKgeDQI

Text: https://github.com/ouspg/ouspg-open/blob/master/presentation...

Updates e.g. as pull requests most welcome. :)
My unsubstantiated theory is that neoliberal free-market propaganda is discouraging public investment in ventures that private industry would not risk on its own (like renewable energy), at a time when research is more important than ever to handle the needs of a larger-than-ever global population and rapidly advancing climate change.

Some of the best technologies of the last 100 years have been born out of public investment. The need for intense number crunching during the Manhattan Project and the Apollo Program turbocharged computer research. The government's desire to have a self-repairing information network that could largely survive a nuclear attack led the development of what we have as the internet today.

It is unfortunate that the free-market-at-all-costs crowd balks at the idea of the public spending a portion of their money on R&D because they cannot generate a private profit, even though public investment can create new platforms for investment, lower costs for consumers, and ultimately create a larger and wealthier customer base to sell more things to.
Drupal Contrib Module Remote Code Execution Vulnerability
It really is a great paper. I had an entire semester-long course on just this paper in undergrad. So many hours of lessons and instruction and studying and tutorials. And it wasn't clicking. I flunked the exam 3 times.

Then I tossed out my professor's material and sat down with Shannon's original paper for a weekend. Got an A.

Maybe that says more about my professor than about this paper, but it's a great paper.
Maybe server-side git hooks would do the trick? Can we assume that any "decent" git server will be able to run a bash script? A service could instruct the user to download a couple scripts and put them in .git/hooks. Or just copy and paste a wget command from within the repo root.

https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks
Thanks for the comments. This site wasn't my idea, I found it on a dutch startuplist site and was curious what others thought of it.
Go, D, maybe Nim may be worth checking out for this.
delightful read for the inquisitive mind. do yourself a favor and consume this piece of technology writing at its best.
Some of which are Github Enterprise :p
send me an email and please provide examples of your work, including your latest startup: sixquarks@forward.cat
Would help to have a co-author, no?
Huh? Have you ever eaten a cherry pie? Apple sauce? Pineapple on a pizza? Strawberry jam on some toast? Quince paste? Canned peaches? Dried mango slices? Shredded coconut? Any other kind of food made from processed or preserved fruit? Ever drunk fruit juice, or a smoothie? (I have never before heard of someone who only eats fresh fruit and refuses any other form.)

It’s really no different here. We’re talking about, basically, heated fruit sauce mixed into yogurt as a fast and easy breakfast. This isn’t a gourmet restaurant offering.

Frozen berries are a technological improvement on jam/preserves which dramatically reduces the amount of sugar you need for long-term storage, but requires some energy use for refrigeration. If you plan to heat them, mash them up, and stir them into yogurt, they’re pretty much interchangeable with fresh berries, but are cheaper, keep for months, and can be eaten in any season.

Or is it the microwave you are opposed to? If you prefer, feel free to heat the berries in a saucepan or bake them or whatever. I find a microwave to be a lot faster and more convenient for pretty much identical results, but suit yourself..
> Well, for example all the bad stuff TTIP will bring the rest of Europe? Everybody here is pissed about TTIP. Now the Brits vote to get into a position to do something about such undemocratic bs and suddenly they are the bad guys?

As far as I understand it the UK was a very strong driving force behind TTIP..
Getting us into this mess and then leaving before the consequences start to affect you, isn't very nice to say the least.
Many people(including my brother and sister) spread butter on their already frosted, jelly stuffed pastry. In fact there is a song about it: https://www.youtube.com/watch?v=hlsFgDjyePc
I don't know where you live, but had my salaries have always been a 'take it or leave it' deal. The only way to get a bigger pay check here in Belgium is by getting a new job.
This is pretty much the basis of any discussion on jobs creation. In this case there is no destruction of property stimulating economic activity, which to my understanding is the crux of the broken window fallacy.
But with a small fractional multiplier - the ad sense revenue is a measurement of Google's chargeable added value on those sales, not the revenue or profit accrued to the advertiser.
> Changing the size of int shouldn't be a breaking change in Go since pointer arithmetic isn't allowed and everyone should use fixed-size variables when you're relying on this behavior.

Theoretically one should be using fixed-sized variables, but people may not realise they're relying on a particular behaviour. One of the whole points for using a language like Go over, say, C is that humans are imperfect and so having the computer assist is good, and this imperfection penetrates into all aspects of the software process. With a tasty name like "int" and being generally the default type, I'm sure a lot of code uses it when fixed sized types may be better.

> The only thing that changed was the implementation, not the language.

This is somewhat irrelevant: it still results in code not compiling or possibly changing behaviour, because people in fact have to use an implementation of Go, they don't write in an abstract idealised version of it. Rust's breaking changes are generally the same sort of thing (undocumented implementation details, changing the implementation to match the long-stated desired behaviour and bug fixes), but they still result in people's code not compiling or changing behaviour and so need to be handled as such.
Tesla confirms another Autopilot accident
BTW there seems to be a development for some more sensible marking of GM foods beyond the GMO/non-GMO labeling which really tells you nothing of value.

The idea with this is that you put much more information available:

http://www.marklynas.org/2016/07/time-compromise-gmo-labelli...
You have to live to share. So, the distinction is essentially immaterial. They find something that works, they live, they share randomly for kicks with other bacteria they picked up at the bar, those bacteria become resistant, rinse and repeat.
Well, that's my point! You shouldn't need to test various versions of Rust if you there is a strong backward compatibility policy. I might be mistaken but my feeling is that most of the rust devs are using the nightly version thus the reason of a tool to debug/test different versions.
> My problem with these sorts of discussions is that they try to put technical know-how on the same footing as social aptitude, charisma, and other "soft skills".

You really do need some level of each.

Difference is you can reach a pretty low bar in term of social skills, being approachable and being able to communicate, vs a high bar technically.
Well, the device knows exactly what signal it's putting out through the speaker, so it can predict what the microphone will pick up. It doesn't know what someone with a hoarse voice is about to say.
> Someone who can write well can communicate their ideas to a yet-unknown human audience. Someone who can program can communicate their ideas to a machine with absolutely no brains of its own, but with limitless mechanical power.

How is that not a universally beneficial skill?

This is a great point. Programming machines is certainly analogous to communicating ideas to people. That said, machines and people differ in some very meaningful ways. As a result, it's not clear that learning to communicate with machines is of comparable importance to learning to communicate with people.

For example, a small number of people can create an application that provides a service used by billions (Facebook, Google, etc). This unprecedented degree of scalability and leverage is certainly a boon to the case that programming is important. However, it's simultaneously a point against everyone learning to code.

Why? Because when a small number of people can deploy solutions to the rest of humanity, the marginal utility of other people chipping in goes down. If 1% of the population can grow food for the other 99%, it frees up all of us to do other things. It's not all that helpful to spend your time learning to grow food if you can buy perfectly good food that someone else grew. And it's not all that helpful to learn to write a for-loop if you download apps written by other people.

I wholeheartedly agree, programming is a universally beneficial skill. Nobody is worse off for knowing how to code. But there are opportunity costs as well. An hour/month/year spent learning to code is an hour/month/year spent NOT learning X, where X is any number of valuable and applicable skills and habits that might benefit our society more than mass computer literacy.
Gonna show this to my stats students and see if they can identify why it is misleading.
Unbelievable that they publish a non-Doctor with so many potential conflicts of interest that he has to turn in a separate PDF http://jama.jamanetwork.com/article.aspx?articleid=2533698#A...
Ask HN: Should SaaS charge a non-profit?
What are good examples of companies helping non-profits?

What non-profits thinks about companies helping them and about those which are charging them (no free service for non-profits)?

How to make such help good for both sides?

How to check if someone is really using my service for non-profit purposes?
Based on conversations with other founders who have worked in various industries, I have had this suspicion as well. Some founders have no problem participating in the system ("it was like this with magazines—you bought advertising and then the wrote an article about you"), but others share my view and are trying to grow via different paths. Would be very interested in others' thoughts on what's worked for them!
> This is like asking a group of artisans what is the best kind of timber to make furniture out of, I'm afraid.

I agree. I thought I had left this sort of topic behind at Quora.
Thanks for the report! This should now be fixed.
I change jobs every 2-3 years. Mostly because asking for a raise or a promotion is usually met with an eyeroll. Or a laugh. Or some lame attempt at blame-shifting to "corporate."
I don't know how much time you want to put into it, but the first few videos of the Stanford iOS development course (available on YouTube [1]) has a good explanation of how to layout things. I am, however, also a beginner to iOS dev, so maybe there are better resources I am not aware of.

[1] https://www.youtube.com/watch?v=GOEPVM5OzJk
The team at CERN has made big improvements to KiCad, including the push and shove router: https://www.youtube.com/watch?v=CCG4daPvuVI

Another good reason to think about KiCad is if you care about open formats (vs. Altium for example.) CERN's own statement [1]: "We think that KiCad can do to PCB design what the gcc compiler did to software: ensure there are no artificial barriers to sharing so that design and development knowledge can flow more freely."

[1] http://www.ohwr.org/projects/cern-kicad/wiki
The same as it was before publication.
The only problem I see with this strategy is enforcement of the shelving. If someone is sick, and a "shelved" antibiotic is all that is available to them, they will probably take it, effectiveness be damned.
> Can you list the these `aggressive` breaking changes?

Changing the size of int. Changing methods to introspect the type of their arguments and do things differently. And so on.

> There were only 7 releases since go1 and I fail to find any breaking change in the language specification. On the other side each Rust release has a fat list with "BREAKING CHANGES".

Because we have a very specific definition of "breaking change" that is primarily concerned with the practical effect of changes we make. Go does not consider these changes "breaking". Using Go's definition (changes to the language definition), we have no "breaking changes".

If we were to change the size of int (something we will not do, by the way, due to the practical effects of making such a change), then we would list it under "breaking changes", even if we were technically allowed to do it. That's because we care about the practical effects of our changes, not just the letter of the language definition.

> Many Rust packages only work with specific Rust versions(i.e. nightly).

Because they are explicitly opting into unstable features that are carefully marked as such. We can't stop packages from doing that. Nor can any other language.

> The rust ecosystem(std lib, tools etc) is also way behind Go in terms of stability.

The parts of the Rust standard library that are marked stable have remained completely backwards compatible, in both interface and implementation.

> Why do you need rustup if Rust is so backward compatible?

Because it's nice to keep your compiler up to date and to target different platforms?
No, but to be safe enough it has to be more safe than the Rust compiler, because the latter doesn't get run on untrusted code (with the result automatically executed)[1]. If bounds checks exist in the compiler IR, they're subject to optimization, which is very helpful for performance but also risky, as incorrect optimizations can easily cause memory unsafety. Optimizer bugs in modern backends are rarely encountered in practice, but from a security perspective, that's like saying your C++ program never crashes in practice: it helps, but it doesn't prove the absence of bugs that can only be triggered by pathological inputs; such bugs in fact tend to be quite common.

I've never tried to find an optimizer bug in LLVM, but I have found more than one in V8, so I have some idea what I'm talking about.

[1] More specifically, this doesn't happen in situations where correctness of the generated code is relied on to provide safety guarantees. There are several websites that will compile and run Rust code for you, but none of them try to ban unsafe code, or filesystem/syscall access for that matter, at the language level; rather, their security model relies entirely on the OS sandbox the process runs in. Google's PNaCl uses (or used to use?) LLVM on untrusted code, but AFAIK the output of LLVM, the machine instructions, are still run through the NaCl validator, so getting LLVM to miscompile something wouldn't accomplish much. (NaCl also runs both LLVM itself and the untrusted code in an OS sandbox.)
Thanks. Good to hear!

I'm 51, and I'm a "full stack" programmer, which used to just be a regular programmer before everybody started overspecializing. When I learned programming, you met a guy, he told you what he wanted, and you made the computer do that. You didn't say "But I'm just the Java guy"

It wasn't that you were an expert in a dozen things, you just figured out whatever the heck you had to do.

I've kept with this philosophy and it's served me well.

So I dive in and out of SQL. I picked up my habits on SQL intensive projects in the 80s and 90s.

It'll be difficult for me to switch until I get into a spot where I'm using it heavily for a week or two. Hopefully I'll remember this thread then and give the new way a shot. Sounds freaky, but hell, I wasn't crazy about pointer arithmetic when I first heard about it either. :)
> You shouldn't need to test various versions of Rust if you there is a strong backward compatibility policy.

Can you specify, in particular, what you think Rust is not doing that it should be doing?
No, I make no assumption about the the suicide bomber. I'm say he didn't do anything bad. He could kill thousands. Not bad. The reason is that "bad" is meaningless. There is no such thing as right or wrong in a materialistic view. Aesthetics doesn't get you there. If the bomber things that the death of thousands looks good, it is. Beauty is in the eye of the beholder.
Great, because rust is not yet supported on all of the platforms that FireFox itself runs on (nevermind packaged), and that would put many in an unfortunate position.
There already seems to be a 6502 backend for LLVM specifically geared for c64:

https://github.com/c64scene-ar/llvm-6502

Which means you can just use the clang frontend and even write C++17 code which compiles down to 6502 ML.
I'm disappointed that Microsoft has targeted R for embracing and extinguishing. We hardly knew ye.
It will be nice to confirm this over the next several years, but as of now, and despite the misleading graph, it still looks to be a pretty amazing achievement.
Would be interested in talking further about your experience—contact info is in my profile.
No it's like saying I'm going to eat your food but it's ok because it's at my house even though I've just been round your house and taken it.

Real work is done in one location using real infrastructure then real tax is avoided using tax loopholes and countries who want a higher standard of living than their value added labour allows.
No, Ben is an employee. Marcus Frind is the founder of POF and he did make a thread before he was MarkusPOF. It was very early on, not 2009. A couple of years before that perhaps. God it has been so long since then!

The thread wasn't full of people mocking him (wf wasn't like that back then) but people were telling him it's generally not a good idea and he should go niche instead. I've completely lost touch with all of my contacts from back then and I can't find the thread unfortunately, so you have to take it on my word, I guess.
VoltDB is a real fun platform. I've used it around the v1 and v2 era. Incredibly high tx rate (on few-hundred-dollar servers 5 years ago could get 150K tx/sec.) Being able to use SQL is fantastic. The original research papers (Volt's diverged significantly now I understand) are good reads[1].

It's a good fit any time you're considering storing a bunch of data in-memory for performance reasons. (Like telecom routing info.) Instead of writing a custom daemon, just spit it into VoltDB. Get replication, performance, etc. for free! Very neat.

Sadly the open source version isn't very ACID. They dropped the D from community edition. So you can scale out, but if any node dies, you're toast. There's still some uses, where you're running a transient or easily-rebuildable dataset. Or where you can manually run multiple full nodes (though I guess you'd need to implement cluster failover manually).

I guess it shows that it is hard to make a living off of open source products if they're really great. I've heard this from other open-source companies: the product's fantastic, no one pays. But make a taste as open source, basically a demo/trial, and get them to upgrade to commercial.

1: http://hstore.cs.brown.edu/publications/
To give you a little perspective from a rural part of the US:

I lose power at least one or two times a year. Normally due to a construction/farming accident, but sometimes it's due to a temporary overload. Most of the time the outage isn't more than an hour or so.

Last week when a slew of severe storms came through, I had no satellite TV (water absorbs the signal). Switched to Netflix. Netflix signal went out (I'm guessing there's a microwave link somewhere between my house and the phone company Central Office in the nearest town 10 miles away). Could have been worse: some people were without power for days.

We live on top of a hill and I lose my cell signal just walking across my living room. Would be even worse if we lived at the bottom of the hill. So much for 4G!

But yeah, I still prefer living out here to being back in the city :-)