skysight-inc/HackerNews huggingface dataset:
ehh.. FB wasn't even monetizing their mobile products when they went public. There was huge growth potential there. Snap will have a much harder time. Showing ads between stories, is a tough sell. They aren't contextual and are poorly targeted ( no real known interest graph ). They could possibly determine some sort of interests from people you follow, but all they really have is location and device information. With device information you could possibly correlate PII, but even bluekai's information from device is pretty horrible. Most people don't use their real names and I know for a lot of people its similar to myspace where they just give out snapchat names to random people.
> there is literally no way to poll a file descriptor

https://godoc.org/golang.org/x/sys

https://godoc.org/golang.org/x/sys/unix#EpollWait

https://golang.org/pkg/syscall/

Of course it is a bit of a pain to write OS specific variants if you are building a completely crossplatform solution, but it is supported out of the box:

https://dave.cheney.net/2013/10/12/how-to-use-conditional-co...

That said, I agree [regarding the] puzzling decision to not to treat 'select' as a general contract for all asynchronous ops as that fits perfectly with the CSP approach.
You're right, but the many boomers have been happy to accept the benefit even while seeing the cost fall on succeeding generations, though it's hard to blame individual people from drifting along with their cohort.
"What I'm trying to do with sponsors is what I strongly believe is the most responsible middle ground that keeps the greatest number of people happy, myself included."

The like the fact Troy has his ^own^ blog and can make his own call. There are alternatives ways to think about ^how^ a blog makes money. [0]

[0] Dave Winer, "How I made over $2 million with this blog" ~ http://scripting.com/stories/2009/02/11/howIMadeOver2Million...
I have a question for you. Have you ever traded? This is not meant as an insult.

Just for scale, yuan soared 1% today, bitcoin dropped 20%. Yes, I know there is leverage in the forex markets. But more importantly, compared to the yuan market, bitcoin is a spit in the bucket ($300 bln yuan daily volume vs whatever the bitcoin daily volume is)

What you're (or the article) is basically saying is that the investors which were into bitcoin wet themselves today by the amazing yuan soar and suddenly decided to move theirs money from bitcoin to the yuan, even if these two are completely different financial things (even if both are named currencies), and one who invests into bitcoin does so for completely different reasons than one investing into the yuan.
http://www.catb.org/jargon/html/F/Flyspeck-3.html
I'm not familiar with them. What would they help me with?
"Assuming a perfectly spherical voter..."
You could just put a GPG subkey on it. That way it's revokable if lost, without destroying your entire PGP key.
I unfollowed most people and started liking things. My feed turned into a sort of ghetto Google Reader... but they always tweak it to meet Facebooks objectives.

To be honest, the only content left is the mommy swap pages. Fancy Craigslist. :)
I think I see where you're coming from. It's pretty much a matter teaching the most common thing, since common implies widely-applicable which implies most useful in practice. I think that's a fair point, and should certainly be a consideration to anyone planning to teach any topic in comp sci. However, having taken a semester-long course on 16-bit (8086) assembly language back in college (with MASM running in DOSBox on OSX, of course ;) ), I've never found any need for any further coursework or tutorial-style texts/articles/whatever in order to later write 32-bit x86 or amd64 (or even ARM, PPC, 68k, or 6502) assembly language. Just the reference manuals were enough, because the mindset is largely the same. I feel as though it's broadly similar to other programming paradigms, where if you learn a procedural language, there's no real need to study another before starting to code.

> What else runs x86...?

Well, as far as I know, every amd64 machine can run 16- or 32-bit x86 machine code. So, I'd say pretty much all of your examples of amd64 machines run x86 :p
it's already dead to many asian/chinese users. they moved to line and wechat.
Intel Compute Card (95mmx55mmx5mm) PC in Your Wallet
I just meant that if a tool/lints have proven to be useful, why not internalize them into the compiler?

