skysight-inc/HackerNews huggingface dataset:
Clearly this government office isn't talking to some of the other ones, right?
How do you work out the logistics for the laundry? I.e. do you pick up daily/weekly. Do you give the customers one of those large laundry duffel bags that they fill up? Do the cleaners that come once a week pick up the laundry if they find it lying around? Those sorts of questions pop up for me when thinking about this...
Location data embedded in Instagram pics betrays Congressman Schock
How Apple's new medical research platform was born
How Apple cleverly trademarked the iPad name while keeping the product a secret
> For me, many of these problems are more of an input issue, than an encoding issue.

I think you've hit the nail on the head here. I'm a native English speaker, so I may in fact be making bad assumptions here, but I think the biggest issue here is that people conflate text input systems with text encoding systems. Unicode is all about representing written text in a way that computers can understand. But the way that a given piece of text is represented in Unicode bears only a loose relation to the way the text is entered by the user, and the way it's rendered to screen. A failure at the text input level (can't input text the way you expect), or a failure at the text rendering level (text as written doesn't render the way you expect), are both quite distinct from a failure of Unicode to accurately represent text.
Another possible factor: some people suffer from a kind of "error blindness", when the computer shows them some text, even really simple text, they don't seem to be able to see it, almost like their optic nerve is censoring the text.

You can write your program so that on error it shows a message like:

"Push the red button"

... and many users will just stare at the screen and proclaim "I don't know what to do, what's wrong with it? How do I get back to the thing?"
Microsoft sends Internet Explorer into retirement
Steve Jobs on choosing a target market (1991)
We also have 'not using a custom malloc() wrapper that doesn't actually free memory as a wrapper around free()' to prevent Heartbleed, but instead of this technology being from the future, it's actually from decades ago.
New GPU and deep learning devkit from Nvidia
It has to do with how the text is rendered. For example, if you see the Bengali text on page 3 of this PDF:

http://www.unicode.org/L2/L2004/04252-khanda-ta-review.pdf

it is unreadable and incorrect Bengali. ;-)
[Text for those who will hit the paywall]

It was once used by nearly 1bn people, making it one of the world’s best-known technology brands. But even Microsoft, its maker, has been forced to admit that it is deeply unloved.

Internet Explorer — the software that launched the browser wars of the 1990s and became a symbol of the Seattle company’s former stranglehold on the tech world — is about to be ushered into retirement.

The group confirmed this week that it would not use the IE name for the new browser that it plans to ship with the next version of its Windows operating system, due later this year. The revised software, codenamed Project Spartan, is intended to catapult Microsoft beyond the Web 1.0 world for which IE was designed.

Nearly a decade ago, Dean Hachamovitch, the then-head of the IE business, confessed at an industry conference: “We messed up.”

With Spartan, Microsoft hopes to vault past IE’s weaknesses to produce a browser that is more suited to a digital life lived on multiple devices — part of the strategy of new chief executive Satya Nadella to break the company’s reliance on its old PC monopoly.

Tom Bedecarre, chairman of Akqa, a digital advertising agency owned by WPP, said the 20-year old brand was long past its sell-by date. “In the war of the future, which is mobile, they’re losing,” he said. “Nobody’s going to download Internet Explorer as their mobile browser.”

Microsoft has admitted that it failed to make IE a more loved part of daily life over the years. It even resorted to self-mockery in some of its advertising, referring to it as “The Browser You Loved To Hate”.

“It’s been a product problem for a long time,” said Dan Brewster, a senior interactive designer with Wolff Olins, the marketing agency. “People don’t like it,” he added, but used it only because it came pre-installed on their computers or because they were required to by their employers.

IE’s historic significance was sealed in the late-1990s. Designed to counter the rise of browser pioneer Netscape at the dawn of the internet, it was shipped free with the pervasive Windows operating system — a tactic that later made Microsoft the target of an antitrust investigation.

