skysight-inc/HackerNews huggingface dataset:
>>This isn't exclusive to SLRs.

No, it is not, but, for a given price point, you will likely get faster AF with an SLR today than all but the most expensive mirrorless cameras. Especially with motion tracking. I know that there are some cameras that say they'll be faster, but having tested a bunch in the real world, I had a very hard time finding any that worked as well as SLRs in as wide a range of conditions.

>>This is more about sensor size than whether the camera has a mechanical mirror box inside.

Yes, though it is more complex than this. It also has to do with the distance from the sensor to the back of the lens. This doesn't require a mirror, but most mirrorless cameras are focused on reducing the size of the package, so they try to reduce this distance so they can shrink their lenses. This is not an absolute advantage of the SLR, but the form factor currently lends itself to this characteristic, while mirrorless bodies are typically trying to optimize for something else. (of course, many mirrorless cameras can use adaptors to full-frame SLR lenses, and the results can be great image quality, but typically bad performance on autofocus.)

source: Spent several days with A7R, A7R2, Canon 6D, 5D3, 5DSr. Tested lenses Canon 11-24, 40mm, 24-70ii, 70-200, sony 70-200. Ultimately bought the 5DSr, due to more reliable functioning, ergonomics, lenses, battery life, etc. Despite genuinely wanting to shed the weight.
I lease a car for about $200/month. I don't own it but until the lease is up it's my car. I can put the driver's seat the way I want and it stays there. I know where all the features are and how to use them. It's comfortable, clean, and smells nice.

I find it hard to believe I'll still get all of this for the same relative price in a future when I'm renting rides from an autonomous fleet.
I had at various points in my life, "DAEMON" and "DEV NULL" (in FL).

I go with a standard issue plate now on a totally generic car.
https://github.com/typesafehub/config/blob/master/HOCON.md
All hope is not lost (yet):

> Craig Barratt, chief executive of Access, the Alphabet division containing Google Fiber, also said he planned to step down because the company was shifting to new technologies and methods of deploying high-speed internet.

Fiber is expensive in every way (labor, regulatory hurdles, resistance from existing broadband companies, etc.). If they've found a viable alternative, it could mean they'll be able to accelerate their broadband rollout.

I'm not saying we should assume that's already the case, but we also shouldn't assume this means they're giving up.
That's nice for Chicago, and Austin, but what about LA, Houston, etc.?

I pay $75/month for 150Mbps via Comcast... and most days a speed test will say around half of that, and there's infrequent outages (averaging roughly one every month).

The only other service where I live is AT&T: 18Mbps for $50/month. And whatever you may think of Comcast, my experience with AT&T's service and customer service has been far, far worse.

This loss of competition hurts consumers
Because in engineering there really are such requirements. In software we rarely have a good reason to start yet another 'from scratch' new hip thing that is so much better than that old thing (where 'old' is likely less than 5 years old). Technology cycles are now so short that libraries and frameworks don't even bother pretending to have a life-span longer than the stuff that will be built upon them.

And those engineers with their 'hundreds or even thousands kinds of screws', they very much favor standardization, lots of work goes into attempting to create families of compatible tools and consumables and typically a change like that will result in decades of stability in the fastener industry, it is quite rare for something revolutionary to happen, most of the changes are incremental and logical.

If you attempted to come up with a completely new thread or screw head there would have to be a reason better than 'I don't like the other screws' if you expect to gain any acceptance of you shiny new tech.

I'm trying to imagine a world where every other week the whole of engineering would be up-ended, everybody would have to totally re-train and we'd discard everything we learned process wise over the life-time of the industry.

That would be the rough equivalent of what we do in software. Ok, maybe not two weeks, but we might actually get there, life-cycles are getting ever shorter.
Mossberg: The PC has become part of the furniture
Your arguments could be used against worker protection laws as well: 14hours/day workdays, lack of safety regulations. You could even import some slaves from poor countries, many people will sign up as working on a plantation for food and shelter is better than starving.

