skysight-inc/HackerNews huggingface dataset:
> I mean when can it be considered as released and ready for production?

A fair question :). Let me summarize:

* KDE Frameworks 5 made its first stable release on July 7th, 2014. That's since been followed by Frameworks 5.1 one month later. It's monthly releases from here on out. This is production-ready code.

* KDE Plasma 5 made its first stable release on July 15th, 2015. This was followed by Plasma 5.0.1 one month later. Plasma 5 does monthly maintenance releases, while feature releases are on a three-month interval, i.e. Plasma 5.1 will be released in October. 5.0 is considered a stable release, but it's a dot-oh with some rough edges (nothing comparable to 4.0 at release, though), and the distros are also still doing their integration work right now. The release notes and an errata list provide some guidance there. Most distros will replace Plasma 4 as default with 5.1 or 5.2 later this year, when everything will have settled nicely.

* KDE Applications is doing a 4.14 feature release this month. This will be the last one built entirely on the KDE 4 libraries. Future KDE Applications releases will start shipping ports of apps to Frameworks 5, at the discretion of their individual maintainers/dev teams (some have had porting branches for a good while).

> Will Kubuntu ship Plasma5/KF5 next release (14.10) even if the applications are not yet ready?

I'm not 100% on top of the plans of the Kubuntu community, but I believe 14.10 is still going to use Plasma 4 by default - you might want to look into that more closely though, I'm not certain. I'm sure they'll offer Plasma 5 for interested users in some form as well though. They probably do already. KDE 4 apps still run in Plasma 5, of course, so that's no limitation (and KF5 apps also run in Plasma 4, for that matter).

Yes, on the promo front this does mean we don't get to do a big "BANG! It's KDE 5!" moment, but it also has some advantages for promo - e.g. driving home that KF5 isn't useful just for making apps that run in Plasma, and by implication that KDE Applications aren't useful just in Plasma.
For c# just:

public int Age{get;set;}

no need to declare private variable, get or set methods.
> If only there was a decent launcher on Linux, I could definitely put OSX behind me.

I like synapse, it's very fast and simple.
What's wrong with getters and setters?

It's just redundant code. Most of the time developers don't actually need to override the basic get/set operation on a variable. Yet you have to write the get/set methods over and over.

How do other languages address this issue?

Scala does a good job. You don't need to actually write a get/set method. But if you wanted to modify getFoo() you would simply implement the method with your custom getter
Ah yes, the type inference argument. I give the onboarding here for new hires about C++ and so I get some form of this objection (and the subsequent argument) every two weeks like clockwork. Here's what I say (feedback welcome):

1. Sometimes `auto` helps readability immensely. Sometimes it hurts immensely.

2. All generalizations about when and where to use it are generalizations and likely to start an argument.

3. Ultimately it's up to you and your diff reviewers to do the right thing. There will be people reading your code in the future and they will judge you and your decision, so choose wisely. Future-you included.

4. `auto` can often improve correctness/generality, not just readability, e.g. "int sz = v.size(); //BAD". No one writes "vector<int>::size_type sz = v.size();" I dare you to search your code for it.

5. The only controversial generalization I feel safe making, knowing saying it will get me into trouble, is that experienced non-C++11 (whether coming from C++03 or other languages) coders tend to be more apprehensive and cautious, using `auto` less than experienced C++11 programmers. Take it for what it's worth.
Calling this post "Hiring the best developers is rarely a good idea" was a violation of the HN guidelines. Please don't editorialize titles.
How did Buffett obtain the large capital to initially start investing?
I know that he was always into finding different ways to earn money since a young age, i.e. putting gaming machines in public places, paper route etc... All of these things tie into his incredible work ethic, however, they certainly didn't generate much income.

Initially he said that he started with only 10k after graduating from University. Starting with 10k is a very small amount and would take significant time to grow even if he was making several multiples on his investments.

