skysight-inc/HackerNews huggingface dataset:
Are there any examples using this in the wild? I couldn't find any 'Sites powered by Aurelia' page on the site. Would be interesting to see some full fledged sites (besides the project site).
Which two?
It's a high performance, portable, systems programming, with a huge history. That's why people still use it. I'd argue most programmers today don't need to program in such a language.
What have you done to try and fix it? Looking in from the outside you can speculate all you want, but maybe do something to work your way inside and see what it is really all about. There you'll see things can change, but you have to be willing to put in the effort, but too few are unfortunately.
This is a really interesting analysis. Has it been expanded into more detail anywhere? Can you suggest references that map onto programmers, founders, product engineers, etc.?
Yes we would not have this cute little ditty.
http://youtu.be/_uJsoZheTR4
You should follow Adrian Kennard's blog: http://www.revk.uk/

He's the CEO of AAISP, arguably the best and most transparent ISP in the UK (also quite a small one).

On costs, there's also contracts with other ISPs (most lines are leased from other ISPs, not leased by the ISP itself), customer hardware (routers and other gadgets), marketing, support, subcontracts for personnel across the country, etc.
Objection.js, an SQL-Friendly, no-DSL ORM for Node.js
This will only happen when there isn't a significant portion of new programmers entering the field/language/type of work. As long as there are people that don't know how to write pure, well-written and fast web apps, large frameworks will have a place. This is a good thing, because the more new programmers that try to figure this stuff out themselves the more clusterfuck projects we have. Frameworks allow for an easy onboarding process, where the people that need to reach deeper to accomplish something then look how to do that, and learn as they go.

There are parallels here with languages. Perl, which garnered a reputation as a write-only language, has seen a dramatic increase in the quality, legibility and effectiveness of modules over the last decade, and this corresponds well with the lack of an influx of new programmers (but with a minimum core of users still present to implement new modules). That said, there are many, many other problems when you don't have enough new blood flowing into your ecosystem, so I don't recommend it.
I feel like the author missed a golden opportunity to call this Vimacs ...
Glad I could help. And also noticed that you fixed the error in my version as well - ha!
Yes... I'm really surprised that people aren't talking about this more seriously. They have removed the worst of it, but it still looks like it gives Facebook an advantage in any patent conflicts with any company that uses React, Immutable, Hack, HHVM, GraphQL, etc. anywhere in the dependencies. It appears that the PATENTS file claims that if Facebook infringes on your patents, you can't defend your patents without a risk of immediately losing the ability to use React (or other Facebook library). Maybe a lawyer would be able to make more sense of that PATENTS file.

I'm surprised that Apple might be using React, since they have had big patent battles with Facebook:

http://www.meetup.com/ReactJS-San-Francisco/events/227071839...

http://www.theguardian.com/technology/2015/jul/21/facebook-g...

I've heard that Google doesn't use React, but I don't know how long companies will be able to do that as Facebook libraries increasingly become dependencies of other libraries.
"Blocks" is what Objective-C calls closures.

A closure is just a function that captures ("closes over") the surrounding scope.

Edit: strictly speaking, the construct here is an anonymous function. Objective-C calls them "blocks" and Swift calls them "unnamed closures" or "closure expressions." Both are, or at least can be, closures. (I'm not sure if the term "closure" can be used to refer to a function that could refer to variables in the enclosing scope but doesn't. Probably not.)
How to Use HubSpot Analytics with Your WordPress Website
I think absolute standard of living rising faster is a hypothesis that has not been proven. If I "grow the pie" by $999 and give you only $1 of that growth, what you will find is that merchants are now charging $2 for the same goods as before because they will find people willing to pay that price. This didn't work out well for you, the $1-receiver (and the question then becomes whether the $1 receiver looks like most of the population or the minority of the population).

In short: in capitalism, sitting still means sliding backwards if the economy is growing.

