I keep my old 15 inch MacBook pro around for TF2 and to run more involved deployments on VMs.
2,951 karma · joined August 28, 2011
I keep my old 15 inch MacBook pro around for TF2 and to run more involved deployments on VMs.
As someone who's already emerged on the other side of that process, can you speak to one's capability to capitalize on that experience and personal growth throughout one's life? Does middle age have to be a time of complacency and conservatism?
The beautiful thing about bayesian probability is that the first experiments conditional probability is the next experiment's bayesian prior. We acknowledge the epistemological fact that our initial understanding of the world is flawed, and correct it from there.
If it's battery life you want, then you definitely should go with the macbook air.
After that, having spent a good length of time in Boston, I can say that there is a small but very healthy startup community there.
Trust me, no you don't. Pointer arithmetic is one of the easiest things to screw up in C, and the raw form can be very dangerous to work with.
For sure, treating a pointer as an integer and incrementing by a fixed number of bytes each time is fine, but more often than not languages have this implemented, just as a JIT or compiler optimization.
Thirdly, the notion that all you need to be a tech journalist is an understanding of programming, when technology journalism today touches on hardware, electrical engineering, business, politics, environmental issues, and finance, not to mention the fact that many of these people are actually trained journalists, which is a worthy field by itself.
However, the most damning implication, the one which tends to lie at the root of many self-delusional blogs beyond this one: the idea that only insiders' word is worth hearing. Only an insider in a very particular segment of the tech world will be able to immediately tell you which of the NoSQL databases is the odd man out.
The notion that someone who can't isn't worth listening to is a surefire way to seal yourself in a stifling echo chamber where you cling to your own (usually flawed) ideas like a teenager clinging to a safety blanket while the other kids are out making friends and growing.
Think about it: the author writes touching human interest story that pulls at readers' heartstrings by genuinely presenting the dilemma he is faced with. The story resonates with the combined holy trinity of geek social news: "Apple is a soulless and evil," "The patent system is a parasite on the world," and "Indie game/software developers are sacrosanct." Outrage ensues.
What could make this all go away for PRC? Apologizing and offering the author a free copy of their product before he decides to launch a crusade and a PR nightmare. Instead, no such offer came through.
The question I want answered is, Why? Are these companies so clueless that they don't see the PR catastrophe brewing? Do they know and don't care?
I propose a teaching about the nature of social news in the form of an admittedly unlikely third explanation: The company performed a cost-benefit analysis and realized that the intersection of this blog's audience and the company's customer base is so small they can get away with ignoring them.
Your outrage is impotent. You can rage about this on the internet all you want, but it's not going to cause an inch of motion in any direction. If you want to do something other than express frustration, send letters to newspapers, don't post comments. These companies are going to have to lead marketing campaigns. Get the jump on them and make the first impression on their potential customers.
That is how you get things done.
And this is perfectly fine. For instance, Qualcomm set up Code Aurora specifically so that they could keep their propriety and open source offerings separate.
The shifty thing here is that Microsoft is trying to paint this as some sort of altruism, as thought Microsoft is doing the open source world a favor by setting up a legal formality.
1. According to ARM's promotional materials. No corroboration from licensors, as far as I'm aware.
2. Without caches. If you look at those pretty pictures of Intel chips, those huge swatches of regular rectangular stuff are caches, and they take up space.
That's a question I submitted while in the process of researching my final paper for Alfred Aho's advanced compilers course at Columbia University. In the paper, I discuss why compiling Python to C is difficult, and present some of the process that PyPy uses to make the translation happen for RPython.
Here's the link:
http://www.scribd.com/thejfasi/d/83851011-COMS-6998-Final-Pa...
EDIT: The title of this post is slightly misleading. It doesn't discuss how PyPy works, just how the translation framework happens.
By now, gasoline powered cars have been around for a hundred years. Everyone knows they are complex machines with lots of movings parts, and that they require regular maintenance to keep in working shape. What Tesla is putting forward here is the fact that the same principle applies to their electric cars: they need their own kind of TLC to be kept in good shape.
However, there is another point Tesla fails to get across. Over those hundred or so years, not only has the need to care of a gas-powered car entered into the public psyche, but also how that care must be carried out. Everyone knows that cars need oil changes and exhaust checks and all that. It's obvious by now.
However, that sort of awareness doesn't exist when it comes to electric cars. Saying they need care is great, but Tesla is missing an opportunity to develop the same sort of intuitive public awareness with regard to their vehicles. It's not just 'these cars need care,' it's 'these cars need care, and its of a kind you don't expect, that's OK because you haven't need raised on these vehicles since you were young.'
This way, the message would move from being an ever-so-slightly condescending implication that you forgot that electric cars need electricity, and refocuses on the need to augment the way in which people think about maintaining their vehicles.
The JVM has a very hard time integrating existing C code and extensions. For instance, in the case of python, Jython lacks the ability to take advantage of the significant number of modules written in C.
Consider what this means for performance. Imagine a pure python module that attempts to import a C submodule for performance, and falls back on on the pure python implementation specifically to allow it to run on non-CPython implementations. json is an example of such a module.
This module was likely engineered and architected with C module optimization in mind. I'd assert that in most cases the pure python module is a crutch to allow a CPython-targeting module to run on other implementations.
This leads into the social reason. Community takes a long time to build and using the JVM for dynamic languages is a relatively new trend. The JVM is a very mature, well-optimied technology for static languages. It is only now that dynamic languages are starting to gain traction on it.