With that said, you need reletively large sums of capital to make significant profits, so I'm guessing he was running a hedge fund of some sort in the early days and investing other peoples money and taking a percentage?

Can anyone back this up?

Thanks.
It's even freer here: http://libgen.org/scimag/
Mailgun probably offers better deliverability and it's definitely easier to use. Although not that easy, judging by the need for OP.

Other than that, you can whip your server into shape, configure TLS, SPF, DKIM, DMARC or whatever you mean by security and authentication. And by doing that you make a tiny contribution to keeping e-mail decentralized, not turning just yet into a handful of ESPs talking to Gmail.
You really will. Eggs, for example, have been controversial forever [0]. And who could forget the USDA Food Pyramid, encouraging people to eat 6-11 servings of carbs [1]? The 90s heralded the low-fat craze with the mantra "Sugar doesn't make you fat. Fat makes you fat." [2] We've swung the other way in recent years with the anti-carb options that started in earnest with Atkins and branched out to keto/paleo.

Nutrition is tricky and is heavily marketed by extremely powerful industries.

[0] https://www.google.com/search?q=eggs+health+controversy

[1] http://upload.wikimedia.org/wikipedia/commons/6/6d/USDA_Food...

[2] http://articles.baltimoresun.com/1998-10-25/features/1998298...
Here you are:

Source: https://github.com/lhorie/todomvc-perf-comparison/tree/gh-pa...

Live: http://lhorie.github.io/todomvc-perf-comparison/todomvc-benc...

The implementation was written by JP Monette, but it has been refactored several times by Leo Horie (the author of Mithril). Looking at the revision history should give you an idea of the various ways to use the framework.

The current version relies heavily on viewmodels, to the point of making the controller virtual.

Edit: you may also want to have a look at the comparative benchmark: http://lhorie.github.io/todomvc-perf-comparison/todomvc-benc...

Note that the benchmark sometimes returns NANs. It is happens when the todo count doesn't match the expected amount (it's hard to correctly benchmark async code). At the moment, Quiescent consistently NANs out in Chrome, and so do Mithril and Mercury in Safari, but only occasionally.

It is due to the test harness, not to the frameworks or the TodoMVC implementation. ==> Uncheck Quiescent when testing with Chrome, and re-run the benchmark if you get NANs in Safari.
I _think_ the latter interprets javascript while the former only allows you to read the rendered html ?
The dropdowns replacement is really useful all on its own. I wish Bootstrap had that built-in. You should request to have this added this to the Bootstrap Expo! http://expo.getbootstrap.com/about/#suggestions
One thing I'm getting from this particular thread is that I need to focus more on use cases and concretes and less on technology, at least in my initial splash page. For some reason these two responses kind of crystalized that for me... I went to the site and viewed it with new eyes and thought "this would only be appealing to a very narrow, technically focused sort of user."

Here's what some current users are doing:

* "Office LAN with no office" for file, printer, and other devices sharing and collaborative development. One comment was "cool, now we can use git as an actual peer to peer version control system."

* Allowing a distributed team to access a license server that must be online to use some commercial app.

* With bridging to extend an office into VPN-space (regular VPN replacement).

* A few users have used it to create a private backplane network between servers in the cloud. I wrote up a blog post on this:

https://www.zerotier.com/blog/?p=176

* One user is researching it as a way to link together small embedded devices with cellular connections in the field. I've been working with them on this. It builds and runs fine on Raspberry Pi and works over cellular Internet.

* It's got a bit of a following as a way to tunnel out from behind the Chinese Great Firewall, though I'm not sure if that's a sustainable or monetizable area. But I do have one paying customer from this market. It's a commercial user with an office inside China and an office outside that finds it very convenient to have a single LAN spanning their China and Oregon offices.

* The public network feature has a bit of a following in the decentralized networking community. This is not likely to be a direct revenue source but has resulted in a lot of high quality technical feedback.
> I think the fact that sexism reduces the desire of women to participate in something is established.

