Is overloading a bad thing? Despite a wide variety of new languages supporting some form of it I continue to find articles that say overloading is bad. Worse, I find many articles that somehow think overloading operators is bad but that overloading functions is perfectly okay. more⇛

Each time I start a new project I find myself looking at the latest batch of frameworks. Lately those are web frameworks, such as CakePHP, RubyOnRails, perhaps JQuery, or any other of the thousands which seem to exist. Usually I end up using none of them. more⇛

Storing user credentials is one of the key roadblocks in creating a sessionless web application. Somehow you need to safely identify the user without storing data on the server nor allowing tampering on the client. more⇛

Welcome to BrainBrain Poker

more⇛

This is just my first entry in my blog. I will use this site to trace my poker exploits: starting from the penny tables to either WSOP victory, or when my funds run out. more⇛

Using reflection to simulate function pointers is truly awful in Java. There is not short form, you have to load the class, collect the signatures, pack parameters into an array, etc... Plus it isn't performant (significant overhead last time I checked). replies⇛

My last comment didn't get formatted and had a few small errors (the command classes would probably be inner classes of CardStack for example). more⇛

Oh, the haXe programmer or whatever it is has finished talking. I guess I should say something now. :) My main comment is that you don't have to put every Java class in its own file. That's only required, as far as I know, for public classes. more⇛

Some time ago the wealth of patterns was gifted upon the world of programming. At first they were beautiful, giving name and purpose to a once chaotic swirl of functions and data. Once embraced however, they swelled and engulfed all which we knew. more⇛

A link back to my experiment→. replies⇛