Incidentally, "Reducing economic equality is merely a lesser form of eliminating it" is also an unproven hypothesis if you're speaking about effects. If you're not speaking about effects, then my response would be "A small amount of elimination may bring benefit where a larger amount would bring ruin."
Android Full Disk Encryption Cold Boot Attack (2012)
Pangu jailbreak iOS 9.2.1 can get every apple devices
The Boy Who Could Change the World the Writings of Aaron Swartz
It's actually not too contrarian - The problem isn't the average speed or what happens when things are working, it's what happens when it fails or when things need servicing. Packet loss and latency or slow response times for servicing of the routes affected our customers greatly. Far more than a small bandwidth improvement would buy us on a service that isn't bandwidth constrained at all.

In large part, this just boils down to the fact that less people use it, so less people notice problems and they're addressed less quickly. However, it makes it very unusable for applications like VOIP to customers when there are issues occurring. So while the bandwidth may be better on IPv6, I have no experience with that side of things personally, we're far more concerned with link stability - packet loss, latency spikes, that kind of thing. Again, just anecdotal, but not necessarily contrarian either.
Craig Venter describes work that Human Longevity Institute is doing [video]
hellofunk: Reasoning is easier in functional languages, so fair enough.
As of Swift 1.something, C structs get imported with an empty initializer that sets everything to zero. So that pattern can be written in Swift as:

var bar = foo()
foo_init(&bar)