Nope, I can send you videos from several hip-hop concerts that strongly contradict this statement. I wouldn't though, because that would be an isolated example, taken out of context. I would, however, like to see if, for example – there are other fields which in which women participate a lot despite them being more sexist. 'yummyfajitas mentioned some examples and it would be interesting to ask people in them, "What makes you go into this field despite it having an atmosphere that we in the tech field might describe as being sexist?", and learn something from them.

As people who would preferably like to see carefully constructed arguments starting from first principles, statements like "oh, of course, something is established, so someone who is questioning the statement has an axe to grind" give off a petulant, uncompromising vibe, and should, in my opinion, be avoided. Broadening our horizons a bit as to how people behave in different circumstances might give us some new insights into increasing female participation in tech.

> Most people are socially aware enough to understand that 'sexism doesn't repel women' is a poor null hypothesis

I would like to replace "most people" here with "people in cynicalkane's particular socio-economic milieu". Again, this takes the form of "It is obvious that...", and should be avoided if we want a nuanced, carefully discussed argument about the fairly broad umbrella of sexism.
Ask HN: Should programming resumes be one page or two pages?
I'm finishing my last year of college (graduating April 2015) and I'm updating my resume and portfolio to get ready for a full-time job search in web software development. Most advice articles I see on the Internet advise graduates to limit their resumes to one page, but this advice generally assumes the applicant is trying to get a non-technical job. Most of my friends who work in technical roles have two-page resumes, and I assume this is because the extra page is needed to accommodate a larger listing of projects, programming languages, etc. Is the assumption correct that recruiters expect two-page resumes from undergraduates for technical roles, or should I still limit myself to one page?
Thanks for your feedback :-) I've added it to TODO.
Noke: The World's First Bluetooth Padlock
Hmm, I guess I'm remembering it wrong (I thought they were controlling stuff in a van or something). Luckily, the scenario would still be impossible since every gauge/pump/etc. has a hardcoded interlock that shuts it down if it goes past that limit. You physically can't over-pressurize a steam pipeline because the once the pressure gets above a certain point, the pump is hardcoded in its local circuit board to stop.
That's a very anti-safety attitude. If your assumption of safety comes from the concept that everyone should be perfect all of the time then it is deeply flawed.

Even pilots need systems like ACAS to avoid collisions, and that is on top of on-board radar, significant training, and ATC who are there to make sure such things never occur. Yet how many times has there been a collision averted by ACAS since its introduction? Dozens? Hundreds? Who knows (FAA maybe?). A lot.

If our attitude to driving was more similar to our attitude to airline safety then our roads would be significantly safer today. In the airline industry it is all about continuous improvement and learning from even minor accidents, on the roads we just ignore such things as a "regular problem we have to put up with."
No, he isn't. Can the old urban legend about exteritoriality please already die?

The difference is that noone forces Ms. Knox to Italy, because the USA don't extraditre their citizens, I guess.

Assange isn't in Australia. He's in the UK, and the UK forces him to Sweden.

If you don't see the difference, then there's nothing more I can do or say.
Let's go back to step II:

Imagine that the coin that we're flipping isn't fair, and comes up heads with prior probability p. Further, suppose that the ratio between the small population and the large population is R (in the article this is R = 10 / 100 = .1). In this situation, upon discovering that you're inside the small population, the posterior probability of heads ends up as

p / (R - p * (1 - R))

So what if the coin is very unlikely to be heads instead of 50/50? If p = .001 (and we leave R = .1), our estimate of the probability heads after we observe that we are in the small population only comes up to about 1%.

Thus, the real fallacy in the argument is that the choice of prior is unimportant. (If anyone tells you the prior is unimportant in any situation, they are wrong.) With a suitable estimate of the prior likelihood of Doom Soon, the posterior likelihood of Doom Soon is still low enough.
I think these articles are kind of missing the main point. I don't really care who buys the multi-million dollar houses since I'm never going to be in that market anyway.

