skysight-inc/HackerNews huggingface dataset:
The importance is that the VC funding allows the service to offer its service free of charge to users until it can scale enough to either land a cushy acquisition based on connections the VC firm has or (much more rarely) monetize via a method that isn't viable until they've already scaled up.

In either case, you are not the customer, since you are not paying them. In the absence of VC funding, however, companies are much more likely to be forced to charge their users, meaning they have a more vested interest in customer service.
I hear you. At the beginning of my career, I always used to be the most offensive person in the room - and I could afford to be, because nobody cared what I thought. Nowadays there are always five people in the room who are more offensive than me, but that won't stop them from complaining if the big bad ogre (me) hurts their feelings. Kids nowadays. ;)
What we believe will end up doing is making Dragdis free forever, but supporting with ads or you will be able to pay a little premium and get Dragdis without the ads.

We want to give this to as much people as possible. That's why we went the ads way.

Thanks!
It's one of those undocumented obvious features - been there for a while...:)
I've lost several domains that simply got deleted from my account. Every time I tried contacting them about the subject they refused to answer.
Go is still a very young language and will probably subject to a lot of changes, especially for optimization. No big industry builds apps using Go, in the same way that no big industry build app using Laravel. They prefer for instance CodeIgniter, which has been combat-tested and is more mature.
I don't know how you came to this conclusion.

There are instagram accounts kathleen (displayed name Kathleen) and ___kathleen (displayed name kathleen).
Is there evidence that misleading indentation had a role in enabling the bug?

You can make a typo, you can duplicate a line, you can misindent a line, you can put a brace in the wrong spot. I believe different languages simply trade forms of potential mistakes for other forms. Ultimately no language will magically fix or make bad code known; it has to be detected somehow. Tests, static analysis, manual review, whatever.
Exactly. And these things can be enforced by style checkers, so you don't even need to have good habits.
Ha ha :) Thanks for support! :)

Integrations are coming. I know I keep repeating that, but integrations are truly our main focus from now on and for the future :)

Thanks again!
Wall of text! Anyone know how it differs from normal Fedora?
Sorry not at the moment :/
It's a tricky thing: Suppose you volunteer to run the phones for your local NPR funding drive. While you're there, they provide you with breakfast. Will it make our country better to tax the free food?

Food at work makes work more efficient. It may be a perk, but it's less portable than getting paid the street value of whatever food is provided. You can't take it with you, or use that food to earn interest, nor can you get it if you're not at work. You don't get to pick what food gets served or how much it costs, nor can you refuse it in lieu of cash.

There are valid arguments for taxing perks, but it's a tricky issue.
It's not StrongLoop marketing. I wrote the article and also haven't heard about your modules. I try to stay up to date with NPM (running http://npmawesome.com/) and unfortunately completely missed your work :(
Thanks for this!

Just nabbed https://github.com/stephen was inactive since 2008.
I like this train of thought.

I doubt they can make a good, commercially viable phone straight away. If they just could release a backbone and a starter set of modules at a nexus7-ish price point, that might get things going. They need to get this thing into some people's hands (especially potential module developers) and see what they can do with it.

Also, selling this as a way of long lived phone sounds like a terrible USB. I would put 'easily repairable' above it but the real value is the potential module ecosystem. Without that it's just some form of cheaper and that's a hard promise to keep.

Phone is a relatively small part of what smartphones are. Is the phone a module here? It would be interesting to know what all the starter set modules do.

It's disappointed to see all the cynicism on this thread. Commercial viability aside (come on, who knows), this is a cool fun project with interesting possibilities for making hardware innovation accessible.
I recently learned that SigmaVPN uses NaCl on Android, if anyone needs it.

https://play.google.com/store/apps/details?id=com.frozenrive...

It seems based on QuickTun, which is where the NaCl implementation comes from:

http://wiki.ucis.nl/QuickTun
I agree that it's totally shocking that Apple did not have an example of each kind of bad cert. Even a rudimentary unit test of this code would have caught this bug. I bet they do now.
> This is another example of the emerging electronic class system. Those who are members of the Silicon Valley clique are privileged to take what they want from those who are not.

There's nothing new about this "class system." Instagram's servers are the property of Instagram (and therefore Facebook), so they can do essentially anything they like with them, including things that make them look really bad from the outside like this incident (assuming everything happened as was implied).
Few languages that have copied their if statement from C have adopted C's exact syntax. Most, if not all, make the braces mandatory. It is a flaw in the language that it permits such a dangerous style.
Yes, but they didn't say they would do that, they said they would remove them - although the ToS probably doesn't give the offended customer any recourse, and the fact that the service is free means they have no leverage to challenge the ToS in court. The lesson here is that if you're not very busy and you have a name someone else wants, it can be taken away from you.
So everything is in the cloud. You can access it from whatever device on Dragdis.com

Saving stuff locally will be possible soon as we are working on Dropbox and Gdrive integrations :)

