skysight-inc/HackerNews huggingface dataset:
Parts of OS X El Capatian are written in Swift . Source :

http://daringfireball.net/thetalkshow/139/federighi-gruber-t...

"FEDERIGHI: We have all types here within Apple. They start out with the “I love Objective-C. I don’t want to change” to “OK, maybe there’s something to this Swift thing” to “Let me give it a try” to “I love it.” We’ve gone through all the phases internally. You know, we’ve had some really great adoption by teams like … the team that does the Dock and the window management on OS X, implemented all their new features for El Capitan in Swift and started mass-converting all of their code, and say that they couldn’t imagine going back and that they’re more productive with it. Part of what our internal teams need to deal with, though, is that they’re working on, let’s say, the current version of Swift 2.0 while it’s not done yet. I mean, while it’s not even WWDC-level done yet, right? And they’re working on the interfaces in terms of our internal frameworks that haven’t been modernized for Swift. And so, they’ve got it rough. They’ve got to really love it to make that leap because they’re working on a very, very bleeding-edge environment when we use it internally. Thankfully, with Swift 2.0 now well out the door, that’s stabilized things a good bit and they’re really open to it.

But there’s been just lot of feedback. And a lot of it has helped with the impedance, making sure the impedance between Objective-C and Swift is absolutely minimized because of course we have and will continue to have and continue to write more Objective-C code, and so the ability of Swift and Objective-C code to work together completely naturally is a huge focus. A bunch of things like generic collection, support for lightweight generics in Objective-C, were big pain points internally and something we fixed in the language, and is now great for all of our app developers externally. So, it’s been a not dissimilar road for us internally to what you see outside. But in terms of Swift and writing big apps, it’s certainly the case that when Swift 1.0 came out — heck, we didn’t support incremental compilation in the very first update. And so that was going to be a limiting factor for productivity for people who had big apps. A lot of that stuff has changed. And then in 2.0 having a good error-handling model, having the availability check so you could span API versions — these sorts of things. I think it really addressed the vast majority of pain points that we were experiencing, that I think the community was experiencing about writing larger apps. And so much about Swift is actually inherently better for building big apps because it handles modules and namespaces in a way more naturally than in Objective-C. It makes the API contracts a little more clear, the code more obtainable. So, we’re very comfortable."
4 issues with this...

1 - A team can succeed in one environment but fail in another.

2 - If the team does fail, you have a lot more rebuilding to do.

3 - Teams that are independent of company can have different loyalties. The principal-agent problem [0] gets a lot worse if an entire team is being held hostage.

4 - Many times you're not building the project team from scratch. You start with people who have succeeded on other projects.

[0] https://en.wikipedia.org/wiki/Principal%E2%80%93agent_proble...
This is usually true; but in this case he's parroting a data "analysis" that excluded 99+% of IEX's orders. Essentially, in < 1% of types of trades, IEX underperforms, in the rest it outperforms.

However, the IEX opponents decided to pretend that this minuscule fraction of trades was important, and Matt Levine was either careless in believing this; or he purposefully wrote a dishonest and misleading article.

I won't state which it is, but he's a smart guy... it's hard to believe that he'd make such an egregious error by accident.
Usually when applying for time on a large telescope there are a few different categories of time. Most ordinary observations don't have to be done at any particular time and many of the larger observatories use queue observing for these targets. There's just a big list of these targets and the observer goes down the list and observes them one by one.

You can also apply for a "target of opportunity" when you don't know exactly when or where the event will take place, but there is a good chance that some event will occur over the next observing cycle. If you execute on a target of opportunity you jump to the front of the queue. If there's a particularly high time sensitivity (like for an FRB) then you might even interrupt an ongoing observation.