It overtook Netscape within three years and went on to dominate access to the online world, accounting for an estimated 95 per cent of browser usage soon after the turn of the millennium. But a combination of complacency and the failure to anticipate the shift to mobile sealed IE’s fate.

First the open-source Firefox browser and, more recently, Google’s Chrome ate into IE’s market share, using faster technology and slicker design to win users. Microsoft’s share of browser usage has fallen to around 20 per cent, similar to Firefox, while Chrome has risen to nearly 50 per cent, based on online activity.

Although being pushed into retirement, the IE name will live on, if only for a short time. A new version of IE will be included in the next Windows launch as well as the Spartan browser, to make life easier for companies that have developed software to work with the browser.
Rust is one of rare class of memory safe languages that are

- easily callable from other languages because of the C ABI

- runtime free and not Posix dependent

- portable across CPU architectures.

Rust will provide you memory safety where other languages can't even run.
I don't imagine it does. The userland is a whole different thing. But that doesn't mean that I (or Samsung or Amazon or Mozilla) can't make changes to the kernel in ways that aren't possible with iOS, or benefit from Google's improvements to e.g. Linux power management regardless of whether or not my device runs the Android userland.
Really disappointing that it only gets 5.5 hours of Wi-Fi browsing with a 91 watt-hour battery (on integrated graphics). The rMBP pushes 9-10 hours under those conditions.
The Science of Disbelief
Send Money to Friends in Messenger
Not unifying them means that the fonts automatically work when you mix text/names written in these alphabets. It also means that mathematical/physical/chemical stuff (that typically uses Latin and Greek letters together) will just work. There is a similar reasoning behind all the mathematical alphabets in Unicode.

Furthermore, Unicode was supposed to handle transcoding from all important preexisting encodings to Unicode and back with no or minimal loss. Since ISO 8859-5 (Cyrillic) and 8859-7 (Greek) already existed (and both included ASCII, hence all the basic Latin letters), the ship had definitively sailed on LaGreCy unification.

On top of that, CJK unification affected so many characters that the savings would really matter and it happened at a time where the codepoints were only 16 bit so it helped squeeze the whole in. All continental European languages suffered equally or worse back when all their letters had to be squeezed into 8 bits /and/ coexist with ASCII.
I'm reminded of this Radiolab segment where they talk about how younger kids are entrenched with imagination and fantasy, and than a few years later they begin obsessing with rules, fairness, and civil relationships more.

[0] http://www.radiolab.org/story/153809-rules-set-you-free/
BitTorrent-Style Updates Revealed in Windows 10
As soon as we have a full port of OpenSSL in Rust, this will be interesting. Talk is cheap; who's going to step up and do the hard work?

I do believe that the right developers, using the right practices, could make a more-secure OpenSSL. But it would be expensive in terms of developer time. Maybe a group with the right experience could crowdfund it?
ASan is a runtime detector; it only works if you have a test case that covers the buggy thing, like in this case sending a malformed heartbeat request. OpenSSL pretty clearly didn't have a test case for that - if they did, they'd've caught the problem, with or without ASan. It's like the difference between a type system and unit testing.
Using a plain-old mutex in Go isn't encouraged. As you said, the memory model is _share by communicating_.

Sometimes, yes, using a mutex makes more sense -- and that does introduce the possibility of a data race.

If you follow effective Go code -- I imagine the code is on average about just as safe as Rust code is. It is partially comparable to using `unsafe` blocks in Rust -- don't do it, unless you know what you're doing. Stick with channels.
http://en.wikipedia.org/wiki/Complex_text_layout

Hypothetically you could construct a language where the glyphs are easy to generate procedurally on the fly by people who are fluent in that language, but who's full space of possible glyphs is staggeringly massive.

Suppose a language with tens or hundreds of thousands of "base" glyphs, but with a unique variant on each glyph depending on what is to the left and right of it. With that alone, for N base glyphs, you could have N^2 variants of each glyph.

