Web socket is a technology developed to establish a bi-directional communication between client and server, over the web. It works on top of TCP and hopefully will render hacks like long polling obsolete. It’s supported by all modern browsers with 2 exceptions – opera mini and the default android browser (chart can be found here).
CSS has been around for a while and will stay for a while longer and although I think it’s a good and working ‘language’ it has a few pitfalls – the biggest one being the lack of ability to reuse certain parts. Take colors for example, when you want to style a site you need to repeat the color declaration everywhere you want to set it, so when you change your mind, the only way to implement the changes is search and replace. Now that’s not that bad when you have a small site and one css file, but when the number of files grows, that problem grows along. So what can we do?
So you have a requirement – supply the possibility to create and edit rich formatted text in a web application. Seems pretty straightforward – use a ready editor and you’re done.
Now, add some constraints to that, like – the editor needs to be dead simple because the target user does not care about all that semantic stuff (that’s your job), it needs to perform well and be as intuitive as it gets.
This is a pretty valid requirement and in todays web is pretty common, but as it turns out, there isn’t a lot of maneuvering space here.