skysight-inc/HackerNews huggingface dataset:
Not sure I'd agree with "the general public does not see these products as easy to use or convenient as they’d hope"

Redo the analogy and instead of a Nest promotional article comparing the Nest to other thermostats, compare to a nearly identical home improvement product like fiberglass insulation. After all, you're competing with every product on every shelf at Home Depot, not just smart thermostats, so this appears superficially fair. In more detailed analysis, its an even more fair apples to apples comparison.

The financials are similar although insulation pays off sooner and the capital expense is almost infinitely more flexible. The ease of use for insulation is off the charts compared to a Nest, you simply install it and keep it dry and watch the energy bill drop. The convenience factor for insulation compared to a Nest is also off the charts, insulation never requires firmware upgrades or wifi access and has a much longer useful lifetime than "typical electronic gadget" or even modern dumb thermostats.

Overall a batt of fiberglass insulation beats the nest on all specified marketing criteria. Yet, most homes could use more / better insulation despite insulation having been marketed for decades and the nest being a newcomer to the space. If you can't sell insulation to these people, you're never going to sell them a Nest using the same marketing message.

Marketing messages usually have little to do with the actual product, so a message that is unusually close to the facts of the product is statistically likely to be wrong.
Have heard good things about Robot Turtles - I think it was on HN before too --

http://www.robotturtles.com/
Who said there was a problem? I'm sure PolarSSL runs very well on ARM already. However, it's also extremely likely that it could run even better if the PolarSSL developers were more fully plugged into what the people who work on the ARM crypto hardware know. It's amazing what one can do if one knows exact details of what's going on within each functional unit, between them on the internal coherency bus, etc. ARM probably saw an opportunity, not a problem.
It rather sounds like something that would happen fairly regularly when using something like puppet, or some other automated system configurator to push a bunch of config changes all at once. Especially if your configurator wasn't all that well written, such that it wrote all config files even the unchanged ones. In that case your system would go down with every config change once the number of config files got large enough to trigger the issue.
The quest for a reactionless space drive
That's simply not a comparable situation.
Granted a lot of this is just speculation based on following more recent developments and projects on the Oculus forums/subreddit but I think along with the 3d movie idea, telepresence would be a big one.

There are already a few teams working on prototypes that make use of one or more Kinect depth cameras to "record" a room in 3D so you can put yourself back in these recorded 3d scenes later on. Others have been experimenting with encoding and compressing this data for transmission over networks and decoding at the other end to provide a sort of real-time 3d telepresence.

Obviously it's limited by using Kinect depth cameras, current consumer computers, and standard broadband networks but the way I see it, my first Treo smartphone was limited by the SoC and touchscreen tech of the time as well as the wireless data networks of the time. Still, it eventually evolved into the iPhones and Nexuses of today.

I think that at some point, the head-mounted hardware will become more ergonomic and more functional at costs that allow them to be sold to average users. Likewise, the hardware and software to capture and encode 3d video models of a room or "scene" will become more commonplace. Right now it's games and demos...parlor tricks like the first motion picture reels that eventually led to IMAX movies.
Darwin Manuscripts
"overly-clever"? Not sure about that...
BrowserScript seemed to fit. I didn't expect to get whipped that much over it. Maybe I'll just change it back to JavaScript and add a note that this can be applied to any other browser side language. I don't quite see what the big fuss is though, to be honest.
Ask HN: Is it time to give up, or is it time to push on?
Boring details: I started a company in July aimed at creating a new fantasy sports platform, focused on stat-heavy leagues, dynasty leagues, niche sports, eSports, and tabletop games.

Our CTO was hired away last month, our two other developers are learning Node and Angular, but not much progress has been made on the product. Lead developer doubts we'll get a product out before baseball season.

Haven't been able to find a replacement CTO/lead architect to help lead the development side.

Angels and VCs say we're too early, need usage stats to invest.

I'm not going to be able to make rent for January.

