skysight-inc/HackerNews huggingface dataset:
Sure, and evolution would be much more efficient if every mutation were positive and the species adapted that specific one instead of going out on their own creating meaningless mutations.

Who creates the best/bulletproof solutions? You're arguing that we collectively should know which one is the best, among all our different opinions and habits.

I'll instead argue that we move forward through natural selection and that everyone learns from trying, failing, trying, succeeding and learning what the best solutions are by experience.

I'm not saying it's theoretically optimal, or even practically, but I would suggest it's only natural that we've landed here.

That said, I'm all for trying to improve, if you or someone else every comes up with a better route.
Link to the book: http://thinking-forth.sourceforge.net/
And then management, who have never seen and cannot visualise what you are building, decide that this is a damn awesome idea and the canal should now be extended to go straight up North America to Canada.
Copying my comment from the earlier submission that didn't gain much traction here:

What an absolutely amazing tour-de-force of a devastating design flaw in all versions of macOS and iOS and tvOS and watchOS!

The negotiations detailed in the bug report timeline about meetings between "senior apple and google leadership" for keeping this secret past the general deadline really underlines that.
It's a technological Beholder, only misses the tentacles. :D
Lambdas in Python are somewhat limited - the syntax allows for only one expression. You can use inner (nested) functions however.
http://cx.codaxy.com/
Memes officially bigger than Jesus
And people wonder why feminism is important.

It's not just a non-western phenomenon. The church in Ireland operated a system of forced labour detention for women considered "immoral" known as the Magdalene Laundries: https://en.wikipedia.org/wiki/Magdalene_Laundries_in_Ireland . The last one closed in 1996. There was eventually a state apology and compensation, but astonishingly as far as I can tell nobody has even been properly prosecuted for it.

"Patriarchy" is a word that often seems over-used, but only because violent words and attitudes have so often been the prelude for violent actions with state and social complicity. You can find plenty of cases in the west where women speak up and face death threats. Such as for suggesting that a woman's face appear on some bank notes: http://www.bbc.co.uk/news/uk-25641941

The line between people sending death threats on twitter and the person who strangled his sister for posting selfies is very thin.
https://workflowy.com/
Slightly unrelated, how has SyncThing worked? Any corruptions with large files? Especially video files?
A short article, lacking in details. Interesting that they can state "72% year-on-year decline" when in fact the Apple Watch has been on sale for only about 18 months. Not yet enough sales data to compare two complete sales years against each other.

In any case, this was discussed to death in another Smart Watch thread here on HN a day or so ago. My take on it is that that Smart Watches need way too much 'babying' (i.e. time and conscious energy) to keep them operational at this point in time, that the motivation to go back to 'dumb' devices that don't require so much thinking and planning to keep active is just too strong.
The GP said such people were mythical, that's not a statistical claim it's an absolute claim. One counter-example destroys such a position.

Inverse relationship between religiosity and intelligence may be true, just not sure what it tells us. A statistical appeal to authority??

Many more people are theistic or spiritual than are religious -- I doubt any statistics exist for that, but again proving a truth that tells us nothing about the basic proposition seems pretty worthless.

You appear to think reasoning about a position requires someone to come to your conclusion.

Re the anecdotal nature of the data-points, are you disputing that the mentioned people are intelligent. What in particular is questionable about those data-points, they don't disprove the aforesaid conjecture but they do cast doubt on the implied conclusion being drawn.
IIRC, the idea was making IndexedDB low-level, giving way to the library authors to create something easier to use.

I'm not sure if that ever happened.
Also, a position in the middle of the two US parties usually quite right-leaning in the global context and hardly a good benchmark for neutrality outside the Washington Post.
Thomas Merton is pretty far out. Some amazing souls have walked the earth. Get away from your screen someday, and you mind may be blow, like really blown far away.

Add to your list to explore:
Dorothy Day
Allan Watts
Ram Das
Krishnamurti

