197 karma · joined April 1, 2013
There is a potential benefit if the minifier can apply some performance optimisations, but one would hope V8 et al are already doing most of these and more.
Even for client-side applications, HTTP2 + Web Assembly will eradicate concatenating and minifying JS files soon.
I'd argue the threat here is that malicious extensions at this level can be done by somebody with little to no experience, compared to kernel extensions which actually require some modicum of skill.
Requiring signing is a recognition of the fact we are increasingly moving our lives online, and hence into the browser.
It would be fantastic to take this set visualise their causes. It would be really interesting to see whether the causes are that different for large corporations vs smaller startups. I suspect, as in the article, it remains that configuration, error handling and human causes are still the most popular regardless of whether you have vast quantities of process or money for tooling.
The fact that browsers don't get this stuff right by now is pretty worrying. Makes it difficult to imagine the web being the platform of the future and complex applications being built atop it.
One approach to this problem, as the article mentions, is to list by popularity - however what would this mean? If it's by the number of "stars", not many people curate their list to keep them up to date. It would have to be some kind of rolling popularity measure, perhaps number of unique users who've cloned a repository in the last month or something.
[1]: https://bitbucket.org/site/master/issue/5009/list-of-project...
Of course it goes without saying that this isn't something most of the millions of unknowing Samsung customers are likely to be able to do themselves, let alone be aware it's even a good idea.
Some of the best lessons in life can come from those who haven't been tainted by long stints doing the very thing they're commenting on.
[1]: https://blog.bitbucket.org/2013/09/16/take-control-with-bran...
I can see this being useful for running as a batch process in Node/IO.js and uploading to, say, S3.
Some notable ones include:
* Facebook Haxl, an abstraction around remote data access [1]
* Microsoft Bond, a cross-platform framework for working with schematized data [2]
* Google Ganeti, a cluster virtual server management tool [3]
* Intel Haskell research compiler, a custom Haskell compiler used internally at Intel Labs [4]
---
[0]: https://wiki.haskell.org/Haskell_in_industry
[1]: https://code.facebook.com/projects/854888367872565/haxl/
[2]: https://github.com/Microsoft/bond
[3]: https://code.google.com/p/ganeti/
[4]: http://www.leafpetersen.com/leaf/publications/hs2013/hrc-pap...
It was really refreshing to see somebody write about the struggle to pick up Haskell - indeed, I had a lot of the same issues. I often feel the Haskell community is burdened with this stigma of "if you have to ask questions, you're probably too stupid to get it". This is despite the fact that there is actually a really great group of people always willing to help in #haskell. It's primarily an image problem, one a lot of FP languages suffer from.
We need more articles talking about the pain points of Haskell so we can get better at making this stuff accessible. We need to be honest with new starters, tell them it's okay to find this stuff challenging and show them where to find help. More than that, though, we need to think about what we can do in the language to fix some of these pain points in a way that the community is happy with.
"Readability" may be a personal thing, but you'll reach convergence pretty quickly by following the approach you outlined. I see it as no different to something like writing, in that respect, in that an editor and a writer begin to converge on a style together without really setting out in the first place to do so.
Works: writing code should always have one purpose, deliver some value to somebody. Writing code that works, that it’s actually deployed somewhere making somebody happy is one of our top priorities. So we were kind of surprised every time a developer didn't include that item in the answer.
Couldn't agree more.
It's really hard to get the motivation to finish such a project, serious kudos to you; I shall be buying that e-book!
Most frequently, this is done by disabling submit buttons or debouncing asynchronous function calls that happen as a result of a UI action.