skysight-inc/HackerNews huggingface dataset:
When you're IO or network / database bound, then, you won't notice.

When you're just CPU bound without having to cope with lots of memory transfer / throughput, then you won't notice.

Without a doubt, there are many apps that don't need this pure speed, but for specialist apps and even general apps on the desktop (compare firefox to chrome and safari for example), you can notice the difference quite distinctly.

In my experience writing high performance applications for the VFX industry, where both memory performance AND memory compactness (so you can fit as much in memory as possible) are important, when profiling applications, I've found that maybe 70% of the time it's the memory allocation / deallocation that's the actual bottleneck, not actual calculations.
Being able to separate stuff into separate allocators based on different use cases adds complexity, but gives huge benefits when you're memory throughput constrained.
I liked this, a pretty cool origin of a now common phrase we use. I liken it to the origin of the term Computer, the person who would compute the result of some mathematical function...
The Best Team Chat App for Your Company
Cool. Just in time for the end of free AppFog.
So can you confirm that specifically:

a) There is no list of accounts that is protected from scrutiny?

b) There is no group of accounts that is watched very closely for violation of terms?

c) That bans happen almost always shortly before a payout would be due?

The description of the latest known policy in place reads as it is carefully tweaked to be defensible even in a court of law, so even if the "leak" is true, I am not sure if a class action lawsuit has a chance.

To skew the outcome in Google's favour is basically guaranteed if bonuses and goals drive the team members to interpret the procedures in a way that a impartial observer might interpret as unfair.

(using a throwaway account for whistle blowing does make sense, and not necessarily reduces credibility)
I am at an internet of things meetup at Google Tel Aviv and just saw a first hand demo of the sensor. I can guarantee this is real and working.
Lack of empathy is usually when one is a sociopath not suffering from schizophrenia or autism.

The problem is some people on the autism or schizophrenia spectrums cannot express themselves, but they have empathy and compassion, but are misunderstood by society and the news media. They just lack social skills and people skills, but can be taught them by books and therapy. Most are even nonviolent and very good people if only they were understood.

Sort of like Sherlock Holmes, only Doctor Watson seemed to be able to understand him, everyone else misunderstood him and didn't want anything to do with him because they thought he was a mean jerk with no empathy. He had empathy but got rid of distractions to focus on solving crimes to save humanity from evils like Professor Moriarty and his gangs of sociopaths.
The $999 price (now $899) was always for the 4GB model. That did not change. Your initial assumption was wrong.
There are no mainstream alternatives when you need a declarative, extensible mark-up. JSON doesn't fit this bill, unfortunately.
W3C Java Validators
You underestimate the technical competence of MIT's gender studies, anthropology, and theater students :-)
Collections: How we increased cash flow by 111%
Do you have any financial accounts (such as Fidelity in the US) set up using this address? How do you handle situations when their "compliance" department says "we have flagged your address as being a mailbox-type-service" and demand a physical address? Do you just give your physical address instead?
> Let's take as an example dependency injection. The genesis for DI was to facilitate the testing of objects that are dependent on objects that are not easily constructed, such as DAOs.

Really? Because I've always seen DI advocated for loose coupling, with testability just coming along for the ride the way it does in general with loose coupling, I've rarely seen it advocated for testability independently of the broader architectural motivation for loose coupling.
Then let the post office charge enough to replace the advertising revenue.

I also suspect your wrong in saying that advertisers will completely give up if the number of deliverable boxes shrink. I mean, sure, they will want to pay proportionally less, but I suspect post office revenue from advertisers would decline smoothly with the rise in revenue from the paid opt-outs, assuming you got the price right.

My understanding is that fourth-class "to resident" mail is usually targeted at the most price sensitive customers; people for whom clipping coupons is often a good use of time. Exactly the people who are unlikely to pay money to sort their mailbox.

Most of the higher-end mail, like those goddamn pre-approval notices from AmEx, are lovingly personalized, and ship out 'pre-sorted first class' or something. I'm only talking about opting out of the fourth class "penny saver" type junk.
I have wanted this since Docker was announced last year. In my eyes the biggest gain of Docker for development over VMs is boot time. Now I can turn all my Vagrant VBoxes to Docker containers, and work much faster. Thanks to all the maintainers for the hard work.
Right. However, in many DI-heavy apps I've seen, nobody ever makes use of that flexibility. Otherwise it's just extra, unnecessary complexity, sitting around in verbose XML files and annotations, causing code clutter.

These are "enterprise" Java apps with Spring, etc.
> Technology can't be "driven" by people who aren't skilled enough to evaluate and prioritize the work.

And what makes engineers the ones who are skilled enough to evaluate and prioritize the work? They understand the technology side, but do they understand what customers want and need? What will sell and market well? How a product will fit into the company's product lineup? What the competitors are doing? The problems customers are calling support about? Etc.

