skysight-inc/HackerNews huggingface dataset:
> Also I don't really see how Dart is "proprietary" since it is being standardized in Ecma TC52 and is licensed under the BSD license.

I guess most people feel that it's some OOXML-like rubber-stamping process. Or how many of Darts numerous flaws have been fixed in ECMA through the participation of other members?
Selling Swift: what a fool believes
Slightly OT, but I'm constantly amazed what swedes manage to pull off, considering their small population size they have a lot of impact.
mustNotBe?
And, in fact, bubbling errors up is very common in my code:

func (t *Thing) Delete() error {
count, err := db.Delete(t)
if err != nil {
return err
}
if count != 1 {
return errors.New("delete Thing didn't delete 1 row? count: " + string(count))
}
return nil
}
Increase Visits by 200% by setting up wordpress correctly for SEO
Yeah, you're right. I didn't think it through when I asked. I conflated this scenario with the technique they use to put small objects like NSNumber on the stack.
We paid out $41,000 in our first year, and $300,000 in our second. How is something that just grew 632% half-dead?
It is a real question. I get that allowing support@gmail.com would not be a wise idea.
But it seems weird to forbid <randomstring>support<randomstring>@gmail.com.
>So what you're saying is that the fundamental core of Java, Scala, Clojure are anti-patterns ? That's a strong statement for a platform that almost every enterprise application uses.

Just so. You think something being used in enterprise is a worthy argument?
Factors to Consider For Building a Successful iOS App
I worked with a fellow, since retired, who was legally blind. As I recall, he used some text to speech, and also magnification software that displayed characters at a size of may be 10" square.

GSA is a good source for information about tools.
I have a few criticisms of Gittip, with the caveat that I'm largely criticizing you for not being something else that I want, rather than for not doing a good job at the thing that you're currently doing.

1) Is there some sort of legal reason that Gittip doesn't want to manage all of my non-profit giving?

2) What's with the focus on programming? The programming community is tiny, and will be better off piggybacking on the larger culture rather than trying to create one of our own. Why not focus on supporting free culture writ large, like musicians, writers, artists, and charities?

3) The reason my own donation is shitty is because I have to figure out who to donate to and how to donate to them, and then I end up having to maintain as many channels for cash as I have things to donate to. Can't you just offer me curated funds where percentages of my monthly tithe go to a range of things that are often supported together, and you guys just keep it updated?

4) The greatest sin that gittip commits in my opinion is not being donator focused. It seems to be a platform for people to get money donated to them, rather than a platform to manage my donations, as a person who has money.

OK: I hope this isn't too incoherent, because I'm a bit busy; my bottom line is that I want to donate $10K - $20K a year, like many people I'm sure, and if you can help me with that problem, that's where success lies. Right now, it seems like you primarily help marginal people receive money instead of helping me give it.

I want to give to 100 software projects that I know about, and 200 that I don't. I want to give to 10 charities that I know about, and 20 that I don't. I want to give to them whether or not they're aware of gittip. I don't want to be Joan Kroc giving all of her money to NPR because she didn't know of the myriad of other companies that make up public radio. I don't want to spend more than an hour a year on it. Can you help me?
Note that the other two hip languages of the moment, Rust and Swift, also do not rely on exceptions for error management.
I ended up using my own badges from shields.io because the widgets generated for me say "I receive $null from GitTip." And the buttons don't say anything useful: People don't know what "Gittip" is by itself, and "3.00" (actually, for me, they say "NaN") doesn't mean anything either. I made a badge on shields that says "tips|accepted" because I 1) wouldn't want people to know how much I'm making on Gittip and 2) don't care how they donate, really. But I like the idea of Gittip and hope it continues and grows.

I'd love to see actual stories of donors/receivers there, too.
Actually I think Dart has a lot of benefits in terms of syntax compared to Java. I am working with java since 2001, so I can tell. If you are interested to briefly look at it, you can do that here: https://www.dartlang.org/docs/synonyms/

