1,629 karma · joined February 14, 2011
> Have feedback on this post? Let know on Twitter.
Not everyone uses Twitter. It would be awesome to give feedback using the one account I'm guaranteed to have: a GitHub account. Otherwise I have to ask my question on HN...
Self-hosted blogging still has a place in this ecosystem!
You mean the same core developers of io.js, who clearly are shipping now that Joyent is out of the loop?
In other words, pot for elitists. It's not enough to just open a different kind of store, the marketing has to establish a hierarchy. And people will eat it up too, who can resist the opportunity to signal that you're better than some other group of people?
It already can. btrfs sub snap does snapshots (and they work the same way), btrfs send/receive do the diffs, supports lzo/zlib compression and deduplication
That's a really outdated meme. CPAN is small, pretty much every language you hear about regularly has a larger package space than CPAN. Even Go's package space is bigger than CPAN's. JS and Java each have package spaces roughly 3x CPAN's size.
I have never used fugitive, but I can't imagine being unhappy with Magit? What makes fugitive so much better?
More police departments are outfitting policemen with wearable cameras that tape what officers see as they do their job, providing a record in the aftermath of incidents like the one in Ferguson, Mo., where a policeman shot and killed an unarmed black teen.
The cameras have shown promise in reducing incidents involving use of force as well as citizen complaints, according to new studies. Worn on officers' lapels, glasses or hats, the cameras can document a more definitive version of police work.
"If you look at what's happening in Ferguson—basically you have two entirely different versions of events," said Michael White, a professor of criminology at Arizona State University. "If that officer was wearing a body-worn camera we could just go to the tape."
Dr. White, who has studied the use of the cameras, said "there's tremendous potential to head off these types of incidents from blowing up afterwards."
In a press conference earlier this week, Thomas Jackson, chief of the Ferguson police department, said the department had only recently been budgeted $5,000 to buy a limited number of dashboard cameras and body cameras for officers. Mr. Jackson said the department had not yet put them into use at the time of the shooting but plans on incorporating them into vehicles and on officers soon.
In the Southern California city of Rialto, the number of citizen complaints against police dropped from 24 to 3 in the first year that the patrol officers began wearing cameras in 2012. Use-of-force incidents plummeted from 61 to 25 during the same period.
Tony Farrar, Rialto's chief of police said, "When you talk about putting a camera on somebody, human nature is going to dictate that you're going mind your p's and q's and you're going to be on the best behavior."
"At the same, I think it's had an impact on citizens—if they know you're wearing a camera they too will be on their best behavior," he said.
A 2013 study found that a quarter of 254 U.S. police departments surveyed used body cameras, according to the Police Executive Research Forum. More than 1,200 law enforcement agencies have purchased wearable cameras from Taser International Inc., TASR +9.44% with about 80% of the company's camera sales occurring in the last 12 months, according to Taser spokesman Steve Tuttle.
Big city police departments have begun to use or test body cameras, including New Orleans, Los Angeles and Las Vegas.
There also has been some resistance in some quarters.
The police union in Las Vegas initially opposed using body cameras, worrying that the footage could be used in fishing expeditions against officers in cases where there were no complaints, said Chris Collins, the union's executive director. The proposal to use cameras had come after rash of police shootings three years ago. Now, some Las Vegas police have begun wearing them after the union and the department hammered out guidelines, including when supervisors are allowed to review footage, Mr. Collins said.
Police body cameras also have sparked some privacy concerns for citizens, but civil liberties groups back their use with some restrictions.
The American Civil Liberties Union said last year that the cameras have the "potential to be a win-win, helping protect the public against police misconduct, and at the same time helping protect police against false accusations of abuse."
The cameras themselves are only part of the expense—The cameras themselves are only part of the expense—Taser's cameras range from $399 to $599. Data-storage and management costs can be significant, according to a recent report by Dr. White, the Arizona State University professor. "The logistical and resource issues are especially challenging for those smaller police departments," he said.
The police department in Mesa, Ariz., did a side-by-side study of 50 officers wearing cameras and 50 without. The results after eight months: officers with cameras were subject of 8 citizen complaints while those without had 23.
With citizens regularly capturing incidents with police on their cell phones, Mesa Police Department spokesman Steve Berry said the department wanted to have their own video "to tell the whole story or certainly both sides of the story."
To prove that software patents are bad, it is necessary, but perhaps not sufficient to point out bad examples. Then again I never said the only way of condemning the patent system was through examples?
- One thing that I think would improve it is putting the starting point in the bottom left corner. It's weird to have that half segment on the bottom.
- I want to see the exact number of points, not a fuzzy visual cue. The first visit each day I am going to look at every story on the front page, and subsequent visits are generally to look at replies to comments I've made. Prioritizing past "here are the stories on the front page" is useless to me.
- From http://hilapeleg.io/media/mockup_720x1981.png I get the impression that the new layout is much brighter than the old. I generally prefer off-white to full-white. It feels easier on the eyes. But without seeing the actual layout its hard to tell which I like more.
- Does this redesign come with comment hiding? This one feature is infinitely more important than an improved visual look.
let is the standard keyword for introducing a new, shadowing variable binding. It is a very old tradition and is immediately recognizable to functional programmers.
> If you want easy adoptation from one of the two largest languages in the world, change what matters and stick with the rest.
In the case of "let", it would be a false consistency with C/Java. Assignment in C/Java does not have the same semantics as a let binding in Rust, although a let binding in Rust has very similar semantics to a let binding in Scheme or Haskell.
> All the money in the world won't prevent you or a loved one from passing due to an untreatable illness.
Death of a family member is much more likely to happen if you are poor. Too bad you can't afford that unreasonably expensive surgery.
> All the money in the world won't buy you friends or genuine respect.
This is such a first world concern. Boo hoo. Also, yes, money does buy friends. When my family went bankrupt most of our friends turned their backs on us. This is a common occurrence. Ask a homeless person what happened to their "friends" when push came to shove.
> It can't buy you love (though it can buy you sex).
Not being poor is more important than finding love. If you want love, have some kids, and love them.
> Furthermore, you don't need to be rich to avoid the hardship of being poor, you just have to make a sufficient amount to afford quality housing, food, health insurance, and minor luxuries.
Please do not underestimate how hard it is for those who are actually poor to "make a sufficient amount."
This seems like a good enough time as any to point out that there are like six empty houses for every homeless person in America. Or, in techie terms, "you thought domain squatting was bad..."
c) The language boundary of Haskell typically ends at the production of an IO value. You can easily give an operational semantics to many IO operations, and in fact there are papers that do this for simple IO operations such as putStr. It's not possible to give a full operational semantics for IO in any language, not just Haskell. Of course you are going to model console I/O, references, exceptions, concurrency features (all of which have been done). But these aren't the only kinds of side effects. Does your model account for the network, and all its complexities? Does your model account for power failures? Does your model account for cosmic rays? Most models don't, but nobody calls them loopholes, nobody implies it's a big cover-up. Every model is going to have a boundary, and Haskell's seems good enough to me. It's no more undefined than, say, ML.
On Chrome 35 the freeze is for a much smaller duration but I can still feel it.
I'm currently on my (fairly beefy) desktop, so I imagine it's even more noticeable on an older laptop or phone.
EDIT: indeed, from a cold cache, it's even slower, and wow there are a lot of HTTP requests.
I have nothing but good things to say about React. Try that instead.
There is no split?
> Gevent is vastly simpler than this.
I prefer asyncio's explicitness to gevent's monkey-patch-and-pray-it-doesn't-block semantics. Also, the asyncio approach makes it very clear when you have released the "lock" on your state--it happens every time you yield from your coroutine. The gevent approach is to hide these synchronization points, which I think is a bad policy. For what it's worth this latter objection is one of the main reasons asyncio is the way it is--GvR had been bitten before by implicit yields.
And it gives you an escape hatch from Java-style module nonsense: of COURSE I want to traverse 7 singleton directories to get to the source code!
I donated a while back, will make another donation soon.
I would like to start using this immediately but I think I'll have to wait until a 3.3 release for "yield from".
Use Magit, which is probably the best Git client anyway.
Thanks for making this post, I have been meaning to say something similar for a while now. And, re: one of your other posts in this thread, the GC handbook is excellent. One of my favorite textbooks.
What most people on this site call "garbage collection" would be more accurately called "tracing garbage collection."
Really? At least in my fields (programming languages, networking) everyone has their articles on their homepage. You can find whatever you need by using regular Google or CiteSeer.
But that is what the fork is, OpenSSL with new stewards. What is your objection? That they are using a different name? That they decided to remove certain platforms which were a maintenance burden? That FIPS is broken by design and therefore isn't a priority? I imagine the OpenSSL team disagrees with the LibreSSL team on all of these issues. The only option was a fork.
> Right now, native libressl only works on bsd's, when openssl codebase works on many os's. There are ports being made, which will introduce more bugs.
One step backwards, two steps forward.