No worse than the C version, as long as the unnecessary initialization is not a performance problem (which it usually isn't).
This came up before and dang's suggestion was to focus on quality content.

Paywalls are inconsistent, and between cookie policies, country restrictions, per-article restrictions, personal or corporate subscriptions it's hard to say what percentage of readership has access to it.

I believe it's also a self-solving problem, as a story behind a very restrictive paywall won't get upvoted (e.g. you don't see many ft.com or nature.com stories on HN).
Hey, I tried to get back to all applications that included experience aligned with the description above. Sorry if I missed yours, if you re-send I'll definitely take a look.
At work we are using Polymer / Web Components since version 0.5 and have been enjoying it's structured approach. I was skeptical at first to use html tags to add data models, AJAX requests and non-visual parts of a web app. After the initial shock though it does result in more declarative code and helps our codebase stay organized. Long term, the investment in web components makes sense as they become standard and native to most web browsers.
Did that in the US in the mid 2000s, though spent hardly a week on either IIRC. Something like base 20 Mayans, base 60 Sumerians, and base 2 computers. Do math in each and convert them to/from base 10.

I think that's been dropped from most US elementary school curricula now, bit of a shame.
Exceptionalism
That's not true at all and simply more hearsay and rumor. Banks see government receivables as reliably as if you invested in treasury bonds with cash assets. It's the only customer in the world that is 100% guaranteed to pay, on time, as long as you perform to standard. You're speaking to the wrong people if someone told you that. I'm speaking, however, from experience.
Happy Eyeballs is supposed to make sure that doesn't happen.
I'd assume if we used base 12 for everything we'd also use it for writing numbers too.

1 2 3 4 5 6 7 8 9 a b

so 10 would be 12
It's really not a big deal for a child to memorize this table. I also think memorizing the squares up to 25 is worth it.
This one I'm entirely unconvinced of.

It is easier for the computer to adapt to us, rather than vice versa. And over time things get easier and easier for the computer, while staying the same for us. Which is why over time we wind up interacting with computers in ways that are more and more adapted to us rather than them.

We already have acceptably good algorithms to convert to/from different representations, and roundoff errors are generally acceptable. (If they weren't, we wouldn't default to using floating point for most things.) Where precision matters, we have reasonably efficient implementations of exact integer arithmetic and exact fraction arithmetic. The performance hit from using these is less than the hit from using a high level language like Python versus a low-level language like C.

The main challenge is getting programmers to use the right representation for the purpose that they are using it for. Which is mostly challenging exactly because floating point works so well in practice that it is easy not to learn what its limitations are.
"Try it!" is not an objective argument (I have tried it extensively eg. in Bash and I neither like or hate it), and positional mismatch is not a concern when you use name-based syntax, which interpolation forces you into due to its nature.
Well then scheme isn't one either. But then, scheme isn't one. And javascript is just a language in which the functional paradigm is common. it's a multi-paradigm language. Anybody who says otherwise doesn't know what their talking about.
1. Thermite.

2. Use both as sleds.

3. Tie sled from aforementioned suggestion behind a car and see who can hold on the longest.

4. Find some way of combining thermite, sled and car suggestion.
New statistics/machine learning algorithms are always welcome, but the big plus for productionizing is ML pipelines persistence.

That said, during Spark Summit Databricks guys themselves were most excited about Dataset API. Looking forward to giving it a try.
This is, basically, 100% of sysadmin/operations jobs. It's just SOP.

I recommend a structure where you get paid for on-call -- even if it's just a token amount, it makes you feel less bad about having someone cover a week for you, and sometimes people are actually happy to do so.. rather than feeling like they're doing you a "favor".

While I've had plenty of sleepless nights over the past decade, everywhere I've worked has respected me and my time. Maybe I've just had good bosses, but "show up to work whenever you want" is doubly true when you're on-call and may have been fighting issues at night.

Similarly, my bosses have always had my personal cell phone number. It's paid for by work, and it's not a scam. I can count the number of times I've been called on vacation on one freaking hand. I volunteer to provide my international phone number when I'm overseas and pick up a local SIM, and in exchange, my boss NEVER CALLS ME.

I'm always wary of folks who are so guarded and defensive ("never hand out your home phone number", etc)

I treat my superiors and coworkers with respect, and they do the same for me. If I ever found myself taken advantage of, I'd put a stop to it, or I'd quit. It has never come to that, because I work for reasonable people.
Nothing is guaranteed, so I'm not sure what the lack of one has to do with anything.
That's an interesting way to distinguish them, though I've seen people change from one to another. Motivations can change in a person.

I'm currently in the process of teaching one of the agency devs we hired on contract how to think with the end-user in mind. At the same time, I've tried to teach other how to reason through things from a purely technical perspective.

"Product engineers generally pick mainstream languages and tools." <-- going by that characterization, a "product engineer" will miss out some strategic advantages that comes from learning non-mainstream languages and tools. This is coming from the idea that, say, there are powerful abstractions and concepts that can be applied broadly, including UX.

For example: Promise Theory is a formal language for describing intentions and a powerful framework for creating cooperating agents in the context of uncertainty. It is typically applied to configuration management, infrastructure and microservices, but it can be applied broadly to human-to-human and human-to-machine interfaces -- literally, UX. For example, knowing that humans will typically assess trust in an iterative way, you can pick apart the entire user flow in terms of the perceived (implied or explicit) promises (user expectations) the product makes. It starts from the advertising (signaling), through user signup, through onboarding, and any useful impact that product makes. It extends through into support and infrastructure scaling, and back to the user signaling to other users that, hey, this is a useful too.

Another huge aspect that conception of the product engineer misses is strategic thinking. Strategic thinking is the art of making decisions in face of uncertainty. Engineers typically don't think strategically, usually thinking in terms of relative advantages instead of strategic advantages.
Yes, everyone, including coders, thinks they are the best product designers. The difference is that top-level coders actually have the influence to implement their ideas, whether they're good or bad. That's how you get your foot in the door. Walking in to a startup wanting to be the one that tells everybody else what ideas they should be implementing is not going to get you far. I'm not saying that product managers are not useful, but good product managers are data driven and their main job is to gather and summarize the available data and enable a conversation within the company about the product direction, not to be the grand visionary that hands down ideas from on top.
With that Windows flowchart tool, no clue.

But with Node-Red, I can use Flow-Cloner to close the main repo to my local machine.

Then I can do work, and make sequential updates to my project in projects/project1/flows.json and use GIT as normal. Then I submit them as any source commit.

Then the project owner can then clone the .json file into stable/main/dev as appropriate.

And yes, that works, because it's what I do.
The odd thing I've found in my experience is that hex is thought to be taught to everyone in grade school. None of the schools I attended from elementary to high school (in the US) taught hexadecimal. I learned that in my CS courses once I started college.
Maybe the better question to ask is, "What kinds of problems are these technologies intended to solve? And how can I go about understanding those problems, and what other approaches might be used to solve them? Are Spark/Hadoop really the answer, or is that just what people are talking about because... it's what they keep hearing about?"

Remembering that, like everything, Hadoop, Spark and whatnot are means to the end -- and not even necessarily the best solutions for the problems everyone talks about using them for. And that understanding business problems end-to-end (and how they drive technology choices) is infinitely more valuable than being able to play back what you learning in some online course somewhere.

And in the meantime -- don't worry about the rejection slips; just be awesome in the skills you do have, + continually seek to become awesome in whatever new areas you may be exposed to (which might be something relatively "unsexy" like Postgres or Solr) --

-- and eventually people will come to see that it is your awesomeness, not your online coursework or having this or that keyword show up in your most recent job description, that is your main selling point, and will be happy to bring you on board and throw you at new problems, and newer, even hotter technologies (way more interesting than whatever the online courses are pushing these days).
> to simply make web markup what it should be: Interactive

I guess I missed the memo. When did it happen that web markup suddenly got a need to be interactive?
How long are people going to pretend that the lack of full employment for now close to 40 years everywhere across the globe is the fault of people being "too lazy" to work?

You can't fix globalization and automation with personal work ethics.
So they don't have to learn it. Not sure what the problem is.
Date formatting preferences are done at the desktop level and apps should query for it. All frameworks I can think of have a way of doing so, and you can just tell them "I want a long-form date & time", "I want a short date", "I want a short non-numeric date".

If you are a fan of ISO8601 (which I am), you can then set this globally on your desktop, rather than expect the app developers / translators to choose for you.
Four elements earn permanent seats on the periodic table
Django on AWS Elastic Beanstalk with Docker
I am in the process of reading 'The Story of French' by Nadeau and Barlow. There's a chapter on how France was able to push their influence, during the renaissance, to get the world to switch to the metric system. Prior to developing the metric system, France had no standard for the pound; unlike England. This was the height of enlightenment in France, so the reformers wanted to replace the Gregorian Calendar with a metric time. I believe they wanted to call it the Republic Calendar; rather, the equivalent in french. So, they commissioned a poet to rename the months of the year, keeping twelve months of 30 days, with 5 or 6 ambiguous days at the end of the year. However, the major downfall was moving to a 10-day week which reduced the 'weekend' (not that it was called that) from 1 day out of a 7 day week to a 1-in-10. The plan was to have poetic names for the days of the week, but they felt that they were push their luck so instead they went with ordinal numbers.

The only country to actually use the calendar was, of course, France for 16(!?) years until Napoleon repealed it during his imperial reign.

https://en.wikipedia.org/wiki/Metric_time

Anyone, feel free to correct me. I, literally, just read about this (fascinating) subject a couple nights ago. I haven't had time to independently follow up on the topic, but I plan to do so soon.

Amendum: A better link, https://en.wikipedia.org/wiki/Decimal_time#France
It's either a vote of confidence in Lyft or a desperate attempt to stay relevant.
One of my uncles was an engineer at Boeing and said he felt the Imperial system was a competitive advantage (30 years ago) when competing with BAE and other non-US companies. He claimed the standard thicknesses of rolled sheet metal in the U.S. provided better graduations between thicknesses and led to lighter engines.
Theres nothing wrong with presenting work at an intermediate stage. For instance, Chris Valasek and Charlie Miller presented their automotive research a year before they could control cars remotely[0].

They cobbled together the primitives you'd need to build an exploit, thus proving it to be exploitable. That seems like a reasonable time to share your work to me. The title is provocative, but not to the extent which makes it clickbait.

[0] https://www.youtube.com/watch?v=tnYO4U0h_wY
That's the definition in the article for "out of the workforce".
"If you are building things in the US/UK/Canada then you are using feet and inches."

I don't think that's been the case for a pretty long time in the UK - certainly DIY supplies are metric e.g. here is the Homebase site:

http://www.homebase.co.uk/en/homebaseuk/diy/timber/planed-ti...
Vim Operator Flashy: Highlight Yanked Area
I've been using just the custom elements polyfill (6KB gzipped) and love it. I definitely think web components will do to React what querySelector did to jQuery. It's so nice to get rid of the bloat of these libraries, get out of dependency hell, and just write pure javascript again.
Ignoring the tone-deafness of "meatbag", human workers will continue to be part of Amazon's systems for a long time to come, so it makes sense to develop things for humans.

Robots are - and will continue to be in the foreseeable future - massively expensive, require long lead times, and slow to scale. In the current state of the US economy I can hire several thousand humans to do a job practically overnight, while buying/renting several thousand industrial robots requires both considerably more money and time.

Amazon's business is highly seasonal, which naturally favors options with low initial cost but high marginal cost (humans) rather than high initial cost and low marginal cost (robot). Near-total replacement of a high-variance business process with robots is likely impractical and will continue to be for a long time.
It's also "actually pretty easy to become financially independent" if you hit the lottery. Both our examples aren't really conducive to an actual discussion.

1. The number of fields allowing a new grad to get a six-figure job are very small.

2. The number of places offering the above while also allowing the new grad to live in an area where they can have a sub-$2k/mo footprint are incredibly limited.

3. Of the people who are actually able to take advantage of the above, the majority of them will have no interest in doing so. For every highly-compensated employee at Google living in a van in the parking lot there are several in houses they can't afford with credit card and student loan debt to boot.

4. Gaining financial independence for the sake of gaining financial independence is sort of a pointless goal.

My guess is if you collected every person in the US who retired by the age of 30 and removed those who inherited money, won the lottery, and started a business, you could fit them in in a single large room.
Congrats on the launch!
Positive: I like the UI, like the organization of notes, and love the inline and real time markdown editing.

Negative: I felt a little confused when first starting a note. I understand the concept of hashtag to organize notes, but didn't understand your notation - separating words by a dot. I also wasn't sure what the difference between the two buttons on the right hand of the note were. I tried one and it saved the note.

I clicked on the "?" button to get answers to both these questions - and I just got a guide to markdown formatting.
What's missing is material feeling, like you see a switch, you see your hand touching the switch and you feel something.

Could that be done using e.g. a metallic powder held in an oscillating magnetic field? If so, then shouldn't it also be possible to coat the particles with plastic, wood etc for a more realistic feel?
It's a distinction without a difference. Any protocol with addresses larger than 32 bits will necessarily be incompatible with IPv4, so what does it matter whether there's a "4" or a "6" in the name?
I used spacemacs for a bit a few months ago but launch-times were really long. I use emacs as my default editor and I really hated the bootstrapping process when I fired up emacs to edit a config from the command line.

If someone has a simple fix to this problem I would gladly use it since they seemed to have the right ingredients for a top notch experience.
The big problem with The Glass is that people don't like being overtly recorded in private spaces. Bars started banning them for good reason.
I'm curious if this will be another generation-gap thing. Like right now, the stereotype is "only old people still have cable-tv". Will it end up being "only old people still own cars"?

Maybe it will be 90% for <30 year-olds?
This is really nice, from the scientific side, and it creates awesome puzzles as well. Any chance that we can see this software as a service, or maybe even for download?