skysight-inc/HackerNews huggingface dataset:
Would it have all suddenly been illegal if "the client" only owned 49%? I'm very curious about how this all works.

In my non-lawyerly understanding, basically yes. Here is the theory.

If I own something, and you act to deprive me of my rights, then you are a thief and I am allowed to take certain kinds of action to assert my rights. But if I take action and you dispute that I have those rights, then you are allowed to take action of your own up to and including invoking the legal process. What kinds of action are allowed is a matter of local law. For instance threatening bodily harm is not allowed, but taking control of key systems is.

In this case, the act of selling 51% of the company that you run means that you have agreed that the buyer can make decisions under specified conditions, even though you created it and may still be running it. That agreement is why you were paid a (hopefully large) sum of money.

By contrast if you sell 49% of the company, you have agreed to many things, but not that.

There are many cases where sales might come with complex conditions about when someone has veto power over certain decisions. That is why a legal review would have been needed in this case to verify that they were OK to proceed. But fundamentally you agree to a contract about how decisions will be made, and are then bound by it.
Yes. Yes it is.

Bring a lawyer.
> Surely not every meal you eat is such a delight. An awful lot of food is just calorie stuffing to maintain energy.

It is? Not really for me and people I know. You can still make calorie stuffing enjoyable. Even if I'm alone I can whip up a 10 minute meal that tastes damn nice compared to what Soylent is supposed to taste like. E.g. heat a wok with a bit of oil, dump in a package of pre sliced wok vegetables and a handful of cashew nuts. While that is going soak some noodles. After a couple of minutes add soy sauce, rice vinegar, ginger syrup and the noodles, and you are done. With some practice you can make this in 5 minutes. I don't understand why somebody would rather save 3 minutes (roughly 1/500 of a day) and drink Soylent. Can't you sleep 3 minutes less instead?

I've always thought of food like sex. It keeps you healthy, but that's not why we do it. Optimizing food (or sex) to minimize the time spent while ignoring the enjoyment completely misses the point for me, so that's why I find it interesting and incomprehensible that Soylent is so successful.
I could be applying it incorrectly but they just threw out a case of threats over facebook (http://time.com/3903322/facebook-online-free-speech/)
His first one zip2 was mostly luck. After that, he had massive amounts of capital and connections which greatly enhanced his chances for future success. The snowball effect.
How do traits limit you? Could you give an example?
there is often difference between a rant and a credible deliberate threat.
Weird, I have horrible gas, but when I drink mostly soylent then it goes away.
Generally you are right.

However I am paid to negotiate and buy things for people (not real estate). I have even had people tell me that they will pay me more if I can get them a better deal. I tell them that they don't have to do that. That I charge a fixed fee. [1] (And the fixed fee varies btw.) The truth is I get them a good deal because (as I mentioned in my other comment) this is a game for me that is fun and that is the reason that I do this. The money that I make is secondary (one reason is it's not my primary source of income).

In one case I already had a buyer and a seller agree to a deal. The buyer (my client) agreed to the price that I had negotiated and was very very happy. However when talking to the seller I sensed weakness. So I exploited that and got them a better deal than they had already agreed to. Just for the fun of it and because I could. Just to hear the pleasure in my client's voice. Was worth a great deal to me. Didn't make 1 penny more.