I don't know if that sort of language exists. I don't see any reason why it couldn't though.
Wikipedia is not forced unto the world as everyone's only source of knowledge.

Unicode on the other hand is the only way many people have to input and see text in their native language. When one group proposes being the ultimate solution to everyone's problems, and then pushes their standard forward as such, complaints about inadequacies in the solution presented are perfectly fair and valid.
That would have been my guess as well. For many B2B problems you kind of have to understand the right hand side B which means some industry experience. Same for something like aerospace and finance I'd guess.

That being said I also intuitively assumed a younger age. Most certainly bias on my side since it's the youngest founders I tend to read about online.
> ... he wouldn't be able to go through the planning...

The article goes out of its way to make this point. Namely, that Osmakac had no capacity to plan an attack, therefore he wasn't a terrorist until the FBI made him into one.

If you happen upon a gun on the sidewalk, then use it to carry out your desires to murder an old enemy, is your guilt or innocence determined by the details surrounding how the gun got to the sidewalk? That's the point I'm getting at.

> Point #2 is protected free speech.

> As for point #3, another interpretation is that he's willing to fall into things in front of his face

And? I wasn't suggesting that he be arrested for those things. I was pointing out his actions and behaviors prior to the FBI getting involved were sufficient to warrant civilians turning him in to the FBI. The FBI wasn't looking to make a terrorist out of some "retarded fool" for kicks. They were following up on assertions made to them about the danger of an individual, and they determined those assertions to be credible based on whatever they knew or were able to uncover about his past. That's just police work.

> Also, why did you mention the Patriot Act?

Mea culpa. I was using "The Patriot Act" as a stand-in for "The Over-reaching Federal Intelligence Community". I think the Patriot Act is a poorly-aimed law used to justify whatever the government wants it to. My point was that even though I do believe the US' three-letter organizations are overstepping their bounds in some areas, this doesn't smell like one of them to me.
You don't determine language based on codepage. I give you ASCII text; what language is it?
I'm fluent in Japanese and speak some Mandarin Chinese as well. These 3 characters are identical, not similar.

For a different example, 国 and 國 used to be the same character, but China and Japan (left) have both diverged the traditional form still used in Taiwan (right). Unicode treats them as separate.

今 Looks slightly different in traditional Chinese vs other languages. In traditional Chinese, the little straight line between the two angled lines is sloped, while it is horizontal in simplified Chinese, Japanese or Korean. Any reader of any of these languages would have no issue if the variant they are used to was replaced by the other one. They might think you have a sloppy handwriting or an ugly font if they even notice, but that's about it. Unicode treats them as the same.
This sounds good to me. I'd want to know more about the meals first.
A copyright license that includes an explicit patent license would allow non-LLVM users to use the patents as well, as they would need to be able to in order to exercise their rights under the LLVM copyright license and use LLVM code in something that is not LLVM.
... if it were attached to a cable, it wouldn't float away.
Rust isn't technology from the future, for the most part. It's engineering from the future -- everything is in one language with a native ABI -- but with very few exceptions, each technology in Rust has been around for a while.

Memory-safe arrays, which is what's at issue here, is precedented in tons of languages. Even GW-BASIC got this right.

It should be an embarrassment to the entire systems programming community that it's 2015 and we're only starting to think of replacing C.
That's semantic quibbling. How about the degree of fitness, controlling how many children are produced? How about fitness for raising/protecting children? There's definitely a correlation, and 'survival of the fittest' is a reasonably concise expression of that correlation. Its definitely not black-and-white failure/success at reproduction.
That sounds about as expensive as a live-in maid, without the extra services and sense of personal connection that a maid could provide.
Atlas of Beauty
This is great, thanks for the encouraging note!
Same thing, really, in this context. The biometrics are what uniquely identify someone (username, UUID, whatever). The password is what provides authorization. The problem is biometrics are being treated as both the identifier and the authorization.
Why in god's name does a laptop that large not have independent home/end/pgup/pgdn keys. This trend drives me nuts.
This is a fantastic example, from both perspectives.

