skysight-inc/HackerNews huggingface dataset:
Player’s cancer diagnosis unites World of Warcraft community
Show HN: Sweetlyclean.com – Need Advice on SEO and Feedback on Iteration 2
https://developer.mozilla.org/en-US/docs/Web/API/Window.matc...
SEEKING WORK: US or remote. Will travel.

- Python - Django, Flask

- PHP - Codeigniter, Laravel, Wordpress

- Objective C - iOS 7

- Java - Spring

Why me?

I have been consulting with startups for the past 5 years and have a proven track record.

Contact information: Please look at my HN profile.

## Note ##

Get in touch even if you don't require my services. I might be able to connect you with the right people.
A Space Company You Haven't Heard of Worth Billions
Fresh Food Delivery Service Launched
New All Natural, Organic Hair Recovery Products by Moroccan Eco-Biologics
To people worried about fragmentation, retaining binary compatibility means it really doesn't matter. Scalaz can be written in the Typelevel fork and you can use it without issue from code compiled with the standard Scala compiler.

Also, from the announcement:

"As a conservative fork, our aim is to be merge compatible from the Typesafe Scala compiler, and a key objective is to feed pull requests (many of which will resolve long standing Scala bugs or feature requests) back to the Typesafe Scala compiler."

So we aren't looking at radical changes, and hopefully these changes will get into Typesafe's compiler.

So basically it's an opt-in better Scala compiler with no effect on compatibility. What's not to like?
There are tools to make use of HTTP in all sorts of ways. Curl, Wget, Restful APIs, Sinatra, Grape, etc. Fast, flexible, lightweight.

Email - not so much. Want a local email server? There's Postfix - yuckkk. The overhead of spam - yuckk. The lack of tooling, the lack of configurability, the DNS complexity. The fact that it requires a SAAS to do shared inboxes. Yuck.

Email could be so much better.
Just be glad it wasn't "boffin speak" as the contemptuous British press are so fond of.
Bigger discussion: https://news.ycombinator.com/item?id=8251945
Uber taxi app banned throughout Germany after Frankfurt ruling
Makes YC look bad, that's why.
DataCollection.js – Manipulate data from API responses with ease
Any feedback on SEO, the site, recommendations, call to actions etc? I've done a soft launch while i work on the local SEO - i.e. get on yelp, google plus etc. Looking for all and any feedback. This is my second iteration/rewrite of the website.. almost feel like I need another major tweak. I like the look, but I'm just the owner. I like everything i do.
Curriculet - Full Time - San Francisco, CA - http://curriculet.com

Curriculet enables students to read more deeply and teachers to teach better in their classrooms. We're an online reading platform that allows teachers to embed lesson plans on top of books, articles, other texts. Our team is made up of former educators and startup veterans. You'll be joining a well funded company that is <10 people.

Senior Software Engineer:

* 5+ years experience

* Smart, motivated, ready to build something that isn't another todo app

* Ruby on Rails / Backbone experience preferred, but not required

Mobile Engineer:

* iOS or Android (or both!)

* Someone who can own the entire app cycle from development to deployment

* Has an opinion about API design and isn't afraid of looking at backend code

Introduce yourself here: jobs+hn@curriculet.com
A brief look through Front suggests that it is a specialized ticketing system. I predict that, if successful, it will incorporate more traditional ticketing system features.
Awesome thanks!!!!
Dockerfile config and custom runtimes for Managed VMs
Simple Java SSH Client
Maybe you could present a paper? Because amongst most hunter gatherers researched the modal age is much lower...
Managed VMs Cloud SDK for Trusted Testers
Why isn't anyone making servers with them?
They are obviously in violation of German law. What exactly is it you're arguing here?
Red flag. Copy-paste from another comment: "37 old Java professional from Sweden spends all of his savings in two months? You have 5 kids or something?"
This is a collaboration between NutriSystem and the startup I'm contracting with, FreshRealm (http://www.freshRealm.co), that is launching today.

