skysight-inc/HackerNews huggingface dataset:
...Which explains why I hate workspaces in Eclipse so much

Files work. Images work. Trying to emulate one inside the other really doesn't.
a lie and the truth is pretty easy. Lies are plural, truth is singular.

On the other hand, convincing a foreigner whose native language doesn't have articles, that articles are necessary... that is challenge.
The "dark" part of it is if the dialog doesn't explicitly tell me that it will take me to the App store once I click on one of the buttons.

Otherwise I don't mind such dialog boxes.
unless the key to reproducible builds is hidden somewhere inside "How to Implement Compatible IDs in Printing Devices", that link may be wrong
thanks, it didn't seem quite right
To be clear though, you only have control of the domain's DNS in the specific case that:

- The original owner made that specific service the authoritative server for the domain with their registrar

- They then either never added the domain to the service, or added it, and later removed it...or killed the entire account.

As I mentioned, this is certainly an issue. But, the domain is basically abandoned. It's very similar to letting it expire. Something that should be fixed, for sure, but not a way to take over an actually functioning website.
I am very sympathetic to your comment. The old OpenWRT and new LEDE did a really poor job of end-user interaction. There wasn't a list of recomended models which was kept updated. The regular documentation was often out of date. The forum was poorly administrated. Project goals were unknown. Lots of back-room dealing with little transparency of what project direction should be.

Hopefully LEDE will change this, but I'm not very optimistic. It's the same devs as before, and they didn't like dealing with end-users before, so why start now? It took LEDE over six months to set up and end-user forum, and they decided not to make a lede-user mailing list at all. Not very end-user friendly actions I'd say.

Note that I don't interact with DD-WRT, so that's why I don't make comments about DD-WRT.
We are working on this here:

https://github.com/angular/tsickle

It's already used within Google to effectively optimize TypeScript apps. However, someone still needs to write the integrations between tsickle and the multitude of public JS build systems and there's not a lot of pressure on me to do it (I have lots of other work to do).
> And here I was thinking, damn if the interviews weren't hard enough .. well good to know they haven't stepped up a whole three notches

Ah yes, interviewing in tech, from what I hear: ten times harder than interviewing for a C-suite management role at the same company... with no more than a tenth of the effective pay.

Edit: Supply and demand of course.
Unfortunately, if you're not turned onto politics, politics will turn on you.

https://www.youtube.com/watch?v=Q3dvbM6Pias
I commented elsewhere in this thread, but: tsickle is mostly the work of one person (me) who also has other responsibilities. I'd love some help on it, particularly in integrating it into the world of webpack etc.