Should keep you busy, for a few decades.
It's also true for CRUD app #34, because the hard part is never the implementation, it's dealing with shifting requirements, either due to the nature of businesses, unsufficient understanding of the problem being solved or sabotage from project stakeholders (conflicting agendas, politics, etc.).

When you plan to build a bridge between A and B, everybody can see that the problem being solved is connecting A to B. You then have to match material knowledge and construction experience from other bridges with the specifics of the new location. Also, you define project completion when you can cross the bridge.

When you start out building a "simple form" to solve some business need, nobody agrees on what that need is or what the form should actually solve. Navigating this is research. Also, nobody can tell when the project is indeed finished (i.e. solves the problem).
Evolution is nothing like engineering. Evolution by its very nature makes forward and backwards movements relative to what an outside observer would consider to be an optimum, and selection pressure is what eventually gives rise to a perceived movement in the 'right' direction.

Software is - in principle - an engineering domain, but we tend to be much more liberal in applying engineering norms to software production schedules and reliability. This need not be the case.

If on the other hand you wish to argue that software is produced in a random fashion and selection pressure is what decides what survives then I rest my case, that view definitely does explain a lot of what I'm seeing.
In a way, yes. On the other hand, it boils down the code that some poor soul of a maintenance programmer needs to deal with to a single line which is more readable, too. Win-Win.
Indeed. As a political independent I was hoping for a Republican president this time around in order to give the more extreme right wing partisans some chill after 8 years of demonizing Obama. Hillary is probably the worst possible choice for those people and they are openly talking about armed revolt.
How Do You Find the Right Path?
There are few options

https://thinkswift.github.io/2016/10/01/swift-the-language.h...

https://thinkswift.github.io/2016/10/03/language-library-fra...
In the Lisp Machine world in the early '80s, one guy's first car had HLRZ as his vanity plate, that's the PDP-10 instruction that implements the CAR (IBM 704 Contents of Address Register) operation, which gets you the first element in a list, and his second, or another's, was CADR, which gets you the second element, and was also the name of the 2nd generation, beyond the prototype Lisp Machine that was manufactured in small quantities by MIT and LMI.
Mozilla is also currently working on something like that, although it's not yet clear, if they'll include it in Firefox: https://testpilot.firefox.com/experiments/min-vid
I have been a C++ dev for all my career (about 14 years), so JavaScript was pretty cool relatively speaking. For various reasons I had been a Luddite of sorts and late to the webapp party. But when I finally got in, (more like circumstances left me no choice, technically not financially or socially) mid 2015, I was amazed at the influx of ideas I had. I mean, not only am I porting my desktop apps to web, I am also tinkering with ideas that never made sense desktopically so had never occurred to me. I have to admit that JS was a PITA, albeit of a different kind from C++, but it has certainly made me more confident and viable in starting my own thing. (For those who care, the front end is in Vanilla JS and for back end I am planning ASP.NET and WebAPI.)
Would love to see the following experiment:

1) Take a bunch of people from different backgrounds, ages, etc

2) Test if they know about the golden records

3) Take the ones who don't and close them in an office/workshop with access to pen/paper/computers/tools but no internet

4) Task them with decoding the record and report what they find in it
Another new tech company realizing their show boating methodology doesn't work as effectively once you're out of cyberspace.

On the bright side this isn't the complete end to the infrastructure that enabled Google to do this originally. They are very likely to keep a lot of their fiber team so they can use it for setting up their wireless infrastructure (or at least leverage it if local interests try to play hardball), likewise they'll need to keep some around for upkeep.
Looks detailed. But if you are someone doing an App all by yourself it looks scary. At the end of the day, a lot depends on if you have built something that the users cannot refuse I guess.
I use Wunderlist for ToDos.

Rest of the info I store in .txt files in a folder.

