Seattle could take a cue from Salt Lake planners

Wednesday, June 11th, 2008

Brigham Young famously wanted streets wide enough to turn a team of horses and wagon in, and the superblocks were designed to be neatly divided into plots that would give the settlers enough land to grow crops, have an orchard and sustain themselves.

Few wagon trains are pulling U-turns in downtown Salt Lake these days, and the office buildings and parking lots don’t leave much room for fruit trees. And even the most meticulously planned community loses its luster over time and needs some modernizing especially if the alternative for new investment is not unsettled wilderness but the growing suburbs and towns strung along the Wasatch front.

So Salt Lake is embarking on a major redevelopment effort under an umbrella plan called Downtown Rising in which nearly $2 billion will be invested in new offices, residential and retail buildings, arts, culture and governmental facilities and transit projects.

There’s a Seattle component to this. Seattle-based architecture firm Callison is a participant in one of downtown Salt Lake’s biggest projects, City Creek, a 20-acre mixed-use project across the street from Temple Square.

Seattle-based retailer Nordstrom was one of the drivers behind the redevelopment effort generally and City Creek in particular.

“Frankly, the heart of downtown has for the last 20 years been slipping into a worse state of repair,” says Callison principal Stan Laegreid. “It was turning into quite a liability. Everyone agreed something needed to be done.” As a downtown tenant with a lease nearing its end, Nordstrom was “watching the value of a downtown and a commercial market just steadily slip away.” The retailer was reluctant to stay unless “there was a larger commitment to turn downtown around.”

Beyond those specifics, Salt Lake’s efforts to rejuvenate its downtown have some interesting parallels and contrasts for Seattle as it considers its own redevelopment efforts in places such as South Lake Union, south downtown and Sodo.

Salt Lake and Seattle are hardly alone among western U.S. cities considering large-scale redevelopments that involve millions of dollars in investment and years of planning and wrangling. Some cities get a blank canvas to work with in the form of abandoned rail yards that cover acres of potentially prime developable real estate. Sacramento, Calif.; Santa Fe, N.M.; and Spokane are in varying stages of rail-yard redevelopment projects. Renton is working with former Boeing property near Lake Washington. Yakima is looking at what it can do with a former sawmill.

Salt Lake differs somewhat in that it’s trying to work a somewhat coordinated plan into and around an existing downtown, although Laegreid says there’s actually considerable open property in the downtown core.

But the biggest difference between Salt Lake and Seattle is the influence and participation of The Church of Jesus Christ of Latter-day Saints. Temple Square is at the physical heart of downtown, drawing visitors as both a religious center and tourist destination.

“They have deliberately spearheaded this effort,” Laegreid says. “That introduces a dynamic and a patronage in the process that very few cities have. That was a big trigger in allowing this to happen.”

Contrast that with development efforts in Seattle. One striking feature about Downtown Rising is the breadth of business sector and governmental participation in a shared plan for downtown. With Seattle’s fractious political scene, very little gets done in a coordinated fashion unless, of course, a private developer such as Paul Allen’s Vulcan in South Lake Union has the size and drive to come up with a large-scale redevelopment plan on its own and push it to reality.

Not that having such an influential partner meant immediate unanimity in Salt Lake. “There still were a lot of vested parties that collectively had to share a vision,” Laegreid says. Once the first ideas were floated, human nature took over. “Everyone’s got opinions,” he says. “There was a certain amount of compromising, everyone getting their voices heard.” Although Salt Lake isn’t as consensus-crazy as Seattle, “given the high profile of the project, it started to feel much more like a Seattle” process.

Google’s Mac efforts begin to bear fruit

Thursday, May 15th, 2008

“One thing stood out,” Singh said. “There was no easy way to do file systems.” So Singh decided to create one, even though he worked for Google’s search team at the time and wasn’t part of the company’s Mac development efforts.

The reaction of his bosses to this use of company time? Go for it.

Singh’s project, which became the open-source file-system utility MacFUSE, is just one of the many employee-driven efforts that go on within the walls of the search-engine and text-advertising giant all the time.

Google calls it “20-percent time,” encouraging its engineers to pursue other Google-related interests for up to 20 percent of their work hours—even if that interest has little to do with their regular duties at the search and software company.

Efforts such as 20-percent projects by engineers like Singh are par for the course at Google, a company that sees encouraging employees to pursue subjects they find interesting as a critical part of its own development goals.

“A lot of things that happen at Google are based on empowering people to come up with ideas and pursue them if [those ideas are] good,” said Sundar Pichai, Google’s director of product management.

Many 20-percent projects have wound up becoming major Google products: both Google News and Gmail, for instance, started that way. Among the Mac-specific efforts that began as 20-percent projects are Notifier, which offers Gmail and Google Calendar notifications, and the Google Mac Developer Playground, an online collection of open-source Mac projects created at Google.

First BETA Version 4.0 of HttpComponents- HttpCore Released