FreshRealm has some pretty amazing tech in the logistics chain and in their patented shipping vessel. They're currently only in Southern California, but of course plan on expanding to be nationwide. Feel free to ask any questions, I can pass them on to the folks here!
I know it's such a tiny point, and very much off topic, but please don't "pluralize" words such as Kanji, Katakana, etc. As someone who has spent a lot of time learning Japanese, and who knows that Japanese words don't change between singular/plural (with certain exceptions, such as attaching "-tachi" to a word), seeing you write "Kanjis" or "Katakanas" so many times in a row really bothers me.

I'll go back to my corner and leave you alone now.
From a couple slides later:

Given the extremely tight coupling between the template and it's context (a controller/component), the concerns are the same, and splitting the DOM into a template is an arbitrary separation of technologies rather than a legit separation of concerns
Why we should encrypt everyone's email
Email is wonderful and terrible. SMTP is pretty simple, and everyone with a static IP can run their own email server. Configuring it requires some study, but it's not too hard.

OTOH creating email clients is hard. I wrote a web server and wanted a webmail client. Basic SMPT messaging is straightforward enough, but MIME is a confusing tangle of protocols and rules that is difficult to understand and implement correctly.

I mostly succeeded but it took a long time. Part of the problem is the complexity means protocols are often violated and my webmail client has to deal with loads of exceptions to protocol rules to work in the real world.

But that's hardly limited to email. Look at http, it has arcane rules too, and some of the common security issues on the net are the result of "sloppily" implementing programs using http. (You know, XSS attacks, SQL injections and so on.)

Email has warts but what doesn't. Certainly email "replacements" will have warts too, especially as they are extended to cover the breadth that email has encompassed.
Oh no that is all a little too pedestrian for me. I've moved my sights much higher now. These days I use template haskell and applicatives to generate HTML forms: https://github.com/yesodweb/yesod/wiki/Multi-select-field-po....

I'm all for applying theory to enrich the practice of programming but lets be reasonable here. Lists and Options existed way before anyone added monadic sugar on top of it as did mapping and filtering collections. I like category theory as much as the next guy but lets just pull back a little bit. Not everything needs to be point-free, functorial, and shapeless.
We've been bitten by this as well. We started several projects within a few months of each that also used what we believed to be similar enough versions of Play but there are just enough inconsistencies between versions of play (and Scala language versions as well) to make it exceedingly frustrating to work with.
Why would the US invade Canada in that position?
Desperately Seeking Cofounder – Gaps and Overlaps
I would agree that emails are not suitable for some use cases. Many to many updates on many projects, as you pointed out, is one that email is not a suitable medium. However, I don't see that particular use case as significant by the normal Internet users, rather an enterprise problem. The fact that emails have used for that just shows its robustness and popularity (hey it's good enough and all the people I need to connect with have it, so why not just using it?)

I don't think your analogy with vinyl records app as emails are actually the electronic version of the communication method human have been using for hundreds (if not thousands) of years: mails. People know exactly how to use email and what exactly do they expect from emails:
- to send an email, you need an address
- to receive emails, you need a mail box
- once you hit send, you don't have control on the emails anymore, some thing (or post office workers) have control of it
- you don't expect to get a reply right away, that lowers your expectation of an instant reply
- a lot of emails are replies, which means there is a strong context which is what was said in the previous emails

There are many other good things with email such as the openness, federated and robustness nature of the underlying technologies. However, just from the end users perspectives, it matches perfectly with a communication model that most humans have used and understood for many years, and one that doesn't go away very soon.
Because it's such a thin layer over JavaScript, you don't have to port/reimplment all the stuff that JavaScript has already solved to your templating language / abstraction of choice. I still prefer Handlebars, but JSX elegantly sidesteps lots of issues at the expense of not actually being real HTML and handling flow control stuff somewhat awkwardly, but you really gotta try it out to get a feel for the tradeoffs.
After reading the FAQ, I think you just need a simple blog system with every category representing a special timeline. And you only need to modify the theme.
I think it is an interesting strategy, creating what is essentially an alternative to ARM/Mali as a single license SKU. There are rumors floating around that this chip is in a soon to be unveiled Chromebook. I take those with a large grain of salt since every hardware vendor seems to say "This is in the next gen (Google/Apple) device!"

