JavaOne Is Over, But I Didn't Write a Thing Until Now

JavaOne is over, but I didn't write a thing. Getting home at midnight the last few nights, I'd think "Do I want to write a blog entry?", and I'd think "No, maybe tomorrow." I worked the show floor for three days, so I didn't get a chance to hear any keynotes or presentations, and I felt a little behind the times when people would ask about some of the interesting announcements.

Still, this was a great three days to talk to developers and to meet Sun employees from all over the world. So many voices on the phone, it's really nice to finally meet people face to face. During one conversation, the person said they needed to talk to David Lindt about something, and I thought for a moment, gee that's me. Turned out to be a very productive conversation since we were all there, including me.

The booth layout for JavaOne was really nice. Clusters of four groups, and we had Sun Studio 10, NetBeans 4.1, Java Studio Creator, and Java Studio Enterprise in our cluster. Thsi made it really easy to send developers to the right booth. It was also nice to see the people from Prague at the NetBeans booth, which was right next to our booth.

One of the more interesting conversations I had was with the people at the Global Education booth. We got to talking about how computer science and engineering students learn about developer products, and how we can get more information to students. The SDN Student Developer Program tells about resources for students, internet gamers, and researchers.

Busy couple of days, and I need to think about what we learned from talking to the developers that stopped by the Sun Studio booth. JavaOne isn't the main show for a product containing the C, C++, and Fortran compilers, but we found a number of people that needed to call legacy C and Fortran codes from Java apps. There is a connection between the languages, and we just need to communicate the relationships between the products and languages. A lot of times, it's easy to get into this debate of Java versus native languages, but it doesn't have to be either or. Developers use Java, C, C++, or Fortran, based on their requirements. Where it makes sense to use Java, then use Java. Where it makes sense to use C++, then use C++. Lot of important legacy Fortran apps out there, so don't write off Fortran yet. As technical communicators, we need to give you the information you need to do your job efficiently and with the right languages and tools.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

dlindt

Search

Top Tags
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today