How long did it take you to find your next startup when you were looking?
867 karma · joined June 18, 2012
How long did it take you to find your next startup when you were looking?
As a gamer, though, I can hardly see any other application of VR having more potential to become mainstream than VR in gaming.
Selling it to Facebook seems to me an indication that the leadership no longer believe that Oculus can be as successful in the gaming industry as they hoped.
> First, compiler languages require some learning.
Every new technology require some learning. This shouldn't be the number 1 reason not to use one.
> Second, both languages make debugging a harder process.
Haml harder to debug than html? How so? Coffeescript harder to debug javascript? Maybe there is an extra step, but how do you weigh in the better readability in CoffeeScript when it comes to debugging complex code?
> Lastly, there are just too many dependencies.
"Every time I touch code, I am forced to touch two levels of abstraction." I seldom if ever need to touch the javascript file compiled from the coffeescript. And I really don't see how come more coffeescript files is more complex to handle than a couple of coffeescript? I can assume that you don't manually compile them one by one right?
All these are really important productivity booster. Because we all spend a significant amount of time navigating our code base. VIM is really a great editor with its programmable command line interface, but it's not as nearly easy to navigate code in VIM than in JetBrians IDE.
JetBrians' integration with Git is also amazing, combined with its own local history system. In JetBrian IDEs, when I open file, any local change (according to git) will be marked at the left, a simply click can revert that particular local change. With the local history and auto save, I never need to worry about saving the files.
In ruby, you have to have close to 100% test coverage because if you don't you can't have any confidence when you refactor. For example, in ruby project, even a simple delegation call needs to be tested, otherwise you may break it without knowing it when you rename the method delegated to.
You don't need to write such test in a Scala project because there is no business logic in a simple delegation and the compiler will check the rename for you, actually the IDE will do the rename refactor perfectly for you.
In general, some of the unit tests devs wrote in Ruby projects are not to test against business logic but to test type matching. For type related refactoring, they actually have to refactor both the code and unit tests. The dilemma here is that if you are changing your unit tests, how confident you are that they are still covering your refactor?
My guess is that he hasn't extensively used a Nexus 7 tablet. It fits fine in my front and back pockets. I used it way more than my smartphone. And I rarely have the need to pick up my 10 inch tablet.
========================
object Cards {
type Deck = Seq[Card]
case class Card(r:Rank, s:Suite)
type Rank = Int
sealed trait Suite
case object Spade extends Suite
case object Heart extends Suite
case object Diamond extends Suite
case object Club extends Suite
}
==================================
Granted, all this code is unnecessary in Clojure but there are two benefits of writing them:
1) compilation type check
2) for developers who have no context of playing cards, this provides a clearer picture, while in the Clojure code they will have to browse more code to get the full picture of the data domain.
I was using Ruby as my main language for 3 years before I switched to first Coffeescript and then Scala now. Personally I prefer the simplicity (a function is a function) of Coffeescript and the richness (so many things to fool around) of Scala over Ruby.
The popularity of languages don't die over the course of a couple of years. Projects with legacy code rely on them and maintenance of their libraries. And legacy code is very very hard to kill.
If the interest is in finding out the trend of the "favorability" of a language, it might be more accurate to survey how many green field software products(not libraries, which could be driven by the need of improving some legacy code) are choosing it. Unfortunately, such survey is more expensive to perform, and might be close to impossible to perform retrospectively to understand the trend. Given the fact that the "popularity" of a language isn't that important, the favorability is probably even less, such survey is probably hard to justify.
Chrome
AngularJS
Go
Selenium Webdriver
dart
Even Google Hangout with screen share helped our distributed team a lot.
5 years ago, what did Google offer? GWT?
And, of course, the search engine, we developers probably use it more than many other groups users. I hardly heard anyone use alternative search engine for day-to-day software development related search.
All these are of zero cost to us.
http://www.amazon.com/Tokyo-Nobody-Masataka-Nakano/dp/489815...
In the article:
"a system with about 30 advertisers in the US in which it shows banner ads for companies including SouthWest Airlines on pages which include them in web search results"
So google knows by the fact that the name of the client is in the search term.
I really hope I can do something like
for (
ra <- asycn_opA(),
rb <- async_opB(ra),
_ <- asycn_opC(ra, rb)
).run()