I am not a busy man :)
Having made my fair share (if not more) of terrible (and terribly embarrassing) errors in C using the for-loop, I love foreach and its brethren in other programming languages. I only write classical C-style for loops very, very rarely these days.
"On most networks, it wouldn't hurt if logging into the network for the first time took five more seconds ..."

This doesn't give the impression that this is well thought out. That would unacceptable to most modern consumers.
"Everyone" probably thinks Teslas are the first electric cars, yet electric cars existed in the late 1800s.
And if somebody doesn't use the library, but pixels or percentages, you get the same problem. You can't use a library to replace communication in a team.

But having 7 rem-relative steps, that fit together makes the common use-case way easier: Joe: "I need more padding on this, so I use pa2 instead of pa1".

If you feel the urge to check your code base it's easy to write scripts that count the occurences of "pa1..pa7". It's not so easy if you have to take into account "padding: 1px", "padding: 20%", "padding: 3em" etc.
That seems like a really unfair comparison. I'd argue that the software industry has evolved magnitudes more in the last 20 years than what you call civil engineering has evolved in the last 100. Sure, the latter has existed much much longer, but it's by no means evolving very quickly. Software development has traded safety for rapid evolution in areas where possible. This could be argued for or against, but I'd rather have a multiple generations more mature software industry at a point I'd need to develop "safe" software, than a safely evolved industry several generations behind.
Why post your opinion without even doing the simplest of google searches?

https://en.wikipedia.org/wiki/Wikipedia:Neutral_point_of_vie...
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1247

Note: cvedetails explicitly says it does not show "Rejected or reserved CVE entries", and so shouldn't yet be showing this CVE.
I have been working on a product with my cofounder for around 18 months; spent around six months of this doing consulting to keep the lights on. Released a few early videos, gauged interest, but had to keep fending off users who wanted the promised software immediately. Those emails kept us going - even though we didn't validate by asking for money, the fact that people pestered us even after we told it won't be ready for a long while, gives us hope that when we release there will be at least a few people who would find it useful enough to pay money.

I've been asked by a lot of people why we haven't released yet. We're dogfooding it; it is useful to us today, but it is not where I want it to truly be. Since I'm my own customer (this is a technical product, scratching my own itch), I will know when it is ready. It will be ready when I can build a functional front-end application from a design in two days, that would otherwise take me a month.

What is taking us so long? We had to learn the internal API of an ever-changing software, learn a new language, build a Rails server, a Node server, a chrome extension, a Sketch plugin, an entire compiler-like thing, we had to figure out new ways of solving the design -> code problem, we had to duct-tape the hell out of so many things, and in the meantime we had to content with other aspects of life that are not technical.

It is quite annoying to see the way people talk about the Lean MVP approach being the only way to build software. Some stuff takes time - not everything is a CRUD application that you can throw out into the void, put up some marketing pages, and have a hockey stick in three months. But the downside to my attitude is that most people who fail typically use the same argument - that we're exceptional and the lean MVP approach doesn't work for us. I actually think the produce I'm building is an exceptional case, but hey, isn't hindsight the only true foresight?
If they want to address the market of sportsmen, they won't be selling any watch until they provide larger bands!

I'm not even a sportsman, (I use my arms only to type on a keyboard), and even the largest bands sold by Apple are too small but to cut the bloodstream in my left hand. Needless to say, I wear it only on rare occasion, it'll serve more as a testing and debugging device than as an actual watch.
What happens if you access the database simultaneously from different browser tabs? Also, is there some eventing mechanism to push messages through the database between tabs?
He's saying "I don't understand why..." shouldn't be followed with a conclusion or statement (here, "They have literally no value to society"). That it should instead be followed with "could someone please explain this?"
If you're talking about the currently very experimental Scala Native, my response is that comparing such a fledgling implementation to languages built from the ground up for AOT compilation and static linking is just silly.