There are many competing priorities, and I don't think any one person or role can know enough to be able to accurately prioritize what work is most important. You need a team that works well, and members of that team need to be able to clearly explain the benefits and costs of doing or deferring any important piece of work.

As an engineer, we need to know those costs/benefits and how they trade-off against other tasks to make the right decision of which one to do first. That doesn't change if you're the one with the final say, so why does it change when you have to communicate it to a PM so they can weigh it against the other work to be done?

In the OP, the manager is doing the cost/benefit analysis. If Cindy and Bob were great engineers, they would have done a similar analysis themselves.
This is (to me) the most interesting thing I've seen Square do since they launched. It's a bit pricey, but there are lots of great examples of pickup/takeout working well -- chipotle, for one. If smaller stores could do this easily, I'd be a lot more likely to order from them, especially if it's a larger/group order where spending the time on the phone is a pain (and often incorrect).

I don't think the economics of a lot of the delivery services work, especially for single-person or other small orders; here, it's pure cost savings. The 8% cut is ...ambitious, but it might make sense, and they can always drop it to something more reasonable like 5%.
While the story is fake, it still very well illustrates how powerless people are against Google.
What can I do with this that I cannot do with the command line?

My use of brew is rudimentary, but I only ever use four brew commands:

brew install
brew update
brew upgrade
brew uninstall

If this helps make brew more popular, then I think it is a great addition. It seems I am not the target audience, but hopefully one exists!
> The idea that a layman is going to reasonably protect their bitcoin assets is silly.

Take wallet.

Encrypt wallet.

Put sufficiently complex password on wallet (ie, no dictionary attacks).

Wow, you suddenly have a bank. Feel free to back up that file all you want, hell, if your password is solid you can publish it publically. I wouldn't, since you don't have to, but you still won't password crack it any time soon.
Google acquires a taste for Power – IBM's processors, that is
Hence on top of command line applications. The power and flexibility are still there for people who want them, but so are the GUIs.
Google's Radical Plan To Change Android
"In most web applications the "bottle-neck" is going to be DOM interaction. It is very unlikely that you will notice a performance hit at all."

uhhh, 2 wrongs don't make it right?

"It is very unlikely that you will notice a performance hit at all."

Until you do..

--

I could never justify using this stuff at work. It's inefficient, unfamiliar to most JS developers and even if it did pass a peer review, nobody else would actually want to maintain it.
Everybody is afraid of interviewing.

I've been rattled by every job interview I've had. That includes interviews for roles that I'd been courted for. It includes interviews for jobs I didn't even want, where I was interviewing mostly because a friend had asked me to. One of those interviews was for a company I actively disliked and would under no circumstance work for. I didn't sleep the night before! I did a multicast streaming media company in the late 90s and owned the router; later, I interviewed at a friend's company, got asked how to implement Towers of Hanoi without recursion, and for the rest of the day forgot everything I knew about routing protocols --- despite having spent the preceding two years doing nothing but implementing them.

Job interviews suck. They're hostile processes that involve complete strangers not just sitting in judgement of you, but also working under the delusion that their job is to break you so they can avoid hiring "B players".

I basically interview people for a living now and pay pretty close attention to this, and have come to the following conclusion: there is zero correlation between how people comport themselves in job interviews and their ability to do a job.

My best advice is, know the stuff you know. If you want to bone up on algorithms and data structures, don't cram. Implement them in your most comfortable language and watch them work, and go to the interview knowing not that you can recite them from memory, but that push-to-shove you can in fact throw down and get them working. Then just answer questions honestly.

The hardest interviews you take might be for the worst, most dysfunctional teams; a mean (or even just wicked) streak in interviewing candidates is a sign of broken teams, not weak candidates.

Good luck!
Sorry I cannot reply to every thread.

My condolences to everyone who had a family member or friend die of complications caused by schizophrenia or some other mental illness. I myself have schizoaffective disorder since 2001 which is like schizophrenia and bipolar mixed together and less than 1% of the population gets it and it is very rare and misunderstood.

I have lost friends I worked with and went to high school with to mental illnesses and they killed themselves. I've been suicidal myself in my life in the past. But I vowed I would not try suicide ever again and work to improve myself so that one day I can return to work and earning a living.

You have my deepest sympathies, empathy, compassion, and love. I really care about mentally ill people and their families and friends, even ones that passed on.
We'll have to agree to disagree on this. I think the severality and pre-emption aspects of this case are also very different. In a nutshell (and quoting from the judgment):

Subscribers can upload...material onto the bulletin board so that any other subscriber, by accessing their computer, can see that material.

To me that's obviously distribution because a) multiple downloaders had access to uploaded material (severality), and b) when a subscriber logged into the BBS, the copyrighted material was already there, listed as available for download (pre-emption).

