Link

I would have to agree

There are some harsh criticisms in this post about certain aspects of the HTML5 spec.

I would have to agree with Luke Stevens because he mentions that adding in elements like ‘sections’ have created confusion for many people, including me.

I googled ‘purpose of section tag’ and a lot of what is returned is individuals such as my self trying to make light of the the purpose of such a tag. ‘In all honesty why is it there?… isn’t it just a div?…’ These are all the sorts of comments left by individuals. 

When i first saw the new tags at first thought i was dreading all the changes i would have to make to my HTML and CSS, all my navigation areas will now need to be wrapped in nav tags etc…

Again more confusion, but after some more reading i came to the conclusion you don’t need to change anything, in fact most of what we have written will last for years to come. 

 

Beautify JavaScript + JSONP = HappyFamily

If you are using JSONP to do cross domain grabbing of data to show on a page often you will want to see the raw response in your browser. The issue with this is it can get confusing because the browser just dumps the JSONP response to the window.

Enter jsbeautifer

All this website does is format your JavaScript to be more readable. I commonly use this site with JSONP responses and for all the times i have used this page I am glad it’s free.

Have a try, grab some JavaScript, JSON, etc.. and paste it into the window and click beautify. 

Enjoy

Really handy, saved me writing one myself for my XML Importer in SSIS

Chris O.'s avatar foreach(bill) paywith(skill);

kick it on DotNetKicks.com

MIT LICENSED

Ever get a System.Xml.XmlException that says:

“Hexadecimal value 0x[whatever] is an invalid character”

…when trying to load a XML document using one of the .NET XML API objects like XmlReader, XmlDocument, or XDocument? Was “0x[whatever]” by chance one of these characters?

0x00

0x01

0x02

0x03

0x04

0x05

0x06

0x07

0x08

0x0B

0x0C

0x0E

0x0F

0x10

0x11

0x12

0x13

0x14

0x15

0x1A

0x1B

0x1C

0x1D

0x1E

0x1F

0x16

0x17

0x18

0x19

0x7F

The problem that causes these XmlExceptions is that the data being read or loaded contains characters that are illegal according to the XML specifications. Almost always, these characters are in the ASCII control character range (think whacky characters like null, bell, backspace, etc). These aren’t characters that have any business being in XML data; they’re illegal characters that should be removed, usually having found their way into the data from file format conversions, like when someone tries…

View original post 602 more words

Very interesting

thecodingbrain's avatarthecodingbrain

After much procrastination, I am finally posting the results of my research into how the frequent use of computer programming languages affect the brain.

As followers of the blog will remember, after reading theories about how learning languages affect the brain, I wanted to know whether computer programming languages also affected the brain. With a few notable exceptions (e.g. Murnane, 1993) most research about the cognitive effects of computer programming seemed to have focused on programming as a problem solving rather than a linguistic activity. If computer languages were indeed languages, I thought that it would make sense for them to affect the brain in a similar way to other languages.

This is quite a big subject, so I honed in on bilingualism. If computer programming languages are languages, then people who spoke one language and could programme to a high standard should be bilingual. Research has suggested that…

View original post 515 more words