ootachi

22 ms·

181.
by ootachi 15y ago
"Programmers are just about the only people left who have a plausible explanation for how robots won't simply take their jobs in 30 years." Unfortunately, they lack a similarly plausible explanation for how cheap offshore labor won't simply
182.
by ootachi 15y ago
Khosla didn't say 25, my mistake -- he said 35: http://www.washingtonpost.com/national/on-innovations/the-ca... The 25 quote comes from an unnamed VC quoted by Michael Arrington in this story: http://techcrunch.com/2011/04/30/internet-en
183.
by ootachi 15y ago
Nope. In fact, many VCs (Khosla, etc) are quite open about the fact that they are unlikely to fund you if you are over 25.
184.
by ootachi 15y ago
Wrong. Listen to all these stories. Everyone on this site will end up either unemployed and unable to find work if they don't win the startup lottery or die before reaching 40.
185.
by ootachi 15y ago
Listen to this man. This is the fate of everyone on this site. If you think you're exempt because you're awesome, I'm talking most of all to you. Get out of the tech industry while you still can. There are no jobs in this industry for anyon
186.
by ootachi 15y ago
None of those people are employable, except as vanity hires at companies like Google. Think about it -- why would it be in a company's best interests to hire Linus Torvalds? They can get the kernel for free.
187.
by ootachi 15y ago
In other words, the average salary of a Bay Area engineer is something like $20k, if you consider the fact that you'll work for 10 years at $80-100k and then get laid off and will be unable to find a job for the next 50 years until you hit
188.
by ootachi 15y ago
Bringing up a Linux kernel on a Raspberry Pi is not a relevant skill. Facebook, Zynga, and LinkedIn do not need kernel engineers.
189.
by ootachi 15y ago
So, in effect, you should work all the time. Half of the time you should work for free, so you can get hired again after you get laid off, and half of the time you should work for pay at your current job. What a wonderful industry we work i
190.
by ootachi 15y ago
Mozilla is working on a PDF reader and "integration with Firefox is a possibility if the experiment proves successful": https://github.com/mozilla/pdf.js It's mostly working already. I rarely ever find PDFs that it breaks with.
191.
by ootachi 15y ago
I'm so incredibly proud of Apple right now. Their mastery of the employee supply chain is nothing short of genius. Likewise, is "don't be evil" officially dead yet?
192.
by ootachi 15y ago
That's a Chrome Frame opt-in. Its only effect is to instruct an installation of IE with Chrome Frame installed to switch over to Chrome Frame for these sites. That said, I do think Chrome Frame is a bad idea because it hijacks one browser a
193.
by ootachi 15y ago
It's still a trap. When you copy and paste your content into the iBooks software, you instantly hand over all the distribution rights, as part of the terms of an EULA of a consumer product . Sure, this is the kind of thing that the record
194.
by ootachi 15y ago
So Microsoft should own the rights to distribute Harry Potter because it was composed with Word? After all, J.K. Rowling surely benefited from Word's spell checker.
195.
by ootachi 15y ago
You are being obtuse. It is immoral if you bury onerous terms (such as "you will give us the sole right to distribute your works") in an EULA that you know ordinary people have no hope of comprehending (such as this one). For all the other
196.
by ootachi 15y ago
The parent comment was pointing out that there exist programs in JavaScript in which the types cannot be inferred. All I was saying was that this is not unique to JavaScript, or to dynamically typed languages generally.
197.
by ootachi 15y ago
Well, statically-typed languages have a "dynamic" type too. Consider void * in C and C++ and Object in Java and C#. You have to downcast to do anything with them. That's the equivalent of what JS is doing with its dynamic typing. The basic
198.
by ootachi 15y ago
Nonsense. JavaScript bytecode would still be dynamically typed. At best a JavaScript bytecode standard would be equivalent to a compressed AST. That still might be a useful thing to have, but it wouldn't improve runtime performance.
199.
by ootachi 15y ago
Of course you can promise types to the JS engine. Ints in particular are easy. With modern type-inferring JITs like SpiderMonkey, an expression like "var x = 3;" will infer x to int, and there will be no type checks or unboxing. In more com
200.
by ootachi 15y ago
Because browser wars are expensive (look at how much money Google had to throw at Chrome to make it the #2 browser), and browsers are hard -- finding people who are qualified to work on browsers is not easy.
201.
by ootachi 15y ago
That's completely false. You, as a programmer who wants to fork Chrome, do not have the advertising power and reach that Google has. You do not have the Google.com home page. You do not have the ability to air ads during the Super Bowl. You
202.
by ootachi 15y ago
Google is often set as the default search engine for IE in preinstalled OEM configurations (and frequently these days Chrome is the default browser). For antitrust reasons Microsoft can do nothing about this.
203.
by ootachi 15y ago
C# has yet to drive meaningful business value for Microsoft. It certainly didn't topple Java the way they hoped it would, and it didn't even manage to gain internal mindshare for Windows Vista and Windows 7 apps. There's XNA, but that's n
204.
by ootachi 15y ago
It is not automatically easy to use an open source implementation of something just because it is open source. This is a very common misconception. If Google had wanted it to be easy for other browsers to use the open source implementation
205.
by ootachi 15y ago
Incorrect. Firefox at least displays the text with the second-in-line font and then switches over to @font-face when the font is downloaded.
206.
by ootachi 15y ago
The author realizes that these 5 restrictions don't even apply in Silicon Valley, right? 1. I can fire you, if I want to. California has at-will employment, but you sure can't fire someone based on gender or age anywhere in the United State
207.
by ootachi 15y ago
What an insulting and belittling post. As others have pointed out, the Pascal's triangle problem is dependent on intuition regarding the characteristics of the triangle that happen to be the most useful for solving the problem (in this case
208.
by ootachi 15y ago
Indeed. Hiring programmers is about hiring people who bring business value to your organization, not about bringing in people who can solve Pascal's triangle faster than the other 90% of candidates. The entire first thread on this page is a
209.
by ootachi 15y ago
No, in the Bay Area. There are tons of programmers here who can't find jobs. There simply aren't enough positions available for even talented programmers to find work.
210.
by ootachi 15y ago
It's not a tight market for dev talent at all. There are so many programmers out there and not nearly enough positions. Those that do exist now will be rapidly drying up due to industry slowdown and consolidation.

More ›