So my point is although I think in general (and a book that I can't remember the name of talked about this concept with regards to realtors) you are right there are almost certainly realtors who act the same way that I do in other words they do act in the client's best interest because it is a game for them like it is for me. I guess the key is finding that type of realtor.

[1] Some people who do what I do charge a fee based on "how much they save someone over their budget". So the game there is that they try to get you to increase your budget while knowing that they will be able to buy for much less so they are playing you knowing you don't know what they know about the market.
List of books about video games
Visual Studio Code has Intellisense for Javascript. I never want to go back.
There's no guarantee that CP/M would have maintained its lead. It could have been the case that MSFT didn't just curl up and die but fight and regain the monopoly. Say what you want about Microsoft, but Gates and Ballmer were/are smart and even smarter with business.
The problem with all the talk about 'effective charity' is that it invariably focuses on magnitude while ignoring sign. The great thing about donating to local soup kitchens as opposed to interfering in other people's countries thousands of miles away where we know little or nothing about what's really going on is that there is a much better chance of being able to verify that all the activity is doing more good than harm.
Yup. Read my comment above if you're interested. I had never heard of the guy, but you are being way too easy on him. Presenting the arguments as he does is in my opinion an objective intellectual fraud.
Or just a practical concurrent language with strong libraries that lets you be productive quickly. I'm aware of many of the theoretical benefits of Erlang and Haskell over Go. But Go is still a much better choice for getting things done.
The same FAQ has a question "Why is it case/style insensitive?" and an answer giving four reasons, none of which supports "style insensitivity" in any way.

"Style insensitivity" means that in Nim the following identifiers are treated as equivalent: nOpenFiles, no_pen_files, Nope_NFiles. Insertion and removal of underscores, as well as case, is ignored. I hope you weren't expecting to find anything in your codebase using grep.

It seems a reasonable guess that, oh, maybe 99% of people wondering why Nim is "case/style insensitive" are more worried about "style insensitivity" than about mere "case insensitivity". (The other 1% haven't yet learned that Nim is "style insensitive".)
Are you really asking why you can't substitute PowerShell for a UNIX shell? There is basically no way in which they are compatible.

Even if you decided to re-invent all your UNIX scripts and tools on PowerShell, you'd be missing most of the composable tools that make UNIX what it is.

And PowerShell as a user interface is quite poor compared to, say, a 15-year-old version of GNOME Terminal.
most charities appears to use up the money given to them for purposes other then their stated primary goal... it is always better to donate directly to the people who needs help (unless maybe if you are only doing it for a tax break)
> The cheapest macbook is $1299.

Is there a reason that you are not including the MacBook Air (not that it gets you that much closer to the $299 price-point).
Erlang is probably the only true object-oriented language.

http://www.infoq.com/interviews/johnson-armstrong-oop
I remember when Melbourne wanted to build a new 'city square' sort of area, which required knocking down an existing building. The building was the Gas & Fuel Corporation Towers, which was a pretty boring orange-brick high-rise[1]. A Melburnian all my life, I'd never heard anyone posit an opinion on the building, good or bad, in person or in media. It was boring. It wasn't pretty, but it was just there.

But then they wanted to knock it down, and out came a media campaign where all the newspapers were talking about how ugly it was and what a blight, and suddenly people were ferociously hateful towards it. "Don't you just hate that building?" Well, no. And neither did you until you read about it in the paper. The weird thing was that the campaign was unnecessary (IMO) because people didn't care one way or another. It's not like people treasured the aesthetics or it had some historical tie...

They replaced it with a building that looks like a pile of glass at the recyclers [2]. Admittedly it's not boring, but neither is it attractive.

[1]http://www.walkingmelbourne.com/building465_gas-and-fuel-cor...
[2]http://upload.wikimedia.org/wikipedia/commons/5/5d/Federatio...
[2a]http://www.loftoncollins.com.au/images/gallery/800px-Federat...
Having used both on a few projects, including a JS frontend, my advice is:

"Don't use protobufs if you don't have to".

Protobufs can be much faster, and provide a strict schema, but it comes at the price of higher maintenance costs. JSON is much simpler, easier to implement, and MUCH easier to debug. If your GPB looks like it's building properly, but fails to parse, it's a huge pain to try and decode/debug the binary. You'll wish you could just print the JSON string.

If you need the speed and schema, then GPBs are great. In our case, we got a huge speed boost just by avoiding string building/parsing inherent in JSON.
Documentation only makes software easier to use if it is read. People don't read it.
> When a good idea (e.g., equitable treatment of people) gets branded with a label (e.g., feminism),

Feminism isn't just a "good idea". It has a lot of baggage about what that exactly means that not every reasonable person is going to agree with (such as equal opportunity vs. equal outcomes), and the underlying theories and ways to achieve whatever they are trying to achieve.

Saying that feminism is just a "good idea" is kind of like putting all political ideas and movements into one soup as "good ideas" if their ultimate goals are well-meaning. It just so happens that feminism has an ideological monopoly on gender matters... but that doesn't mean that Feminism==gender matters.
I've been burned a number of times. Both from audits (that was expensive, even after we were told we were compliant) to spending all night up because ReaderWriterLockSlim deadlocked across our entire cluster and took our entire platform down. Also I've had the tools melt like butter in my hands. And I've had my fair share of inherited shit balls. Not only that they've been treacherous bastards historically.

But the thing for me is the cash is pretty damn good and some days you can get so much done its unreal. I've worked with Unix platforms for the same time (20 years now) and know both inside out and windows is way more flexible, particularly when it comes to the end user.

What comes after exbrace, extend is no longer extinguish though. Any sane person these days makes portability choices. We're rebuilding our stuff as microservices now (4MLoC C# projects won't survive without this). Now their stack is getting a look in because we're already experienced with it but if they shaft everyone this time, its trivial to port our services away to other tech. We rewrite most of our stuff perpetually so they'll evolve into zero risk.
Grovo.com | New York | ONSITE | Openings across several functions!

Grovo is reinventing learning for the 21st century workforce and we want your help! We’re looking for passionate hackers, thinkers, problem solvers, and innovators to bring our vision to life. Come join a tight-knit team of 15 developers in a highly collaborative environment, where you’ll help shape the next generation of our platform. From product inception all the way to deploying code to production, you’ll get to make an immediate impact at one of the fastest growing companies in tech. Oh, and the work you do here really does matter. Your code will power learning for brands like Capital One, Major League Baseball, Pitney Bowes, and more. If that sounds good, we want to hear from you! Come join us and leave your mark on the way the working world learns!

We have openings across several functions:

* Director of Platform Engineering: https://boards.greenhouse.io/grovo/jobs/56884#.VWffuGTBzGc

* Senior Software Engineer: https://boards.greenhouse.io/grovo/jobs/69925#.VWff9GTBzGc

* Data Architect: https://boards.greenhouse.io/grovo/jobs/68929#.VWffmmTBzGc

* DevOps Engineer: https://boards.greenhouse.io/grovo/jobs/43973

* Software Engineer: https://boards.greenhouse.io/grovo/jobs/10425#.VWfgF2TBzGc

* QA Engineer: https://boards.greenhouse.io/grovo/jobs/41751#.VWff3WTBzGc

If you're interested please feel free to email me directly at cjenkins@grovo.com

You can also check out our careers page: grovo.com/careers or Glassdoor profile http://www.glassdoor.com/Overview/Working-at-Grovo-EI_IE8108... for more insight into our Culture!
It's reality. I should have included the link. http://www.scmp.com/lifestyle/article/1804420/hong-kong-litt...

The point about genes vs environment/expression is right on, I assumed it was common knowledge and therefore implied.
I think that's the wrong way of thinking about it.

Facebook is not a public service. They aren't required to give anyone a platform and if they see any benefit in banning inmates then they'll just do that.

The fundamental problem is that people treat facebook like a public/regulated service such as the postal system, bank accounts or common carrier internet providers that should provide service to everyone on an equal basis.
Users are entrusting way too much of their internet presence to a single commercial entity.

Just another reason to put further thought into federated social networks. I'm saying "further thought" since I'm aware that current solutions are not practical.
A pretty thin line I would argue.
Lean Startup isn't primarily about building things, it's about the process of customer development.

To make an analogy, before the advent of the scientific method, people would talk about theories, and maybe perform some experiments, but they did not rigorously interrogate the natural world through a cycle of experiments and theories.

Some "flaws" in Science one might point out are: "It's all about doing experiments based on hypotheses, but what about discussing theories?" (In practice, scientists do both.) "Science doesn't tell you what hypothesis to test." (True, not directly; you have to build up a model of what past experiments are telling you and get a bit creative.) "If you run five experiments to test five theories, the only thing you can possibly learn is whether one of those five theories is true!" (Also true, to a point, though you might come up with other ideas along the way. Time is finite; you have to choose something test and not test something else.)

To rebut the article more directly, it is absolutely in line with Lean Startup to build cheap prototypes, or even build nothing and use humans to run a service at first. It's also necessarily to have a dialogue with the customer, but because of the very point raised in the article that customers don't know what they want until they see it, it is not just a single conversation but a series of conversations over time. As the entrepreneur (like the scientist), you develop hypotheses that you can only test by putting something in front of the customer.

When you think of yourself as building the business model, not the product, it becomes even more clear. If a potential customer says, "Heck, I would pay you $X/month just to be able to do ABC," don't take their word for it -- see if you can get them to actually pay for some minimal thing that does ABC, even if it doesn't scale and you are playing Wizard of Oz behind the curtain. That's the spirit of Lean Startup. If they don't make any statements of that form, but you have a strong hunch, then you really need to test it.
> a repeatable and scalable business model

implies rapid growth.
> Is Nim unsafe?

Are the binaries hosted on SourceForge?
What do you mean by "sets of types"? Traits in Rust handle more duties than interfaces do in Go, but in their role as interfaces the only difference is that Rust traits are explicitly implemented whereas Go interfaces are implicitly implemented (i.e. nominal types vs structural types).
I'd argue the point is the opposite of learning new things. As the Go team themselves say, Go is an engineering project. It's about sticking to well understood, well defined ideas that allow large teams of typical skill to develop and maintain good software. Go is boring compared to some other languages that push the envelope and try new things. But that can be a good thing if you start thinking like the business owner instead of a code monkey.
Note that I said:

"After a real estate deal last year I bought the broker a gift and delivered it."

So importantly this was "after" not before.

And it was "a small gift". Not a large gift. (Don't recall exactly perhaps < $50?)

Not a large enough gift to do anything other than say "I appreciate what you have done for me".
I think the author gets closest to the mark in the Conclusion, but still falls short. Go is very attractive as an "upgrade" from Ruby/Python or Java. It's a good replacement for the interpreted languages when speed/performance matters and it makes the async paradigm feel much more accessible. And compared to Java, the fact that Go compiles to a native binary is a huge benefit. It's not a replacement for C or a good "teaching" language, nor would anyone call it "mature" at this point, but it does fill a niche and fills it pretty well.

http://blog.disqus.com/post/51155103801/trying-out-this-go-t...
Tragic Incident Old Man Crushed by a Giant Kite
The target audience for Soylent is people for whom the pleasure of "eating tasty food" is weaker than it is for you. If you think of a use of time that you theoretically approve of but rarely feel inclined to choose over other activities (looking at paintings is an example of this for many people), you have a good approximation of what "eating food" feels like for many people.
There's a lot of luck in everything. I've been involved in startups in remote sensing, computer-assisted surgery, medical imaging, and other areas, and while there were various reasons for the failures luck loomed large in all of them.

The medical imaging play got scooped by a patent issued to another research team a month before our patent application was ready to go (this was before applications were published.) That was pure bad luck. We were a small team who weren't publishing our work while it was in development, they were a small team who weren't publishing their work while it was in development. They started a few months before us, or long after us but had more resources, or long before us but worked more slowly, or didn't go down the same blind alley we did part way through. I defy anyone using the information available at the time to pick out a better set of choices than we made without flipping a coin.

The key to understanding the role of luck is to realize how scarce information is when you are building something new. You don't know how big the market is. You don't know what customers are willing to pay. You don't know what the "killer application" will be. One company I worked with thought they were aiming for selling a service to the bottled water sector. They ended up selling it to the sewage treatment sector.

I also know people who were one decision away from success: if they had taken deal X or added feature Y they almost certainly (in hindsight) gotten rich. Given the information at the time, they made the best choice they could. That it happened to be the wrong choice was luck, and nothing else. These are people who had built successful companies during the dot-com era, mostly. If they had exited at the right time they'd be hailed as geniuses today.
Best Practices of Writing Software to Scale
As for inferior, for what's wrong with it--well, let's start with the easy stuff. The language is not designed to be exploratory and is really hard to write off-the-cuff even when you know it cold. It inherits from .NET in ways that make it actively difficult to type on a REPL (as that's all a shell is). I like .NET, but the BCL is not the right tool for the job and none of the tooling built around PowerShell can compensate for just not being easily written out when I'm exploring a problem by hand. I know PowerShell probably better than most people who use it every day--I'm not an expert but I've studied it at length and used it on the regular for nontrivial tasks--and I can't think in it on the fly. It's a worse solution to a solved problem, for my money, and I'm fairly convinced it was designed to be an RPC layer for GUI apps rather than a way for a skilled and knowledgeable user to interface one's brain with the metal with as little trouble as possible. And that's fine, but that's worse with regards to the things that I care about.

As for substitutability: this should be obvious. I can't substitute it because it isn't interoperable with literally everything else in the stack. It is Microsoft for Microsoft's sake and incompatible with the rest of the non-Microsoft universe in ways that, it must be noted, Apple did not do; while they have proprietary tools in their environments I can still use it with the bog-standard tools that exist on every other Unix machine I ever touch.
This wouldn't work, the majority of users don't read so they would blame Firefox either way. And showing message box every damn time one site has Javascript/SSL (and considering that almost every site nowadays has one or another) would infuriate the users that really want to use this feature. It's a lose-lose option.

I think it's fine to have these options as extensions or even inside about:config, where the user would never disable by accident.
I'm struck by the parallel between architecture in your example and software engineering. You could say the same about the engineers who don't ever consider the humans who will be using their software.
I have seen a few people suggest: http://c.learncodethehardway.org/book/

I bookmarked this discussion a little while ago which has several good links: https://news.ycombinator.com/item?id=9333520

My suggestion is always to work on a real project but for that you need to know the basics of course.
Funny how HN was on the Go bandwagon just a few years ago, and now an article like this is almost unanimously upvoted (without much contrarian discussion(!)).

I contributed to Go in the early phases and I really enjoyed using it and learning it, but I found myself going to either Java if I wanted to write something for production or Node if I wanted to write something as a prototype. Unfortunately, I haven't used it almost at all for the past couple of years :(
This diet for 5 years and you will be dead.

Add more almonds.
mozilla, meet sourceforge.
Got Fury? – Mad Max Fury Road Spoof
git-tfs[0] is excellent.
Amaze your co-workers by actually usefully merging between branches, and work without the dreaded check-out!

0: http://git-tfs.com/
I have never heard of an -ism that people don't personally choose to identify with, and instead other people dictate that they are part of against their will.
This is very interesting. Could you give any specifics? Thanks!
http://2doapp.com uses CalDav to sync task items across iOS, Android and OSX. This works with both iCloud (Reminders) and third-party CalDAV servers, including self-hosted http://sabre.io.

If you sync a 2Do app instance with SabreDAV, you can see that the 2Do developers have added app-specific fields to the standard schema, to store text notes, audio attachments and app-specific metadata, without losing interoperability.

CalDAV clients: http://caldav.calconnect.org/implementations/clients.html

CalDAV libraries: http://caldav.calconnect.org/implementations/librariestools....