Dart makes me excited, when i am honest :-)
Wow, what a gigantic middle finger to people that try to communicate with you. No, deleting your emails programatically because you haven't got around to reading them is not a good idea. What about all the no-reply alert emails you'll miss?

As for this: "Government departments and legal entities who communicate only through email can override this" - who decides this? The mail provider? Are you trusting the sender to use that flag responsibly?
Yes, we're saying the fundamental core of Java is an anti-pattern. Exceptions are dangerous. At any point in a function, you can suddenly jump out of that function due to an exception. It's certainly possible to write correct programs with exceptions, but it's quite hard, and almost no one does it correctly. If your code isn't chock full of try/finally blocks, then you're not doing it right.

Explicit is way better than implicit by an order of magnitude. It means you can look at any Go code and instantly understand what the control flow will be. You can't do that with languages that have exceptions.
I'd like to see some comments on how Java falls short. I always felt that it had an undeserved bad rap. One way in which it was very bad is terseness - but that's getting much better today with better type inferencing and lambdas.
> You panic when a program is expected to crash because of
> irrecoverable corruption.

Or programmer error.
That would be neat and a very pragmatic choice, but I'm not sure that Kotlin provides enough of an advantage over Java to make migrating worth for a significant amount of Android developers. Scala goes a step or two further, but the overhead (cognitive and at runtime) are a problem too.
Why are they still on Java 6? Oracle stopped supporting it in February of 2013 [1]. What's preventing the move to 7?

[1] http://www.oracle.com/technetwork/java/eol-135779.html
I think a major factor is that TinyOS is written in nesC, so to bootstrap it on a new device you first have to get the nesC compiler ported, then get the OS working. Contiki, meanwhile, is written in fairly vanilla C.
A finely balanced piece providing a solid counter to Kerry's comments, in his own language, backed with legal and historical precedent. It's tough to improve on that.

Recommended reading for those keeping abreast of the situation.
Those are claims that need some serious evidence to back them.
It's sadly much too common to abuse exceptions for non-exceptional situations.

That doesn't mean Go's "error handling" is any better.

It's probably the worst approach one can pick. (But this has been discussed dozens of times already and Go fans have decided that they don't want to hear it.)
Don't panic in the middle of your code. You can occasionally use panic during init() when it indicates a programmer error. Otherwise, just return an error.
The link[1] was on HN frontpage on Friday, I just felt that:

1. I wanted to read the majority of the statements and the interface in [1] was not very appealing;

2. Some content there is really inspirational and wanted to share it with the community.

[1] http://www.tdcj.state.tx.us/death_row/dr_executed_offenders....
I used to be able to easily find the street names, now they're crowded with POIs and I have to zoom in and out and pan around to find the street name.
I don't know what codebases this covers, but GOOD Go code does not panic.
I like erlang's model here. Fail often and fail fast and let the supervisor of that particular node just restart the thing. Bug fixing comes later when you inspect your logs. Do errors bubble up in actors in go like they do in erlang?
Well, Java tried to make it explicit with checked exceptions, and everyone hated that. And checked exception are a much better design than the way Go does it: either you catch, which is like checking the error value in Go, or you don't and annotate your function signature with "throws MyException", which is more explicit and terser.

The thing that some Go fans miss is that it's actually pretty rare (in my own experience, but I've seen a lot of people echo the same thing) to have to deal with an exception. Usually an exception means that the show is over -- at best you'll report it to the user and continue running your main loop if your application is interactive. Or you may retry the operation a certain number of times.

But most of the time you just want to stop the application, or let some upper level deal with it, and those are exactly the default behaviors of exceptions.
Or Google could just embrace Scala. You can already use it to develop on Android, it already has all the good stuff Swift has (and more), you can use all the existing ecosystem because of the compatibility with Java.

Having it officially pushed by Google would mean better tooling and more Scala-ish APIs.
What you should know about the Optimizely vulnerability
SponsorPay is one of the top 10 mobile advertising companies. We are located in Berlin, Germany.

