220 karma · joined February 13, 2013
Highly recommend!
I assume BT is a European (or British) ISP?
Is "seppuku" a common analogy people use? I just looked it up and was a bit surprised at the result.
Most frameworks weren't even at 1.0 stable yet. I initially wrote a fairly extensive prototype with Ember, but there were breaking changes so frequently I couldn't keep up with the learning curve. In the end I chose Angular because it had the best documentation, Google dogfooding, and testing was an obvious priority. Worked out so well we're on our 4th major Angular app now.
Clearly at this point both architectures work, it's childish to see this as an argument for server-side rendering. Obviously it works, so do client MVC systems.
The value in this article is the humble detailing of their mistakes that many of us also experience in our careers.
I can't find the exact article I read where the authors discussed this, but I did find a presentation by Brian Ford[1] that touches on the subject.
[1]https://docs.google.com/presentation/d/1Gv-dvU-yy6WY7SiNJ9QR...
"There's been a story going around that it's been proven that black holes don't exist.
Yes, they do. <link>"
https://twitter.com/StartsWithABang/status/51488524891693875...
Edit: Re-reading my original comment I see my choice of words was poor.
https://medium.com/starts-with-a-bang/yes-virginia-black-hol...
[1]http://astro.uchicago.edu/cosmus/projects/UCLA_GCG/ [2]http://en.wikipedia.org/wiki/Accretion_disc
"My home page goes from 31,803 bytes to 71,488 because of the JavaScript I've added to track visitors to my page and what they do. "
Using bytes to make it sound extreme is just silly. 70KB is hardly relevant today.
When I do personal development or small side projects I could care less about my history being clean. Nothing is ever so large or complex that it needs to be fixed in such a meticulous manner. It may feel that way, until you start working on larger software. The stress of a $1,000-$20,000 job is laughable compared to the scale of enterprise failure.
In enterprise, it's often the case that applications are built by teams of people in constant flux. They may need to be patched or rolled back at a moment's notice, and every hour the bug stays live is an hour of enormous financial burden to the client and intense stress on my employer. In this case, having a trustworthy VCS with a clean history in invaluable.
At any rate, kudos to the team for trying to move the industry forward.
While I agree with the sentiment, this statement is a bit extreme. Especially since it's a distributed system so you're not exactly losing your work. Also, you can get it back online if you jump through the flaming hoops. In reality there is no better option for hosting OSS code right now than GitHub.
Apparently users like being told what they want
I'm not suggesting it won't work, I think it's a fantastic program and I'm rooting for its success. I'm just suggesting you may want to consider remote opportunities (maybe with occasional visits for in-house tech talks) for future iterations which would undoubtedly increase the talent pool and presumably be more effective at delivering your end-goal.
As a full-stack developer it interests me because it lets me visually create the visual part of a site. I don't like writing CSS when I have so much other development to do, but at the same time I don't want some shitty, bloated WYSIWYG editor that spits out garbage code. Macaw's authors have emphasized the quality of the generated code since the beginning so even if it's not perfect right away it's certainly comforting to know it's a priority for them.