Things are trickier at a smaller observatory because they generally don't use queue observing. What happens instead is that an astronomer is granted some number of nights and they have the whole telescope for that amount of time. All you can do then is call them up and ask nicely. Usually they will though because they get on a paper without too much work. (The most highly cited paper I'm on happened that way!)
Ha. I misread. Thanks for the correction.
I think them building it in rust is a good thing. But rust is a mozilla project so its not as though theyre doing people favors. What it certainly does is showcase the strength of the language considering they have proven to be so badass
I have been looking at the Snapdragon 820 and it at least on that level, it does not seem that android devices should mis anything. The new Sense Id is an improved Touch Id, and I mean that both in terms of the finger print sensor itself, as well as the hardware protection itself. They implemented full UAF in the SecureMSM for the authentification. The best thing is that this is exposed to the layers above and can be leveriged in the growing fido ecosystem.

The major issue with android systems does not seem to be lacking software and hardware, but rather the unwillingnes of providers to push best practices as defaults to all users.

I somewhat agree and somewhat disagree with your analysis of the politics. Their are both advantages and disadvantages of both situations
> Dark matter makes up 95% of the universe now?!?

The article was very poorly worded. As @infogulch noted, the 5% is of the total energy content of the universe, not the "matter" content. So that's been known.

But what seems to be new is that of that 5% of normal (baryonic) matter, we've only been able to account for about half of it (stars, gas in galaxies). These FRB observations claim to have found evidence for the other half of the "missing baryons", likely in hot gas between galaxies.
Yea I understand that. My comment is more about how it's possible that HD streaming would cost that much more.

I've been able to do it at a bitrate that is acceptable over a crappy network. I'd say that I'm not very smart and that a group of well-paid engineers should be able to do better than that.

If the cost is just "because people will pay that much more for it" then that is fine but as it rests right now it is because "the bandwidth would cost that much more"
Upgrading from React 0.11.2 to 0.14.7 in 347 easy steps
I care about syntax so Swift is far more appealing to me. Compare print("Hello, world!") in Swift to Hello World in Objective-C, which the article jokingly calls "gibberish."

https://www.binpress.com/tutorial/objectivec-lesson-1-hello-...
I'll be sure to check it out. Probably going to be a good read.
Well perhaps I should include a screenshot because when I view the link I included the screen image is clearly going over the thumbs. Your screenshot is not the same as how it appears in my browser.
It may be, but the above poster also left out one of PHP's strengths - availability. It's already running and ready to go on whatever cheap shared host you've been on for the last 20yrs. Ruby/Rails likely isn't.
On exactly what front are exchanges competing? Order types? Fees? Volume? Differences in any of these are very often opaque to the customer.

From what I've seen, exchanges are basically functionally equivalent, since they provide a utility-like service. And, as Vanguard points out, more trading venues means higher market frictions and costs.

TBH I'm still trying to forming a strong opinion on the issue, as indicated by "probably" in my initial comment. And I think it's a topic worth discussing.
With Concepts, we will also have "auto" in function arguments. It avoids "template <typename ...>" for simple functions.

I already use it as a "catch all" over specialized functions (gcc -std=c++17).
Every Mac with OS 10.9 and later comes with speech recognition software that works without internet access and is really really good. You can dictate entire documents, emails, even have it type commands in terminal etc. In OS X 10.11 you can even drive the UI by only speaking.
Ftmpl: Fast and typesafe golang templating
the aforementioned lingo/patois was the de facto verbiage of the early days of the movement, and some don't graduate away from it.
The "fast PHP7 engine" part not. Raw Ruby was slower (but comparable) to raw PHP, so with this new engine which consistently runs real life workloads 2x, PHP7 should be like twice as fast.

And PHP still has more vendors, support in all kinds of hosts, even in third world facilities, and more companies offering commercial support. Plus there's stuff in PHP that don't exist with the same level of maturity/adoption/community in Ruby/Rails, e.g. Wordpress.

And even a path to static typing, through Hack.
> What happens if someone has scheduled time with the telescope. Do they get bumped? Who has priority?