If not, please explain.
You know, returning home to the USA a couple times a year, I am really struck by how many freaking power and phone lines are everywhere. It seems like every single street, except for the very core of cities downtown, and only the very wealthiest neighbors, have buried lines. In Germany, almost every town and every highway is free of these (IMO) ugly poles with lines everywhere. It's really an eyesore when you finally glance up.
Yeah - the failed mitigations followed by a "long term" fix was interesting as well. Apple literally had to change execve() this late in the OS's development cycle to allocate new task and thread structs(that's two extra allocations and copies in hot path!) to fix it for good. That this design problem lingered around for so long doesn't look good for Apple - it's one thing for a use after free bug in obscure piece of code to linger but bad design affecting a ton of their own frequently used code to stand so long is somewhat brown bag category!

I wonder what other fallout we might experience from this.
I don't disagree. But then again I've had peers review code similar to this and flag an issue saying it's too clever because that poor soul might not know what "where" is doing or that the use of lambdas is "too complex."
I would also appreciate a sanity-check from any Windows users who can confirm the "nslookup" syntax that is equivalent to `dig ns <domainname>`. I haven't used nslookup in many years and I don't have any Windows boxes around. I believe it should be:

nslookup -type=NS <domainname>

(in the non-interactive mode of nslookup). Do I have that right?
That does not begin to explain the sometimes orders of magnitude difference between estimates and final costs, elapsed time and required manpower.

I've sat in on meetings with people discussing a new project, it is absolutely incredible how much of the future derailing of a project you can see happen in real time during those preliminary meetings.

A probable clue you can find in this nice video of a product meeting between 'engineering' and 'customers':

https://www.youtube.com/watch?v=BKorP55Aqvg&feature=youtu.be
Can you tell us what it is?
Really, if you think the good version is overly clever, you probably have a very fundamental problem with your abstract reasoning. A very human one, as history is full of people having that problem--and ultimately, the good version taking over anyway.

How about this:

subtract(n){
if(n==0){
return m;
}
r=m;
for(x=0;x<n;x++){
r--;
}
return r;
}

People for a long time had strong objections to a number "0", because it doesn't make sense to have a number for nothing! Why not just have no number at all! 0 is not a number, it's a special case! Wrapping it up in arithmetic like that is just overly clever! After all, 0 is not a number!

The whole problem with that is the preconceived and completely unjustified notion that 0 is not a number. Just accept that 0 is a number, and suddenly, things become much easier to reason about, much more elegant to work with.

Similarly, the whole problem here is that you have the preconceived and completely unjustified idea that removing the first element is a special case. You can define it to be, just as you can define 0 to be a special case. But you could just as well simply let go of that preconceived idea and accept that it's not, and suddenly all the problems that you imagine are there disappear, and you have simpler code, just as having integer types with a zero makes for simpler code.
How would you determine the cost of your downtime?

If you're assuming that all you're going to do after you leave a company is become a wage slave at another one, then getting paid the same wage for a few years might be enough to compensate you. However, if you really aspire to start your own company that might become hugely successful (e.g. the next Facebook or Google), how would you be compensated for that?

The point is that even if you're paid for the time when the NDA is in force, you are still being harmed, because your freedom to invest your time is restricted.
> You see 1 million photons per eye per second.

One human retina has about 120 million photoreceptors. In reasonably well-lit conditions they will all fire many times per second. I think this figure is too small by a factor of at least 1000, maybe more.

> A light bulb generates 10^60 photons per second.

Back of envelope: energy per photon = Planck constant times speed of light over wavelength (there might be a factor of 2pi or something missing there) or about 4x10^-19 Joules at visible-light wavelengths. A typical light bulb might put out, say, 10W of visible light, or 2.5x10^19 photons. If it's an old-style incandescent, a lot of energy goes out in the infrared; let's be generous and say it's 2.5x10^20 photons.

So this number is too large by a factor of at least 10^39.

It's still true that the great majority of photons emitted by a light bulb don't affect what you see when you look at it. For instance, because most of them are emitted in directions that don't let them reach your eyes. It is entirely beyond me how it is useful to categorize this as "ignorance".
* Google docs

