It's like me calling a program open source and ownly making the roadmap/initial spec publicly available.
80 karma · joined May 11, 2010
It's like me calling a program open source and ownly making the roadmap/initial spec publicly available.
1. People don't search properly before posting
2. There are a lot of "low quality" questions that could be answered by reading documentation (also see 1)
3. Most of the questions that apply to 1 & 2 have already been answered on StackOverflow.
4. It's overwhelmingly (US) English, so people who are not fluent pendants are down-voted.
5. The people who need the most help are those who are least suited to post, as they rarely give enough detail ([example][1] - where to start?), ask very generic questions ([how to build a website][2]), or ask questions that have been answered before
When StackOverflow started, I spent a great deal of time on it as it felt like a good way to help and share knowledge (or just show off). Nowadays, I'll vote when I find an answer (usually via Duck Duck Go), but [the last question I asked][3] is still unanswered (allowing Facebook to use this as a support forum is a joke).
I feel that it's become a victim of its own success, and is getting to the point where it's as bad as the sites it tried to replace.
[1] http://stackoverflow.com/questions/9395670/dataset-getting-m...
[2] http://stackoverflow.com/questions/87305/how-to-build-a-webs...
[3] http://stackoverflow.com/questions/8077747/what-are-facebook...
However, I think that sprinkling andro.eventer all over the place is a stumbling block to me - it's essentially a global variable.
I realise that you don't want to polute the objects too much, but why not just add bind and emit methods to the composed object? Either that or pass andro as a parameter to the mixin's setup method?
Also, the bind(this, "touch", function...) to me looks like you're binding to the "touch" event of "this". Is the closure tax really so high that you can't store "this", or use something like jQuery.proxy()?
Like I said, I think this approach has a lot of potential, and seems to fit quite naturally the eventful model that the DOM uses.
my done list: git log
----------------------------
What’s the elevator pitch?
EMI is making some of its artists' content available via an API. Developers can work with the content in a sandbox environment and propose ideas for applications. If a proposal is taken forward, EMI will handle the tasks of clearing the necessary rights and marketing the application. Revenues will be shared between the developer, EMI, artists, The Echo Nest, music publishers and any other rights holders.
I read this as EMI want me to take the risk of developing an application, and then, if they think it's going to make money, they'll take it on and make money out of it. Sounds like they're trying to apply the same model to developers as they do to musicians.
That said, they aren't always the fastest, and don't do anything to dispel my hatred of Java UIs.
I used WebStorm to do node.js for a while, but haven't renewed my subscription as it didn't provide me much extra from vim. The jQuery/Web stuff I've done with WebStorm was pretty good though.
There's a reason no-one else does login like this.
An interesting article, but I don't have time nor the inclination to understand the code, which is the core of it.
The original paper is based on use of `eval`, which people using NodeJs wouldn't do (I've not seen one example of it) -especially when V8 has an efficient `JSON.parse`.
The attack against NoSQL databases is a Sql(JS?) Injection attack - and not even a sophisticated one. Sure, services like iriscouch open themselves up to this kind of attack, but the way the paper describes it is pretty much by design.
Even as an experienced programmer, I'm still reticent to use node in any real projects, (mostly because I'd spend half my time updating it to work with the latest release).
Of course, it can be fun to hack on a fast moving platform, but it can be annoying too, when you spend your evening trying to get an environment set-up on an obscure platform rather than writing any useful code.
I know people who actually implement this are going to have their heads screwed on around the right way, but having a page where you know you can generate server processing, and that is potentially not going to have much security around it screams out to me to be a good place to start an attack from.
Especially as the spec is a bit vague about exactly what happens when (no head specified for example, doesn't say about including cookies or any other information). Also, fiesta.cc's CSP Report URI returns a response that says to keep the connection open.
And, if you manage to get a script injected to a popular page, the site itself acts as a distribution system to enable distribution to multiple users.
Something about this says it's not been thoroughly thought through to me.
This article basically takes the approach that "the cloud" is AWS.