Stress is getting to me. I'm thinking I should just shut the whole thing down, but I've got that voice that says, "Giving up is way harder than trying".

Any advice would be appreciated.
This was put together by some people on my team. We also build http://www.supportkit.io

We try to showcase the most interesting reviews in the daily email and are exploring options for mining for interesting things.

As for Android, it's definitely in our sights as we continue to improve Reviewmatic.
1) Google was behind angular, Google has a huge marketing team, and there is a surreal amount of Google love in the developer community.

2) Angular was the first framework where you could take developers who didn't know JavaScript (or hated it for its worst parts / memories from the bad old days), but were used to learning frameworks (think Java people) and dealing with framework workarounds, and say, use this, you'll feel right at home.
This is ARM we're talking about. They're not known for being open-source friendly.
I've actually never used any javascript framework. It is stuff like this that drives me away. If you pick any one framework, you get half of a crowd telling you that it sucks, and then a year later your version is now deprecated/replaced and you get to re-do everything again. I've attempted to avoid the whole web-app scene, but with the current job market, looks like one has to know one of these frameworks...
The notebooks trace Darwin's work immediately prior to his coining of the term "natural selection" in 1842, up to the publication of On the Origin of the Species in 1859. The notebooks were digitized one page at a time—over 12,000 in all—and are made available online at Cambridge Digital Library
Amen. Look back 10 years ago and we were having the exact same discussions about mod_perl, php, and java servlets. Nothing has really changed except perhaps for an increase in the number of regurgitated comparisons.
Angular's scope system is only weird because they picked the name 'scope'; more modern angular applications / usage drop that one and use the 'controller as x' syntax, where instead of assigning values to a $scope object, it's assigned to the controller itself via 'this'. It's still effectively the same, but you won't be confused with scope anymore.

The dirty-checking loop is IMO a compromise they made because the ES6 standardisation body and consequently browser support for object observable is very, very slow - although it's been added in Chrome 35. I'm sure they'll rely on that full-time in Angular 2.0, maybe even as an option in a future 1.x Angualr release.

I agree on the module system, it's weird, causes naming clashes and I don't think it adds much since it's also not linked to a script loader of any kind.

As for the rest of your statement, I'm still going to say that application frameworks in Javascript are in its infancy; the single-page application paradigm is only ten years old (with Gmail being the first major one), and there have only been frameworks dedicated to SPA's in the past five years, with AngularJS only becoming popular in the past two (and solving a number of issues from its predecessors, like two-way binding, testability, etc).

