skysight-inc/HackerNews huggingface dataset:
Even if you could relieve some of the pressure, you could theoretically make the big one less intense. It sounds like we're not even remotely close to being able to do it in practice though. (Although if we were, there's no reason why the described magnitude 6 over a month would be a limit.)
“With us, you’re holding the thinnest wearable ever made so it kind of tests limits of those tolerances. Over time, as we figure things out, we’ll make that variability smaller and smaller.”

How is this card in any way a "wearable"?

Also, if he is to believed (a big if), those are some pretty poor yields...
Best resources to learn C++ as an experienced engineer?
I'm sure a question like this has been asked plenty of times, and would appreciate any previous HN links.

I'm a fairly experienced engineer, and I'm familiar with low-level and high-level concepts. Like most of us, I am used to picking up news languages frequently.

I have familiarity with C++, and prefer a bottom-up learning approach--I'd really love to avoid chapters on for loops, etc., so that I can dig into what makes C++ unique and powerful.

Any favorites you recommend?
Seattle Is Booming and So Is the Ferrari Club
My experience too, but it's strange to hear that the article mentions workers using or bringing in their own tablets for work. I have to wonder what they use it for.
I think people in the 2nd hand car market (like me) will quickly switch to electric. They are simpler to fix and cheaper to fix. Nearly all my cars die with head gasket issues, or oil leaks or timing belt issues. does quick count so that's 4 of my cars and 2 of my partners.

Electric engines won't die like that. And when they do, just grab a used one from a junked car and off you go. With 'in wheel' electric motors, this may be as simple as changing a wheel. This is huge for the 2nd hand market. Most people I know who aren't 'techies' are really looking forward to electric cars.
I love the transparency here, especially for the situation. Maybe this could be good for the people who were laid off (closure?). Taking good care of your employees even after they are gone/admitting your mistakes goes way farther in marketing than some think.
"Ten years ago a prediction that this would be the future would have been met with scorn or laughter"

... this sounds like bollocks, I guess I am an outlier as I worked on J2me apps at the time, but mobile phones where everywhere in 2005, the US was a bit behind, but certainly in the UK mobile wasn't the future, but the present - many of those people used apps and games, they just didn't know what an 'app' was although they used them.
"I cried and many of them cried. It was emotional for everyone. Some were angry and some were already focused on what to do next."

I would lean to believing the other way given this comment, but it is not quite clear from the text.
The point was that many optimizations can be made if you make the quake happen at a specific time of day.
I've since moved on to KiCAD and been pretty happy with it. Something like this board would still be near difficult to impossible, though, as impedance matching for the DDR lines doesn't really exist in KiCAD.

I also ordered a few ICEsticks to play with the new icestorm open source toolchain. That FPGA is in no way comparable to a Spartan 6, though.
It's more important to find agreement on what it isn't: It isn't the black race, and the cure isn't harsh discipline and criminalization of behavior in schools, and stop-and-frisk laws that target mostly black people.

Unfortunately, while the libertarians might make HN look wise about the Drug War, there are way too many people, even on HN, who are happy with, and who have various justifications for, prisons filled with black and latino prisoners.
The same thing that happens if you get into a zipcar with barf on the seats.
There is no such thing as strength: a parody
Yeah I agree,

I saw a round of layoffs go by at a company I worked at that caught me by surprise. It always felt extremely disrespectful to me that I wasn't alerted beforehand. A simple heads up the night before would have done wonders.
> A pretty nasty no-win situation.

It's a pretty easy win-win situation–offer both, inform users appropriately. And then provide a third set: a list of the sanitized files not present in the virus-free dump. I think a quick spot check through those would show whether any editorializing was going on.

I have serious concerns about their publishing the private emails of employees of a private company that, from all I can gather, turned out to be pretty non-evil. But the virus issues, while not Stratfor's or Wikileaks's direct fault, could have been mitigated by Wikileaks pretty easily.