What I think is different about this new service is that (as far as I can tell) if I use it to generate printed copies of, say, a New Yorker article and 3 Techcrunch articles, the resulting document is sent only to me, is not offered for download or printing to others, and is not retained on the server after the hard copy has been printed and mailed out. Furthermore, I can't select these copyrighted works on the site itself, but must submit URLs of my own choice. So what's being offered here is a reformatting and printing service for an individual only. My use of the service as described above would not make the content in question accessible to you.

Now, if I collected 50 articles into a 'magazine' othat reflected my interests, and that was made available to other customers, then it would certainly be a case of distribution and blatant copyright infringement.

Incidentally, although this situation has superficial similarities to the Aereo case before the Supreme Court at present, I think a key difference is that Aereo pre-emptively stores broadcasted content for later download, and likewise has buolt an infrastructure of receiving antennae which they essentially rent out to customers. In my view Aereo is relying on a flawed post-hoc rationalization of their action, whereas personalpaper.me (as far as I know) didn't hit up any URL until someone requested it to be added to a print queue.
You invert the dependency. The abstraction is over the things that the higher level code needs. I don't need to know about query types, indexes etc. I need some business answer (all log records between x/y, a user matching username x), I program to an interface that provides all the answers necessary for the high level code.

The implementation of that interface is data store aware and implements the interface in the most effective way possible for the data store holding the things I'm interested in.
In the end, it's just business. Heroku is owned by Salesforce.com and they want to make more money.

The Ruby community is for Ruby. Period. A company can't dictate their own policies based on ideas of just one community.
Dokku might help you out with the repo-per-site-on-nginx plan!
What you call the person who graduated dead last in med school?

"Doctor".
Depending on the situation and the relationship you have with Jim, saying "I'm not in a position to ask for that right now. Happy to help in other ways." might work.
I particularly enjoyed the one about the rare calendar. You'd think the act of scratching off a month from last year and replacing it with one from this year would be a Clue(TM) that this is not that rare an event....
Why would they take all of your earnings for one month instead of 1/3rd to infinity?

That's just dumb.

That said, I have noticed AdSense policy enforcement ratcheted up, but protecting the advertisers is in everybody's best long term interests.

My experience with AdSense policy enforcers was fair.

I preferred having ad units that encouraged unintentional clicking,
I made more money like that,
but I understand why they made me change it.

Having made my ads less blended to the site, I have had no issues since.
It is a positive sentiment that even PHP haters can agree to. Seems like a very carefully crafted sentiment to endear themselves to PHP devs without alienating tribalistic Python/Ruby/etc devs.

My bias: 80% hate, 18% apathy, and 2% curiosity into what facebook is doing with the language.
Hi,

Your story is really nice and your motivation is well stated in your blog post: "...the fragmented condition and outdated technologies of the commercial real estate industry continued to frustrate me.....I decided to find a better solution"

I feel your story stands out with that one sentence - it would have been better to lead with that. I also feel the emphasis on your age and role as a single parent takes away from your central motivation when you lead with those points.

My 0.0000424 btc! Good luck with your startup
> The engineering world would be a much better place if more people built beautiful, easy to use GUIs on top of the confusing command line apps we all rely on.

I'd correct that to:

The engineering world would be a much better place if more people built beautiful, easy to use command line apps

It can be done, although it takes a lot of effort to do well- and a lot of the developers who write CLIs* have very few notions of HCI design. As a result the vast majority of CLIs are inspired from programs that are decades old, and in which no thought was given to the interface, thus perpetuating the cycle.

When well executed, a CLI is insanely superior to a GUI on many fronts (with a few exceptions, naturally, such as image/video editing), and more respectful of the users. It is much more friendly to users with vision or motor impairments: any font and any color scheme can be applied, any method of text input can be used, text readers behave in a much more predictable manner, etc. And of course it enables scripting to a level that GUIs just can't compare to.

Ideally you'd have a well designed CLI for the users who want it & scripting, and a well designed GUI - but let's face it, doing both is a huge drain of time. If you're going to do one, then a CLI is much, much preferable.

On the usability scale, there isn't "CLI apps" on one end and "GUI apps" on the other. Some GUIs are extremely usable, some aren't; some CLIs are extremely usable, some aren't.

I am a staunch supporter of the idea that while GUIs became mainstream and CLIs were relegated to a niche position, it should have been the opposite. But we had mediocre CLIs and decent GUIs, so it's only natural that it went that way. Great CLIs would have been preferable on many fronts.

Traditionally, the main argument against CLIs is the lack of discoverability that GUIs afford, which is a very valid point. That being said, most CLIs don't make an effort to enhance discoverability, which makes the argument still valid, but a little unfair.

