- As a noun, it means "road" ("El Camino" – "The Road").
- As a verb, it's a conjugation of "caminar" ("to walk" or "to go"). The -o ending makes it "I walk" or "I go".
508 karma · joined March 4, 2009
- As a noun, it means "road" ("El Camino" – "The Road").
- As a verb, it's a conjugation of "caminar" ("to walk" or "to go"). The -o ending makes it "I walk" or "I go".
Once a function has run many times, the compiler can use the gathered statistics (such as knowing that the arguments were always floats) to produce better optimised machine code (such as using float-specific ops, and eliminating code paths that expect arguments other than floats).
This is a common tradeoff for all JITs; Should I wait longer to produce better code, or compile sooner to run the faster code earlier? You can play with this number in most Java JVMs (OpenJDK or Sun/Oracle) using the argument "-XX:CompileThreshold". This sets how many times a function should run before it is compiled. It defaults to about 1500 for a client VM and 10000 for a server VM.
As mentioned in a sibling comment, asm.js is a partial alternative to this tradeoff, as your asm.js code specifies all data types ahead of time, and hence they can be compiled up-front fairly well.
https://support.mozilla.org/en-US/kb/reset-firefox-easily-fi...
(In short: Go to "about:support" and click reset. It will prompt you before doing anything, and will rebuild your profile while preserving bookmarks/history/saved-forms/etc)
iOS is also a very different environment with regards to payment:
- On iOS the process of purchasing paid and free apps is the same: you type in your password.
- On the web the process of purchasing paid applications has built-in friction: 'free' is the default, and payment requires the user to trust the store, input card information etc.
There are more people on the web, but web users are less willing to pay for things.
I don't deny that a larger audience is better, but it adds overhead to support more platforms, so focusing on one can be an advantage. Marco, the creator of The Magazine (http://the-magazine.org), mentioned that he hasn't ruled out other platforms, but with limited resources it's easier to focus on iOS for now (he's the sole developer). Apparently after four issues he already has enough income to pay market rates per-word to writers and hire an editor.
I also listen to them at faster speeds. People generally talk slowly, and listening at 1.5x or 2x isn't much faster than most people read, so they can still be understood easily (and after an initial adjustment they no longer 'feel' fast). A ten minute commute, listening at 2x, will consume 40 minutes of podcast per day alone.
The old model was revert-by-default. You had to manually save your changes.
The new model is save-by-default. You have to manually revert your changes.
In the "File" -> "Revert To..." menu you have multiple options, such as revert to last saved document and revert to last opened document. These persist even after restarting the application.
I think the new model is far better design.
I like that it takes less screen space by default, given that most of my usage is just selecting and analysing the CSS. It's great on a Macbook air.
Alternatively, PyCharm has a vi plugin which isn't too bad (depending on which features of vim you expect).
There's many layers of hierarchy (from the release groups themselves down to the hoopleheads at the bottom) so it speeds up releases significantly.
The "Try this" demos on this page show features that Firefox supports, yet they only have "-webkit" prefixed styles so they don't work.
Is the page out of date? Many of the features have been supported since Firefox 4 according to their own browser support chart.
You see a lot more taxis in cities with lower human labour costs (such as Lima), or where the cost of parking outweighs the cost of the driver (such as Manhattan).
http://arstechnica.com/old/content/2008/09/future-of-driving...
Some free options, none of which I've used, are: http://chatonic.com/ http://www.italki.com/ http://www.babelyou.com/ http://www.mylanguageexchange.com/, http://www.sharedtalk.com/ http://www.lenguajero.com/ (Spanish) http://vraiment.info/parlezfrancais/index.html (French)
I do most of my Anki revision through my iPhone: I can use it anytime I have 30 seconds to spare. Such as waiting for the dentist, waiting at a pedestrian crossing, waiting for breakfast to cook, waiting in line for lunch... etc.
I'm a very patient person as I'm extremely happy to wait for things now :)
If I was assembling a team of Java programmers today, I'd prefer to hire an excellent Python developer than an average Java developer * . A great programmer can learn a language faster than an average programmer can become a great programmer. The great programmer could be reasonably productive with Java after two weeks, but an average programmer is unlikely to improve their problem solving skills, or their ability to cleanly structure large programs after the same period of time.
* Feel free to replace 'Java' and 'Python' with any two languages within the same paradigm. I don't mean to pick on Java as a language.
2) In the article he's ignoring many advantages that smaller languages have going for them:
- Much, much higher signal-to-noise ratio when hiring: The people who currently know Scala or Haskell learnt it because they love to program – they sure as hell didn't learn them to land a job. You can't say the same about Java, C# or PHP.
- You may make your company more attractive to the best developers: A company advertising for work in Java sounds very average (and a place to work for pointy-haired bosses). It will have to work a lot harder to stand out from the crowd. A company sounds interesting if it uses interesting languages.
- Great programmers will usually prefer to work with languages they are passionate about.
- Great programmers like working with other great programmers. I can assume I'm working with better programmers when joining a Scala team than a Java team. When hiring, you have to work harder to convince me you're good if you are a Java team.
- If you only hire great programmers, you can have smaller teams: ie, you don't actually need to hire as many programmers.
- And, of course, it ignores whether these languages may be more productive to work in.
Phishing attacks could definitely be a big potential problem. I'd be interested in seeing how much of the phishing and usability problems could be solved via good browser support for OpenId.
Unlike an ID card you can have as many OpenID accounts as you wish – they can be freely created just as easily as email addresses. The solution is the same as for email: Give a different account to each site.