To strictly play devil's advocate for a moment; why do developers think it is appropriate to benefit from the free/open source library, yet not provide that same benefit back to others (in the form of using it in the proprietary software)? To me, this was the exact type of situation in which the GPL was crafted to avoid, and part of why rms didn't just declare his software to be in the public domain. I'd also imagine rms' response to this complaint would be along the lines of, informing the developer in question to work on a free, non-proprietary version of the software, so they could in fact, use the library (totally disregarding the fact it is due to external pressures, such as the employer, that they're developing proprietary software in the first place).

This is, of course, assuming the original developer licensed the library under GPL on purpose and knowing the resulting implications, as you eluded to.
Not sure how 'wealth' is related to fitness? Poor people are renowned for reproducing much more than the wealthy in modern times.
John Carmack: “I just dumped the C++ server I wrote for a new one in Racket”
I'm not that surprised Unicode includes very shallow code points (pile of poo), because nobody really cares. Bengali on the other hand, requires no mess up in order to satisfies the Billion+ users.
I am severely lacking in performance analysis skills.

Does anyone else spend hours tweaking builds/configs only to then just assume you have made an improvement without confirming it?

I wish I had learned of Knuth's "premature optimization is the root of all evil" quote sooner.
Uganda's Hottest Music VIDEO
> If they are talking about unifying these alphabets, then they are out of their minds.

AFAIK the author is just discussing han unification:

http://en.wikipedia.org/wiki/Han_unification
Just the AMA? Or could it possibly be all those regulatory and license laws that revolve around medicine/doctors?

Granted, I couldn't find much info about the extent of the AMA's power.
come on, no one uses retina anymore
with technology that is much safer than traditional passwords

From what I understand this is simply not true - could someone with a security background weigh in if this statement has any basis (were they comparing to <first_name>-"1234" and "user"-"password")?
I can't think of any telecommunication or computing device that I own or have touched in the last few years that was built by white, English speaking men.

Regarding software, I googled a bit to find numbers, and one of the first articles actually giving numbers says 19 percent of software developers are in the largest English speaking country, the US: http://www.techrepublic.com/blog/european-technology/there-a...
> The vast majority of Japanese and Chinese characters are not only similar, they are identical. Not all are. Some are clearly different characters deriving from a common historical root, and should not be unified.

And what about traditional versus simplified? Which glyph set do I use? Oh wait, thanks to Han unification, I now need to rely on bloody environment variables to decide!

For Chinese text, rendering a string of text involves not just the string, but also the local runtime. Joy of joys.

> You don't want a in German and a in English to be different letters just because Helvetica and Baskerville look different.

If following the spec means my users become partially illiterate then there are problems with the spec.
Elon Musk Says Tesla Will Be a Leader in Self-Driving Cars
Beer sales: It's no longer Guinness time
I think you got that wrong by a factor of 10. I get between 500 and 1000 lines / sec on my laptop. It depends on the code style. The more straightforward the code the faster the compile. Still with incremental compilation it means I wait rarely more than a couple of seconds.
I think the writing was on the wall last year when they dropped the I/ON brand and just invited us as "trusted partners".
To be fair, Apple does sponsor FreeBSD, with donations and employment.
Heh, exactly my thought when I saw the headline. As a webdeveloper since 1995, I can only say "phew, finally" - that browser probably cost me 2-3 years of my life, spent hacking various webprojects to make them work in IE.
They're practically same, but rust pulled it off without a gc.
Change How You Type Forever
Tanzania Releases
Thank you, I wasn't sure about enforcing purity, but now its clear :)
Once the Uber Affiliate Program pays out as a % of revenue (or even some sort of flat-fee CPA), then I'll be very very interested
> if the data breaches we hear about almost monthly (Uber, Target, etc) are any indication, your password is just as at risk as your fingerprint.

Two things - let's assume these companies follow best practices and both the fingerprints, biometric details and passwords are all hashed. Still:

a) Unlike a password your biometric data is publicly obtainable.

