Hollywood Hacker hacks wikipedia
-
Wikipedia hacking 2 - Uber Hacker Series #1 – 07:14
— Hollywood HackerJust realistic enough to fool a non-technical person, but full of injokes and little references for us. I approve.
-
Executable name in CamelCase... It hurts on the inside a little.
-
not as bad as someone calling PascalCase camelCase.
-
SHOUTY_SNAKE_CASE<lol
-
Wikipedia says you're M$ fanboy.
-
BeautifulCase
-
-
Wikipedia knows all and sees all.
-
I suppose you have them mixed up.
.getName() is Java and .GetName() is C#.
-
-
I suppose you have them mixed up.
Maybe he's naming classes? Java convention there is ThisCaseStyle. Though that also holds true of most of the C# code I've seen too.
-
Though that also holds true of most of the C# code I've seen too.
Yeah, I don't think I have even seen a language where the standard would be to camelCase classes. Maybe for some nested private ones, but I doubt even that...
camelMethods if public are definitely Java, though.
-
OK, I thought you were just deliberately going for the labeled bait and this would be done. But you got replies going more into the differences in style by taking it, so bravo.
-
Yeah, I don't think I have even seen a language where the standard would be to camelCase classes. Maybe for some nested private ones, but I doubt even that...
It might happen in Tcl, where there's a strong tradition of starting public command names (i.e., for functions, operations, all that sort of stuff) with lower-case letters, though there's quite a bit of upper-case usage there too. The language itself doesn't care at all; it's all loose convention and lazily trying to avoid wearing out the Shift key. :D
-
It could be worse. It could be Ada_Case.
-
Or have .exe extension!
-
I think my brain hurts from just seeing that.
Or maybe I went to the YouTube link, read the comments and looked at the related videos list. That's probably what did it.
I think I'm going to go hack layers eight and nine of the OSI model with vi now.
(Sadly, my reference material only lists the first seven layers. Perhaps it needs to be updated:
)
-
Port 8080 (double http)
-
It's the only way you can reach the web 2.0.
-
I never understood 5th and 6th layer in the standard OSI. I prefer the simplified 4-layer IP stack, it makes sense.
-
I never understood 5th and 6th layer in the standard OSI.
The session layer talks about semi-permanent sessions between applications, and the presentation layer talks about how to transfer the meaning of a message between applications and not just some byte sequence. In the TCP/IP world, some of these things are done at the transport level (TCP has session-like features) and much of the rest is done at the application level.
Though it's arguably the case that if you were moving XML messages over HTTP, you'd have the applications working on the XML infoset, delegating to a presentation level that handles serialisation to XML and deserialisation back, which in turn in the session layer uses cookies to maintain an auth context. It doesn't really do to worry about it all too much though; it's just a model.