Btw, I've now dropped over $1,700+tax on Logic. From my original purchase of 4.0 from EMagic that I ran on Windows, Logic 6 post Apple acquisition, Logic Studio 9, and now Logic Pro X.
I am totally fine with the $200 pricing which is less than the cost of the previous upgrades. Everyone seems to be forgetting that there was a point when Logic cost $999.
Yes, this is a head-scratcher for those that complain there is no 'upgrade' pricing when the cost of the full app is what the upgrade price /used/ to be.
Same could be said for FCP X: Used to sell for $1600 and new price is $300, and then complaining that there's no upgrade price.
Used for example only, I realize that it wasn't so much an upgrade as a step backwards for functionality.
Tumblr has actually managed to pull off ads very, very tastefully. With brand and product recognition and well thought out ad-campaigns that feel like a part of Tumblr rather than banner ads.
I am very fortunate to have cashed out at the peak of this bubble. It's a damn shame mtgox is having these problems. I consider it to be a huge vulnerability of the system.
That said, many people are working on alternatives. It's a growing pain. I need to do more research but the concept behind this project looks very promising: https://github.com/macourtney/Dark-Exchange
Interesting but it looks pretty useless until they can figure out a solution to spam trades (people accepting their own fake trades and impacting the value of the currency), something that doesn't exist yet for now unfortunately, as they admit https://github.com/macourtney/Dark-Exchange/wiki/FAQ
My company moved away from ember-data recently in favor of our own simplified replacement. I like the concept of ember-data but we just ended up fighting with it more than we'd like.
It's a bad idea if you go into ember expecting it to be a solution to all of the javascript development hurdles. You should expect to fight the framework from time to time. You should expect a learning curve.
The solution is to be a patient developer, become familiar with the ember code base and it's concepts, keep up to date on the community happenings.
We are more than ecstatic about the results of our nearly complete product and I am positive having used any other framework would have made our development more difficult, and without a framework would have taken multitudes longer.
I've been mixing in TDD and BDD for the last 1.5 years of my 11 year coding career. I can't think of any reason not to test except for laziness and someone's unwillingness to truly use their brain to evaluate it's value.
Contrary to this article, one great reason is that TDD/BDD allows me to make refactors and major changes and know whether or not I broke something. I find it passe to have the opinion of this article.
A perfect example for TDD/BDD is a complex REST API with dozen of end-points and refactoring a piece of the authentication system. How do I know if I broke something or introduced a bug?
My experience is that most developers do not test and this is exactly the kind of way complex bugs get introduced. You actually make the job more difficult on yourself because instead of knowing YOU broke something, a bug gets introduced and you spend more time tracing the cause. I have worked at many places that have this obnoxious cycle of deploying, breaking, deploying, breaking.
It is irritating to see articles like this pop up because it's not like it's a school of thought or a religion. It's a purposeful tool that can and will save you time and effort and probably impose a few good design practices along the way. I'm not saying shoot for 100% coverage, fuck, I'm happy just knowing a few complex pieces are working. And I don't always think it's a good idea to design API's from the tests, especially when you are experimenting and researching.
Your "perfect example for TDD/BDD" is actually about testing in general, not TDD. You are stating the value of having a test suite when making a large change, not the value of writing tests first.
Sure. I guess I forgot to also make the point that the best way to write tests is to do it as you write the code you are testing. Otherwise the tasks becomes somewhat tedious and intolerable.
How about a synthesizer? I can immediately think of many useful ways to use a synthesizer with this controller. For example, touch pressure to filter cut-off or LFO amount. Finger vibrato to OSC pitch, OSC detune, filter, and so on.
I think the video does a reasonable job showing how it can be used creatively. I get the point you're trying to make about harmony between the input device and sound source. However, I would argue in modern days with really incredible software synthesizers both software and hardware (I own one of these: http://www.studioelectronics.com/products/synths/omega8/) the inverse is more common.
Input devices do a poor job of exposing the features of the instruments.
This is the first device I've seen that seems to actually care about the performability and feel without making you look like a douchebag. That's what makes it interesting to me.
I hope you understand it's not meant to sound condescending. Maybe my comment (http://news.ycombinator.com/edit?id=5211177) will help with the insight. Imagine the worst experience of your life. [rhetorical] Did you go through it with someone or were you alone? How much did that affect the experience? That's it. Having someone with you who has been through it before.
Again, I think my comment might give you some insights as to the claims about wisdom and maturity. There are also a vast amount of very smart people who have gotten a lot from LSD. I'd highly recommend this read: http://www.themorningnews.org/article/the-heretic