I think history shows that this kind of thinking leads to bad outcomes. The main reason is that there is power unbalance between employers and would be workers. In natural state of the world the workers would just take resources by force and share. As we are guaranteeing that this won't happen (by enforcing property laws) we need to give something back as well to people in worse negotiating position (worker rights, minimum wage, some contracts being illegal are all example of it).

-
i throw it in a pile in my mind and usually forget entirely about it. probably not a helpful practice, and definitely has some influence on why my life is the way it is, but that's what I do
Why are you linking to an harmful essay then?
Zendesk new design
I don't have a specific recommendation, but when I see a project uses a JSON file as configuration, I wonder: "hasn't the author ever needed to include a comment in the configuration ?".
Actually, we don't have the original AT&T. They went bankrupt. Cingular Wireless bought the bankrupt assets and changed their name to AT&T. But yes, building infrastructure is hard.
I don't think so, Apple stopped supporting Safari on Windows since v5 & right now Safari is at v10.
Linking to openssl was deprecated (lack of binary stability) - not the command line tools.
Video encoding tech doesn't change very quickly, and a 3x improvement is huge, so a competitor might well be happy to ask John to take 6 months off and pay him a joining bonus to make up for it. If the improvement is big enough they might pay him to take a couple of years off.

So how long should John be banned from working for a competitor for exactly? 5 years? 10 years? Until his current employer says he can?

What if John leaves and starts an open source project doing the thing he's learned how to do really well? Should he be stopped from writing code in a particular domain as a hobby?

What if John leaves because he's had a brilliant idea that his current employer refuses to listen to? Should John be banned from starting his own competing company? Should an employer be able to restrict an idea from getting to market when they're not using it themselves?
Så går det när man skriver för fort! Rättade det och ett fel till! Tackar.
Learning Style Space with a Human Touch
Yes, from what I heard, it could be a good fit, but I only see negative comments about evernote so ... :)
Why the Hiring Process Takes Longer Than Ever
The Top 5 Most Horrifying Excel Errors: A Halloween Special
Does GCE have the ability to automatically resize based on the recommendations?
Funnily enough, as I've been experimenting with Chef and trying to stick to JSON config files where allowed, I was again struck that (a) it's not a good choice for config files (b) it's an OK choice though (c) lots of people are using it anyway (d) nearly everyone that does so (including Chef) allows comments, so in reality are not actually using JSON at all.

Point (d) is the important one. I really think we need a standard for json-with-comments. JSONC or whatever, but it should have a different standard filename and it should have an RFC dictating what is and isn't allowed. Personally I would allow only // comments because there are too many subtle issues with C-style comments, but it may be too late to agree on that.

Half the point of JSON is that if application A stores its data as JSON then application B can parse that without any nasty surprises. Except, there are now probably thousands of noncompliant implementations in the wild that only exist because the standard doesn't allow comments. Each one of those standards adds subtle differences (in addition to the comments themselves) depending largely on how they remove the comments before passing to the standards-compliant JSON parser (assuming they do that, which being DC's recommended approach, is as close to a standard as currently exists).
All due respect to Linus, but the second example is much less readable. Proof of that: the code was reduced in half, but the amount of comments was doubled.

I think concepts like "elegance" and "good taste" of code should exist, but they are obviously subjective. My choice of good taste always considers readability first.
China halts work on partly built coal plants.

http://dailytimes.com.pk/business/23-Oct-16/china-axes-part-...
Dad, I have an idea for another app
It's tough to evaluate the usefulness of the 80% claim without a baseline. If a simple heuristic of "plaintiff wins" is correct 85% of the time, the model isn't that impressive.