The issue that we are seeing is investors (Chinese and otherwise) who are just plonking money in the real-estate market for normal homes. The homes we are seeing right now are pretty basic in the sense that a first-time home buyer would not be considering them if they had a million dollars cash in the bank. Yet these homes are going for all cash or 50% down -- I think the main reason is people with extra money have few options to park their cash; since asset prices across the board (and across the globe) are at all-time-highs.

http://www.nytimes.com/2014/07/08/upshot/welcome-to-the-ever...
What To Do When You Have Your Next Big Web Idea
If the code compiles without error on the new type, then there is a good chance that there is no need to worry about it (unless, say, the developer changed "int foo()" to "short foo()").

And if you use "x" in some way that isn't allowed by the new type, you will still get a compiler error; although the error will be on the line where you use x and not on the line where you declare x. The compilers I've used (Visual C++, GCC and Clang) will tell you where x was declared in the error message.
I do like how C# handled this, FWIW.

public int MyProperty{
get; //public
private set; //private-only setter
}

but obviously there are a lot of ways to skin that cat.
It's true that you can't open a random REPL and change the features of another process.

It is the norm for a webapp in Common Lisp to have an accessible REPL or "remote console".
People are talking about hidden notes but it seems like a better system is to just have all the notes immutable with the ability for patients to comment on line sections (like code review tools).

This way you can correct without rewriting history.
A hash literal syntax in a strong, statically typed language works just fine; conceptually, they aren't much different in that regard than array literals, which Java already has.
Julian Assange plans to leave Ecuadorian embassy a free man
They could, although it'd be needlessly elaborate compared to turning it off, or driving an old car without such functionality. I see more and more luxury cars have things like radar-based collision avoidance built in, which will probably become standard and eventually mandatory on other vehicles. So cars will have to distiguish between what another car is telling them and what their own senses indicate.

Also, but a fit farther down the line, even if a vehicle is falsely sending 'I'm slowing down and driving totally safely, nothing to see here!' to other vehicles, if that message is inconsistent with the vehicle's telemetry (approaching rapidly), other cars are going to know there's something amiss.
In space, astronauts’ immune systems get totally confused
6 Best Social Media Management Tools For eCommerce Companies
No, the core problem is a developer that thought "auto" exists to make code easier to write instead of existing to make code easier to read.
> The obvious flaw in that version is that it is based on finite possibilities: that is, finding oneself in this or that kind of universe out of so many possible ones.

As far as I know, that's a requirement for any thought experiment involving SSA vs. SAA.

https://en.wikipedia.org/wiki/Self-Sampling_Assumption

https://en.wikipedia.org/wiki/Self-Indication_Assumption
"Please use your turn signals." "No, if you get in that lane you block the bike lane in about 100 feet." "Your brights are on!" "If you would be so kind as to reduce the bass just a small bit..." "Are you blocking the post office drop off lane because you're driving a Lexus or have you suffered some sort of heart attack?" Yeah, this'll be good.
WordPress is a CMS (Whether You Like it or Not)
Maybe he should clarify which one then.
I suppose. Things like Stuxnet require government-scale resources, though, so I'm not sure you have to worry about that kind of attack as much for V2V standards.
Yes, that's correct. It is, in fact, the same kind of behavior you get with templated code: you can instantiate your template with any type you wish; compile errors will occur when the instantiation is used in ways that are forbidden by the type. This behavior has been recognized as less than ideal, and the issue will be addressed by concepts. My question is: if we have this behavior not only for templates, but for every variable, isn't that less type-safety? Isn't that less than 'strongly typed'? (Come to think of it, I think I'm really asking about the definition of 'strongly typed'.)
I looked this up:

"Returns pointer to the underlying array serving as element storage. The pointer is such that range [data(); data() + size()) is always a valid range, even if the container is empty."

