It's silly that unbound events are initially null, so you need to do needlessly complex check to call them safely. Even more so if you want it to be thread-safe also.

It should have been trivial to either:

a. Initialize events to some dummy handler that does nothing (yeah, a tiny speed penalty, perhaps - doubt it would matter anywhere at all).

b. Add a little syntactic sugar to the event call to do the null check automatically and properly.

Note that you cannot actually use the null-check for any useful purpose anyway, as once-bound and unbound events may or may not be null AFAIK.

@Nelle said:

 I see no WTF here.

You have no Symantec products and therefore you have no problems.

 

But you are not protected either, even though it claims so. (Unless this was ironic, like "protected from Symantec products" :)

It's silly that unbound events are initially null, so you need to do needlessly complex check to call them safely. Even more so if you want it to be thread-safe also.

It should have been trivial to either:

a. Initialize events to some dummy handler that does nothing (yeah, a tiny speed penalty, perhaps - doubt it would matter anywhere at all).

b. Add a little syntactic sugar to the event call to do the null check automatically and properly.

Note that you cannot actually use the null-check for any useful purpose anyway, as once-bound and unbound events may or may not be null AFAIK.

Let me introduce you to the FPU status word:

And, most of all, why would anyone even want to plot this on log scale..

@arh said:

Yes, he was non-native. But he was still way beyond anything acceptable, often it was so bad it was difficult to comprehend what he was trying to say.

I've had a CEO that was worse than this in his native language (which was not English). Fortunately he compensated any difficulties in understanding by marking all mail "Very important" in Outlook and using three exclamation points after every sentence!!!

@shimon said:

Yep, they think of statuses as some stages through which $foo goes, one by one, sequentially and chronologically. But my immediate task which made me open this can of worms, is add a new status in the middle. I'm not even mad...

Simple! Just make the new status 4.5. This method has infinite extensibility!

@TheCPUWizard said:

 Not as useless as it seems....The context menus are associated with accelerator keys. This means that automation of keystrokes can easily get to those areas; something that is difficult to do when mouse only. Yes, a botton (with accelerator key) could do the same thing, but would be more "in your face" for something that only a few users would utilize.

Not only this. It also shows the current shortcut key (such as ctrl-L for path bar) for each function. And if you enable editing shortcuts, it also allows you to set the shortcut by hovering over the item and pressing the key. Quite discoverable and convenient alternative to the usual huge list of shortcuts in a settings dialog.

And I was hoping for Spectate Swamp Media Search.. (how does SQL Management Studio shorten to SSMS?)

@Maciejasjmj said:

Filed under: Who needs any other datatype?

You might laugh, but some people take this seriously. Sure, it might be a beginners' language not designed with performance in mind, but arrays as strings... fuck.

TCL takes this even further: in this piece of code:

if $foo {
   puts "Hello!"
}

The if is actually a command that gets called with one argument: "$foo { puts "Hello!" }"; it then splits that into two pieces, and executes the second if appropriate. Why yes, executing strings is of course a fundamental part of the language :)

@El_Heffe said:

@Smitty said:

Out of genuine curiosity, is it faster/easier to find what you want among 400 tabs instead of organized bookmarks?

I often wonder the same thing. Everyone has their own way of doing things but more than 20-30 tabs has always seemed crazy to me.

When those 400 pages are something you need this week but probably never again, it makes perfect sense to have them in tabs. My previous job involved reading a lot of various documentation due to quick "help this guy figure this thing out" tasks. Treestyle tabs is great.




I guess a sensible history manager could be equally good. One that could show the path you have wandered and bring you back to the point you were reading.

@Soviut said:

Put it this way, soon software engineers will actually become relevant. The same way a guy has to sign off on the fact that a bridge slated to be built isn't going to collapse, we'll start seeing engineers who sign off on software safety in places other than manufacturing and nuclear plants.

Unfortunately, the way it goes in software development world, I bet people would just get fired if they didn't sign off a pile of crap. So the only point of the procedure would be to shift blame from the company to the individual developer.