1.5. Раскройте скобки, употребляя требующуюся форму инфинитива, переведите.

1. Не seems (to read) a lot.

2. Не seems (to read) now.

3. He seems (to read) since morning.

4. He seems (to read) all the books in the library.

5. I want (to take) you to the concert.

6. I want (to take) to the concert by my father.

7. She hoped (to help) her Mends.

8. She hoped (to help) by her friends.

9. I hope (to see) you soon.

10. We expect (to be) back in two days.

11. He expected (to help) by the teacher.

12. The children seem (to play) since morning.

13. I am glad (to do) all the homework yesterday.

14. She seems (to work) at this problem ever since she came here.

15. I am sorry (to break) your pen.

1.6. Прочитайте и переведите отрывок из речи б.Гейтса.

Changes in Technology: Hardware and Software Advances

Now, this work is more ambitious every year. Developers can write applications that were not possible before. What's the reason for this? Well, there's really two key things, one is the advance in hardware, and the second is the advance in the software platform. And we can't underestimate the important role that hardware improvement plays here. After all, we can add exponential improvement in the performance of the microprocessor itself. The increasing clock speed has allowed it to do applications that simply wouldn't have been possible in the past. The unbelievable amounts of storage we have today, meaning that databases that record every click for millions of customers, and get data mined for deep patterns, those are now feasible on fairly low-cost systems. And so the sky is the limit in terms of empowering people, and writing very rich applications.

The microprocessor has gone through a lot of changes. We went from the 16-bit processor with a meg of memory to the 286 that gave us a 24-bit memory space, then to the 386 with a 32-bit memory space, and now we're in the transition to 64-bit. And that's quite soon because that compatibility, the ability to run the existing applications is fairly straightforward, at the driver level we need a few changes, but this will be probably the simplest address space transition we've made.

Looming after that, though, is an even more interesting challenge, which is the clock speed will not increase at the same rate it has over the last 30 years. It will largely stay the same, and the additional performance will come from having multiple execution units. And so the need to take programs and break them down into parallel execution units now becomes absolutely necessary to get the benefit of the exponential increase in transistors. We have an incredible amount of work at Microsoft to make the runtimes higher level, and to make it easy to take your code and write it in this parallel fashion. There will be a lot of discussion about this so-called "multi-core" revolution in how we make sure we're all doing the best to take advantage of that.

Beyond the microprocessor, we have the ubiquity of broadband, both through wireless, and wired connections, so that even sending high definition video is becoming very, very reasonable. We have the cloud services. Historically when we thought of the subroutine call, it was always on the same machine. But now with the pervasiveness of the Internet, and standards like the WS* standards, and runtimes, we also like Windows Communications Framework, the ability to call out the logic on another system that might be anywhere on the Internet is just like the subroutine call of old. And so leveraging services, leveraging code that other people have done becomes very straightforward. Calling into, say, Virtual Earth, where we've got all the maps, you can just have that be a part of your program, and it looks just like calling some work that you did. So the whole style of programming the ability to do powerful things with less lines of code is improving quite substantially.

Now one of the big changes coming that I think is most underestimated is the change in interaction. Throughout all these improvements, the way we interact with the computer has hardly changed. We had the graphics revolution that took us from the keyboard to the keyboard and the mouse, and it took the screen from character mode to graphics mode. But still it's that one person sitting there, primarily using the keyboard, and the pointing device to interact with the application.

There's a number of technologies that our research group and others have been working on for these decades that are now moving into the mainstream. It's a combination of software advances, and hardware power that allow us to bring new interaction techniques to a mainstream world. We collectively refer to these as natural user interface, but it's several different things. It's the idea of touch panel, and we gave a glimpse just last week of some of Windows 7, and the thing we chose to highlight there was this touch support, and how we built that in and made that easy for developers, and how end users will like that.

We've also got the pen capability that we're taking to a whole new level in terms of easy recognition, and how that is implemented in the hardware. I think of every student having a device that avoids the need for paper textbooks. The tablet device will let them take notes, record audio, connect to the Internet. It will be superior in every way, and yet it can't be purely keyboard based. It has to have this touch and pen as well.

We also have the speech recognition. On the phone today, if you call up information, that is a piece of software from a Microsoft group called TellMe that's taking those information calls, and we're building up the database, the speech model, of people in general, and people specifically to allow that speech interaction to be very rich. And as so we look out over the next decade, the way you interact with that cell phone, speech will be a major part of it.

The final natural interface piece, one that I think is perhaps the most important of all, is vision. A camera is very inexpensive, and putting software behind it that can tell what it's seeing allows you to have gestures, and movements, things that will be used in a variety of settings. We put out our Microsoft Surface product that actually uses a camera to project up onto a table surface, and there you can point with your hands, or put objects on the table, and the software sees them. It's being used in retail stores, and as that price comes down, that would be in every office, it will be in every home. Your desk won't just have a computer on it, it will have a computer in it. And your whiteboard will be intelligent. You can walk up, take information, expand it, point to somebody's name, start a teleconference with them, sit there and exchange information. And so natural interface really has a pretty dramatic impact on making these tools of empowerment, the personal computer, making them pervasive, and looking at them in new ways.

And so it's very exciting that this decade is when those things go from being really niche type things, to very much mainstream. And so building these things into the Windows platform, both on the phone, and on the PC, and having great tools for those will let you build these new kinds of applications.

If you look at applications, I really envy people who are starting today versus the early years of Microsoft. In those early days, you had to flip the switches, and there was no symbolic debugging, no performance analysis. Things have come a long way. The variety of languages that you can choose from, Visual Basic, which really evolved out of the very first Microsoft product, C#, F#, all these languages connecting in and sharing where appropriate in both the development and runtime environments. There is new concepts like the functional programming that will come along and perhaps be more interesting in this parallel environment that you can mix and match development that's done in different ways.

Now, the success of Microsoft is really due to our relationship with developers. From those early days of getting people to write applications in BASIC, to getting people to write applications for MS-DOS, to get people to write graphical applications for Windows, that's where we had our success. With things like Windows, it didn't happen overnight. There were many years of getting the system better, taking advantage of performance, improving the tools before that became a mainstream thing. We can say the same thing about Web Services, that took some time. The .NET approach, which is now a very mainstream thing, took time for that to be developed. And I would say the same for these new techniques of calling out to services, calling out using the rich new protocols, those are just now moving into the mainstream.

And so it's through dialogues like the ones we have here that we make sure that we're adopting our tools, and maintaining that great strength we've had with developers. We've done that by having a rich set of technical leaders inside the company that understand the needs, and make sure we're being very ambitious in what we do.

Now if we take the opportunity for developers, we can break it down across all the different pieces, and so I've broken this down into the four areas which are a pretty natural way of splitting it up, presentation, business logic, data access, and then the services that will be out over the Internet. We are innovating in each one of these areas, and giving people choices for each of these things, depending on the complexity of their application, so that the appropriate choices are there in every case.