We are looking for Ruby developers (we do mean Ruby, not Rails) and iOS developers:

- You will work in an international team (15+ nationalities) in our Berlin HQ, in a cross-functional team (Devs, QA & Product) using Kanban/Scrum

- You will get to know what bloom filters, hyperloglog and real Ruby multithreading apps are.
- Tons of traffic.

What we offer:

- Competitive remuneration package - German lessons - Relocation package - A team with more than 35 experienced developers, QA, DevOps and product managers

You can have a look to some of our talks:

- Euruko 2013: "..."but we had to kill Unicorns" http://www.youtube.com/watch?v=-q_kS5Dymmc

- RailsConf 2014: "What the Cache!" http://www.railsconf.com/program#sessions

If you are interested have a look to our careers page:
http://www.sponsorpay.com/careers.html#jobs
Gameover Zeus
Thanks! It doesn't do a lot as I was in a rush to ship it on the weekend; I might add some more features if people actually like it. Suggestions?
Objective C is head and shoulders better to program in than C++.

It's still got the same C warts that C++ does in a lot of place, but it is far simpler and less leaky than C++.

C++ is still faster and more cross platform, than objective-c

--Have done both professionally
It is getting better indeed, but there are still features lacking that force you to write code that is much more complex that if you had them.
> First, you're sure to notice the use of the FX branding. Make no mistake: this is the same APU as the other Kaveri parts and it has no relation to the desktop FX processors; AMD marketing simply feels the FX brand has a good reputation among enthusiasts and consumers and they wanted to carry that over into the mobile world.

I don't think customers are going to appreciate the confusion.
11 of the best tricks to run events for your community
FWIW I agree with all the UX feedback but think that the name's great. I wouldn't change it. Also you've got brand equity in it now it would be hard to argue that with zero marketing budget you could outdo it at this stage (plus it's great :)

Best of luck with it, great story!
Why Learning Code is So Important
Cloud Marketer, You Don’t Have a Clue
Every single AAA studio uses C++ to write the smallest portion of their game they can in C++.

Then they put a sane, modern language on top of it many places, Actionscript at EA, Python at many other places, LUA at others, C# at others, and write in a high level language that doesn't leak abstractions like a nut milk bag.
Agree. Kotlin is pretty much Java 8 with Scala syntax. It's neat, but mostly useless.

If Google wanted to stay conservative, they could just support Java 8, but if they wanted something considerably superior ... well, Kotlin is not participating here.

But hey, Google sucks so much at programming languages (see Go and Dart) that I don't expect that they do anything that makes sense for developers.
How is this not an illegal search in the same way that the use of infrared cameras has been shown to be?

http://abcnews.go.com/US/story?id=93127
Hi man, I'm already using your tutorial. I would like to personally say this: Thank you!

I spent weeks trying to get sbt to play nice. I finally said, the hell with that, and I never been happier.
We can do payouts in Bitcoin currently, but it’s a manual process.

We have an Issue on GitHub to remedy this to make it automated while making sure we do it right. Any help would be appreciated: https://github.com/gittip/www.gittip.com/issues/1960
Uberboat
Well, comparing with Java is aiming a bit low, isn't it?

Compare Dart's "shorter alternative" of a bog-standard class ...

// Shorter alternative
class Person {
String name;

// parameters prefixed by 'this.' will assign to
// instance variables automatically
Person(this.name);
}

... with something more modern:

class Person(val name: String) // Done.
Even with dead on prior art, you're still out of pocket $500k to $1.5 million in legal fees before you can kill the patent in court, which is why cost-of-litigation settlements are common. Newer procedures (begun last year) are killing patents at the USPTO with a high success rate for in the range of $100k to 300k.
>> Contiki will soon face competition from the likes of Microsoft, which recently announced Windows for the Internet of Things [0]. But while Microsoft’s new operating system will be free for devices less than 9 inches in size, it won’t be open source. And Contiki has an 11-year head start.

