nicode is an international not-for-profit organisation that started in the 1980s as an effort to "unify" the "codes" for textual characters used in the computing industry. By "code", I just mean a number. Computers only understand numbers, and so you need to tell the computer which number refers to the letter "a", which one refers to the letter "b", etc. so that you can visualise them on a computer screen (otherwise you'd be readingght now). So the problem in the 1980s was that there wasn't a universally agreed-upon set of "rules" for which number refers to which character, and so every programmer was writing their own set of rules, and whenever their programs interacted with programs written by other programmers, they'd need to make specially designed "translators" to allow the programs to communicate. Unicode sought to solve this by creating an international standard - meaning that everyone would be using the same number-to-letter "rule book"

nicode is an international not-for-profit organisation that started in the 1980s as an effort to "unify" the "codes" for textual characters used in the computing industry. By "code", I just mean a number. Computers only understand numbers, and so you need to tell the computer which number refers to the letter "a", which one refers to the letter "b", etc. so that you can visualise them on a computer screen (otherwise you'd be reading now). So the problem in the 1980s was that there wasn't a universally agreed-upon set of "rules" for which number refers to which character, and so every programmer was writing their own set of rules, and whenever their programs interacted with programs written by other programmers, they'd need to make specially designed "translators" to allow the programs to communicate. Unicode sought to solve this by creating an international standard - meaning that everyone would be using the same number-to-letter "rule book"

nicode is an international not-for-profit organisation that started in the 1980s as an effort to "unify" the "codes" for textual characters used in the computing industry. By "code", I just mean a number. Computers only understand numbers, and so you need to tell the computer which number refers to the letter "a", which one refers to the letter "b", etc. so that you can visualise them on a computer screen (otherwise you'd be reading ght now). So the problem in the 1980s was that there wasn't a universally agreed-upon set of "rules" for which number refers to which character, and so every programmer was writing their own set of rules, and whenever their programs interacted with programs written by other programmers, they'd need to make specially designed "translators" to allow the programs to communicate. Unicode sought to solve this by creating an international standard - meaning that everyone would be using the same number-to-letter "rule book"

ven still, there's a high learning curve before you can build a proper application. That's because you need to learn about client-side routing, page layout, and so on. If you'd like to perform server-side rendering for faster page loads, things can become even more difficult.

So, we need something simple but customizable.

Think about how webapps are created with PHP. You create some files, write PHP code, then simply deploy it. We don't have to worry about routing much, and the app is rendered on the server by defaulven still, there's a high learning curve before you can build a proper application. That's because you need to learn about client-side routing, page layout, and so on. If you'd like to perform server-side rendering for faster page loads, things can become even more difficult.

Think about how webapps are created with PHP. You create some files, write PHP code, then simply deploy it. We don't have to worry about routing much, and the app is rendered on the server by defaul

All the Things

javascript fundemntals

the this value

es6 news

javascript the hard parts