Thanks!
Dreamweaver 2.0
The more I read about the case, the less happy I am about having donated to Levison.

Pages 8-12 of this decision convey a narrative about Levison's handling of the FBI requests. In particular, they detail an escalation that Levison himself provoked:

* The DOJ reached out demanding metadata regarding (presumably, and let's just stipulate) Snowden's use of Lavabit.

* Levison rejected the request, on the auspices that Snowden had enabled the "storage encryption" feature of Lavabit.

Here it's worth knowing that Levison had previously complied with similarly narrow requests.

* Levison confirmed to the DOJ that he had the ability to circumvent the storage encryption.

* The DOJ responded to that concession by doing exactly what anyone would have expected them to do: they escalated their demand to include the decrypted Snowden data.

* The DOJ spent eleven days trying to meet with Levison, who stonewalled them; Levison "ignored the FBI’s repeated requests to confer".

* Only upon being threatened with a contempt citation did Levison actually enter a productive discussion with the DOJ.

* Four days after being threatened with contempt, Levison presented the DOJ with a proposal to charge the DOJ $2000 to design and implement his own pen/trap system which would provide data to the DOJ only at the conclusion of the order's time window, with timely updates being provided only at Levison's discretion and only with an additional charge attached.

* Only after this sequence of events does DOJ demand the TLS keys that would have compromised all Lavabit users activities.

Levison's attorneys and the DOJ litigated the question of whether the pen/trap order required him to cough up his TLS keys. But that only happened after Levison did his best to deter the DOJ from collecting information about Snowden. As evidence for this: the DOJ eventually did install a pen/trap device of some sort, without the TLS keys, and attempted to use it to collect evidence. Had Levison complied with the DOJ productively from the beginning, he probably could have worked with them to produce the information they required without compromising the rest of his users.

I already had a problem with Lavabit as an inept and dangerous privacy solution (you can obviously see that it was; Levison was trivially able to subvert the privacy of all of his users, and was eventually forced to do so).

But almost as bad as that is his handling of the legal situation here. Read the language of the decision carefully and you'll see that had Levison simply began this process with his proposal, minus the time lag problem, but perhaps even including the price tag, he might have had that solution accepted! Instead, he seems to have seized an opportunity to poke a giant bear with a stick. The bear then ate him and his users.

Later: Also, bad facts make bad law. Great to see that we now have more case law establishing that pen/trap orders demand TLS keys.
Although I doubt this story is particularly true, if the reduction in pay is roughly equivalent to the cost of food otherwise, employer-provided food is likely still a net-benefit (if you often bring food from home this decreases for married couples, strongly decreases with children). If the food is provided to you at no cost but offsetting some salary, then you're at least preventing the government from double-dipping your taxes for those meals; you wont pay the sales tax on the food.
You don't really know that. The brace could've ended up between the two lines and you have the same bug. Been there, done that.
Alternatively use a whitespace sensitive language. Defining how to handle tab vs space is irritating, but there are plenty of solutions to that.
yeah... :) http://dragd.is/iY2XH
I agree about the need for non-binary punishment, but it's nothing new to "this" generation. Computer cracking laws have been around for decades with the same life-altering draconian penalties. My point is the only way these things are going to actually change is for masses of people to play chicken with the establishment, and see if they're really willing to destroy so many people's lives rather than just a few isolated cases.
Perhaps you could you all the income you save from not having to buy lunch to pay said taxes.
Paleographers have a whole catalog of scribal errors, which can be useful when trying to reconstruct a text from conflicting extant copies. Perhaps it would be helpful to compile such a list of common programming errors, and consider that list when designing a new language. It would include "scribal" errors like Apple's goto or = vs ==, and also low-level logical errors. It seems like this could make a fun paper for any CS grad students out there.
I don't think anyone here is "against coding" - we're just speeding up repetitive tasks that take up way too much time and manual labor to complete. People weren't "against" writing Bezier math or doing typesetting manually - it just became much more efficient to do it visually.

The same thing happened with assemblers, compilers, etc, so it's nothing new - abstraction marches on.
Chris Anderson on drones and open source hardware
Jenkins is invaluable. However, it is also large and crufty. I love it for running builds and so on on the development side of the fence, but i would strongly prefer something simpler and saner on the operations side.
Facebook's friend problem
For this, you don't need a style guide, but a static code analysis tool. This specific error causes unreachable lines and has suspicious indentation.