b) You cannot change your biometric data after it's been compromised.

> As someone who actively researches biometric authentication,

If you are an expert in the field - I think you are doing people an active disservice by telling them the security is just as good.

Finally I think typing passwords just isn't that hard - everyone is used to it by now. I maybe odd in this - but its hard for me to see the greater degree of convenience as a huge breakthrough (even without the security implications).
I think it's interesting that we can now pay almost anybody we have contact with, at almost zero effort and without even having to remove my debit card from my wallet.

You can pay people via gmail now for your email contacts, send money to your personal friends via social media networking. I bought my Uber to work this morning completely frictionless without having to physically use my card.

It's an interesting development of recent years for sure.
Memory leaks are still possible when using GC, of course, unless one operates with a strict definition that only includes unreferenced objects.
Drop me a note at Doug (at) thehappyhome.co - I'll set you up with a free week, and answer any questions that you might have.
Example from personal experience: I'm working on an audio app right now, and I have high bandwidth, low latency data. I'm CPU bound, allocations and the GC are my enemy. It's just not feasible to constantly copy those buffers around. :(

Don't take this the wrong way, I'm not complaining about Go. Just know that sometimes, there are real reasons to share memory. And when you do: Rust has got your back, but in Go you're on your own.
Looks like they use an ads-based business model.
does this say something about how fast snapchat is innovating?
Azure is Down
Did they build out this technology themselves, or was it through an acquisition?

On a side note - no AmEx or Bank Account option...
This is pretty rad. It's either a convincing simulacra of a linux, or it's a linux? or is there a difference?!

This is doing my head in, maan.
Git Patrick
The section responsible for Hearbleed was never allocating more than 64 kilobytes, which can probably be cleared in 1000 cycles on most modern architectures.

As someone else pointed out, OpenBSD's malloc() implementation could have supplied a cleared memory area with no discernible performance impact (in fact, I think LibreSSL already does).
Okay, how would you do it?
If you want bidirectional mixed language support, you're not going to get around implementing bidi rendering at some layer.
Character encoding is not that layer. You are making legitimate complaints, but they are largely in the realm of poor internationalization support. There may be finger-pointing between applications, toolkits, and OS middleware, but the character encoding should not be taking the bum rap for that.

Internationalization is a fundamentally difficult engineering problem and no character encoding is going to solve it.
The vast majority of logged-in users don't post and the vast majority of readers don't log in.

> That's going to be a lot closer to reality

Trying to tease "reality" out of these numbers drove me mad, so I stopped trying. Are bots "real"? Are spammers? How many "real" users does a unique IP represent? It's better, I think, to just measure a bunch of different things, note how far apart they are, and resist over-interpreting.
That may be the 'cry wolf' thing. There are so many pointless dialogs pushed into your face, you stop reading them. Install any package, and pound on 'Next' until the damn thing finishes installing. We're trained to ignore them in this way.
A natural addition. And just like Square Cash, just enter bank issued debit card for fee-free transactions.

Now if it would work outside the US and in-between different countries, that'd be the killer app. Is there anything close to that dream?
Jailbreak iOS 8.3 by Evasi0n8.3; iOS 8.2 and iOS 8.3 – iosjailbreak-download.com
> "We’ll continue to have Internet Explorer, but we’ll also have a new browser called Project Spartan"

Oh joy, another browser from Microsoft to test. :\
BINGO.

But because of Han unification I all of a sudden DO need to know the language.

The same Unicode code point needs to be rendered differently for a user in Mainland China versus a user in Japan or else the user may not be able to read the text! Even if the user can read the character, they are going to experience a degradation in reading speed and comprehension, and be generally frustrated. Not to mention showing the wrong character is insensitive to the customer's culture, and if I pick to and stick just one set of characters to use, I end up (being accused at least of) promoting cultural hegemony based on which character set I go with.
Running Linux or OS X?