Yes they generally get bumped and they will generally get that time back later on in the telescope schedule. Folks who do these "target of opportunity" proposals apply like usual, but don't specify targets. If awarded time, they get the ability to "trigger" their observations once an interesting target appears. So their time allocation is (generally) capped like everyone else's, but isn't scheduled. So presumably the people who get bumped will have their observations rescheduled for later.

In detail the question of priority is a bit more complicated, and sometimes the people observing can refuse to be bumped for a TOO, but that varies with the observatory and their rules.

Edit: Also, people are frequently happy to even "donate" a little bit of their telesocpe time to observe interesting transient sources (sometimes in exchange for co-authorship or acknowledgements in papers, sometimes not). This is partly because astronomy is a reasonably friendly field. And it's also because we can't design and carry out experiments like other fields of science – we have to take what the Universe gives us. So it's good to take advantage of opportunities to view interesting and new sources when they happen.
I was (and still am) trying to illustrate the "physical reality" that exists independent of the concept of personal liberty.

It can be argued in many different ways, but the actual, consequential mechanisms regarding a person's "rights" are enforced at a legal level, and are done so at the discretion of the state. Reality does work, therefore, as I've described, regardless of what eloquent points you might make about the innate personal liberties each person is "born with". This is my "clear" argument.
I'd like to see a chart that shows the percentage of operating cost between fuel and crew salaries given oil prices. I wonder if labor is the more expensive component now and fast steaming is cheaper.
IPhone data is just as much on corporate servers.

To bad flock does not exist any more, a droping replacement for google sync with end to end crypto. Very nice.
This really seems like a redefining of what the word Quality means to make some other point. "Quality is subjective" is a pretty poor statement since quality has a pretty objective definition.
Huh? He explains this all in the article very clearly. He addresses the issue Citadel brings up but then demonstrates how unimportant it is to retail investors.
I think the author hits on an important point under the "Common Ground" section: discussions should be collaborative, not argumentative. If you're trying to make a decision with a "me vs. you" mindset, the decision won't get made. Instead, try to frame it as an "us vs. the problem" situation, which helps everyone contribute and work multiple angles to find the best solution, keeping multiple considerations in mind -- including code "quality".

If anyone's interested in more on this, I wrote a short Medium post on other strategies for making better technical decisions: https://medium.com/@cjcenizal/seven-strategies-for-resolving....
Isn't 2FA standard nowadays. And it still does not disable social engineering as attack option.
It's reciprocal, which is the real thing missing from the collegiate-type "safe space", which only flows to certain people. You need to be able to disagree, and, reciprocally, when disagreed with you need to handle that gracefully, or you aren't doing your job. You not only get your feelings taken into account, but you must equally take other feelings into account. You've got rights, but you've also got responsibilities too.

Contrariwise, the collegiate-style safe space makes it so that the certain people have boundless rights to be offended, but no corresponding responsibilities to consider other's feelings. In a team context this leads straight back to exactly the failing the article is primarily about, one person/group speaking a great deal more than the other.

(And please do not insult my intellectual integrity by claiming that collegiate-style safe spaces are supposed to be safe spaces for everybody. That is transparently false, to the point that you are just discrediting yourself if you try to claim otherwise. It is abundantly obvious who they are for and who they are aggressively not for.)
according to this:
https://news.ycombinator.com/item?id=10819711
over 94% of websites do not use a reverse proxy at all.

Of those, 70% are using cloudflare as their reverse proxy... so 4.2% of websites use cloudflare.

This page:
https://www.datanyze.com/market-share/dns/
says 70,000 of the top 1M websites use cloudflare DNS

I've seen other sources quote cloudflare at 2-4% of websites using them as their CDN.
If the teammates respect each other, and feel respected, then they will feel safe, there will be a safe zone created by the respect.

If the teammates don't respect each other, they will ignore what the others are saying, even if they are forced to listen to them.
>I'm not snarking; I honestly don't know. I tried using PHP years ago, threw up my hands in horror, and have never touched it since.