What? Why even mention windows here, these two OS's aren't even close to being in the same category other than they share the price tag of "free". I'd like to see windows try to run in under 128mb let alone the 1mb for linux or the mere kilobytes need for Contiki. A windows mention here seems very out of place.

[0] http://www.wired.com/2014/04/free-windows/
What product designers can learn from iOS 8's iMessage changes
I am unsure about this. It's big advantage is its size and that it does not require as much HW support like Linux (like a MMU). The disadvantage is that it's not a *nix and you loose the whole ecosystem (no Posix).

In my opinion the space that it occupies (the "Internet of Things"), is not well-defined and it may be probably cheeper to use something like a full-blown small computer (like the rasperry-pi) with Linux on it.
I suggest http://www.raywenderlich.com/ and his fantastic books with examples. While I actually think I've been doing Objective-C longer than most of his writers, when there is some area I haven't worked in yet they usually have a high quality, simple to follow example on how do do a thing that's a great jumping off point to getting going and then understanding further once you get the main thing in front of you.
Well, plus I actually grew up in the states!
Because to us developers, we've seen a lot of business folks who just don't get what it is we do. Unrealistic expectations, no concept of technical debt, endless pushes for solid deadlines despite being told things won't happen on those dates, no understanding of what it takes to scale things past a certain level, etc, etc, etc.

If you're an MBA with a CS degree, or even simply someone who has actually done your share of boots on the ground dev work, this attitude probably doesn't apply to you. MBAs have a perception, rightfully so I think, of not really understanding what happens to turn all of their great ideas into working software. There's also nothing like company wide (or god forbid, external) emails promising features by a specific date without having consulted developers on timelines, or worse, having consulted them on the timeline without taking into consideration that it requires moving everything else they're working on down the line to meet that deadline. "Oh, it's just adding a textbox here, plugging it into a formula, and spitting it out over here here and here, how hard can it be? An hour tops."
I'm not really sure if this would be a good UX, but among other technical challenges:

>Government departments and legal entities who communicate only through email can override this, so the inbox owner knows that something has come from DVLA (driving department) or HMRC (money department)

I can't think of any good (and realistic in the present environment) way to do that. How is your email provider supposed to know what senders are authorized "government departments and legal entities"? In a way that spammers (and others who are offended by this UX) can't easily work around? And who's going to decide what entities qualify anyway?
That is a bit heavy handed but I am pretty sure people could be creative with "Gwalletsupport@gmail.com" or "googleplussupport@gmail.com"...
Show HN: Predictobot, predictive modeling made easy
Predictobot lets you build a predictive model without any programming. You upload a spreadsheet of data, specify the column you want to predict, and it automatically builds a predictive model for a regression or classification problem based on the other columns. You download a new spreadsheet, with the model right in the Excel formulas. That lets you make predictions going forward.

Other services like this are really aiming at helping programmers to build models. I wanted to make something that a regular non-programmer could use, to get insight into their data.

It is open for registration now with no invite needed (unless I get a big rush), so register now and have a play.

There are some examples on the site at https://www.predictobot.com/examples/ with little explainer videos. You can play with the results directly, see https://www.predictobot.com/examples/3/ for instance. Click on the little squares and you can interact with the model.

Your first 5 models are free during beta. Your first model will be free after the beta. Upload size is limited to 75MB (since it is for doing spreadsheet scale data, not big data.)

I'd love to hear your comments, good or bad.
Cocoa, the API behind iOS and Mac Objective-C, is the hardest part, and is still there.

I suggest going through some detailed tutorials on building an X, so you get the feel for how views, view controllers, objects and everything all interact.

The new playgrounds look EXCELLENT for doing that! Best of luck
To anyone who is actually interested in the subject, I highly recommend this excellent free class: https://www.coursera.org/course/plantknows
"The U.S. National Security Agency complies with legal restrictions when it comes to using facial-recognition technology on citizens, according to the agency’s new director."

