skysight-inc/HackerNews huggingface dataset:
> The polyfills are there now and they are solid. Webcomponents.js is small and effective.

This leads to a tangential point which I find somewhat interesting to ponder: If the polyfills are good enough... then why does this actually need to be a browser standard?

I'd really like to get to a place where we (collectively) find some sort of minimal API-type "thing" that browsers need to support such that everything else can be polyfilled. I would even go so far as to include things like future ES standards in that, such that you could just "plug in" (in the page, not the browser per se) a shim for ES2015 and it would work near-natively. I know Microsoft Research had at least one project going in this direction -- unfortunately its name escapes me at the moment.

> The simple click-and-select-stuff(...) that you are referencing about are probably specific to some bloated Paper elements. That's not what I'm talking about here.

FWIW, that may very well be true. AFAIR all my tests were done with the paper elements.

I definitely agree that Web Components in some form is the future of application development for the web -- unless we're talking stuff that mostly just wants to use the browser as a delivery platform like WebAssembly. Of course that may change if/when WebAssembly can interface well with the GC/DOM/etc. (Well, come to think of it Web Components might also be massively useful for authoring documents sanely using custom components for higher-level semantic elements, but that's a digression.)

Just FTR as well, I have actually implemented a small application using Polymer just to get a feel for what it's like. Overall it was reasonably pleasant as Web development goes, but it's really disconcerting that all the state[1] passed down to sub-components gets represented using attributes-but-not-really-because-they're-not-primitive-types-any-more.

[1] At least, that's the idiomatic way, AFAIUI from Polymer documentation.

EDIT: I should edit while I can: I semi-believe that Web Components is sort of along the right lines wrt. what needs to be standardized (and perhaps WebAssembly + an interface to the WebComponents API can do the rest?), but frankly I probably don't have nearly enough expertise in this field to even have an opinion. So there. :)
I don't think the idea of a wearable computer is inherently a privacy concern. Having computers is an enablement, it puts information (and thus, power) in the hands of everyday consumers.

The key differentiator, of course, is that Google Glass is a cloud input device. Auto Upload of photos taken with Glass is mandatory (despite my constant feedback to the Glass team regarding the concern).

I would really love to see a computer in the Glass form factor which was truly open, and kept the control of the platform in the hands of the user. I loved my Glass hardware, but I had issues with the software and the cloud dependence.
The numbers involved are extremely small. Twice nothing is still roughly nothing. My suspicion is at least some young women married an (older?) guy and are doing the stay at home mom thing. Its not like the economy is booming, they're not missing out on anything. "Maybe when the economy is better, and my kid is in preschool, my art degree will really pay off"
That's certainly a fair statement - I found the imperative style generated from JS directly harder to debug/work with in general, but that's why I mentioned it's a bit team dependent. Each developer's experience is going to bias them towards one or the other.
I switched to spacemacs because its key bindings don't use ctrl key as much as normal emacs does.
Does that actually happen though? I feel like it's more common to get emails to my personal email address from people that I've given it to as I've left jobs, than it is to get LinkedIn messages.

I use LinkedIn for two things: getting attention from recruiters, and receiving copious amounts of email spam which must be disabled once or twice a month.
I'm wondering what this does for real estate prices. Cities will become even more livable, but on the flip side suburban commutes will also become way easier.
never did this, what's the "selling point" of this method? Thanks.
I use a NoSQL database created in the 1980s with the last manual printed in 1990.