(Disclosure: I've subscribed to them for many years, but have no interest beyond that.)
My take after trying this out for a few hours mirrors yours: it looks like it was rushed out the door and not 100% ready. It's fun to play around with, but I wouldn't put anything production on it for at least another few months.
How did you capture and render text input, and how did you handle new lines when the text wrapped? How do you handle paragraphs, especially when a user would delete text?

I only ask because I determined it impossible to use React for a RTE over the last year and instead opted to use Redactor/contenteditable. I just could not solve those problems easily/quickly enough to make it worth it :(

I'd be extremely curious to see any at all type of implementation for a RTE in React if you have one you could share.
On demand self driving cars will be amazing. A lot of people I know work part time, or have two jobs. Car sharing kinda works, but it is complex to organize over facebook chat at 11PM.

Being able to rent the appropriate car to match the passengers would make it much easier. 7 people? 2 people? 3 people + 6 surfboards? 2 people with kyaks? I can not wait for this to happen.
Most people I know that live in peninsula and south bay of silicon valley have a 10-25 mile commute (1-way) and it would be a huge inconvenience to not have a car. You can't get around with just Uber down here.
A lot of this would depend on the exact nature of the dispute. If this hypothetical open-source project was, say, an XML parser it'd be hard to claim that it was integral to AWS rather than an interchangeable component any more than, say, Intel hosting a microsite on S3 would give Amazon the rights to all of their processor IP. On the other hand, an AWS deployment tool or compute optimizer developed in a private beta that'd be a much harder case since Amazon could quite reasonably argue a privileged business relationship.

Right now we have one case which hasn't been settled and which apparently did involve a business partner. I think we'd need n > 1 or at least a final ruling before making the kind of sweeping claims presented originally.
Being a Test-Driven Developer is a choice
This is great, glad someone is tackling making this experience better! Reminded me of a problem/project description post from one of the HTSaS class students last year http://www.reddit.com/r/HTSASprojects/comments/2i5gpf/p1_sea...
If it has to be IBM PC (not other classic machines like Apple II, Commodore64, Atari ST, ...), then Sopwith comes to mind:

https://en.wikipedia.org/wiki/Sopwith_%28video_game%29

Haven't played in around 27 years.

Wow, a whole site dedicated to this: http://www.sopwith.org
Nope, hence my equivocation.. I've no special insight into the program, but the LIDARs would be spinning and the interiors were lit up with sensors and displays.
Getting Started as a Software Engineer
Regimes like that already did and they already do. And besides, how do you ask shareholders to accept just pulling (which is what this would be) from a market on ethical grounds?

No, you'd have to get a law from the US government to make companies take such losses on ethical grounds. Some companies might of course pull from the US market to avoid pulling from the world's dictatorships, but probably not the big American ones.
>I know the boss took it hard -- he couldn't come back to the office for months afterwards he was so depressed.

well, you either give good severance and everybody on both sides if not happy than at least not depressed, or, well, you give small severance, if any, and a lot of hard feelings around.
Its basically call employee A and tell him/her. If A rejects the offer to stay then call employee B with the knowledge that B would have got fired if A had accepted.
I also use a smartcard with gpg-agent speaking the ssh-agent protocol. OpenSSH commandline supports it fine. What's the harm in shelling out?
Apple, please kill the 16GB iPhone
If a Tesla Model S costs $70000, even if electricity and maintenance are free (and there's no premium for self-driving) you would have to drive it 875000 miles for it to cost $0.08/mile. This seems like the type of thing that is literally unbelievable without more evidence than "I heard somebody on a panel say this".
Agreed - I think that advice is an empathy thing when dealing with the employees you're laying off. Basically when you're laying someone off there's a natural response to try and talk about how bad you feel having to do it too - maybe to try and relate or bond over a shitty situation?

It's an unfortunate natural response though because if you were truly empathizing with them you'd recognize that your feelings in that situation (since you're in the much better position of still having your job) don't make them feel better, but make them feel worse. I'd guess the problem is that comparing your state in any way to there's causes a more negative reaction because they're not in a place where they'd want to empathize with you - the approximate cause of their current lay off.

Outside of the interaction with the employees you're laying off (which I imagine is not the intended audience of this post) I think it's okay to talk about how it feels to have to do this. To the employees though, you can really only say that it's a bad situation and you'll do what you can to make it the least bad possible.
They are simpler to fix and cheaper to fix.

I think you're ignoring the big problem, the battery. When that goes, it is a big deal to replace, and mucho expensive.
True, but there's at least one really expensive component of electric cars that needs replacement every 8 to 10 years: the battery. I think the current price is about $10000 for the battery if you order from Tesla in advance.

Maintenance and repair costs of a gasoline vehicle over 10 years can be less than that.
If you live in Denmark, you are all but guaranteed to be an "end-user": https://en.wikipedia.org/wiki/NemID
Shocking really. Curious to hear rationale from someone that knew about the odds before moving to the PNW.
"Don't make [public announcements] about yourself" is not the same as "Don't care about yourself or your feelings". The audience is relevant.
It looks like, from the scant info on the website and github, that they initial goal is to use these as autonomous mesh network nodes, probably with lots of crypto processing, given that the name of the board files is PolysomeCrypto01. It looks, though, like this was discovered before the folks were ready to really discuss it.
How I Failed to Build a Million Dollar App
To me the best parts of an electric car is that the power-train assembly is much simpler then with a gas powered one and it can be powered with pretty much any kind of energy... whatever feeds your home. and the downfall is of course the range.
When executing layoffs like this, the hardest thing _for the company_ is to make sure that the negativity from laying people off doesn't destroy the company completely.

Ben Horowitz has some interesting insights on this in this blog article: http://www.bhorowitz.com/the_right_way_to_lay_people_off

I think this is essentially just a better way to make sure that the people 42 floors really wanted to keep knew personally that they were important to the future of the company.

And reading the article again, all they told people is that they were staying, and what was going to happen the following day. They didn't say that the people staying were told who was going to actually get let go.

I think in the context of a pivot away from a failing business model, this move seems smart, not wrong. People affected by the layoffs are being let go - their happiness, in some sense, is definitely going to be impacted by the layoffs. But for those people staying, it seems like they really needed to go through some stuff, and I'm sure they all appreciated the heads up.
not sure if you meant "car miles" when you said sales, but another point:

* Cars are way more reliable than even 10-15 years ago. Growing up my parents had a rule of thumb that a car was a ticking bomb over 100k miles. Today, a car from a reputable manufacturer is just getting started at 100k.

I do think this has some interesting ramifications as the lifetime of a single car starts to increase - at a time when the tech in a car (e.g. driver assists/self-driving systems) is starting to iterate very rapidly.
That's a very Keynesian perspective. The Austrian (heh) school says that in fact, the tax-and-spend policies favoured by Greek voters harm the economy in a variety of ways, one of which is by encouraging malinvestment.

(And I agree with them, FWIW).
Except being fired for cause you are:

* Unlikely to get a reference.

* Unlikely to collect unemployment insurance.

* Unlikely to get severance.

* Unlikely be rehired in the future.

Yes it may feel like the same, but they are very clearly two different things.
Using Monsoon Power Monitor with iPhone 5s
Not mentioned is that much of the tap water in the US tastes much worse than it did 30 years ago due to increased standards which require water districts to add more and more cleaning agents to the water. Cleaner tap water leads to greater use of less-clean bottled water.
Canid mouths are very sterile, by design (google it)...but if a monitor lizard had been licking it, you might want to abstain.
previous discussion: https://news.ycombinator.com/item?id=8632209
The part of this story I liked the most was the team's reaction; gathering up their desks into one part of the office, and breaking down the old desks that were now unused. Seems like a kind of mourning process, and makes me feel like this team must be really special to be a part of.
Nothing about that indicates one way or the other, really. The whole thing is pretty emotional, moreso in smaller companies where everyone knows eachother and becomes a small family. The fact that he cried along with them really says nothing about how he had given the news.
We're a two man development team, most notable for our music service, Noon Pacific. Our skills include branding and experience design, as well as full stack web and iOS development. We work best with smaller startups who need quality work on a deadline.

Location: Los Angeles

Remote: Yes

Willing to relocate: No

Technologies: iOS, frontend web, backend web (database and API architecture), basic Android

Website: http://alexgivens.com | http://clarkdinnison.com | http://noonpacific.com

Email: alex {at} noonpacific {dot} com
For those of us who live in apartment buildings and don't have a garage where we can install such things, then what?

To me this has always been the biggest obstacle of an electric car.
Do you think some of the people who got the call might have talked with some of their friends who work at the company that didn't get the call? We are not talking about isolated silos.
I think I feel that way because my job status is incredibly personal information. For the person sitting in the desk across from me to know that I'm not going to have a job at the end of the day before I do strikes me as incredibly invasive. It also gives them an opportunity to tell people outside of work and to use that information against me before I even know about it should I happen to be in a dispute with them for any reason. I should know before someone not in my reporting chain that I'm going to lose my job, not after.
That's not a very good comparison, is it? After 10 years you'd have a nearly-new electric car (from a reliability/repair standpoint) but you'd have a gas car that was vastly more likely to break down and need costly repairs than when you first bought it.
It should be mentioned that the '100T device pictured actually requires the full paid version of ISE. The free-as-in-beer ISE Webpack only supports up to the '75T. Thankfully Xilinx implemented compatible packages through the device family, so lower devices are a drop-in replacement (mostly).

Maybe one day we'll have a Free toolchain, but FPGA tools are much closer to chip design tools than to compilers, and the space is fraught with patent concerns. However I did read on Deep Chip that some fundamental synthesis patents have been invalidated, which might open up some breathing room.
That one is just a translation, I bet it's still subject to the same copyright. If you already speak Spanish, why bother with it, sing "Las mañanitas" instead https://www.youtube.com/watch?v=j8kZ9AjXYzs
Specifically smartphones. The landscape for which in 2005 was absolutely abysmal. The iPhone was revolutionary in almost every way down to the silence switch and visual voicemail.
If you want a desktop application, you should build a desktop application.
previous discussion: https://news.ycombinator.com/item?id=8632209

The Stanford page for this project also has the paper this work is based on:

http://cs.stanford.edu/people/karpathy/deepimagesent/
You say this like people are good at driving in rain or snow.

They are not.

There is a reason for all of those pileup pictures whenever there is severe weather in the US.

Self-driving cars are going to be WAY better in bad weather than any human could ever be. They will be able to "see" in conditions that humans couldn't dream of. They will be able to control steering far better on slick surfaces. They will be able to respond to emergencies far faster.

I have said this before but it bears repeating, once we get self-driving cars, the insurance companies won't actually let you drive anymore.
The advice was never "Don't make public announcements about yourself" it was "When you're telling the employees they're being laid off, don't talk about yourself". There is a very clear difference there. None of the advice talked about what to do or not do during public announcements.
> Your search results aren't speech.

In the US they certainly legally are, and as a curated list of "relevant" results, I'm curious what else you think they might be?

(I don't believe that's what the article is referring to, though, instead it's Bing as an overeager gatekeeper of what people should see)
First Year University Expenses in Canada
this relevant item was posted today:
https://42floors.com/blog/startups/after-the-layoffs
> Have you done large apps ?

At work we're at 10k loc which isn't huge but it's fairly large for a clojurescript app. Middleware on event handlers is a great abstraction. It's only been a few weeks since the refactor and there are only three of us on the team but I'm not foreseeing any scaling problems. The only changes we made are about 20 middlewares and namespacing our event keywords. We experimented with a forked version of the framework and running multiple re-frame apps nested inside each other but it wound up not being worth the effort.

The only scaling hazard I know of is that re-frame has an internal global atom so that might cause a problem if you're mixing multiple re-frame apps on a single page but it doesn't affect us and reworking the framework to not use a global isn't too difficult.
My point is that you can perform all of those optimizations and still not make the quake happen (since all of the optimizations seem to be occurring before the quake).
Lots of people predict lots of catastrophes. The trick is identifying the correct ones ahead of time. This is much more difficult than you are implying.
Thanks for sharing, this is a great guideline
A battery is on the order of the same cost as fixing an automatic transmission (which basically all US cars have--most of the US can't drive a stick anymore).

And, in terms of labor, a battery is WAY easier to replace than a transmission.
like Uber, but for once-in-an-epoch natural disasters
Senna.js is a blazing-fast single page application engine that provides several low-level APIs that allows you to build modern web-based applications with only ~8KB of JavaScript without any dependency.
http://sennajs.com/

Most of the issues reported by this article are not a problem with it thanks to its approach.

Disclaimer: I have contributed to the project.
Hi HN... Darren, Chris, and Daniel here from Interviewed and happy to answer questions!
Some notes when ordering Google's Project Fi
5 years, 5 products, less than 5 users per product? What? How do you give up after one year of work on one project?

I doubt you even had one decent project if thats what your churn rate is. Do you expect these things to take off over night? It takes years to develop products and businesses.
Wait to buy an electric car until it's convenient for you to charge it?
Currency devaluation is usually preferred to inflation - that's why exiting the Euro is under consideration, so that there is a local currency to devalue. High inflation erodes savings and discourages investment - it can be socially destabilizing.
To be fair, you're forgetting that in public restrooms, not only is there more airborne fecal matter and bacteria (which means it statistically settles on surfaces at a higher rate), but that there is often contact between unwashed hands and the faucet's aerator. The latter is even (and especially) true for automatic sinks which have short spouts and the sensor is placed vertically too close to them. This causes/forces people to basically rub the aerator as they wash.
Certainly, everything has trade-offs, but CSS pre-processors are more heavily weighted toward the positive side of the trade-off calculation than pretty much anything else I can think of, especially in the "web technologies" space. I found lots of the arguments in the OP to ring true – things often feel far too fancy, and the more "boring" stuff has major appeal – but I found the arguments against CSS pre-processors there and in the article you linked very thin relative to my experience with them after years of using raw CSS.
This is a cool thing.

I've been thinking about this with functions, and trying to think of a way to make a programming language have support for a proof checker for this sort of thing built in, with functions having pre and postconditions, and function bodies that prove the postcondition is true after the function is run, given that the precondition was true before it was run, but I've encountered a problem when one allows first class functions.

If one allows first class functions, it seems that it would allow one to make tricks like "if this statement is true, 2+2=5". I'm not sure how to get around it.

It's possible that if one actually tried what I am thinking would be the problem, the preprocessor-thing (the thing that validates all the proofs before the program is actually run as a program) might just get into an infinite loop (through infinite recursion).
But it doesn't look like that would necessarily happen.

And I'm not sure what thing in what I've written should be something that the proof validator should accept, but it certainly does not seem like the proof validator should accept all of it (because it can be used to "prove" anything that can be expressed in the language)