847 karma · joined October 4, 2010
Edit: Many people argue in favor of building restrictions on the basis of environmental concerns, but limiting housing in SF is just pushing more people out to places like Sacramento, which are suburban waste lands and models of inefficiency.
Housing stock on the Geary corridor could be easily increased, and even a modest improvement to the transit system in that area could make a big difference.
It is absolutely crazy to artificially restrict residential building in areas where there is high employment demand. It is almost like we want to prevent economic growth.
The US is a crazy place. We complain that there isn't enough economic growth, but when it happens, we put in all kinds of restrictions that limit it.
Some of my colleagues do get MTM suiting made in places like Hong Kong and Thailand.
The apparel market is massive I think there is room for innovation.
I've had two pair of glasses from them, and I've never had so many comments and compliments on a pair of glasses. So even if the glasses are made by the factories that make frames for other companies, there is something to be said about their design.
I'd love to see Warby Parker's disruptive strategy applied to other parts of the health care market. It shows what free market pressures can do to effect prices.
All the discussion around Nginx recently, has me wondering if I should revisit my own proxy project: http://switchflow.org/
This isn't the case with the default MSVC implementation of malloc() in Windows. In Windows address space is reserved and committed with VirtualAlloc(), and typically that is done in one step.
I think memory is over committed because Linus wanted to keep the memory footprint lower than NT early on in the development of the kernel. The drawback is applications may segfault when writing to memory that was successfully returned by malloc().
I can't stress enough how basic it was. Getting the kernel up and running was only 1/2 the battle. Getting X to run was a significant undertaking, and probably more difficult.
That would be a gigantic change to the language, which I'm sure I don't understand the implications of.
After thinking about this some more, I'm going to stand by my original, even if poorly argued, comment that C++ doesn't really live up to the promise of "precise control" when it comes to memory allocation, and this is one area that can have a big effect on performance. C++ has all the overhead of a low level language, with a promise of control that when you really need it is often difficult to access.
It is difficult to implement multiple allocation strategies in the same application. In another time, I actually did quite a bit of work in this area: http://accu.org/index.php/articles/1308
Over the long term I think Go is going to offer a much more sane environment for implementing high performance servers.
With hand brewed coffee the difference is much more noticeable. If are you in SF, stop at 50/50 on Geary. They spend more effort prepared their coffee than any place I've been. I think you will be surprised by the difference in quality.