https://github.com/angular/tsickle/graphs/contributors
Exactly. I've worked at places where "I'm the super senior manager, and I don't care about the process! Fix it now!" was acceptable, and at that point you might as well have no process. It inevitably turns into a train wreck.
Makes sense. Thanks for the insight. My believe main point that using the term "regulatory capture" is not what the commenter intended or is appropriate in this case (as it's regulation in general that would affect this rather than tangential effects of regulatory capture).
They arent running directly on renewables, but paying others to use as much renewables as they would use
That's Leslie Lamport, winner of the 2013 Turing Award.
Malbolge, right?

https://en.wikipedia.org/wiki/Malbolge
TypeScript understands some of the comment syntax, but the type systems are different, the module systems are different, and a ton of other stuff is different. Look through the test cases in https://github.com/angular/tsickle/tree/master/test_files to see the difference between TypeScript-annotated code and Closure-annotated code.
I suspect you could accomplish this with NERVES without too much trouble. I'd start with an Erlang port[1] that uses Linux's built-in SPI support to interact with the device itself. If you need something a bit higher-level, you might adapt the RadioHead library.

[1] http://erlang.org/doc/tutorial/c_port.html
Who do you think is not allowing people to try out big ideas?
This comment is correct. Atheros was a long-time Linux/OSS friendly-ish vendor, where Marvell isn't. Marvell has been making some positive moves, but they are still GPL violators and don't work with the community like QCA does. That being said, some Marvell-based routers are pretty well supported now, like the Linksys AC1900.
I'm guessing this is tradeoff of practical vs possible?
Like any other kind of thieves, I guess.
Introduction to Malmö – A Platform for General Artificial Intelligence
Krugman was also a very lonely voice going against conventional wisdom and time has proven him right on some big bets.

Contrarian Call #1 - He called bullshit on the rationale for the Iraq war very early.

Contrarian Call #2 - His models showed that the stimulus and bailouts after the financial collapse would not cause runaway inflation.

If you read his review of the book (not an endorsement) you'll see that it's Contrarian Call #3 -- that maybe the bulk of productivity improvements from the internet have already been achieved.

Let's discuss the ideas, evidence and models, not take ad hominem shortcuts.
FeatureToggle
Pokemon Smash on Microsoft HoloLens
Security update? 9.3.4 => 9.3.5? That's an update

9.3.5 => 10.0 is not a "security update".

Constant nagware until you update is asinine. "Update Now or Later?"... f* you, I don't like what I see in 10... but I'm stuck with dancing around daily fucking warnings.

I swear... I'm not bitter :) I also won't buy another iPhone.
Of course, you're right -- which is a behavior I'm even more in favor of, wherein your debug builds fail fast all the time but your release builds don't.
One big issue with working on side projects is that you get emotionally attached to it and sometimes it takes over your mind, more than it should. Learning to balance that would help you be at peace at slow speed of the side project, after all it's called side project for a reason.
> the kind of stories that erupt into flamewars

Should we also ban discussion on Javascript frameworks? How about we ban all discussion on the founder of Soylent? Those threads tend to lay on the side of ideological bullying.

> seemed like a good way to remind us all of the values of this site (intellectual curiosity and civil discussion)

No sufficiently intelligent group would avoid the biological imperatives that set in motion the basis for political events or discussion.

> we hoped we'd learn some things. As indeed we have

Comeing from a company as YC this is very scary. I'm glad that it has become evident that this, at least currently, won't fly with a large portion of the community. In the future I see the "innocently" minded as being the playthings of you and your friends at YC.
>"Prepare for a new set of exploits affecting every major OS except Linux [1] involving SYSRET to a non-canonical address"

Can you elaborate?
Ask HN: If you had access to all Gmail and Facebook data
If you had access to all Gmail and Facebook data for a user (with consent), what product would you build?
James Mickens has an awesome point roughly along these lines. It is one of my all time favorite lines about security up there with some Gene Spafford stuff.

"""
If your adversary is the Mossad, YOU'RE GONNA DIE AND THERE'S NOTHING THAT YOU CAN DO ABOUT IT. The Mossad is not intimidated by the fact that you employ https://. If the Mossad wants your data, they're going to use a drone to replace your cellphone with a piece of uranium that's shaped like a cellphone, and when you die of tumors filled with tumors, they're going to hold a press conference and say "It wasn't us" as they wear t-shirts that say "IT WAS DEFINITELY US," and then they're going to buy all of your stuff at your estate sale so that they can directly look at the photos of your vacation instead of reading your insipid emails about them.
"""
Relevant book: https://www.amazon.com/Natural-Capitalism-Creating-Industria...
Please don't use sexist epithets on HN.
I don't really disagree with you, but it is not unreasonable to come away with the point of view that the parent had. The agile manifesto has caused as much harm as it has good, I think. People use the manifesto as a methodology, rather than using it as a way to reflect on a methodology. In the extreme, some people will use the manifesto as an excuse to not only avoid a methodology, but a method as well! As long as my intentions are pure, then I can do no wrong, kind of thinking.

Having said that, I think to say that "the goal of agile is always having the project in a known good state" is simplifying things a bit too much. A very important part of agile is preferring artefacts that are executable over artefacts that are not.

More relevant to this discussion is the idea that people should be making judgements rather than relying on hard coded rules of process. If someone has made the decision that the risks of doing something is not worth the benefit, then avoiding the problem is not a waste of time. Importantly, though, a process or rule can not make judgements -- only people can. Following a rule blindly certainly can waste a lot of time.

Setting up a team is not easy. If you put yourself in a situation where every single person on your team can and will press the big red "Stop The Presses!" button, then you only have yourself to blame. Every person on a team should have responsibility appropriate for their experience, skill and view of the situation. If you have disputes, then you don't want an arbitrary process determining the winner -- you want a real, thinking, feeling human being to make the judgement call.

I'm rambling on here, but most of the breakdowns I see in teams come from the idea that either employees are stupid and so we should shield ourselves from them with layers of process, OR the idea that my colleagues are stupid and so I should make sure to politically rig decisions so I don't have to talk to them. This is basically guaranteed to result in failure.
Discovering assumptions (1996?)
Okay, put a USB-C port on the phone. Now what? Make the other end also USB-C so it plugs into virtually nothing?

Also, weren't we talking about the non-phone side in the first place?
I'm hoping, as the "duck and cover" generation dies out, we might see a renaissance in nuclear engineering. Some revival is going on at the moment, but civilization only worked on nuclear ideas for about 30 years (1940-1970). We barely touched the surface. I imagine Musk would have a nuclear rocket division, if that was politically acceptable. Maybe a nuclear technology ecosystem is only possible off Earth.
nsa salaries are crap, smart people realized too much blubber in govt and better pay will never come (usually goes to useless people).. only an idiot would stay.
anybody remembers the tiny almost hidden relational editor built into excel ?
Even if we can do sustained fusion, that doesn't make it a game changer. It looks like it will be hugely expensive. It's easy to say "fuel is nearly free and unlimited!" but that's also true of solar power and solar is too expensive to take over the world's energy. Fusion would be worse because it would require more maintenance - such as frequently replacing radiation damaged parts.
Don't forget this classic!

http://www.flownet.com/gat/jpl-lisp.html
In general, I'm disappointed how Amazon went from being a store to a "marketplace". Sometimes I want to buy somebody who'll actually curate their list of products and has a reputation to stand behind that they don't want to sully by selling garbage or price-gouging on items they don't normally stock.

But maybe that's just me.
http://en.wikipedia.org/wiki/La%20D%C3%A9fense

I've stayed there... it's not so bad, and not far from the center of Paris either.
Webpack Blocks – Compose webpack configs like middleware
Pandora Reveals Its Spotify Competitor, Pandora Premium
You can also tell a truth, as in 'an uncomfortable truth', though it's pretty unusual not to have some sort of adjective squeezed in there.
I take your point - though I was not intending to yell, but to represent my state of alarm and bafflement, as the original poster's worldview is both alien and frightening. It's as though someone were circulating one of those "modest proposals" to improve automobile security by installing a sharp metal spike on the center of every steering wheel, without realizing that these things are supposed to be jokes.

A universally trustable third party key provider might not be a bad idea in itself, but a national government - any national government, I was not specifically referring to the US government - seems about as non-trustworthy as any third party gets. To my way of thinking, the whole point of cryptography is to allow the weak to protect themselves from the powerful, and giving the organization which is at least nominally the most powerful agent operating in one's area the opportunity to poison your crypto before you even begin seems... counterproductive.
Learn linear-gradient() by designing a complex chess board
I've also experienced this several times. I just went through the wave of shopping emails that come from Black Friday in the US, and found that most of the time I only unsubscribed from the company's "Black Friday" list. It's a shameful way to get around CAN-SPAM.

Companies know there's a risk of unsubscribes with every email they send. If they have several lists, they ought to show all lists you're subscribed to, with an option to unsubscribe from them all. They might actually keep some legitimate subscribers that way.
It's also easier to refactor code without magic constants, as you have compile time bugs mispelling kNaverUrl instead of runtime bugs because "ww.naver.com" in one of 10 places.
Germany's Wildly Complex Fusion Reactor Is Actually Working
http://europe.newsweek.com/command-control-donald-trump-nucl...

"Why any one of these incidents hasn’t ended in a mass disaster is “pure luck,” Schlosser says in the film. “And the problem with luck is it eventually runs out.” Think about your laptop or car, he suggests. “Nuclear weapons are machines,” he says. “And every machine ever invented eventually goes wrong.”"

http://thebulletin.org/press-release/doomsday-clock-hands-re...

“Three minutes (to midnight) is too close. Far too close. We, the members of the Science and Security Board of the Bulletin of the Atomic Scientists,want to be clear about our decision not to move the hands of the Doomsday Clock in 2016: That decision is not good news, but an expression of dismay that world leaders continue to fail to focus their efforts and the world's attention on reducing the extreme danger posed by nuclear weapons and climate change. When we call these dangers existential, that is exactly what we mean: They threaten the very existence of civilization and therefore should be the first order of business for leaders who care about their constituents and their countries.”

I have personally started to worry always more about the catastrophic software failures. At least here on HN there are people who react to my comments who typically haven't even heard about the concept of developing with the goal of the fault tolerance https://en.wikipedia.org/wiki/Fault_tolerance advocating instead the beloved "fail early fail often" as the best default even when the topic is actually controlling the rockets(!)

http://thebulletin.org/who-would-destroy-world10253

"An existential catastrophe could only happen once in our history. This raises the stakes immensely, and it means that reacting to existential risks won’t work. Humanity must anticipate such risks to avoid them."
But don't a lot of policies like for example a carbon tax indirectly reflect components of a triple bottom line in the bottom line of businesses? I would argue that making externalities show up in the annual report has been part of economic policies for a long time.
Fair point. We are talking about a 5 year old product though...
It seems that the commercialization impact of R&D spending is more complicated than I had thought (https://www.natureindex.com/news-blog/measuring-the-impact-o...), but I would still encourage you to look at how much various places spend on R&D, and how many people they manage to move through STEM university programs (in terms of percentage of their own native-born population).

I think that making people constantly scramble to meet the next deadline puts a harmful damper on innovation and Big New Ideas. https://www.theguardian.com/science/2013/dec/06/peter-higgs-...

We also may need to spend more effort explicitly targeting our R&D industry towards finding mysteries and solving them. Basic scientific advancement, after all, comes precisely from exploring the unknown rather than from merely innovating within the bounds of the already-known.

And then there's patent reform and such to think about. Blah blah.

But you should take everything I say with a grain of salt, since I work for an R&D company.
I just looked at keyboard.io. There is only space on the right hand?!?! I could never make that sacrifice.
forth? :)

though it's a bid of a different mindset. Thinking Forth is great book ( not just in terms of forth ) which really sells the idea.
It's not a matter of being "necessary", it's just the rules of this language.
> I'm curious, have you put it into numbers? You can probably even make stuff up (AKA estimate), as long as it has a rational basis.

Engineers and developers usually have a strong aversion to giving out numbers
out of the ass, and you cannot give such an estimate in any other way
(barring the cases of the most trivial patches).
You can make getting out of "the condition" to your own responsibility, if you want, even if getting there was not your fault. Or you can discuss the terminology of depression and clarify the label of "the condition" believing that this is not offloading the responsibility.

It is your life, it is up to you what you make out of it.

Unfortunately I can not build a 500 billion $ industry on this advice.

My suggested lack of first hand experience is irrelevant.
I was just looking for more progress on Angular2 and it feels very synchronous that Meteor is back in action today.
Apple can't afford to drop it yet. It will be refined for another iteration or two. It may or may not be dropped quietly a few years from now - possibly with Tim Cook.

Watch has been a huge and very expensive misstep. IMO Apple should have tried to own the home automation market, with secure, high-margin, high-quality products linked into the Apple ecosystem and built with some measure of AI and smart collective decision making - the kind of thing Nest tried to do, but never quite got right, and which the other players in that market (Belkin, etc) don't have the smarts to try.

Watch is a mistake because it's not useful in the way that classic Apple products are. It can do some mildly interesting things, but the whole point of an Apple product is that you're supposed to dream about owning it because you can do more with it than without it.

Watch doesn't do that. It's a fashion accessory, not a powerful tool that happens to be beautifully designed. So even if it's refined physically - thinner, etc - it's never going to be a huge success unless someone in Cupertino works out how to change that.
Trump Cancels Obama's Order for New $4B Air Force One from Boeing
Every numeric priority scoring system I've ever worked with at every company I've ever worked with has devolved into this: Start with P1 (high), P2 (medium), and P3 (low). Sooner or later, an exec will swoop in and declare something Even Higher Priority Than P1!!! So, "P0" gets invented, and after some time, you have tons of P0 issues, meaning P1 is the new "medium", P2 is the new "low" and P3 becomes "never". Then something comes in that is Even Higher Priority than P0!!! And now, you're stuck.

For this reason, I always advocate reversing the numbers. The higher the P number, the higher the priority. So you never run out of numbers to express how much more urgent and earth shattering your next bug is. Try it!
That's a reasonable point, but how do you (as a product owner) justify the cost of making those fixes (and doing the regression testing necessary to ensure the system still works properly)?

My group supports several legacy applications (10+ years old). The product owners can barely be bothered to green-light bug fixes. I can't imagine they could find the justification to green-light tech debt fixes.
It's far lower power than something like Nerves, which runs a full linux kernel on top of something like a raspberry pi. Power usage is relative. At the end of the day this opens up new applications for Erlang/BEAM languages.
+1
Not just a Debian base. When you SSH into them, they drop you right into a bash shell! Surprisingly open in that respect. I hear there have been some GPL disputes when it comes to source code though.
I'm going to go ahead and disagree.

I suggest that instead of this approach, you take an approach of starting by overengineering it and making it absolutely perfect in every way - then just ship the part of that you manage to actually do.

Sometimes the best way to write a short story is to write a three-volume epic.
> this has been the case in both situations.

Can you please clarify what the case has been? Has it been the case that procedures that require bringing all code up to standards if just a tiny bit is touched? Or has it been the case that nobody will ever touch legacy code if they can possibly help it?

Thanks.
Sounds really useful. I'll have to check that out.
Agile isn't about developer comfort, its about the fact that nobody knows what they want until they see it and decide that they hate everything about it. It's about the fact that requirements are made of mercury. E-signatures on specs aren't worth the e-paper they're written on, and the stakeholders want it yesterday with today's changes to the requirements.

Agile isn't a process so much as it is conceding defeat on the very concept of process.
when it comes to power, low end chips win by order of magnitudes ( for example http://ww1.microchip.com/downloads/en/DeviceDoc/30009941G.pd... ). But it all depends on what your power constraints really are
Shameless plug, I just launched an overhaul to a side project today (https://instacalc.com).

The biggest impetus was having a friend using the old version who pinged me with some feature requests. It reminded me that the service can help people I know directly and gave me a huge boost of motivation. If friends and family are using it, you'll want to help them out :).
likewise, although it rapidly got the boot when I realised there was ftp support and I could just do things locally.

Still found occasional use in tiny little fixes, but never super comfortable using it.
No, that's how you end up with a bad short story.
The article speaks about Latin, but so conveniently leaves out Sanskrit, ostensibly the mother of languages when you consider structure and logic. I mean, not even a mention, c'mon!!

By the way Sankrit itself means "perfect language" roughly.
It's not directly shaming, but it presents the user with three options.

1. Comply with whatever they want you to do

2. Lie (say that you are going to comply later without intending to)

3. Walk away from the product (perhaps forever).
The title is "how to ship", so, I rest my case.
Sounds pretty cool. What tech is it based on? Just a standard api and db?

Also, can I ask how big your company is? A few million records is decent volume.
I haven't seen anything related to the Erlang changes, but the grisp github project has an RTEMS app which I assume is for running/compiling your Erlang apps with. The progress is really promising, I believe he just has a very high bar for releasing things.