Angular has its faults, but the alternatives aren't flawless either. Angular 2.0 will be the defining front-end framework for the next five years to come. It takes the lessons learned from Angular 1.x, Angular Dart, Durandal, and applies the bleeding edge in client-side scripting (ES 6). It's still got its weirdness (like square and round braces around HTML attributes, I have no clue what that's about), but I'm sure that none of the weirdness in that framework has been without thorough research and design discussions - I'd argue that it will be the most well-designed and well-thought-out front-end application framework in history, instead of a lot of current-day frameworks that sorta evolved into what they are today over the years.
Most homes already have a thermostat installed, making a Nest install pretty easy.

Insulation generally requires open walls and/or roof to install, upping the difficulty a great deal.
I also have been using Angular for my entire professional developer career, which in a few days will hit 2 years.

This article is pretty accurate for the most part, although some of the minor complaints are not quite so accurate.

Performance is something to be careful about, but the Angular team has worked hard at improving it and it has improved immensely with 1.3 - optimizations such as bind once & $watchGroup and optimizations around the $digest cycle and $watch make it a huge improvement over 1.2. I want to say there is a chart floating around showing over 30% improvement.

As far as frameworks go, I believe Angular is the best we have currently. It does a lot for you without getting too opinionated in general, and some of its tooling is just flat out better than much of what you can find in the wild.

I have been experimenting with Polymer lately though with an eye towards web components - there is a lot of change coming in how we will have to structure our code. I suspect that those using React will also not be shielded from the pain of integration with ES6 and web components as well, and so I have been hesitant to recommend it in a core product. Ember claims they will make the breaking changes slower, but I also suspect that it will limit its growth as well.

Frontend seems to be rolling on as fast as ever - I don't see much of a way around everyone having to scrap their code regardless of the major library chosen for their projects. I'm hoping the pain dies down once ES6 and web components becomes the norm though.
They are going to integrate it into their mbed-os(their IOT lightweight event based os, especially designed for real-time low-power devices).Some parts of this would be closed, so it's hard to tell if PolarSSL will be too.
Pelican Books: Online reading experience
Actually the digest loop will iterate until either there's no changes or it hits a configured limit of cycles.
I'll have to disagree here. When I was on the West Coast, I kept in touch with a lot of my friends on the East Coast by building things together on my Minecraft server.
It is not, in the technical sense, O(n^2). Since it is being performed on a persistent basis, asymptotic analysis is not even quite the right tool to use - there is no single "input" and "output".

What is more precisely true is that the time taken by dirty checking per second scales with d×w×l, where d is the number of digest loops triggered per second, w is the number of watches, and l is the length of the digest cycle (the number of times that the watches are rerun before values stop changing).

Specific applications may find these variables to increase in different ways - all three will generally increase with application size, but for example, adding a digest on mousemove will immediately send d to a very high value.

What I really meant when I said O(N^2) was nothing precise though - just that, when I first read "every time you trigger a digest, we traverse every watch," it sounded like N^2 - it fit the pattern of "for every one of (growing number of things), do each one of (growing number of things)".
This is actually pretty nice, the guy is a Tweaker... Which means he is a member of the Dutch newssite : Tweakers.nl which is a very popular site for Dutch speaking persons (The Netherlands and Belgians). There is a video about it on (same as on the conclusion page of the site though) : http://tweakers.net/video/9730/tweaker-hackt-keyboard-om-sna...
Your complaint is about the styling and UX though, not about the functional underlying framework.
There is also @fogus' book: http://shop.oreilly.com/product/0636920028857.do

I haven't read it yet.
> An analogy best describing this would be just because someone leaves their window open it does not give permission for an unauthorized individual to set up a camera outside their window and broadcast the feed worldwide

I think a better analogy would be someone putting up a tv screen on the side of their house showing a camera feed of the inside of the house, with a sign that asks people "Don't look at this TV"
My point is that I've rarely found "predictable and reliable" to hinge on whitespace convention. The Python mention was simply that the same category of complaint comes up frequently in reference to the language but is so rarely an issue in practice that it's not worth discussing.
SyncStop: Stop Dropbox from copying your phones photos
> I also feel like in the age of many-cores we could do away with problems like GC pauses completely.

Unfortunately its not a resources problem, or else there wouldn't be an issue with GC pauses on fast hardware.

There is a solution for that though, and Cliff Click of Azul Systems is willing to sell you the only pause-less JVM GC there is for the low low price of 7500$ per server (see http://www.azulsystems.com/products/zing/whatisit).
Manhattan NYC Startup (video collaboration) withpopular Investor
I am repping a popular startup in NYC growing a team of engineers and product talent, including API, mobile android and iPhone.

Exclusive relationship with startup. Interviewing immediately and thru holidays. Relo available

Call or text me or email me if interested

james@techstardust.com
714-606-3810
take look at Asus Zenbook series http://www.asus.com/zenbook/
I blame Active Directory and the "use strong password" which focuses on special characters and not entropy.
There is probably going to be at least a 1.4 release. The new 1.x dev team that Google just created talks about their plans for the future here:

https://www.youtube.com/watch?v=LG9VkCDbte0&feature=youtu.be

They say the exact plans for how long they are going to support 1.x won't be finalized until after 2.0 gets released, so that they have some idea of how difficult it's going to be to migrate.
Angular 2.0 won't be out until Q4 2015 the earliest.

There is going to be a migration path from 1.3(x) to 2.0, but it may not be a simple one.

Support for 1.3(x) is not going to drop suddenly.

From the folks I've talked to, there's no reason to panic.

You're not going to be re-learning everything for 2.0, you'll just have to modify you're thinking a bit.

Frameworks come and go, but React and Angular are both great for current and future products.

Don't buy into the negativity and cynicism. If everyone did, we'd still be writing shit in BASIC and PASCAL.
If you need to video feed for experiments just search for "inurl:axis-cgi/jpg/image.cgi" on google.
And now we go around in circles. ASP and classic PHP were the forerunners of using code to do the view!
The science of evolution didn't discover a plausible mechanism until the discovery of DNA.

Besides, the sea is getting measurably hotter and more acidic and from the article, which you say you did not read, some of the starfish recovered when put in cooler water:

The virus probably isn’t the whole story, both Lahner and Raimondi say. Lahner took sea stars that were disintegrating at 54 degrees Fahrenheit and cooled their water to 50 degrees. "They all went from falling apart, having their viscera hanging out, to pretty healthy in a day," she says. "I came back, and they were like, ready for the cover of Vogue. They were perfect." So temperature may play a role in the animals’ ability to recover as well.

The north Pacific basin, on average, has warmed by about half a degree centigrade from 1955 to 2013, according to data from the National Oceanic and Atmospheric Administration. "That’s kind of a scary number," says Andy Allegra, a NOAA data specialist. "It’s very large."
Drone flights face FAA hit
My daughter went to a friend's house this weekend and played Junior Explorers and loved it - all about wildlife and nature. www.juniorexplorers.com
The couple who helped transform the way we shop
2014 Elections: A Win for Real Estate
This very very sad ...
I really don't understand how someone can
Live from 0.9 - 4.9 $ apps
My Shortcut to Landing 24 Reviews from Top Tech Founders and VCs
Detect barcodes in images like a boss
Black Seadevil caught on camera at depth of 1,900 feet
My team has mixed people but most of them are reasonably experienced. What we find most useful about Angular is that it offers a "right way" to go about things, which removes the necessity for endless discussions about "which architecture is best". When you have a large amount of apps that need to be built and maintained concurrently, having a similiar structure across all projects is very helpful.
Really cool story about the couple behind Tesco's loyalty card scheme.
Read-Eval-Print-λove v002 – UrLisp
The correlation between weather and mood
The performance problem is well-known and will probably be some of the first blogs / words of caution you'll encounter when starting out with AngularJS, and there have been numerous solutions for it - 3rd-party bindOnce directives, and in Angular 1.3 native support for bindOnce has been added (prefix the value with a double colon (ng-repeat="item in ::myList").

React handles rendering completely different though, and it's not a drop-in replacement for all of Angular. I probably would look at React if actual view rendering becomes an issue though. For the app I'm working on it's not, it's usually a single rendering pass without too much interaction.
Same error here..
I do see that, yes. Interesting!
Amazing fractal in js
Agreed.

AD's password rule enforcement is almost completely inflexible[0] and originates from 1980s US Government requirements they incorporated to get some certification.

It is completely inappropriate in 2014 and don't even get me started on how convoluted Microsoft make adding 2 factor to NT login (i.e. use our expensive convoluted solution or nothing, no RFC 6238 you can just slot in).

[0] http://technet.microsoft.com/en-us/library/cc875814.aspx
This looks amazing. It was about time for the publishing world to bring disruptive ideas onto the table. From what I understand, you will be able to read your books on all devices which is definitely something that appeals to me (I hate Kindles!) Will explore the website a bit more - I see you can also read the first chapter for free.
Same happened to me. I clicked through the top row and when I got to the bottom row, they didn't work. The top row then no longer worked either. Chrome 39 here.
Oh ok, we're agreed. You'll not be having digest loops per second though, that'd be quite a weird situation :)

Digest on mousemove wouldn't be a good idea - look at _.throttle etc. You shouldn't realistically need digest loops more than once per 100ms, as people can't perceive changes happening faster.
The menus are flickery and unresponsive on my Nexus 7.
Sure do, here is my profile with everything you need: https://github.com/atmosx
"our two other developers are learning Node and Angular, but not much progress has been made on the product."

Why are they learning this stuff now while you're under a deadline and have no product?

Do these guys have previous experience with other languages/frameworks/etc that would let them focus on building instead?
I wouldn't recommend either Polymer or the current development version of Angular 2.0 for a production application just yet; Polymer leans heavily on the unfinished web components standard and other experimental and unimplemented browser features, and Angular 2.0 is still under heavy development. I also gather they're either going to use ES6-but-with-extras-because-we-can, or with AtScript, ES6-with-types-because-why-not. I can't say I agree with those motivations (and I'm sure I've got it wrong), and I quite like the more vanilla JS feel of Angular 1.x.

Anyway, my point is, both of those aren't production-ready.
Plan9's successful implementation of the "everything is a file" abstraction has yet to be seen in popular unices... I wish it weren't so, it's a beautiful and simplified abstraction compared to what we commonly have today.

Also, its namespacing, and a few other opinionated ideas...
I don't care about hip or not I talking about huge market of pc's
By the way you have any examples?
Better than that is the exact same but without the "Don't look at this TV" sign. There's just a TV there and the curious are going to be curious
Boost VC Goes Full Bitcoin for Next Round
We don't actually use Github for determining any part of the match, it is just a social sign in so that we can minimise the friction when signing on. The match is generated based on primary information gathered by our app.

We will add another form of social sign up soon so that people who do not use GitHub can sign up - most likely Twitter.
Rvest: Easy web scraping with R
Checkout our #Vagrant box built with #Ansible for #Symfony2 framework
> It matters little whether some find it productive, what matters is that the engineering principles it is based upon are fundamentally unsound.

I disagree. What matters is whether you can produce a working application - and iterate on that, but after actually releasing. Angular is modular enough to allow for gradual optimization (like integrating React et al), instead of doing premature optimization.

Using vanilla JS like you recommend will lead to a lot of reinventing the wheel, and for new developers to have no clue what's going on (they have to learn the framework you thought up). At least you can make predictions about applications when it says 'AngularJS' on the job advert.
Plan9 is genuinely fascinating if you already liked Unix. You will be seduced by the perfection of the "everything is a file" universal abstraction, and it goes from there.

It's pretty much nerd catnip.
You are very mistaken if you think that I wish for JavaScript to die. It is neither my wish nor my forecast. I just hope that other languages will make it into the browser at one time.
Aging.
"Country" is an ambiguous term that's not always synonymous with "sovereign state". For instance, British people tend to think Wales, England, and Scotland are three countries.
"Craigslist DNS redirected due to hacked registrar "

Not correct. Registrar wasn't hacked their account at the particular registrar was compromised.
We operate in an uncertain world. In many cases it is hard to obtain 99.999% certainties, and we must act with less certainty.

Not acting is a choice as well, and everyone bears the responsibility for that too.
Good one. I missed that on HN. Thanks!
Why exactly would Google want to buy someone else's SSL library?
Wind-down tax planning, etc.
Certainly not thrilled to be asking, but I know others have come before me and more will come after... Looking for advice on shutting down a startup from a (mostly) tax perspective. It's a company that's been in business for 10+ years, has no outside investors, have sold off most assets and have a NOL to go against a last wave of revenues. After operations are wound down, I might want to keep cash in the business (c corp, incorporated in DE) if there are still losses. Obviously if I take cash out of the business I'll end up paying personal income tax, but looking for suggestions on anything else to keep an eye out for.
Octobat's blog – Let me tell you about Stripe