Without exactly knowing what exactly bothered you and what you use instead, we can't answer.

As for "PHP: A Fractal of Bad Design", I find the article quite shallow. One could say the same things comparing something like Python to Smalltalk, and yet Python is fine as it is.
Vanderbilt, Google's Verily to Launch Precision Medicine Initiative Cohort
Except the buyers and sellers (mutual funds, etc) aren't the brokers, and brokers ultimately decide where to send the orders. I don't believe there is any regulation that forces a broker to use an exchange the customer specifies; rather, that they must buy or sell on the exchange that provides the best price.
Two points for using Swift on Android: 1) shared code between your ios, mac, and android apps. 2) you already know swift.

That said, there is always a cost to using a non-standard language to develop for a platform. Things like having to translate documentation as you read it, friction between system libraries and your languages standard library, etc.

I've not looked at Kotlin in detail, but I wonder how much that friction is reduced because it's java-based, or if you'll experience just as much friction using Swift on Android as you would using Kotlin on Android. Worth evaluating if you're starting a project 6 months to a year from now as the Swift tooling for Android starts to mature.

As it stands now, I would have a look at Kotlin, but almost definitely write any projects started today in Java. Swift is nowhere near ready, and the advantage of writing in the platform's "native" language usually outweighs any benefits there are to using a "better" language.
Some people like to avoid Java and languages dependent on JVM. For them any non JVM based solution on android is welcome change. So efforts towards that need no justification as to why any of numerous JVM language is not used first.
Externally, Firefox has become a brand. Servo is comparable to Gecko or WebKit (it is a browser engine), although it is new, not finished, and uses novel techniques.

What follows is speculation on my part. I am not a Mozilla employee.

Mozilla might, in about five years, offer a new product for desktops which features Servo, SpiderMonkey (the JS engine currently used in Firefox), and an as-of-yet undefined chrome (the UI bits around the rendered page). It may be a mobile product instead, or a product for a different type of hardware, although the current thinking seems to be to target it for desktops.

Whatever that product is, it may still be called Firefox or a derivation of that brand (as Firefox OS was), although it might have a completely new name (it worked for Microsoft Edge, after all).

(Updated for clarity.)
You can't really define what quality software is, though. You could have a patched together backend that "just works" and has a great UI that customers love, but how is that "quality" software? The software end of it is clunky and patched.

On the other hand, you can have completely documented, easy to read, well thought-out code that has a terrible UI that no one will bother using. I guess you can say the software is "quality," but it doesn't matter.

Then again, maybe "quality" software to you is software that works, like the first example. In that case, it doesn't matter how well documented it is. It works. It's self-readable at least to those who wrote it. Maybe the team will never grow beyond that, so who cares? Or by the time it does, it will be rewritten anyway for other reasons.

The point, I think, the author is trying to make is that quality means so many things it means nothing. It's a useless term because it has no objective meaning. We can argue about what you think quality is and what I think it is, but it's likely going to be different for any two people.
> the right to not speak is protected by the 5th amendment

No, it's not. The right not to incriminate yourself is protected by the 5th amendment. People are subpoenaed and forced to speak all the time. That's why Apple isn't making that argument. (They do have a 5th amendment argument too, but it's not based on self-incrimination.)

> If you're an "enemy combatant," you're sitting in somewhere in Iraq or Afghanistan

It has never been put to the test (because the scenario is pretty unrealistic) but do you really think that if a U.S. citizen on U.S. soil made a credible claim to have planted a nuke somewhere in NYC, that the government would not mount an argument that the Constitution allows them to waterboard that person to get them to reveal the location of the bomb? And that they might win?
Private talks made easy, 2.22.8 released
This is kind of an odd article, didn't completely know what to make of it. There is another definition to the word quality, probably the original, which means "property". For example, color, texture, and density are qualities of an object.