Would love to see additional competition here, but Imagination has not been very forthcoming in the past on specs, so maybe Surface material rather than Android/Linux material.
I agree with the author's premise.

Email is the ultimate "killer app" you can digitally deliver anything to anyone via email, and many folks use it for all sorts of different processes and purposes. Solutions that claim to displace email don't really displace email -- they displace common use cases that were handled ad hoc using email as a lowest common denominator. Most of these use cases cry out for a more structured solution.

For example, There are 1,000 services that displace emailing pictures to each other. There is probably an order of magnitude more services for managing tasks, approving things, exchanging quick exchanges, or performing any number of other tasks.

But at the end of the day, for the core function of email -- unstructured written communication, email is the king.
Encrypted SMTP is already in widespread use. Many MTA's already receive and deliver email over secure channels, and email clients (e.g. Outlook) have supported secure channels for a long time.
$10B Snapchat Valuation – Lessons for Founders
Heh, this completely contradicts this recent piece. Thanks.
Then you didn't understand what JSX is. JSX is just optional syntactical sugar for declaring (virtual) DOM elements. You can use all of React with JSX and your code will be only slightly more verbose.

Your objection is to the very tight coupling of the DOM to React's component abstraction. That's a very valid objection, but unrelated to JSX.
I'm pretty sure IG doesn't like any names that have Insta or Gram in them. (That's why Webstagram changed to Websta). Just a heads up before you develop your brand and then get kicked off their API.
As someone who's been using Scala for the better part of a couple years:

This seems more like a more ambitious version of the Shapeless and ScalaZ libraries (with some of the same crowd/authors).

I (and I suspect most people who program in Scala for a living) don't use those libraries. Not because they're in any way bad. But there are trade-offs using them IME. The biggest being compile-time. So I get by fine without.

I think this is probably generally good news. In the same way that (I believe) JRuby pushed MRI forward and popularized the case for a multi-threading VM, more advanced type features in this fork probably benefit the Scala community as a whole.

I certainly don't see how it could be harmful. Typesafe isn't going away. The vast majority of businesses will still use their compiler. If you didn't use the advanced-type-based-libraries before, this news probably isn't going to impact you anyway.

So from where I'm standing, having made a late 2.9 to 2.10 transition, and now having made several 2.10 to 2.11 transitions, Scala seems a very mature language/platform to me. Libraries are generally upgraded fairly quickly, and source wise, those releases broke very little (2.11 being the biggest culprit just because of the modularization effort, but that's pretty trivial to resolve).

I dunno. It's not Java. But it's not Ruby either. It's gotten new features since 2.9, but it's broken or changed very little. I find working with it, even working through upgrades, very stable and mostly frustration free.
And in Germany it's absolutely nothing like that. The cars are nice (usually Mercedes or BMW), the drivers are always friendly, for years and years we've been able to use an app to get a car in minutes. This is in large part because the city enforces it. So what's to disrupt ?
Don't Break the Net
True, and the cellular wave has made many phone numbers one-to-one rather than one-to-household. But for long form communication, SMS is rather painful, but it would be interesting to see something like Front built on top of it.
I know. I was projecting the shitshow in the payment processing industry onto a national ID program in order to argue that the same techniques used to extract money (not to mention anticompetitive staying power) from the payment-processing system would work just as well if not better in a national ID system.

Is MasterCard to blame for those ridiculous sytems? Not specifically, but if the same incentives are in place (and they are, that was the point of my imaginitive story) then I fear that anyone involved in the business end of a privatization effort for, say, US IDs could copy the business model of "half-ass the security to generate pain, make your money as the exclusive provider (or licensor) of half-assed solutions to the generated pain." It's a good business model, which is why it's imperative that we keep business interests away from the most lucrative targets.

