Java runtime intranet installation? [found it, sort of]
-
Phil Martin... wrote:
I am referring to java.util.concurrent
Ah, I think that was added after my Java stint. When I started there were all sorts of things missing like the sort interface. What is it, like IComparable, ISortable or something? I never understand everyone whining about lack of library encapsulation. When there was no sort interface in Java I just wrote my own. It took very little time and after it was added to the SDK it looked very similar to the one I did so porting was minimal. I think for many novice developers, they started after all these large libraries already existed. They never knew the days when you wrote your own libraries so when a library doesn't have some feature they get stuck, like a pig at an empty trough, they starve because they aren't hunters.
Yeah, I started at around the same time. It's been really exciting watching it grow over the years. And whining - yes, I feel the same. HAve you talked to any graduates lately about how they would do text searching? or sorting? or any sort of container? I'm not sure what it is like in the rest of the world, but in this part of australia, it isn't so promising. But then again, it does allow many people to solve many problems without having to learn all the inner workings of the magic libraries. So it isn't all bad. I'm really looking forward to writing some of these structures in C#, it'll be fun! But the concurrent library, I recommend you read over the javadoc, it is really cool stuff. It has a been around for a while now (couple of years at least), but some of the highlights for me are: Executors - basically a bunch of smarter thread pools, all based off the one interface. So if you write your threading calls to all start using an executor interface, you can try out different scheduling strategies with a minimum of fuss. Callable, Future and FutureTask - Similar to async delegates that return values, but a fair bit more verbose :( But very very cool though. It made a very big deal to heaps of the stuff I was working on at the time. The simple feature of having it start some work, and block whe you call get() (if you wanted it to) simplifed things soooo much over wait/notify code. Futures also tied into executors very well, as you could use different mechanisms fo shceduling the Future onto different threads. CyclicBarrier - handy way to have all threads stop at a common road gate. CountDownLatch - my favourite. Easy way for one or more threads to block until some other threads do some work. Sure it's lazy, but soooo much simpler than wait/notify. Exchanger - It allows two threads to block at a point and then swap objects. I didn't use this one much but it would be very handy to have in the work I'm doing in c# now. I just have to come up with a way to do it reliably in c#, and I'll be laughing. CopyOnWrite containers - very handy to have in some situations. And very hard to write correctly yourself.
-
stickershock wrote:
Obviously when it becomes a real issue,..
Ummm it already is. Apparently you can't read or you don't understand the subject matter of the article. I'm shocked... no really... I am. :zzz:
led mike wrote:
Ummm it already is. Apparently you can't read or you don't understand the subject matter of the article. I'm shocked... no really... I am.
For whom? yeah, for some big math crunching, let's figure out the trajectory of the next mission to the zathar galaxy. for most of the real world stuff, the difference of 4 times faster is the difference in 250 milliseconds or one second. Let's face it, the guy using C# to write apps is probably fast and dirty than gee, sqeeze the most out of these 6 processors I have. If it's mission critical, shouldn't you be developing under unix? :-)
-
stickershock wrote:
Obviously when it becomes a real issue,..
Ummm it already is. Apparently you can't read or you don't understand the subject matter of the article. I'm shocked... no really... I am. :zzz:
Dude, you got 4000+ posts here, you should be writing a book instead of software :-) You could call it my c++ is bigger than yours :-) I don't care to get into a pissing war with someone who has soooo much freee time.