Oh good, the NSA director says what they're doing "complies with legal restrictions". I feel much better now.
Being able to cope with 'rejection' on an ongoing basis makes you much stronger in many areas of life. From finding a mate all the way to gathering sales for your product.

Rejection should not be taken personally most of the time, it is just a signal that you should interpret as your 'hustle' needs refining...
Are you referring to this? - http://users.cms.caltech.edu/~mvanier/hacking/rants/cars.htm...

:)
No, but it can call it.
In other words, you mis-parsed the "plant" in the title to mean "factory". I think you could have said that more succinctly, too. :)
You need a curved display. A 240 degree sphere segment stretching all around you will allow you to display a fully realistic-looking perspective, as long as the viewer's head is exactly in the centre. Or a head-mounted display like the Oculus could accomplish the same thing.
Wish the same was true for emacs. Using a new editor is like learning to walk all over again.
Output of the nesC compiler is one big C-file, so no problems there.
Clickable links:

Main site: https://www.predictobot.com

Examples page: https://www.predictobot.com/examples/

Interact with an example: https://www.predictobot.com/examples/3/
(Hover and click on the little squares).
Indeed the majority of the time the correct way to handle an error is to propagate it up to the caller...no shit. which is why requiring manual plumbing everywhere to do just that is ridiculous. And forgetting this manual check even once is devastating.

And exceptions are not the only thing that do this automatically for you, so this is just flat out horrible design decision.
Docker reslly seems to gain a lot of momentum but there is still a need to mature the tooling around it, this looks like a great step in that direction.

Semi-related see also http://blog.liip.ch/archive/2014/06/01/how-i-use-docker-on-o...
I have an adopted black mutt, and she is the sweetest thing ever.

I fostered an old fat black cat for a year. He kinda hated me in the first month, but later he got around to liking me (I had the tuna!).
I find that I wind up "bubbling up" errors of my own to build a stack trace yet still retain control of my program, like:

func LowLevelCode() (int, error) {
// rest of body...
if /* error condition */ {
return 0, errors.New("LowLevelCode error: " + /* error description */)
}
}

func MiddleWare() (interface{}, error) {
// body of code...
nCount, err := LowLevelCode()
if err != nil {
return nil, errors.New("MiddleWare error: " + err.Error())
}
}

func ApplicationCode() {
// Do cool stuff...
obj, err := MiddleWare()
if err != nil {
log.Println(err) // Prints "MiddleWare error: LowLevelCode error: " + ...
// Handle on a high level, retry connections, etc.
}
}

I'm hoping someone comes in and corrects me with a more elegant way of "building up your own stack trace" without having to do this manually and without panic.
Feedback on our gift recommendation app
I am hoping to get some feedback on our gift recommendation service http://giftri.com

We analyze Facebook data and turn it into gift ideas and I would love to hear what you think about it.
This higlights a point why I actually prefer exceptions to manually passing around error codes.

If any of these calls to panic() are inside libraries, by using that library, you will put yourself into a position where your application will exit without giving you any recourse to fix it.

I've seen too many C libraries doing this too - "mmh - I can't handle this right now - let me just call exit()" (last time this happened was inside a commerical library for reading excel files. If it was confronted with a file that was corrupt in some way, the library would call exit(), terminating my application server in the process. Thanks)

With exceptions, a library can just throw but I as a consumer of the library at least get a chance to handle the error somehow and who knows - I might be able to find some way to still proceed and not crash.

If I don't handle that exception, oh well, then I crash anyways, but that's not different from the library calling exit or panic.

With exceptions, I also never risk that I (or a library I use) forgets to check for an exit code and proceeds to corrupt data (or crash way later at a seemingly unrelated point).

When I fail to catch an exception, I my application dies.

When I fail to check an error code, my application might possibly corrupt data.

Just because implementing exceptions in compiled languages is difficult and messy (C++) and because exceptions are slow doesn't mean we shouldn't be using them. It means that we have to improve our language and OSes in order for them to work without hacks and quickly enough because, honestly, the value they provide to me is big enough to warrant a bit of research.