This way the compiler has a marginal increment of maintenance effort but can remain flexible, change its internals at any point. It will also benefit users who for a multitude of reasons only want/need to use stable.
Look into pump and dump, there are a lot of ways to make a company look better in the short term at the cost of long term net profits.
No - that's an important structural reason, but I dispute your claim that it's the overarching economic factor or that it's entirely out of our control.
I guess I just don't understand the "why" so I am not motivated to look into it properly and at first glance it's introducing loads of new concepts. Maybe as my apps get more complicated I'll outgrow it but just plain Redux seems fine for me at the moment.
Yes but it's worth noting that for a person of any age it's harder to generate the same power in a fully aero position because you are choking the engine!
Nope (though I'd love that). By "merging" I mean things like folder trees. But Dropbox gets so many nice details right that competitors and homegrown solutions tend not to think of:

* When syncing a folder tree (uploading or downloading), it transfers files smallest to largest (globally across all files queuing to sync, regardless of folder). This simple algorithm is remarkably close to optimal behavior.

* When modifying a small file while larger ones are syncing, the small file immediately cuts to the front of the line (even sub-file). This avoids situations where a large folder uploading or downloading prevents you from getting the utility of the quick syncing of small work files.

* Files deleted from the server or another computer are briefly retained on the client in a special folder before being deleted from local storage so that their contents can be matched to other incoming files. In other words, even for very complex folder move and file rename operations, if the new files contain the same data as the old ones in whatever permutations, the client will sort it all out without re-transferring actual file data.

* There are no data loss holes. All operations are on a files-first basis (not folder-first), and Dropbox will never decide that a file was intended to be deleted unless the client app explicitly observes deletion. You don't need to worry that offline renames or moves, even multiple conflicting ones from different machines will result in deletions when the Dropbox clients go back online.

* "No data loss holes" also applies to conflicts of a single file. If a file is modified in two different ways by offline clients, one file or the other will be renamed to make sure that a modification isn't lost.

* The Dropbox client never gets stuck requiring the user to "resolve conflicts". It picks the sanest thing to do and does it (always observing the "never lose data" principle). Syncing is delightful and never fails, not a chore to be dreaded and carefully planned for with a bunch of "conflict" choices, like all systems prior to Dropbox.
I would not want a 35 year old Zuck as President.
I'm wondering how this compares to tsn (aka audio video bridge[0]). Their conclusion was wifi is not reliable enough for time sensitive applications. Great av networking is not only about clock sync anyway so this looks more like a half baked standard, nevertheless a good step towards lag free av.

[0] https://en.m.wikipedia.org/wiki/Audio_Video_Bridging
Docker has not, to my knowledge, actually found a working and scalable business model quite yet. Doesn't mean they won't find one, of course, but that's kind of a prerequisite for an IPO.

Slack CEO's most recent comments suggest that IPO won't happen this year at least; they are also quite savvy (not the first rodeo for the founding team/leadership and they have plenty of investment demand plus the founders are all financially secure). I'd be surprised if we see a Slack IPO even in 2018.
It was a demo page on my HN clone ( with tags) and i thought it was an interesting throwback--> http://tagly.azurewebsites.net/Home/Demo
ALPINE DATA | SENIOR JAVASCRIPT DEVELOPER | SAN FRANCISCO | ONSITE, VISA, http://alpinedata.com/

My company is looking to hire a senior Javascript developer to take change of our Backbone.js frontend.

Here are a few of the things I believe we should try to accomplish (I'm looking for someone to have this conversation with):

* Our Backbone codebase is currently located deep within a Rails app, and served with the Rails asset pipeline. I think we should separate the two codebases. The Backbone Javascript codebase could then use be set up with modern tooling such as npm, webpack, etc.

* Some folks have thought we should scrap the Backbone codebase entirely and rebuild it using a newer framework like React or Angular. But, I believe that it's too large for that, and I'd prefer a moderate approach where, we upgrade to the latest Backbone version, perhaps using Marionette as well, while also refactoring / cleaning the codebase. We could also refactor it to use a v2 of the Rails API.

You should be a modern Javascript expert who has worked on many (minimum 2-5) Backbone.js projects. You should be comfortable and passionate enough about Backbone.js to be willing and interested to refactor a large, existing app to be more performant, easier to work with, and so on.

So -- and thank you for reading this far -- basically we have a great opportunity -- lots of well paid, very comfortable, steady, challenging and interesting work, for the right person.

We offer very competitive pay, a very diverse, friendly, modern (unlimited snacks and drinks! not too many meetings!) and relaxed work environment, as well as valuable stock options. Office is in SF, SOMA and you must be able to come into the office several times per week.

Please apply here: https://www.jsco.re/l-zx OR you can email me directly at kevin@alpinenow.com
You could call the Advertisement Code Commission. See: https://www.rijksoverheid.nl/onderwerpen/bescherming-van-con...
> mechanical and aerospace engineers aren't fit to make predictions of a social nature

this seems like a hasty generalization. it's probably fair to say that a mechanical engineering education is unlikely to include much depth in topics of a "social nature". (of course, there's nothing stopping a mechanical engineer from diving in, be it formal education or self-directed.)

that said, identifying one's assumptions (such as: a decreasing search trend implies decreasing interest or utilization) is an important facet of any sort of research, be it "social" or not. i think describing this as a "science/engineering geeks aren't qualified to talk about social stuff" situation seems to miss the mark.
We all know the web was invented for static document browsing, and that was the REASON the back button was invented. Nowadays with Javascript everywhere on all devices everyone is writing APPS that run in the browser. It is simply bad design to have those apps rely on a browser-level back button, for anything at all, because the back button assumes your previous URL 10 seconds ago was different, and that's a very stupid assumption. If you can define what "back" even means in a way that applies to all APPs go for it. You can't. It's a nonsensical type of question for an APP.
Critique: http://www.genekeyes.com/FULLER/BF-1-intro.html
A useful article, originally from 2014 but updated recently.

Previous HN discussions:

https://news.ycombinator.com/item?id=7359992

https://news.ycombinator.com/item?id=10149019
Sorry for my lack of knowledge about this, but are "ad mailmen" a specific thing in the Netherlands? In the U.S., junk ads just come in the regular mail.
You do them upfront, then store one in a safe place (ie: for github I have yubi and yubibackup registered)
I thought sonos can't even do multi channel audio. It's just a kind of mesh network. Wisa was supposed to fix that but for some reasons it seems it failed to get mainstreem
For context: behind Vivaldi there is part of the original Opera team. Vivaldi indeed really resemble to Opera 12: and that's awesome. But they are using Blink instead of the defunct Presto.
am I the only one who read this and didn't really take anything new away? yeah social media, like anything else is not always a good thing. okay, sure... but i'm sorry developer burnout happens for a lot more reasons then stated in the write-up.
Hi. I'm Jerome. Good to meet you.

Now you have!
Moi? I'd rather buy ten passive backup keys than implant an RFID key that puts out a signal that never turns off. At that point you're robbing Peter of pay...Well...Um...Big Brother.
When new phones or displays come out, the manufacturer will invariably brag about the increased color gamut. Before I get blinded with science, it's time to adjust my f.lux and night shift settings.
It is a very research-oriented experience, but you can definitely frame your work as more engineering-intensive. Quite a few of the residents have done some more really impressive engineering feats in the research domain.
Why Do Decision Trees Work?
I don't believe for a minute that if it Social Security were to be phased out everyone would see their salary rise 6.2%.
Uh oh. They made the browser mistake.
It was a visible-wavelength laser, so I would've known there was a problem as soon as it hit my retina, even without the audible click and the sudden and disquietingly misplaced feeling of having been kicked pretty hard in the nuts. But I take your meaning.

(And I own a pair of wavelength-matched laser goggles now, as should you if you're going to do anything at all with a laser and any kind of focusing optics. Carelessly enough handled, even a 5mW pointer beam can pose a real risk. Don't make the same mistake I did!)
I think it requires some more thought.
Unfortunately the standard explicitly forbids that type of adapter because they could be used to plug two USB-A power supplies together. (USB-C power supplies are designed to prevent this from being an issue.) Source: https://plus.google.com/+BensonLeung/posts/UFCHbSDRa2o

That doesn't mean they don't exist - you can find a few on Amazon - but reputable companies aren't making them, so quality is going to be suspect.
That's not a silver bullet though.

In a large software system you can't expect any individual to be as effective working in any area of the system. So you're winning on the blocking front but you're losing on the productivity front as people ramp in on different pieces and you're also potentially losing a sense of ownership from the developers and instead giving them a sense they're cogs in a machine...

To me a better compromise is to ensure you have enough of a backlog that you can always pick something that is the right combination of expertise/interest/lock-free at any given time. If you plan properly and you have sized your teams properly things should move along better than trying to get everyone to work everywhere on some random feature. That's not to say you can't occasionally do that if something important comes along but to me feature teams in large scale software is to be avoided. [EDIT: realizing this is maybe too strong of a statement, a team can definitely work across multiple pieces and will ideally implement complete features, but those features need to be a match to the capabilities of the team as opposed to just looking a "feature team" as some sort of unit of production for any random feature]

There's another part to this which is that it can be difficult to see the inter-dependencies between features. So modelling your software development as a bunch of teams that can just pull the next feature from the queue and work on it may actually not solve the locking problem at all but create more subtle dependencies and less efficiency.
I think the point is that "RISC" should have been "RISC-V". "RISC" = "Reduced Instruction Set Computer", which encompasses many architectures. It's more of an approach to designing an architecture, and encompasses things like ARM ISAs, etc, whereas RISC-V is a specific architecture.
Why Classic Rock Isn’t What It Used to Be (2014)
There are a ton of great ideas in Vivaldi's user interface. And it's built on Chrome, so you still get all the standards and extension compatibility. They regularly add clever new features that materially improve tab management and navigation. I'm looking forward to making it my default browser at some point in the future when they add sync for bookmarks etc.
It's also possible (and, I would argue, more probable) that they fail because for any sedentary peoples, the accumulation of material wealth is inevitable, and such accumulation is unequal. Thus, some degree of "capitalist individualism" grows organically out of sedentary societies.

The only successful societies with anything resembling fully-shared ownership are those which can't accumulate much of anything.

I say this not to defend ultra-liberal capitalism or anything, but rather to point out that utopias tend to be very artificial (and therefore short-lived) constructs.
This is a library that seems to do something a lot like what lots of other libraries do, except this one costs hundreds of dollars per developer, comes with only a year of support, and has many obvious problems with its licence such as being revocable, being ambiguous about jurisdiction, and literally having the word "DRAFT" stuck at the top of the first page.
I always liked orthodox and unorthodox. I think there are lessons when Sun Tzu discusses cheng/chi that are somewhat orthogonal to the OODA loop, but I see the stated interpretation by porpoisemonkey as a "subset". Lulling your opponent into complacence with the obvious and baiting him into a lethal trap absolutely fits the definition of destroying their perception of reality, but isn't the only way.

Your opponent becoming so paralyzed by the fear of not knowing what you will do next and thus doing nothing also fits the OODA loop in a completely different way, but isn't really cheng/chi. This is also touched on in Art of War, so it's not like they are conflicting ideas.
It's going to be extremely location-dependent. Your best bet is to fill a niche that nobody else has gone after because it doesn't fit their national standards.

Remote location, or otherwise protected against a national moving in?

No current competitors, or only low-quality competition?

But with enough latent demand?

If all three of those are yes, you might be able to make it work.

You'll need to think about fiber or wireless, and if you're doing wireless, how to get fiber to your distribution points. Licenses: right-of-way for fiber, radio operation for wireless.

IPv4 space? Good luck.

IPv6 space? Much easier, but people still won't find it compelling all by itself. (On the other hand, starting an ISP today means you can probably do all your internal work on IPv6. Do so!

Can you get two independent high-bandwidth connections? If not, can your customers stand the inevitable downtime?

What level of reliability are you aiming for, anyway?

What services are you going to provide besides bandwidth, IP addressing, routing, NTP and DNS?

Are you prepared for customer service? Business or residential? Either way, you will eventually have to listen to someone on the phone telling you that they deleted the internet.
I was blown away by the customizability, I used Firefox with a split tab extension, yet this has native support.
Strange they mention supporting 521 here [1], but on the compare page they only list 384?

[1] https://www.yubico.com/2016/05/secure-hardware-vs-open-sourc...

Edit: looking at the PIV tools manual they provide; I can see no mention of the tool supporting 521, it fails when I try to generate a key.

Looking through the .h files, I do see mentions of p521 ;)