Can someone explain the semantics? If the range is valid for an empty vector, what does that say about the validity of tge pointer returned? What value will it have for an empty vector?
Ah, finally. An Earnest Voice of reason.
The partnership charter is a great book that will help you form a framework for your relationship with your co-founder. http://www.amazon.com/The-Partnership-Charter-Start-Business...

Keep in mind, 50% of marriages fail and they have sex, so don't think it is easy or even natural.
you can do it in pure ruby with one of the webkit wrappers (i.e. poltergeist[0])

[0] https://github.com/teampoltergeist/poltergeist)
If I'm reading a new function I shouldn't have to mouse over, or f12, a dozen variables to figure out what they are. I should be able to tell just by looking at text.
The purpose of a getter or setter is to abstract the implementation out from the usage. Computed properties (e.g. C#'s ability to replace a concrete property with a virtual property without breaking any code) do this without requiring mindless implementation (boilerplate code) for the common case (a property that is exactly what it seems to be).

As an added bonus, you don't need to write foo.getBar(), you can just write foo.bar and it Just Works, whether foo.bar is a concrete implementation or a computed property.

Look at this blog post for example:

http://java.dzone.com/articles/java-properties-without

The sad thing is the request here is for something more ugly than what is really wanted (this is just automatic getter/setter implementation -- computed properties are better both for developers and consumers of their output.
Still no solution for the GC fragmentation and pauses? Arbitrarily large heaps and data structures?

They are going to improve lock performance, but do nothing to help people avoid locking like lightweight threads. Not waking up a thread and not locking is faster...

It's weird how so many software projects completely lose sight of the fundamentals.

I know I am biased due to how I use Java. I care very little for syntax and syntactic sugar. Reading and typing speed is not a problem for me. Get stuff done on time is and working around these shortcomings eats up my time.
C# introduces the concepts of fields and properties.
I dont remember which is which but I think properties are in fact getters and setters,without the verbose "object.getProperty()" syntax , you just write "object.property" and it's call a getter function or a setter function.

Basically you keep states encapsulated without have to manually write methods,you just write methods when you need then.

Java verbosity on that matter is totally unecessary.

Granted when one use an IDE refactoring features can help,but still... A great strenght of the Java language is its stability.But stability doesnt mean a language needs to be that verbose.
And you can replace it with a virtual property in the future (changing the underlying implementation) without breaking anything. And user code ends up simpler and more readable too:

foo.baz += foo.bar;

vs.

foo.setBaz( foo.getBaz() + foo.getBar() );
D 2.066 released
Thank you for your work on KDE!
Don't know about Win7, but Win8 has one. You just have to disable the "combine" setting and you have a taskbar with one entry per window.
Audi Hacked YouTube Advertising with free 5 Second Ad
It's going to be untyped in the same sense that the following Haskell code is untyped:

foo = [1, 2, 3]
x = foo

We didn't give a type to x, but the compiler will infer it anyway. If foo changes, x will change too. This does not make Haskell untyped, it just means it can add type annotations by itself in most cases (see Hindley-Milner type inference).

Note that that code won't "compile no matter what", because in C++ construction using "=" is already an operation that not all types have. So if foo returns an object which does not have a copy constructor or move constructor, then that line will fail to compile. In the more general case, you'll still not be able to use operations on x that x's type does not support, and that's what type safety means.
This reasoning uses the self-indication assumption, which I tentatively also agree with, but there are some pretty good criticisms of it. http://www.anthropic-principle.com/preprints/olum/sia.pdf
It's almost strange and unexpected that the economic rise of China actually benefits the poorest most. The "rising tide" of wealth has lots of problems, and it is hard to compare agricultural China with the industrial, much more populous one, but in General, most Chinese are better off.

And despite that, the richest want to emigrate, because they can't get any "richer" in China. They need western infrastructure to grow their own utility and/or wealth.