I don't think you can underestimate the impact of inertia.
It's the dominate ethic among the big players these days: "If we don't bend over and do their dirty work for them, they'll just ban us, and find someone who will."
Summary: the percent of people aged 20-24 who answered the survey an employment survey as "retired" changed from 1 to 2%. Bloomberg then finds a narrative and beats it to death.
I interpreted that as meaning that it's just easier to be a free spirit when you are younger. One you are married/have kids/get older, options start closing.
Google has been using Angular 1.x for DoubleClick since 2012 (http://angularjs.blogspot.com/2012/06/doubleclick-super-powe...). I think it's fair to say that it's one of their most important products.
I am happy with T-Mobile's Binge On. Irrespective of what T-Mobile is doing I would like to keep that service.
And your code, and your load balancers, and....

There's a big difference between "it technically works" and "it does what you want it to do and works at scale"
Google image search latest guide
"Yeah - say you're working already and making, say $90K as a developer already. You're going to be taxed 25-28% of this $25/hr at the federal level alone."

That's a good point. Never even occurred to me.
Dual sim android phone? One sim personal, one sim work, that sort of sounds exactly what you want for the phone part?
No, those languages just don't allow you to modify state. In non-functional languages like swift, you can modify state, and closures respond to that.

What I think a lot of people fail to understand is that a closure is not a special object, with magical powers, but a direct consequence of lexical scoping: closures just follow the lexical scope rules, even if their lexical scope isn't within the current dynamic scope. If a variable within the closure's lexical scope changes, the closure won't keep the value the same. Here's an example of these semantics in C:

int global = 4;
void oh_noes(){
printf("%d", global);
}
global++;
oh_noes(); //prints 5

If somebody complained that the function oh_noes should print 4 in this example, you'd think they were insane. Closures actually work in exactly the same way.
Probably modal editing and plugins that aren't constrained by Vimscript.
That is a stereotype. Of all procurements in the federal government, 23% are supposed to go to small businesses (i.e. startups) in general. Only about 8% actually goes to veteran owned companies.

Plus, that is not how it works. They set aside contracts for veteran owned, minority owned, small business owned, etc. Companies compete within those circles, of which there are thousands of them. The competition is very intense in many areas. It is, contrarily, the large billion-dollar "integrators" that develop that horrible software, not small businesses.

So, stop blaming people and perhaps do something about it. Veterans are not the issue. Startups that would rather make a few quick bucks short-term and sell out, not wanting to put in the time and effort to approach a great market over the long term, are the real issue. Complain all you want about bureaucracy and such, but what are you doing, or even trying to do, to improve it? Complaining won't fix anything. Do something, put in the effort, and you'll see change happen.
I've had conversations with hiring managers who believe that the only good programmers are those who do it for 60+ hours a week whether paid or unpaid (I do not pursue these positions). What worries me about not having "technical" hobbies is falling behind. Theres always an unlimited amount of things to learn, and in much of the culture on this site if you're not actively making things in and out of work then you're not following the ideal.
I come from a culture with close multi-generational ties, so I don't think there is anything wrong with your potential decision at all - if it is your _choice_, not _necessity_
It's not, though - market forces have made it such that fiscal responsibility is bound toward making more money than you spend. And you make money by generating value for other people. If you can generate & capture more money than the average person captures, but live like the average person, then the surplus becomes available for any existential searching you want.
LXC (www.linuxcontainers.org) supports Apparmor, SElinux, Seccomp and what’s probably the only way of making a container actually safe LXC has supported user namespaces since the LXC 1.0 release in 2014.
Isn't there a consequence to letting each "subnet" (and I'm not sure at what level this is defined... ISP?) have its own 64-bit prefix that every client uses, and then sharing 64-bit space underneath it?

Can someone help me understand the consequences of this, and how it ends up limiting the usable address space to some fraction of what 128bit would imply?
You know, whether or not children should learn up to 12 by the age of nine is debatable, but by the time you're an adult, assuming no learning disabilities you should be able to do mental math proficiently enough that you don't need to memorize any tables, you can just do it.

I hope that person you worked with can at least work a calculator.
GA data inflated by SERF
Am I going to be the only one to comment that the article actually was pretty cool? He put up some really nice plots in a masterful way, which is better than most of the hand-waving I see here.

The best attempt he put forward to deal with the distribution of numbers one would see in daily life (a generalization of the "non-metric" argument) is using Benford's Law[0], which is as good a blog post that doesn't turn to hardcore statistics (of all numbers used, if any such thing actually exists) can do.

[0] https://en.wikipedia.org/wiki/Benford's_law
One thing I like about both Polymer & React is that they encourage you to treat your apps as a composition of components, as opposed to each page being a wall of HTML with a few variables substituted in.

That being said, React really makes it easy for those components to be tiny little things that do only one thing, that compose nicely, and that are easy to understand. There's a heuristic in programming that if a function is more than a page in length, it's probably too complicated. The same heuristic applies to React: if your component (JS, JSX & CSS together) is more than a page, it's probably too big.

Just the act of splitting apart the JS, JSX & CSS encourages the components to become much larger.
The simulation you linked has a population density of 25,000 people per sq mile (New York City is 27,000 per sq mi.)

It only accounts for trips internal to the city which already have low wait times with existing taxi cabs, and does not simulate the waits for trips traversing into/out of the city.
When we use the term "art," we're adapting the Latin term "ars" to English. "Ars" also translates as "craft." Using "art" probably worked well 100 or more years ago when most educated people had taken Latin and, thus, had more ready access to such nuances, but today I think "craft" is the better word.

"Programming is a craft" communicates the idea that its practice is not constrained to a set of hard and fast scientific principles; but, rather, that it's an endeavor that requires much experience to fit theory into practice, and that there are even certain aesthetic components to its practice.