Alternatively we could try to fix this horrendous perverse incentive, but I think that's a much shakier approach that would be much easier for the wrong people to work around.
The last paragraph of the article basically says that, but the title needs to get people to click.
http://wish.com/s/9dDgKQ
I get that but disagree with it. I don't see it as an arbitrary separation but a necessary one based on separating the view (which a team of designers can freely modify without worrying about breaking anything or even touching the logic) from any logic that can handle events.

Honestly I try to use messaging where possible for these types of things. The last app I wrote should, theoretically, be able to be moved from an HTML app to a node-qt app only by swapping the views.

But like I said I haven't had a ton of experience with either so I can't make any good, factual points here only my personal preferences and anecdotes.
Forever is a strong word... but I do believe that email will stand still for some good years.

Email will last forever because email has been around since... well... forever. That is one key factor that the article misses: practically everyone is used to email. It's really tough to replace something so well known and widespread.

I guess the desire of doing so it's due to so many people struggling with email. How many times have I peeked people's email client looking to hundreds, heck sometimes thousands, of unread emails.

I always had inbox zero. I won't say that for me email is a joy, but is definitely no struggle. I guess I'm more organized than most people anyway...
If you cannot trust OSX, there is no reason to trust a browser extension as it can be compromised... so why not stay at the lowest possible level.
Automatic iOS App Testing (by app exerciser)
> how do you parlay technical strengths into increased responsibility & promotions.

Suggest tech focused projects that might serve the companies unmet needs. Sales & Marketing might need a dashboard to asses the customer pipeline. The CFO might need a tool to monitor energy usage & costs. Volunteer to help, you'll get known as the brains who figures stuff out.
Don't use it. JSX is a syntactic sugar for you to manipulate HTML-like stuff, but it's all javascript in the end. It's completely optional.
you can open a producthunt or hackernews focused on indian startups..
Okay fair but I still dislike the JSX syntax :)
I built a social media analytics tool. Check out the video on the homepage
It doesn't even have to provide debit. Banks here in Portugal also issue cards for university students, in partnership with them. In the end it's just an advertising scheme, you don't need to have an account to attend school :)
This is not an example of evolving syntax. It's just a bunch of parameter sets added to Where-Object. New syntax is the -in operator for example (reverse of -contains).

However, I find myself using the new parameter sets for Where-Object very infrequently. Since they can only model

Property -Operator Value

their use is limited to certain operations, which I find myself to need not that often. And if the conditions get more complex I need to write a scriptblock anyway, having to refactor your former form into the latter.
We're reluctant to make language up in titles, but since that phrase appears on their About page, it's fine and we've changed it.
Japan Is Launching an Asteroid Mining Space Program
What a useful way of putting it.

Can you think of an institutional or cultural way to get people in the West out of some of their consumer credit traps? I don't think the lenders are going to help!
Invited Technical Co-Founder: the role you don't want to be in
Sorry, this is beyond factually incorrect, and only proves you never dated before email.
The WSH can be disabled via group policies and often is.
Third flight in nine days diverted by fight over reclining seats
If the rule is a) designers only touch .html/.hbs files and b) only developers touch the view/controller .js files, then if either of them change a property name from `{{displayName}}` to `{{display_name}}`, the whole thing breaks, which is the coupling React is trying to avoid by keeping these similar concerns within the same technology/file (JavaScript).
"It's such a tight coupling to the DOM which is just the opposite direction I want to go"

That's what I liked about ExtJS4.

They had their own "virtual" component model, which then was rendered as DOM later. But the DOM could change in different versions, because of performance reasons.

There was/is probably much wrong with ExtJS, but I liked this approach.
IMO, written communication en totale will fade away within the century. Thinking [0] is much faster.

[0] - http://emotiv.com/
>I'm all for applying theory to enrich the practice of programming but lets be reasonable here. Lists and Options existed way before anyone added monadic sugar on top of it. I like category theory as much as the next guy but lets just pull back a little bit. Not having needs to be point-free and functorial.

I agree that Spire/Shapeless/Scalaz tend to go far beyond anything I would use in a production app, but Options/Futures/etc are barely usable without for comprehensions, which are just syntactic sugar for flatMap. I see the ability to write

