In those, the answer to the OPs question, "Percent of time spent developing internal tools?", at least on certain teams, is in excess of 90%.
348 karma · joined November 17, 2010
In those, the answer to the OPs question, "Percent of time spent developing internal tools?", at least on certain teams, is in excess of 90%.
But what isn't? Plenty of Rails is sitting atop JRuby and friends. Nothing is immune.
Don't get me wrong. I'm not a massive supporter of .NET (outside of XNA) by any means. My point is if legal issues are what you're looking for; you'll find them; everywhere. It's just all so ubiquitous it's simply not cause for concern.
Anything can be made to be seen as illegal from a certain perspective. Everyone is suing everyone else. Does that mean we all pack it up and go home?
Furthermore, in its current state, this product is not considered a beta; rather an alpha.
Nevertheless, I wish you all the best and indeed hope you are successful; especially given Mojang's complete lack of interest to fill these voids :)
* Paywall
* Forced registration
* Advertisements galore
* Popups
It's laughable anyone would consider an organisation willing to produce this abomination of a website an authority on technical progress.
I'm tremendously disappointed this had made the front page.
Some tech details: canvas-based rendering engine, firebase for chat and presence, sockjs for realtime events, phantomjs + beanstalkd for rendering static tiles (for zooming way out), python on the server side, mysql where convenient and mongodb where convenient.
The developers (chatting in-game) were rather friendly and particularly forthcoming about their sound choices for their technology stack which I found to be refreshing. This kind of transparency, at least in this industry, is somewhat rare and is absolutely commendable.
If you indeed enjoyed the experience, as I suspect most did, please continue to support these developers and their work. It is through this process we, as a community, will continue to manifest works such as this.
Do not underestimate the power of getting the word out about these endeavours. A "like" on Facebook. A tweet. A blog post. It all adds up. And we really do appreciate such a priceless commodity.
We too often forget our code sits atop a stack of compounding encapsulations we'd all find horrifically disgusting whose only true merit is that it actually functions.
If you're commentative enough at what you comment that you have time to comment on your inner comments about how good you comment, you're commentative enough to need more commenty comments to comment.
History will remember the entire Ruby industry as a series of compounding failures.
The de facto formalisation and specifications.
The black-box behaviour of core development.
The broken-linked, un-versioned docs.
The rampant cargo-cult mentality.
The arcane exceptions.
The meta-frameworks.
Gem hell.
1.9/2.0
Rails.
There's a reason it's called Gene EXPRESSION.
- "Steam may well be doomed"
- "Steam is just the wrong side of geeky"
- "Microsoft sold at least 4 million copies of Windows 8"
- "Microsoft is poised to apply a Wal-Mart Effect to PC software"
Metro is indeed where asses are told to go.