James Gosling Q&A session
summary
Says Java would drop the java.awt.event model, regrets not shipping generics and lambdas sooner, and warns value types require multiple PhD theses because getting performance and layout right is hard. Talks about production tech: uses ZooKeeper as a database, NetBeans, GlassFish/Jetty, and prefers JUnit tests for every feature. Describes current work building ocean robots with robust collision avoidance that survive storms, notes libraries drive cloud fit more than a slimmer JVM, and advises keep learning and have fun.
AI-written summary · about
chapters (33)
- 0:00Introduction and welcome
- 1:18Changes James would make to Java
- 3:26Java's evolution and future direction
- 7:44Future of programming and IT automation
- 9:56Easter eggs and fun in programming
- 11:22Java's advantages over other languages
- 16:27Java's portability and ecosystem
- 17:30Features James misses in Java
- 18:55Java's community-driven development
- 20:26Working with Liquid Robotics
- 23:36Challenges in current robotics project
- 24:24Tools and technologies in use today
- 27:36Personal dreams and aspirations
- 28:06Career advice for developers
- 29:08Audience Q&A begins
- 29:30Alternative JVM languages
- 31:38Java for cloud and microservices
- 34:28Java's cloud optimization
- 35:54Work-life balance in tech
- 37:01Hardest technical problem solved
- 40:01Testing practices in Java
- 41:05Java syntax and Scala comparison
- 44:20Checked vs unchecked exceptions
- 45:52Motivation and lifelong learning
- 46:57Balancing fun and responsibility
- 48:03Hiring needs at Liquid Robotics
- 48:51Java's competition and future
- 52:50Early programming journey
- 56:08Null pointers and engineering trade-offs
- 59:23Development process and management
- 1:03:48Dealing with burnout
- 1:06:18Oracle vs Google lawsuit impact
- 1:07:45Closing remarks and thanks