for {
x <- f1() // returns Option[T1]
y <- f2(x) // returns Option[T2]
z <- f3(y, x) // returns Option[T3]
} yield foo(x, y, z) // for expression returns Option[T4]

as a huge part of Scala's success
Spreadsheet Driven Development
One more book I found to be useful, at least for its introduction to the hyperreal number system: http://www.amazon.com/Infinitesimal-Calculus-Dover-Books-Mat... It's short and focused.
Indeed. Most of what I've implemented so far can be captured in a blogging service, except for the timezone support (but you can still argument that a simple theme with javascript can do that).

But I'd like to do more with the structural data of timelines, e.g., visualization, today in history, ...
Ember definitely smashes Angular in terms of 'big apps', it seems it's somewhat behind Backbone.

Ember:

* Vine

* Twitch

* Square

* Heroku (dashboard)

* NBC News

* Discourse

* Huboard

* Travis CI

Backbone:

* Rdio

* Hulu

* Disqus

* Khan Academy (also uses loads of React)

* Stripe

* AirBnB

* Pandora

* Trello

etc etc..

Backbone has been around a lot longer, but Ember's apps seems to be built more recently.
Personally, I wish there was a GraphemeCluster class, with a way to coerce a String into an Iterable<GraphemeCluster>, Collection<GraphemeCluster>, etc. Because most of the time people don't want to iterate over code points - they want to iterate over user-perceived characters instead. It makes more sense that by default "école".reverse() (that's the two-code-point version of "é") would be "elocé" rather than "eloće".

But I've said a lot on the subject of strings already:

https://news.ycombinator.com/item?id=8198811

https://news.ycombinator.com/item?id=8066158

https://news.ycombinator.com/item?id=7606084

https://news.ycombinator.com/item?id=7574665

https://news.ycombinator.com/item?id=7075858
Adding keywords: ruby, rails, devops
Totally agree. Which is why I'm excited about the Gmail API and Inboxapp
The service looks interesting, although I can't comment on it as it isn't available in my area.

I did, however, want to say the the trend of fixed menu bars on web pages should be carefully considered before you choose to implement it. On my screen the fixed bar takes up roughly 1/4 of the available vertical space (safari on a 15-in MBP). This makes reading and scrolling feel unnatural, as it's difficult to contain some of the longer sections in a single screen.
To the point of needing email as soon as you're interfacing with a person outside of your group: I'm seeing more and more options for this built into things like HipChat and Slack (both of which have the concept of 'guest' users).
Everything looks fine. Please try to modify the css of the top frame. It looks little old. You can try modern flat colors.
Salamander skin peptide promotes quick and effective wound healing in mice
I just finished reading Astoria: John Jacob Astor and Thomas Jefferson's Lost Pacific Empire: A Story of Wealth, Ambition, and Survival[1]. It's a about a piece of american history that I had no idea had ever happened. The Lewis and Clark expedition is generally well known...at least that it happened...but the Astorian expedition was completely unknown to me and to probably a ton of you as well.

Very interesting.

1 - http://www.amazon.com/Astoria-Jeffersons-Pacific-Ambition-Su...
I have to take back my previous comment. It looks like VT has to maintain "neutrality" and avoid stepping on any commercial AV companies' toes, in order to get them to cooperate. "The most important rule governing VirusTotal's usage is that none of its publicly offered services/applications should be used in commercial products, commercial services or for any commercial purpose." https://www.virustotal.com/en/about/

An example of what I was talking about earlier: a third-party found malware and then used VT to find interesting info about it. http://www.spamfighter.com/News-19068-F-Secure-Intercepts-Ne...
Check out OpenSMTPd, that makes setting up an email server so much easier. It's still far from what it could be, but pure bliss compared to Postfix.
Anyone who finds this interesting may want to check out a fun movie timeline creator that I helped work on recently. It has a pretty powerful data-driven approach that builds the timeline skeleton for you and then makes it easy to edit and add media from there. Could work on top of any type of data.

http://iknow.io/explore/movies-1/timeline/#/start