Popular @
Forum Controls
Spotlight Features
The Rich Engineering Heritage Behind Dependency Injection
Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.
NetBeans 6: Matisse Updates
NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
Introduction to Groovy Part 3
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Easier Custom Components with Swing Fuse
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Benchmark Analysis: Guice vs Spring
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
What Every Programmer Should See On YouTube
At 12:19 PM on Jan 1, 2008, Geertjan wrote:
Fresh Jobs for Developers Post a job opportunity
Josh Bloch on GWT
Any long chatty conversation with a leading developer in some area. Also, anything with Josh Bloch. For the perfect combination, see Voices That Matter: GWT - Conversation with Josh Bloch (52:31) and Effective Java Programming with Joshua Bloch (9:31) . Really good straight-talking stuff. (Funny how the first one features an interviewer with an 87-year old mother who seems to be something like a Java guru.)
Eric Arseneau on Squawk
Nice, smooth, polished, snappy presentations with jingly tunes are always good. On top of that, of course, there should be, if not deep technical discussions (preferable, in my book) at least some vaguely coherent high level content on some area you're new to, for it to be a winner. Squawk Java Virtual Machine (2.30) , by Eric Arseneau, is one that falls into that category for me. I like how he ends with his wish that one day your toast will pop up because Java told it to...Bill Pugh on Annotations
Bill Pugh's JSR-305: Java Annotations for Software Defect Detection made me think that every JSR should have a mandatory movie on YouTube. What better way to present the (often dense) material in a clear and transparent way? Not everyone is going to dig through the details of a JSR, but most people should be able to spare a few minutes to watch a movie that hits all the high points and gives references for further reading. What better way to start the week than to go through the latest proposals via introductions presented by the main advocates of the proposal in question?James Gosling on JavaFX
Another good search string on YouTube is "james gosling". One I watched recently is James Gosling on Sun JavaFX Mobile Gosling (1:51) . Always pithy opinions clearly expressed, with new high level insights and ways of looking at the Java world.Joseph Montanez on Learning Java
A seemingly endless list of Java programming movies is made available by Joseph Montanez from Gorilla 3d . Covers lots of Java programming basics, starting with Java 01: Hello World . Really relaxed, lowkey presentation, with a soothing voice.Any tips out there from anyone who's seen interesting programming stuff on YouTube (and why they're interesting)?
16 replies so far (
Post your own)
Re: What Every Programmer Should See On YouTube
Some more interesting ones for programmers (not all directly Java related):InfoNode - Swing components -- OctLight - Java game engine -- JCore - Java core components
Re: What Every Programmer Should See On YouTube
That's really cool. I wasn't aware of these videos on YouTube.Thanks, Geertjan.
Re: What Every Programmer Should See On YouTube
Yes, these videos are very fine, but it's diffcult to find these materials.Re: What Every Programmer Should See On YouTube
The best Joshua Bloch video I have ever seen (though not on YouTube) is "Effective API Design and Why It Matters": http://www.infoq.com/presentations/effective-api-designRe: What Every Programmer Should See On YouTube
For anyone claims Java can't creat good UIs... http://www.youtube.com/watch?v=p9ytsfaGWts(Now someone must be able to do something with the features shown).
Re: What Every Programmer Should See On YouTube
great post but the 2 min Gosling video was worthless.Re: What Every Programmer Should See On YouTube
There is another dedicated site especially for Java lovers inhttp://www.parleys.com/
which I covered in
http://geekycoder.wordpress.com/2007/12/31/excellent-video-podcasting-resource-for-java-junkies/
The video contents are excellent and cover interviews from Googlers, framework and library creators.
Re: What Every Programmer Should See On YouTube
Douglas Crockford (creator of JSON) has two great sets of videos on intermediate and advanced JavaScript:"An Inconvenient API: The Theory of the Dom"
http://yuiblog.com/blog/2006/10/20/video-crockford-domtheory/
"Advanced JavaScript"
http://yuiblog.com/blog/2006/11/27/video-crockford-advjs/
Re: What Every Programmer Should See On YouTube
Happy New Year to all !Here's a video I thought was pretty thorough, about closures:
http://video.google.ca/videoplay?docid=4051253555018153503
I haven't gone through all of this, but these series are interesting too:
http://video.google.ca/videosearch?q=Advanced+Topics+in+Programming+Languages
Re: What Every Programmer Should See On YouTube
Great tips for cool movies in the replies, thanks. Will be sure to check them out (esp. the Josh Bloch one about APIs). And I wouldn't say that "the 2 min Gosling video was worthless", I think it's pretty interesting, some of the off the cuff remarks he throws out there are always intriguing.Re: What Every Programmer Should See On YouTube
> Here's a video I thought was pretty thorough, about> closures:
> http://video.google.ca/videoplay?docid=405125355501815
> 3503
[warning to anyone to anyone who would complain that this thread has degraded from "good videos" to "closures", please move along now.]
I enjoyed the closures video, and for the first time, I think I see clearly where the pro-closures and anti-closures thinking diverges. Neal uses the ability to create your own "foreach" as an example of what closures are good for. He presumes that it would be a good thing for applications to be able to define their own flow control contructs like foreach. I think that flow control should stay in the domain of the language; I don't want to be able to define my own foreach construct, I want the language to provide it. If every application could define its own "foreach", then most applications will do just that, and every time you move to a new application, you'll have to learn how that application does it.
One thing that makes Java fundamentally different from C and C++ is that you can't define your own language constructs in Java because it doesn't have macros and templates. (Well, of course, you *can*, but no one ever would, as it would end up being so ugly).
So I'm glad we all had to wait for the Java "foreach" as part of the language. That way I can read your code. If we had had closures first, then I'd have to ask you "how does your foreach contruct work? Mine works like this...". Let's leave the metaprogramming to the LISP folks.
Re: What Every Programmer Should See On YouTube
> > Here's a video I thought was pretty thorough,> about
> > closures:
> >
> http://video.google.ca/videoplay?docid=405125355501815
>
> > 3503
>
> [warning to anyone to anyone who would complain that
> this thread has degraded from "good videos" to
> "closures", please move along now.]
>
> I enjoyed the closures video, and for the first time,
> I think I see clearly where the pro-closures and
> anti-closures thinking diverges. Neal uses the
> ability to create your own "foreach" as an example of
> what closures are good for. He presumes that it would
> be a good thing for applications to be able to define
> their own flow control contructs like foreach. I
> think that flow control should stay in the domain of
> the language; I don't want to be able to define my
> own foreach construct, I want the language to provide
> it. If every application could define its own
> "foreach", then most applications will do just that,
> and every time you move to a new application, you'll
> have to learn how that application does it.
>
> One thing that makes Java fundamentally different
> from C and C++ is that you can't define your own
> language constructs in Java because it doesn't have
> macros and templates. (Well, of course, you *can*,
> but no one ever would, as it would end up being so
> ugly).
>
> So I'm glad we all had to wait for the Java "foreach"
> as part of the language. That way I can read your
> code. If we had had closures first, then I'd have to
> ask you "how does your foreach contruct work? Mine
> works like this...". Let's leave the metaprogramming
> to the LISP folks.
I agree with you wholeheartedly but I think we should move this discussion to http://www.javalobby.org/java/forums/t104586.html
PS: I also think that the original discussion thread should have included both Neal and Joshua's presentation videos. I got a lot more out of them than out of the slides.
Re: What Every Programmer Should See On YouTube
> I agree with you wholeheartedly but I think we should> move this discussion to
> http://www.javalobby.org/java/forums/t104586.html
>
> PS: I also think that the original discussion thread
> should have included both Neal and Joshua's
> presentation videos. I got a lot more out of them
> than out of the slides.
I think we should let that thread ride off into the sunset in peace. Don't worry, I'm sure there will be another closures post on the main JL page within a week or two
Re: What Every Programmer Should See On YouTube
I agree also.On one hand I think it's cool to let you add syntax, or what looks like syntax, but people will want to impose their glorious concoctions and ways of thinking onto the rest of the world. Thanks but no thanks.
It should not take away from being able to have ordinary closures though.