int BN_nist_mod_192(BIGNUM *r, const BIGNUM *a, const BIGNUM *p, BN_CTX *ctx);
int BN_nist_mod_224(BIGNUM *r, const BIGNUM *a, const BIGNUM *p, BN_CTX *ctx);
int BN_nist_mod_256(BIGNUM *r, const BIGNUM *a, const BIGNUM *p, BN_CTX *ctx);
int BN_nist_mod_384(BIGNUM *r, const BIGNUM *a, const BIGNUM *p, BN_CTX *ctx);
int BN_nist_mod_521(BIGNUM *r, const BIGNUM *a, const BIGNUM *p, BN_CTX *ctx);
I wonder if this can time-sync wifi and ethernet devices together, because I feel like a lot of installations will have a mix.
that seems like a strange analogy. they serve many markets (India is a major one for example). there is nothing which forbids them from serving alcohol to non-Muslim travelers.
> FB wasn't even monetizing their mobile products when they went public

Back then they were saying FB couldn't do it and there wasn't enough screen real estate on a phone to make it meaningful. Google had the previous years good but it was about to end. Their ad platform at the time was also a failure and they were bleeding money. Lots of it rhymes with Snap, there are lots of parallels.
The hands down best reason to use react-redux is because if you use `mapStateToProps` and `mapDispatchToProps` you can keep your connected components 100% dumb (I like to export both the dumb version and the connected as the default). This way, when using something like react storybooks or and in your tests you don't have to mock your whole the redux world.
Firstly:
https://www.statista.com/statistics/264810/number-of-monthly...
Facebook's MAU is now at 1.7B users (That's almost 1 out of 4 people on the planet!) and is growing at about 10% per year.

Secondly:
Saying that Facebook's popularity will rise and fall in a similar trend that Myspace did is like saying Google's popularity would rise and fall like Ask Jeeves's.

Thirdly:
Facebook owns Instagram and WhatsApp

Conclusion:
Big brother Zuck is here to stay!
The ability to do useful things without the GC would be nice.
sorry for repeating myself, but I think they will have a much harder time and will do worse than twitter. At least with twitter you can identify an interest graph. Snapchat is similar in a sense but monetizing stories is a tough sell, because there is no real contextual information on what your friends are actually creating stories about. I just don't see people following brands on snapchat like they do on twitter. Snaps filters I will say are effective, but just how effective we'll see.

Snapchat's entire premise is based on ephemerality so even if someone were to advertise or brand, it goes away and is done. You can rewatch stories but even that is limited. Like twitter I don't see this product crossing over to a more general use of the population like facebook. Even expansion overseas will be hard because there are already major messaging platforms that have a strong foothold. Line, whatsapp, Snow ( snapchat clone), wechat and kikao. I also can't see them really expanding beyond the US.