Programming is a craft in the same way that non-fiction writing -- or architecture, to use your example -- is a craft. We can of course say "art," but then we get distracted by the thought of men wearing hair buns and skinny jeans.
Gotta wonder how long the circuitry in those earbuds will hold out. One of the biggest concerns I see with implanting technology under your skin... is the fact that you're going to have to endure such a procedure repetitively, more than likely.
Anytime I see someone claim that immutability is "less useful" than mutability, I know that the individual has not spent a long time working in an immutable language. Because things are tremendously easier when mutation rarely enters the picture. But, it can take some experience to grasp this.
You forgot video games, which had the exact same reaction. People were afraid that "murder simulators" would ruin our morality. Expect that to be paraded around again, with a teensy bit more credibility.

Of course, cynicism is good for the tech. It's a way of making sure we know what we're doing.
I'm going to say yes. I thought it was common knowledge at this point not to base your entire service on the good will of another service? They're also banking on Slack not changing their API without telling them.
The US doesn't use Imperial units though! They use the US customary system (if that's quite the right term): https://en.wikipedia.org/wiki/United_States_customary_units

Though either way, you are quite right that the US has little influence on the UK in this respect.
I have a toyota, and the system in it is pure junk. I only use it as much as I need to interface with my phone. It has a navigation system (a very expensive upgrade forced on me by the dealer as part of their package bundling strategy) that really sucks.

I vowed this: I will never buy another car that does not support CarPlay. If I have to, I'll go to older cars and buy used and retrofit a third party carplay system in it-- hell going to CarToys and having them do that would be a lot LOT cheaper than what I paid for the useless navigation system.

Car dealers (And everyone else hardware oriented it seems) can't make decent software... barely anyone but Apple can.. so why they think they can force proprietary systems on us an d make us think its "choice" is beyond me.

Furthermore the only reason CarPlay exists is because Apple is dong the car companies jobs for them (since they suck at software, and Apple does not.) IT's a very nice system designed to be flexible... the car makers should be ecstatic that the experience in their cars is no longer so subpar.

Remember, this is an industry that wouldn't give us audio in, let alone bluetooth for decades. (People were using walkmen and CD players in the 1980s. Audio In plugs only became common in 2010 IIRC)

Toyota can sign onto this open source choice-- that's fine, but if they don't also offer CarPlay, then they lose me as a customer.

And I've been driving toyotas for over 30 years.
Aside from trial payrate, the overall process seems really good. I'd like to see experiments in this method in other companies. Maybe even in large companies at the branch or store level with manager taking place of CEO in pre-approvals.

The more interesting part, though, is questions to gain the most insight. There are forums where experts in marketing, site optimization, etc detail the results of their experiments to show what had real value and what didn't. They become sets of tactics one can throw at new, but similar, problems. If it doesn't exist already, hiring people should create such a site for coming up with assessment questions and tactics. Curated by good moderators and industry veterans if possible. Thoughts? Existing examples?
Almost every not-typical-big-corporate job has less bullshit work assigned than the lot of BS assigned to typical big corporate job workers. Startups and even mid-size companies don't magically solve the problem of having to do BS work, there's typically just a lot less of it. When what you do or don't do is all up to you, the portion of BS work goes to 0 because you don't want to do it so you don't. Companies fall on a BS scale that correlates to their size and determines how much BS work you don't want to do that you have to do anyway (or rather, you always have a choice, but if you don't do it then you're fired/the company goes out of business/a customer is pissed off and sues you/etc. which makes it not much of a choice at all).
Good point. I don't understand it very well, and haven't really spent a lot of time trying. When I need to get something going, I have the option of doing IPv4 only and being confident I've done it well. Or, also include a half-baked IPv6 solution that I don't fully understand and could have security holes and other problems. Since there's very little consequence for not implementing IPv6, it's hard to justify take that risk.
He's probably the responsible Engineer who knows how the plant/line works they wouldn't be the one manning the hoses.
Funny. Faith in institutions created a great society. People worked together for the common good. Then, the corruption and abuses of power in those institutions left that society disillusioned; uncommitted. Everyone became disengaged and individualistic. What happens after that? It really seems like a pattern in large social structures. Maybe it isn't, though. It's hard to say without generational bias. Any sociologists want to chime in?
Interfaces which use the pattern:

struct foo bar;
foo_init(&bar);

Can be very annoying in swift, it does play nicely with CoreFoundation which does not use this pattern
> These regulations should be fairly basic: pass all IPv6 traffic unmodified, pass all IPv4 traffic unmodified except for NAT.

Erm, pretty much NOBODY does this - even today. Every packet you send out from your ISP has (and has had for at least 4 years - probably longer) headers, cookies, etc. injected long before it reaches the public Internet. Then along the way more companies inject things into it. Then the load balancers at the other end likely do as well.

This is not all for evil purposes, either: lots of DDOS and botnet traffic gets blackholed thanks to these optimizations. Trouble is, the ability / need for legitimate network management requires tools that can also be used for less awesome purposes, and those less awesome purposes are usually how you can justify the money for the tools in the first place.