Saturday, March 1st, 2008

The Apache Hyper-Text Transfer Protocol Components project, has released the first BETA version of HttpComponents HttpCore 4.0-beta1. This release marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained. It includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.The focus of the development efforts will be towards providing better test coverage, documentation and performance optimizations. The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are sufficient to develop basic client side and server side HTTP services with a minimal footprint and no external dependencies. HttpCore NIO extensions can be used to build asynchronous HTTP services based on non-blocking I/O model capable of handling a great number of simultaneous connections with just a few I/O threads.

First BETA Version 4.0 of HttpComponents- HttpCore Released

Sunday, February 24th, 2008

The Apache Hyper-Text Transfer Protocol Components project, has released the first BETA version of HttpComponents HttpCore 4.0-beta1. This release marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained. It includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.The focus of the development efforts will be towards providing better test coverage, documentation and performance optimizations. The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are sufficient to develop basic client side and server side HTTP services with a minimal footprint and no external dependencies. HttpCore NIO extensions can be used to build asynchronous HTTP services based on non-blocking I/O model capable of handling a great number of simultaneous connections with just a few I/O threads.

First BETA Version 4.0 of HttpComponents- HttpCore Released

Saturday, February 23rd, 2008

The Apache Hyper-Text Transfer Protocol Components project, has released the first BETA version of HttpComponents HttpCore 4.0-beta1. This release marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained. It includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.The focus of the development efforts will be towards providing better test coverage, documentation and performance optimizations. The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are sufficient to develop basic client side and server side HTTP services with a minimal footprint and no external dependencies. HttpCore NIO extensions can be used to build asynchronous HTTP services based on non-blocking I/O model capable of handling a great number of simultaneous connections with just a few I/O threads.

First BETA Version 4.0 of HttpComponents- HttpCore Released

Friday, February 22nd, 2008

The Apache Hyper-Text Transfer Protocol Components project, has released the first BETA version of HttpComponents HttpCore 4.0-beta1. This release marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained. It includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.The focus of the development efforts will be towards providing better test coverage, documentation and performance optimizations. The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are sufficient to develop basic client side and server side HTTP services with a minimal footprint and no external dependencies. HttpCore NIO extensions can be used to build asynchronous HTTP services based on non-blocking I/O model capable of handling a great number of simultaneous connections with just a few I/O threads.

First BETA Version 4.0 of HttpComponents- HttpCore Released

Sunday, February 17th, 2008

The Apache Hyper-Text Transfer Protocol Components project, has released the first BETA version of HttpComponents HttpCore 4.0-beta1. This release marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained. It includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.The focus of the development efforts will be towards providing better test coverage, documentation and performance optimizations. The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are sufficient to develop basic client side and server side HTTP services with a minimal footprint and no external dependencies. HttpCore NIO extensions can be used to build asynchronous HTTP services based on non-blocking I/O model capable of handling a great number of simultaneous connections with just a few I/O threads.

First BETA Version 4.0 of HttpComponents- HttpCore Released

Monday, February 4th, 2008

The Apache Hyper-Text Transfer Protocol Components project, has released the first BETA version of HttpComponents HttpCore 4.0-beta1. This release marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained. It includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.The focus of the development efforts will be towards providing better test coverage, documentation and performance optimizations. The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are sufficient to develop basic client side and server side HTTP services with a minimal footprint and no external dependencies. HttpCore NIO extensions can be used to build asynchronous HTTP services based on non-blocking I/O model capable of handling a great number of simultaneous connections with just a few I/O threads.

First BETA Version 4.0 of HttpComponents- HttpCore Released

Sunday, February 3rd, 2008

The Apache Hyper-Text Transfer Protocol Components project, has released the first BETA version of HttpComponents HttpCore 4.0-beta1. This release marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained. It includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.The focus of the development efforts will be towards providing better test coverage, documentation and performance optimizations. The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are sufficient to develop basic client side and server side HTTP services with a minimal footprint and no external dependencies. HttpCore NIO extensions can be used to build asynchronous HTTP services based on non-blocking I/O model capable of handling a great number of simultaneous connections with just a few I/O threads.

First BETA Version 4.0 of HttpComponents- HttpCore Released

Saturday, February 2nd, 2008

The Apache Hyper-Text Transfer Protocol Components project, has released the first BETA version of HttpComponents HttpCore 4.0-beta1. This release marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained. It includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.The focus of the development efforts will be towards providing better test coverage, documentation and performance optimizations. The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are sufficient to develop basic client side and server side HTTP services with a minimal footprint and no external dependencies. HttpCore NIO extensions can be used to build asynchronous HTTP services based on non-blocking I/O model capable of handling a great number of simultaneous connections with just a few I/O threads.

Archives

September 2008
M T W T F S S
« Aug    
1234567
891011121314
15161718192021
22232425262728
2930  

Other

Syndication