* Google Calender

* Wunderlist for task today (life and work)
For 99% of fixes, though I'm unsure about the specifics of this one, just having unattended upgrades enabled will do little/nothing to protect you.

Installing the upgraded package often won't restart the service, meaning you're still running old code, and in the case of libraries, won't restart every process on the system that has loaded the library, meaning you're still running old code...
Michael Wolf: Chatbots Will Reshape Messaging Apps
In this age of information, an excess of social conservatism is a systemic weakness for a culture; perhaps an existential weakness.
afaict, this is a parsing library implemented to fulfill WHATWG's spec for URLs. https://url.spec.whatwg.org/
It likely helps that physics puts a hard constraint on things. Over the last decade or two, the physics of computing (aka the hardware) have been changing just as much as the software.

Maybe there is a reason why we seem to see the most impressive code work on "constrained" devices like the C64.
Firefox is the second best browser on OSX in terms of battery efficiency (at least from what I've gathered from benchmarks) and has good developer tools, too, so you might be able to compromise with that.
I kind of started with adwords and a landing page and built out from there. First, find something people are searching for in good numbers. build an ad and landing page with a question, 3 benefits and an action button and google analytics. Next, I use wufoo to capture survey type info. Then you can refine the process from there. knowing you have possible customers.
Not anything major. It's just syntactic sugar for "\x -> x == 10".
See whenever I've seen a noncompete like that it's specifically said "within 5 miles of this location, up to 2 years, cannot contact any clients of this business"

I'm in a right to work state though and that means that noncompetes don't hold up at all unless they have a reasonable and non excessive scope. In a right to work state nobody can prevent you from earning a living so in order for a noncompete to hold it has to ensure that you have plenty of other options in your field in the area outside of the scope of that agreement.

I think we are talking about the same thing just using different terms.
I use Google ecosystem (Reminders, Inbox, Keep, Drive)
I would say it's the complete lack of Software field being treated like any other major profession. Lack of empirical evidence or evidence based design. A mixture self appointed experts with opinions instead of facts. Sales people who over-sell a product when the engineering department is under-staffed. Over optimistic and out of touch management not knowing how to call developers out on their bull-shot.
No, that's not healthy. I didn't say "eat nothing but bread and cheese". If someone recommends you try the bonbons in France, do you eat 3 meals a day of only bonbons for 30 days? When people suggest you try a food they usually aren't suggesting you try and make it your entire diet. I was instead recommending eating the local bread and cheese (of course in moderation.) For the places I've lived in this holds:

- NYC? Get a bagel with cream cheese, or a chopped cheese ($3).

- Idaho Falls? Go to Reed's Dairy and the bakery by the public library with free samples (can't remember the name.) Amazing stuff, and pretty cheap.

- Netherlands? Cheese is pretty cheap and good quality everywhere in the country. Bread is incredibly cheap, and even if you're literally surviving off change you find on the sidewalk you can afford it.

- New Hampshire? Go to Cabot Cheese. Best cheddar in the world.

Of course also remember to eat fruits and veggies, but those are always cheap. I just bought 3 large peppers and a kilo of apples for €1.50 here in the Netherlands.
Ok, I understand.

But you can press ALT+D, type your google text, hit enter.

No need to close tab, no need to open home page, no need to move mouse.
I'm inclined to agree with the article, but it's a bit of a ramble. I wish it explored what motivates of journalists to become cheerleeders. I can take guesses, but those guesses are just speculation:

guess 1: Publishers want to cultivate relations with big institutions that are the sources of their stories.

guess 2: Individual journalists enjoy the prestige of being associated with big-name institutes.

Are either of the above correct? Are there other possibilities.
nice to see all those hateful bigots who call themselves democrats
Apple files first annual revenue decline since 2001
BloomReach acquires Hippo to build first intelligent digital experience platform