Language:
switch to room list switch to menu My folders
Go to page: [1] 2 3 4 5 ... Last
↑↑↑ Old messages ↑↑↑            ↓↓↓ New messages ↓↓↓
[#] Tue Apr 14 2009 07:59:24 EDT from dothebart @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

and... the moaning about the problem:

http://joshua.schachter.org/2009/04/on-url-shorteners.html



[#] Tue Apr 14 2009 13:26:50 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

It would seem that if a webmaster is aware of a need to make their URL's short ... they would fix the problem not by building in a meta aliasing framework, but rather by simply *making* *them* *short* to begin with.

[#] Tue Apr 14 2009 22:31:17 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

yeah.
And moaning... lets see... why aren't they whining about phone numbers? Phone numbers have been around a lot longer than urls, and whereas they used to be useful, when they included letters for location, the all number 10 digit sequence is pretty tinyurlish.

[#] Wed Apr 15 2009 09:22:38 EDT from dothebart @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

yes, I'm pretty happy to remember my own phone number plus some of the old style short ones still arround...but thats it.

I used to remember around 20 phonenumbers I frequently used before the ISDN times. (well... my parents just had a pulse dial phone, no way to store numbers ;-)



[#] Wed Apr 15 2009 15:15:26 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Everyone's got speed dial now, and a lot of people change phone numbers frequently enough that they're not worth remembering.

It's possible that in the future, phone numbers could go away completely and be replaced by SIP addresses, which look a lot like email addresses.

Are you ready for SPIT? (SPam over Internet Telephony)

[#] Mon Apr 20 2009 18:37:48 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Cute! He did a really good job. I'd have omitted the mini LCD screen and put in a touchpad, and made the touchpad emulate a KoalaPad. That would have been even cooler.

[#] Mon Apr 20 2009 20:14:01 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

http://www.ibm.com/developerworks/websphere/techjournal/0904_chang/0904_chang. html

bwahahahaha.
they've finally come full circle and are now doing things the way we did in the 90's.

[#] Wed Apr 22 2009 11:12:56 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Wow, it's very surprising that they did this without using XML as the file format.

It would have been amusing if they used .INI file format :)

[#] Thu Apr 23 2009 07:56:47 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Wow, it's very surprising that they did this without using XML as the

file format.

It would have been amusing if they used .INI file format :)

They're replacing the myriad of xml files they currently use now, and that's the point, I think they ARE using the ini file format.

[#] Sat Apr 25 2009 09:24:47 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Weird. XML is a bit richer in terms of what it can express (multiple levels of nesting, etc) as well as more machine-readable. As everyone knows, I'm no fan of making everything XML, but I can't see why this one would need to get switched back to something else.

[#] Sat Apr 25 2009 17:35:47 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


Well, at a guess, on a Windows machine, INI files can be read via system calls, which grants you the ability to make changes to INI files from different processes without risk of fucking up the files (two processes trying to write to the same INI file at the same time).

You have no such protections with XML unless you go to an awful lot of trouble to use a single process to handle the manipulations... and even then, I'm not sure how robust any process could be in writing to an XML file format.

[#] Sat Apr 25 2009 21:16:31 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

knows, I'm no fan of making everything XML, but I can't see why this
one would need to get switched back to something else.

You should see some of websphere's config files.
Also, ini's are just dandy with dot notation namespaces.

websphere.version.2.suck = yes
websphere.version.3.suck = more

and so on...

[#] Sun Apr 26 2009 22:00:44 EDT from LoanShark @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


Oh god no, never look at WS's config files. If you try to edit them by hand, you are so totally screwed. Aren't they all binary *anyway*?

[#] Sun Apr 26 2009 22:39:37 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

One of the nice things about dumping config files or whatever into XML is that you don't have to worry about them being in an architecture-specific format, which is what you get with just writing structs out to disk.  On the other hand, you don't need XML for that; any text-based format will do.

Hmm ... since we're talking Java here, what format do you get when you use the Java serialization API?  Is it portable?

 



[#] Mon Apr 27 2009 14:18:48 EDT from LoanShark @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


It's a binary thing, but it's portable.

[#] Mon Apr 27 2009 14:19:33 EDT from LoanShark @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


It's portable in the architecture-independence sense, but it can be brittle if you subsequently change the layout of the class that was serialized.

[#] Mon Apr 27 2009 17:05:40 EDT from dothebart @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

 

Hmm ... since we're talking Java here, what format do you get when you use the Java serialization API?  Is it portable?


You know, except for compile once, debug evrywhere, its portable ;)

it doesn't know byteorder unless you use JNI.



[#] Mon Apr 27 2009 21:07:40 EDT from LoanShark @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


the whole "compile once, debug anywhere" thing is kind of unfair to Java. Java doesn't really suffer from that problem in a major way unless you are using AWT/Swing.

Go to page: [1] 2 3 4 5 ... Last