In the long run, such a model would likely be confounded by the parties, who'd model and adapt their arguments to drive the model to a favorable result or settle cases where the model provides a strong signal to which they can't adapt. (Which is not to suggest that this wouldn't be a very socially valuable result.)
Is Esquire always like this? "A tall, bald fifty-four-year-old"... "met a striking dark-haired computer geek"... "her friend was short, swarthy, and squint-eyed". "Alperovitch was in New York when"... "on a rare vacation, in Italy"... "while piloting his hand-built Polynesian proa around Cape Horn." Too many inane trivial details!
"NaN and Infinity"

Yeah. And I learned this the hard way with the Perl module JSON::XS. It successfully encodes a Perl NaN, but its decoder will choke on that JSON. (Reported it to the maintainer who insists that is consistent with the documentation and wouldn't fix it)
tl;dr JSON with a bunch of shitty extensions is awful. The error handling among JSON parsers is inconsistent.
It's ironic. In the Middle East, they use "porn" of you as revenge. In America, the government uses porn you look at to shame you.

http://www.bbc.com/news/technology-25118156
>That sucks for citizens of the US.

This seems a little hyperbolic. Where I live I can get gigabit either via Comcast or AT&T here in Chicago. The rollout to gigabit is slow, but its coming. Sweden has 9.5m people. We have 320m and a huge landmass. Infrastructure upgrades simply take longer considering our size and population and a variety of other issues.

Its not exactly Google or bust. Its clear Google doesn't have the chops to enter more markets. Its assumed they were never serious about being competitive and wanted to jump-start gigabit for the home. Whether or not they accomplished that is unknown as both AT&T and Comcast had gigabit plans before Google rolled out its own product. I'm sure it helped push things forward a bit.

Lastly, Google is looking towards a WISP-model for its services. The fiber runs are too encumbered with right-of-way and crony monopolistic practices. Even then Google is taking a loss with its service according to some analysts. With the proper wireless bandwidth and licensed frequencies, you can deliver internet services without a fiber run to the home.

Google is also a mobile company much more than an ISP. It makes no sense to have this artificial division between home and mobile internet. With voip over lte it makes no sense to even have things like gsm or cdma anymore or have your phone number 'owned' by some mobile carrier. It seems google is retooling for a more beefy project fi or something similar that will bridge the gap between home and mobile internet. I imagine, in the future, the idea of having a home internet and a separate mobile internet is going to go away.

edit: -3 score? Please reply instead of drive-by hating.
Why not skip the middle step and just have the municipalities provide it to the customers directly?
Smartphones are tiny embedded systems in the sense that they are embedded systems, and their total circuit board area is a small multiple of the die size of their larger chips. They're physically quite space-constrained and don't have room for very many separate components, and the larger ones usually end up stacked.
How is the number of web frameworks any different from the number of possible building facades? Even if you decide you want a glass facade, there are dozens of companies that can build that for you, and they've all re-invented essentially the same thing.

The same can be said for nearly everything else. Insulation systems, HVAC, lighting, interlocking brick, drainage...
Seeing Odersky's talks, that is a gross mischaracterization of what he has said on the topic. There's a certain readable, elegant, concise style of code that is expressed very naturally in Scala, and if you take Odersky's courseras, it's very clear that it's something that was a preeminent design goal of the language.

The Scala community, on the other hand, got hijacked by a bunch of Haskell neckbeards who spew executable ASCII art over every codebase they get their hands on. The formation of the Scala Center feels like a response to this -- an effort to "retake" Scala.
Well, then let's go back to DNC Leaks:

NSA Whistleblower: US Intelligence Worker Likely Behind DNC Leaks, Not Russia

http://theantimedia.org/nsa-whistleblower-dnc-russia/

I have William Binney and you have Vice (owned by Disney) and Esquire (by Hearst). Someone like Binney beats journalists working for corporatocracy. Every day. :-)
I have actually used Lua before with good success. It was on a smaller scale, so I can't speak to edge cases, but I would certainly recommend considering it at the least.
When did that stop a troll?
Grow bamboo.

Harvest it.

Bury it.

That's the sort of thing we have to start thinking about.
Although I'd expect the number of transistors manufactured to keep growing for some time... the exponential growth of this "collective pursuit" appears to be limited. I wouldn't even claim that it is necessarily limited by technology (although it appears to be), but it is certainly limited by investment.

Since investment typically follows the ITRS roadmap, announcements like this have a huge effect on future growth.

https://www.hpcwire.com/2016/07/28/transistors-wont-shrink-b...
Freedom to contract is unlimited. You can draw up a contract with any terms you can imagine.

Limited government has limited power to enforce contracts. Take, as an example, an assassination contract. You can write one up and sign it. If you or your hit man later breach the contract, you cannot sue each other in any civilized government's civil courts. You may, however, be able to engage a black-market arbiter to resolve your dispute, and that arbiter may allow terms of the contract that are otherwise illegal to be considered in rendering their judgment.

This is, in effect, saying that no government court will honor any non-compete clause in a contract. It is not saying that you cannot put such clauses into your contracts. But you won't be able to convince the government's justice services to enforce it for you (at lesser cost) if you do.

As government is widely considered a social contract for mutual benefit, a democratic form can certainly alter it such that government power is less readily wielded by those who might use it to harm or exploit the people. Businesses that use non-compete clauses can either assent to the change or start shopping for new jurisdictions.

With respect to your #3, having to pay an arbitrary and unnecessary barrier to entry in order to work profitably using a particular skill set is, in my opinion, unconscionable. It is indicative of an environment where the worker has little bargaining power. Any sane group would band together and use their collective power and mutual self-interest to halt that extraction of rents from their members. Since certain types of worker seem to be knee-jerk opposed to collective bargaining organizations, that leaves government edict.

Your #2 cannot be generalized. It can only be fairly judged on a contract by contract basis. But when enough unconscionable non-compete agreements cross a legislator's desk, the practice is judged by the worst examples. And the worst examples are when big companies collude to depress worker wages, using agreements that are non-negotiable and provide no tangible benefit to the employee. Some people were abusing it, and the only cost-effective way to stop the abuse also stops many of the legitimate uses.
To Do lists:
emacs org-mode and agenda. I have one 'todo.org' file with top-level headings for each project. I keep an org-agenda buffer open to display the todo's scheduled for the current day. I try to go through my todo file once a week and clean it up, archiving 'DONE' items and deleting items that are no longer relevant or haven't been touched in a while. All my emacs org files are synced via dropbox. BTW, org mode really is amazing. I keep finding little nuggets that delight when reading about others' org-mode setups.

Bookmarks:
Pinboard, as well as pocket/instapaper for offline reading of bookmarks.

Financial tools:
Mint by intuit to keep track of all my accounts, numbers/excel for budgeting.

Calendar/Reminders: Google calendar and macOS calendar. I use siri/google assistant to capture spur-of-the-moment things that I don't want to forget.

Files on Disk:
Dropbox. Backblaze for backups. Google photos and icloud photos for extra photo backups.

Wikis/General Notes:
Emacs org mode. I keep a journal.org file, that I sporadically update, as well as an ideas.org file for things I'd like to investigate/try build in the future.
I use evernote for lists/notes from mobile devices as I haven't figured out a good way to use org files on iPhone/Android.

There isn't much overall integration, I just know that for important files I reference dropbox, Financials and Bookmarks have their own services, and then notes are going to be in emacs or evernote. Events/reminders handle themselves as I typically schedule them in the stock calendar/reminder apps and forget about them until I get a notification. I don't find the lack of integration to be a problem actually, as long as I know where to look for something based on what it is (e.g. notes -> orgmode/evernote, events -> calendar/reminders, files -> dropbox etc.)
i actually like hcl: https://www.terraform.io/docs/configuration/syntax.html
Control Cmus with Media Keys Under MacOS
Pokémon GO, scaling profile services with Couchbase and NoSQL
It doesn't really matter how inefficient you are if you have the cash to buyout any potential competitors before they have a chance to threaten your bottom line.

In a purely capitalist society wealth (power) accumulates at the top. Money creates money so whomever starts out with the most money tends to win. This is why highly capitalist societies turn into Dubai, with an ultra rich ruling class and a serf/slave class with little in between.
Be a prolific sharer
But everyone moving to fiber IS building new infrastructure. Sure, they're continuing to cash in on telephone wire and coax, but fiber is new infrastructure.

And Google discovered that you CAN'T just make money deploying Gigabit fiber for $60 a month. Getting even a 50 Mbps fiber circuit around here is hundreds of dollars a month.
Well, first and most obviously, if you are thinking of rolling your own JSON parser, stop and seek medical attention.

Secondly, assume that parsing your input will crash, so catch the error and have your application fail gracefully.

This is the number one security issue I encounter in "security audited" PHP. (The second being the "==" vs. "===" debacle that is PHP comparison.)

As one example, consider what happens when the code opens a session, sets the session username, then parses some input JSON before the password is evaluated. Crashing the script at the json_decode() fails with the session open, so the attacker can log in as anyone.

Third, parsing everything is a minefield, including HTML. We as a community invest a lot of collective effort in improving those parsers, but this article does serve as a useful reminder of a lot of the infrastructure we take for granted.

Takeaways: Don't parse JSON yourself, and don't let calls to the parsing functions fail silently.
> Trade secrets, IP, secret sauce: covered by NDA and IP assignment agreements

> Client lists, contract terms, sales strategies, reported metrics, financials: covered by NDA and in some cases SEC regulations about insider trading.

This is largely unenforceable as I'm sure you're aware. The fact is that legally preventing someone from working at a competitor is simply the only effective way of deterring IP getting to a competitor.
I don't see a major problem with using the openssl command for this, but using system() to do it is completely insane.
You are not considering a hostile environment like the internet where an attacker will use edge cases to get unforeseen results.
This is what I use, it's very good.

https://github.com/typesafehub/config
The Internet of Things Is Taking Over Cities
Yeah, basically the json parsers and generators and the programs that use them seem to have settled on implementations that mostly work together.
>> So I fail to see how this camera what outperform a DSLR.

It might be better to look at it with a less narrow perspective. If you're a hardcore photographer, what you are saying is absolutely true.

But a lot of "normals" want DSLR-like quality without bulk.

A lot of people buy DSLRs because they want better quality photos and more flexibility, but after the honeymoon period, they get tired of lugging a big camera with them.

This is probably why Sony's RX100 series has done so well.

"The best camera is the one you have with you" -- that's typically someone's smartphone. If you can give a consumer a camera that size that roughly performs like a DSLR, it will probably make a lot of people happy.
:-) Unfortunately none of the other names for mirrorless/interchangeable lens like EVIL really stuck while SLR is really an anachronism because it was in contrast to twin lens.
I think you slightly missed the point there. The video is of a bridge designed to span a highway that was to be expanded from 2x4 to 2x5 lanes + an emergency lane on both sides with minimal interruption to existing road and rail traffic.

The decision was made to construct the bridge off to the side of the road on a separate spot, then to create a special purpose roadway across the road to the location where the bridge would be placed. And finally, to move the bridge from the construction site to the final destination in one piece.

The whole thing was conceived and executed according to plan, including a < 24 hour closure of the road and one week of interruption on the rail line (it was not possible for many reasons to have the track installed prior to moving the bridge).

That is engineering. In the 'move fast and break stuff' world that would be 'move fast and kill people'.

If this were software we'd be looking at a multi-year software project with a few hundred programmers delivered on-time, within the budget and working flawlessly on the day of delivery.

I have yet to see such a project. But as you say, 'Amazing!', the fact that you make it seem like this is 'no big deal' is exactly what is so good about it, you fully expected it to work didn't you?

The trick apparently is to make the complex and impressive stuff look so boring, I really wished that we could make software look that boring.
Secret life of physicist: moments of transcendence offset by months of confusion