In my project, that could could have never gotten into production, because the tools would have stopped us, even without a single unit tests.
I think Cryptocat illustrates and affirms the points I'm making about amateur cryptography, and doesn't rebut them.
The Derek Yang that owns @derek is also a Facebook employee (I believe).

[1] www.linkedin.com/in/dereklyang‎
The reality is very few projects will ever be approved in every field with "I don't know?" as the answer to "How much will it cost?"

Estimation is by far the trickiest project management tool. 2 identical projects with identical caliber teams will come up with very different results. All you can do is use the estimate for a very imprecise first guess to get things started.

Of course very little is known for sure early on. The scope isn't final. The tolerated risks aren't final. The project team isn't final. The target quality level isn't final.

So what can you do? Admit that these are in flux, and be proactive about managing them. "Ok, now that we know more, it looks like things are more expensive. Do we fix the cost and reduce the scope, or fix the scope to reduce the cost? If hitting the budget is the most important thing, should we preemptively cut scope?" These are the way discussions have to be managed.
Are you curious about using them or implementing them? What level of detail are you looking for?
Would gym "membership" at a company owned and operated gym be taxed? What about "membership" to other company owned and operated 'perks', such as access to a woodworking shop at a tech company?
I don't see modularity/repairability on that list either, for what it's worth.

I think it would be really foolish to believe that aesthetics don't play a huge role in smartphone purchasing decisions.
> but he's disingenuous in saying that random line duplication can't cause catastrophic problems in Eiffel.

I think you're referring to this part of the article:

With such a modern language design, the Apple bug could not
have arisen. A duplicated line is either:
- A keyword such as end, immediately caught as a syntax
error.
- An actual instruction such as an assignment, whose
duplication causes either no effect or an effect limited to
the particular case covered by the branch, rather than
catastrophically disrupting all cases, as in the Apple bug.

To be fair, he's not saying that it can't cause catastrophic problems in Eiffel. In fact, he's not strictly talking about Eiffel but about better constructed languages. He is saying that while it could be cotastrophic, that it wouldn't be nearly as bad as what happened here since it'd be contained to one branch of execution rather than exposed to all branches of execution.
Quick note about client retry, I highly suggest some type of guard on side effecting operations, either rejecting duplicate transaction ids (generated by the client or retrieved from the server before the side effecting operation) or returning the previous result if the transaction id was recently processed.

Obviously being stateful and correctly routing the request across shards becomes harder and can hurt this scale out solution. It also depends on the functionality of the request, for example an update of the same data may not cause any damage, but a double submit of an order could be.

https://en.wikipedia.org/wiki/Idempotence#Computer_science_m...
source? genuinely curious if those words are written somewhere.

IRS Publication 525 -- "In most cases, you must include in gross income everything you receive in payment for personal services. In addition to wages, salaries, commissions, fees, and tips, this includes other forms of compensation such as fringe benefits and stock options."

It would seem to me that the IRS should tax income, specifically income that I can use to pay taxes (or which can reasonably and reliably be converted into something that
I can use to pay taxes).

I'd love to send 40% of last week's corporate-paid lunch to the IRS but my guess is they wouldn't accept it.

You can't send the IRS 40% of a fully paid vacation to Hawaii, including use of the corporate jet either. Should companies be able to give their employees such vacations without out the employee being required to pay taxes on the value?

Think about what incentives that would create -- individuals could evade taxes altogether by simply negotiating with their employer to provide whatever goods and services they wished to consume rather than money. And because such benefits wouldn't make up part of the AGI the individual would also be eligible for government social programs.
> This is why I never ever let the interns not use braces.

And hopefully nobody else either.

Beware the "experienced" developer who skips braces "because it's more elegant" or "because it's unnecessary typing".
I think you're just conveniently forgetting all the languages that didn't go anywhere. https://en.wikipedia.org/wiki/Timeline_of_programming_langua...
Node.js is Human
Intro to cart abandonment recovery email campaigns
The posts above you are talking about the Chromebook Pixel, which had a release price of $1299 (similar to MacBooks) but inferior specs.
Thanks for the heads-up. I flagged the post too.
Note that this opinion rests almost entirely on the fact that Lavabit/Levinson failed to raise any of his legal arguments before the trial court. Any lawyer can tell you that, if you want a court of appeals to consider a legal issue, you have to raise it before the lower court first to give them a chance to rule and to develop a record for the court of appeals to review. I'm sure there are those out there who will want to make this into a major privacy ruling, but it just isn't.
At least according to the quoted policy, it appears being tagged by others or logging in and viewing photos doesn't actually count as activity at all. Which is a really shit policy.
A major limitation of using try/catch is that V8 will DEOPT your function call, which can be a 5-10x performance hit (to the current closure). The best way to avoid this is with a silly hack:

function trycatchit(fn, that, args) {
try {
return fn.apply(that, args)
} catch(e) {
return e
}
}

var value = trycatchit(fn, null, 'someValue')
if (value instanceof Error) {
...
}

Really though, you should just let co or whatever generator library you're using catch the error and rethrow it (or pass it to a callback) or be mindful to minimize your error handling.

[1] https://github.com/CrabDude/trycatch/blob/master/lib/trycatc...
That's fine for email, but services like Instagram thrive on literal word of mouth with people saying it over the phone or over TV or radio. Watch some TV and see how many adverts include the Facebook logo or a hashtag (implying Twitter, although a competitor could steal that market overnight). It's not just about clickability, it's also about having an identity easy enough for people to remember to check out. 'I haven't looked at Joe_Blow's Instagram in a while' is an easy thought to form, having to perform a search to find the random string of the actual account name, which is unrecognizable for most people if the search returns more than one result - that's a pain.
You should write a blog post about this. There are a lot of parallel efforts going on to bring sanity to async errors in JS, and it would be great to see what the outcome of cross-pollinating these ideas would be.
I would argue they make the code less readable, merely because they are not the original names. I certainly had no idea what "set -o errexit" did—I've never ever seen it in the wild and it doesn't sound familiar to me at all (and I've done a lot of shell scripting).

But "set -e"? Oh yeah, I use that all the time. It also has the benefit of being the same name as the command line option. That's especially useful for "set -x" which I use all the time when debugging bash, especially in the form "bash -x myscript".

I would never say "tar --extract --file" either–it's just not done.
Actually (edited), if you use @whatever in your comment, it should resolve appropriately for me. Just put a name:link pair to whatever account in your about text.
Land Rover’s Transparent Bonnet Is Part Of A ‘New Age Of Discovery’
Really, really good points, especially about "guy" and its corresponding lack of a casual, female equivalent. Unfortunately, "girl" conveys a sort of latent, sexist diminution, such that the phrase "Product Girl" is dismissive. As a man, I'd cringe if another man described a female coworker as "Product Girl," in much the same way I cringed in the Entertainment business whenever a female creative exec was referred to as "Development Girl" (or its even more diminutive form, "D-Girl").

"Gal" feels hokey and anachronistic to me, and I'm sure it falls tinny on a lot of this readership's ears. For whatever it's worth, though, I've been noticing that the word is making a steady comeback. I have no personal n-gram analyzer in my daily life (and I wish I did!), but I could swear I have heard "gal" more times in the last two years than I had in the preceding 20. I've heard it from men (and the first time I did, it struck me as weird and Mad Men-esque), and I've heard it from women (most typically, women currently in their late '20s to mid '30s).

In a weird way, I'm almost rooting for it. Our language needs a casual term for women that is not latently diminutive and, thus, a micro-aggressive power play the way "girl" often is (whether its user intends it to be or not).
Ha, I was thinking of the same thing. Who knows, maybe he's built for this kind of thing. On that note : if he can get a good night's sleep after all that caffeine, then I envy this man's constitution, which can absorb so much caffeine and still not reel from it! Poor me has to strictly follow a no-caffeine after 6 p.m. rule if I have to get any sleep. Actually, come to think of it, the only time I can handle coffee gracefully is right after I wake up from sleep.
Yeah, I do this too, though I try not to stay for more than two or three hours, and make sure I always have something in my cup. Fear of getting overcaffeinated drives me to other places.

I do think a shared promotional community between the coffee shops around here (Seattle) would be good, but most are doing pretty well so no one feels any pressure.
i actually came here to say pretty much the same thing. as a front end dev, i thought the site looked and functioned pretty well. if you can get someone to build that complex of a site with some "non-coding" tools, well done. my concern is that you've taken the problem of coding and replaced it with a new one. people who don't understand how the web works won't be able to build amazing beautiful sites with this product (ok, maybe some will, my guess is a low percentage). what you've done is create a better WYSIWYG, and we all know what WYSIWYGs get you: Geocities.

again, no knock on the site, it looks like it's really well done, i'm just not sure that a series of complex controls solves the problem of web development any better than just learning how to code yourself.
They may own their servers, but you also entered a deal with them (as miniscule as it may be), which means that this applies:

http://en.wikipedia.org/wiki/Good_faith_(law)

This (if it happened as described) would be a violation of this.
How do you know how much I would have spent on lunch? Or if I would have spent anything at all?