A lot of people on HN seem to have a purist view about how Internet traffic should be handled once it leaves your house. The companies that actually manage said traffic haven't shared this view or even operated a network that looks remotely like it for a decade or more. Your data is everywhere; and if it's not being sold by your ISP (which it is) it's being sold by your bank, by Amazon, by Google -- pretty much anyone you do business with on or off line.
They fined Amazon daily because they were found to be in violation of the law that protects the bookseller's guild against deep discounts.

Last I heard, Amazon responded by paying the fine... And continues to pay the fine, because the value of the French market still exceeds the fine.
> another reason in literally infinite ones

There are perhaps about three good reasons to push metric units, and the vast majority of us don't find them compelling enough to care. It's truly a non-issue.
1.2 What is the official pronunciation of Spacemacs?

As it is written, that is space then macs.

I was wrong this whole time. I always pronounced it like "space emacs" or "spacey-macs" if you will.
This is about Lennon/McCartney-written songs, which is just about all of them.
That works for everyone except those who would have to declare to their employer that they're working on the side, for whom they're working and on what. Also, there are places in the US which allow an employer to claim any ideas related to your occupation that occur both on the job and off it (i.e. any code a developer writes, period.)

I'm assuming that type of thing is a no go and leave off a larger chunk of candidates than most people would be willing to admit.
Congrats on the launch. It's frowned upon to make sockpuppet accounts to upvote and comment on your own posts.

While I'm here, a little feedback: You're entering into a very crowded market. That's not necessarily bad, but you do need to differentiate your product from other bookmarking apps. You need a webapp or a browser extension to make this practical - I don't want to manage bookmarks separately on mobile and desktop. You mention the ability to add notes to bookmarks. Are there other key features I missed that differentiate your offering?
I'm asking why did the create IPv6 instead of a version of IPv4 with an expanded address (IPv4-version 2)? Why did they not do an incremental change instead of a whole new thing?
> How about doing what every other language of the last couple of decades does and just not allow them?

I fully agree. But this is not without tradeoffs: eliminating undefined behavior pretty much means (a) the performance and runtime overhead of a GC (most languages); (b) forbidding malloc (verified "mission-critical" variants of Ada, C, etc.); (c) requiring programmers to learn a lot of new concepts (Rust†). I do think that there is rapidly becoming little reason to use C except for throwaway programs, and as an industry we need to be more open to (c) if we are ever going to move beyond making the same memory management mistakes we've been continuously making since the 1960s. But I also understand the reasons why programmers continue to choose C and C++.

† It's interesting to me that the biggest reason C++ programmers give for bouncing off Rust is fundamentally "I want my undefined behavior back", though very few actually word it like that.
That's silly. C is legendary for non-deterministic execution. Macros make a mess of type checking. And portability is possible but only with a tremendous amount of work for any library or product large enough to matter, with many different compilers and platforms bringing their own flavor of library semantics - if they're even available.

No, people write C because it's the only choice in many cases. Like where you need total control over memory management, or because you want to interact with a kernel or hardware directly, or because you want to write functions in the lingua franca of compiled code.
To be honest PySpark and SparkR are always going to be 2nd category citizens (because of the serialization/pickling between the two environments). Databricks shows nice graphs, saying they are equivalent for DataFrames, however those count only for built-in functions that basically translate code into execution plan for Catalyst. For anything bespoke (UDFs, custom Transformers/Estimators) you're better off using Scala.
The Ultimate Impact of DevOps and Machine Learning in 2016
>We have nothing approaching basic income or housing that anybody could live off reasonably.

State welfare programs, section 8, food stamps, "earned income credit", medicaid, SSI, TANF, SNAP, etc. There's lots of aid in the US. Over 100m people nationally are on some level of means tested welfare. That's pushing one third of this nation. National spending accounts for $1T in welfare spending. That's slightly less than Mexico's entire GDP; a country of 122m.

http://object.cato.org/sites/cato.org/files/pubs/pdf/PA694.p...

The narrative of the US not having any welfare is asinine. In fact, the spending is staggering. When I lived in poorer neighborhoods in Chicago, most of my neighbors were on a fair amount of welfare to the point where they never had to bother getting a job. If you're willing to live in an urban area and live a modest lifestyle its largely trivial to game welfare benefits for a living.
A defense of C's null-terminated strings
That's just wrong, in most cases. Mutable closures are incredibly useful. Erlang, however doesn't actually need them, because where I (a scheme programmer) would use a closure with mutable state, Erlang programmers would use a process running a function that takes that state as an argument and runs forever, tail-calling itself to change the state. In most languages this is impractical, because most languages don't have erlang's threading semantics.
I had a job once where we hired a derivatives trader who couldn't multiply 8 and 4. In the job interview.

At my next job we hired another trader who came up to me and said "what does the little 2 in a superscript mean?". As in what does 3^2 mean?

Both very friendly people.