jquery rewritten for mobile. smaller, faster.
CSS selector search/replace for html editors
Why doesn’t it exist? Quick, somebody, make an eclipse plugin. (and by ‘quick’ I obviously mean start a committee and work on it for a couple years. Gooooooo eclipse!)
This is a nice technique but I wouldn’t exactly call it elegant. Maintaining a copy of the content in the textarea just to set the height of the textarea is always a hack, no matter how clean the code is. This is pretty clean code though.
My first reaction was not positive. But after reading some more of the details and considering the alternatives, I think Dart could be a good thing.
At a glance, it looked like Google was just trying to make Java for the client side (which is funny considering that’s what Java thought it was for). But it’s not quite that.
The main thing is that the developer gets to decide how strongly typed something is. Which is nice. I wish JS was more strongly typed sometimes, and I wish Java was less strongly typed often. Being able to choose what’s right for the situation… WANT!
And writing in a language that was designed to have sensible class definitions, rather than having it grafted on by something like DojoToolkit (leaving behind all sorts of weird syntax quirks) would also be a boon.
I’m going to keep my eye on Dart.
Somebody mentioned this to me today. Looks interesting. WIll investigate.
Nice recap of using Compiled CSS for more than just some convenience functions. Some discussion in the comments about perf claim OOCSS is the best bang for the buck.
But the developer benefits of the technique described could outweigh the perf benefits of OOCSS in some situations.
The article describes a pretty little technique, though it does expose a certain gap in CSS/JS. An array of stylesheets, each containing an array of rules, is a terrible abstraction. It leads to the keyframes = stuff you see in the screenshot: generating CSS as text. It would be nice to have a dynamic css class definition library.
On the other hand, if the world had a dynamic css class definition library, the first thing to happen would be it’s horrible horrible abuse. Every event (hover, click, keypress) would cause the entire page to redraw. IE would just melt down. In short, pandemonium. So maybe it’s best we just continue to specify every browser’s styles in our static css files.
Nice talk on mongoDB.
