jeffyaowei的专栏

We are currently facing an avalanche of data, and this data contains many insights that hold the keys to success or failure in the data-driven world. Next generation Hadoop (v2) offers a cutting-edge platform to store and analyze these massive data sets and improve upon the widely used and highly successful Hadoop MapReduce v1. The recipes that will help you analyze large and complex datasets with next generation Hadoop MapReduce will provide you with the skills and knowledge needed to process large and complex datasets using the next generation Hadoop ecosystem.

想在项目上用上extjs的人有福音了,这个包含目录,是完整版!

关于ActiveX的经典书籍！虽然现在java，.Net等语言横行天下，但是开发基于web的软件，有时还是要用到activeX等知识！

Agile, agile, agile, Ruby, Ruby, Ruby. It seems like every conference you go to these days<br>talks about either agile or Ruby. Those are the big buzzwords in the industry. Everywhere<br>you go, that’s all you seem to hear. And as my friend Rob Stevenson says, that’s all he<br>wants to do. In fact, the only books he reads now are Ruby books. The real question is,<br>why? Personally I think it’s because he likes a limited selection of books. But the other<br>reason is, Ruby is fun. It’s fast, it’s cool, it’s new, and it makes development a pleasure.<br>And computer-savvy developers seem to love anything new. I honestly get a bit tired of<br>everything coming out calling itself agile. Its such a key word these days that I am just<br>waiting for recruiters and sales managers of consulting companies to start telling their<br>clients they need agile developers.<br>The real question has to be, what is meant by agile? What is needed to make something<br>agile? Agile development keeps the ease of development while still making the code<br>clean. And I think that’s what every user is really looking for. It’s why Ruby is popular, and<br>it’s the attraction to Trails. There is so much work going into plumbing these days that it’s<br>almost overwhelming. Every team seems to want to reinvent the wheel. Larger companies<br>have extended frameworks such as Apache Struts and are using it for what they think<br>are specific needs. Sometimes this is useful; other times all they have done is added a<br>layer of confusion.

Since JavaServer Faces first arrived on the Internet technology stage as the new standard<br>for building Java-based Web applications, it has gained significant attention from the Java EE<br>Web development community.Many developers are excited that they can use the standard<br>JavaServer Faces HTML Basic RenderKit to create HTML-based Web applications, much as<br>they did in the past with other technologies, such as Apache Struts. However, this is only the<br>tip of the iceberg—the true power of JavaServer Faces lies in its extensible component model,<br>which allows you to go far beyond those humble HTML beginnings.<br>Based on the recent surge in demand for improved usability in Web applications, it is<br>understandable that the hottest topic at the moment is Rich Internet Applications (RIAs) and<br>how they offer distributed, server-based Web applications with a rich interface and the interaction<br>capabilities of desktop applications. Although RIAs hold significant promise, they still<br>have issues with compatibility, portability, usability, and reusability. Many Web application<br>developers are struggling to keep up with new RIA frameworks, both open source and vendor<br>specific, as they appear on the market. What is needed is a standard way of defining an RIA<br>regardless of what RIA framework is being used.

Working with technology is a funny thing in that every time you think you have it cornered<br>. . . blam! Something pops out of nowhere that leaves you at once both bewildered and excited.<br>Web development seems to be particularly prone to such surprises. For instance, early on, all<br>we had to deal with was plain old HTML, which, aside from the never-ending table-wrangling,<br>was easy enough. But soon, the simple web site began to morph into a complex web application,<br>and accordingly, scripting languages such as PHP became requisite knowledge.<br>Server-side development having been long since mastered, web standards such as CSS and<br>XHTML were deemed the next link in the Web’s evolutionary chain.<br>With the emergence of Ajax, developers once again find themselves at a crossroads. However,<br>just as was the case with the major technological leaps of the past, there’s little doubt as<br>to which road we’ll all ultimately take, because it ultimately leads to the conclusion of clicking<br>and waiting on the Web. Ajax grants users the luxury of accessing desktop-like applications<br>from any computer hosting a browser and Internet connection. Likewise, developers now<br>have more reason than ever to migrate their applications to an environment that has the<br>potential for unlimited users.