Ultimately, I fully subscribe to Jeff Raskin's argument that if you're going to build a tool that users will use on a daily or weekly basis, then it's better to build something with a steep learning curve the first few hours which then results in an efficient and effective tool, rather than something that any newcomer can master within seconds but that will be tedious for extensive use.

GUIs that you can master in seconds belong in smartphone apps that you will use a handful of times and then delete a few weeks/months later (this isn't dismissive- if there's a market for it, then it's legitimate). Powerful CLIs that are a bit rough the first handful of hours but become extremely powerful tool belong in your browser, your email client, your text editor, your calendar, and so on: tools that you expect to use for years, if not your lifetime.

* : In this comment, by CLI I mean any form of program that runs solely in a command line, but that also includes highly interactive apps built with ncurses etc. There are very, very few command line apps that are solely "type a command, get an output" anymore.
iOS users can read about Firefox here: https://www.mozilla.org/en-US/firefox/desktop/

A bug to make this easier for iOS users filed here: https://bugzilla.mozilla.org/show_bug.cgi?id=1003379
I like the update, looks a lot better. It is the small details that keep me using Chrome's dev tools. For instance,

- why can't I drag and drop DOM elements in the inspector?

- Chrome's autocomplete seems smarter. If I go to edit a style and I type `li` Chrome gives me line-height, FF gives me lighting-color?

- I prefer the color highlight when you hover over DOM elements in the inspector, I can see the box model in Chrome but just a dotted outline in FF.

FF's tools do seem to get better and more robust with each update though.
http://phalconphp.com/

Fast and a really good documentation.
Creativity Must Be at the Center of Education | Big Think  GESF | Big Think
Docker Is a Symbol of the New Stack
So, to sum this up, you feel like the music industry is at least as sexist as the technology industry, and therefore the heat should be off the technology industry.
Oh please. Spare me from your GUI-MASTER-RACE bullshit. I can review a commit diff way faster in Tower than you ever could on the command-line even with your "customizations."

Also - "automate tasks and customize" your workflow to actually not do your job properly. Good job bro.
I'm responding to the original claim of unauthorized republication in the TC article. I'm not claiming that that's the beginning and end of copyright law.
> "so-called 'computer vision' algorithms that are little more than simple image processing"

Implementing any learning algorithm should be the absolute last resort. They're complicated, hard to generalize, and difficult to guarantee in the real world. Not that image processing is much better, but it's definitely more deterministic and predictable in its results. With any system geared toward a specific goal, your first approach should be to look at the simplest solutions (no matter how rudimentary they may be).

> It is tempting to dismiss sophisticated techniques because (a) they are hard to understand and (b) the task seems so easy to our own brain-equipped vision systems. But the fact is, most interesting computer vision problems (including this one) require sophisticated representations to achieve robustness and generality. In other words, any good solution will need an answer to the question "What is a Waldo?" that is better than "a 50x50 patch of pixels with red and white stripes".

Yes, of course. I'm using waldo as an example toward a problem I often see reading research papers, that is an overly complex system made to try to solve more than just the initial task. "What is a Waldo" is irrelevant to the task at hand. Identifying the best candidate for Waldo is the goal. In this situation simple correlation (or even more efficient correlation methods: MMCF, OTSDF, QCF, etc) can give good results (except on that all waldos page...damn that's even hard for a human) most of the time.

To make a euchre analogy - you don't pass on a biddable hand, and you don't waste your trump cards.
I'm just questioning whether its ethical for you to 'quickly nip them in the bid'. Most people reading this discuss have no idea what role Google plays in the day to to day operation of the advertising industry, and I think its improper for Google to be the first voice that they hear when they're exposed to accusations like this.

This shouldn't need to be nipped in the bud by a google spokesperson. The only way you're going to do that in a legitimate way is if a third party comes in to investigate it.

I doubt thats going to happen, but I think this accusation is not obviously impossible, and because of that, if the consensus becomes "no, google would never do this", I don't want it to be because of a whitewashing effort by google. I want it to be because no one has any reason to believe this is actually the case.
> And that is objectionable because of putting too much of a burden on people writing controller logic, because of separation of concerns, etc.

No, the controller needs to be aware of a method of creating new services. Depending on the specific language and other constraints, that might be a factory function passed into the controller's constructor, a factory object passed into the controller's constructor, a refernce to a service locator object, or some other mechanism. Specific direct knowledge of the DAO class is generally neither necessary nor desirable.
Have you tried the Nightly builds of pentadactyl? Those usually work upto and including Fx30, and usually are updated to work with whatever is on Aurora.
Does Vagrant do any setup to allow you to run Docker within the dev container, say if you're working on a project that you wish to ship as a Docker container image?
Why are you getting your jimmies rustled for no reason? Stop getting offended over nothing. They didn't say "PHP developers are makers at heart. No one else is."
Crashes on launch on 10.8.5. Great work folks!