As such the QA dept reports on the current status of a project in several dimensions, not that it has met a binary threshold of excellence.
> The US Congress does, really, have line-item authority over regular US laws.

Except that, in this case, only if they first vote to change their own rules, which were set when TPA was passed. So they dig themselves a small hole, which they can jump out of without help. Nothing unconstitutional about that. Congressional-Executive Agreements are a pragmatic solution to a coordination problem, using constitutionally provided tools to solve a problem whose complexity was not envisaged by the authors.

Fun fact: the U.S. avoids entering into treaties which override our laws, despite explicit constitutional language which says that they would. Best to change laws by statute, so everyone is clear, and everyone doesn't have to do a bunch of supremacy analysis. We'll even pass implementing legislation for treaties that in other nations are self-executing.
From Shader Code to a Teraflop: How GPU Shader Cores Work (2010) [pdf]
This is a great summary. Some very minor details that you didn't cover:

Rust and Servo were basically announced to the world at the same time, as "the Servo project." It was really important that we build Servo at the same time as Rust, to make sure that the language was actually useful at building a real practical thing. The experience of building Servo helped Rust's development immeasurably. Furthermore, it also helped Rust be built in Rust itself. There's a danger when you build a boot strapped compiler: you might make a language that's great for making compilers, but not much else. Servo made sure that wasn't true.

https://bugzilla.mozilla.org/show_bug.cgi?id=1135640 is the overall tracking bug for moving Rust stuff into Firefox. Firefox 45 on Mac and Linux will contain a teeny bit of Rust, and just got turned on for Windows a few days ago. It's an MP4 metadata parser. The URL parser has a patch, but it hasn't landed yet.
Maybe Mozilla isn't a big enough company to tackle it, or it diffuses their focus, but it's important to do.

Ubuntu is still trying, so there's that, and that's great.

http://www.ubuntu.com/phone
What _is_ quality, then? I've never heard an objective definition regarding software.
How much of your design assets are diffable? Are the assets in the same repository as the code?
FROM CONVERGING TO FUSING
Show HN: Chrome extension to block sites
Woah, real numbers! Thanks!
This is what everyone in capital markets execution has been doing for over a decade actually.
It would certainly put a whole new perspective on range anxiety.
I love Kotlin, but being able to develop libraries in one language and use them in both Android and iOS is huge. I have been using J2Objc for this until now, and while it's a great tool, it forces me to use Java, which I don't love. I would prefer being able to use Kotlin on iOS, but using Swift for Android development is a great boon.
Growing a Site from 0 to 10k Visitors a Month: Nat Eliason Edition
We support substitution tags in email templates. In other words, you can replace -name- with the name of your customer - it works a lot like {{name}} in a handlebars template.

And yes, you can still sign up through the Microsoft Azure marketplace: https://azure.microsoft.com/en-us/marketplace/partners/sendg...

Hope this helps!
So media companies (corporations) shouldn't have freedom of speech?
Sit down.
I am specifically talking about base cash salary here, but point taken.
We already do this @ Gigster. Except you don't get hired to be full time employees. You get "hired" to work on short term projects (that you can accept or deny) which is arguably more fun.
Yes, it is much faster, see https://about.gitlab.com/2016/02/22/gitlab-8-5-released/ and https://gitlab.com/gitlab-com/operations/42
Zero.

> There also isn’t a clear way to see a “diff” of the visual changes being made on Github which makes the feedback a bit more difficult — we have to download the file and manually compare with the previous version.

This also ignores the fact that design assets are massive regardless, more than what git is intended to be used for in the first place.
That must be related to the publicity of "Flash Boys" and the fact that some entities are rallying the public to send comment letters.

BATS when it became an exchange was nothing but a vanilla competitor marketed as a Better Automated Trading System. It didn't have anything like a speed bump.
Is there planned support for gitlabs sometime soon? I've been moving all my projects slowly off github due to recent events.