51–60 of 84 posts
I hate to be pedantic but that should be "rendered entirely using CSS". The logos were designed by their respective designers using whatever tools.
Its confusing as well. Before clicking the link I thought they would be icons (newer ones, naturally) which were designed from scratch using CSS.
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry! It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post…
Not really.
A CSS logo would be useful for performance issues and overall page rendering speed. A CSS animated logo, such as the Atari example, even moreso than a Flash / JS counterpart. CSS renders more quickly than images, and definitely more quickly than embedded Flash.
Earlier quoted context omitted.
"Semanticallity" (sic), wrt templates and css is not all it's cranked up to be. It's just voodoo thinking on the part of web designers that were taught about it circa 2000. And it basically comes from the misunderstanding that the html page is the data, when it's really just a RENDERING of the data. The data is what's on the DB or storage system --and that, yes, has to be semantically stored and attributed. The templ…
The rendering of data is data itself. We structure databases semantically for backend developers. Why shouldn't we structure display markup semantically for frontend developers?
Only if you have a poor system of sharing data, one that necessitates the rendering to be the data. Why put that inflexible requirement upon yourself? We have plenty of renderings that are not supposed to be data (i.e mechanically readable) by themselves, from graphical UIs to paper printouts.
> We structure databases semantically for backend developers. > Why shouldn't we structure display markup semantically for frontend developers?
Because the target audience of the display markup is not "front-end developers", it's our website viewers. And they could care less how we structure our display markup.
A truly intelligent system of content/display separation wouldn't use "semantic markup" and such nonsense, but true separation, i.e multiple types of data output.
Take accessibility for example. What's good for a web browser is not equally good for a screen reader.
The optimal path would be not to share the same display markup, but to create a specialized screen reading output that can leverage the same underlying data.
We only do a half baked work when we add media css, alt attributes and such to "semantic display markup". It's a leaky abstraction.
And then you go and implement an interface to the website as an Android or an iPhone app, and suddenly the "semantic display markup" is useless, you do it with custom queries and native controls. Or you go an implement a voice operated interface to the site, like voice xml, and the "semantic display markup" is of no use here too.
Heck, even when we output something as basic as an Atom/RSS feed, we don't get to reuse the "semantic display markup", we output a customized feed.
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry! It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post…
This is really impressive. I've never seen something like this in pure CSS. If anyone knows of anything this impressive, please post a link to it.
Made something similar a while ago: http://sy0t0s.bplaced.net/demo/hero/ - Apple logo http://sy0t0s.bplaced.net/demo/tubes/ - Nixie tubes http://sy0t0s.bplaced.net/demo/opera/ - Opera Browser in your browser I have more, but don't want to spam links. If you want to see more you can crawl through the /demo/ folder on the page. Most of them are experiments with CSS3, javascript and html5.
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry! It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post…
If you rake your memory you could probably find points in time when you were working on something you really enjoyed, even though you had other good ideas that would better benefit the community. I know I certainly have been in that situation.
Maybe a dumb question from someone who isn't proficient with CSS -- but if you can render these as vector images, can't you autogenerate the CSS for them? And the reason I even ask is I feel like I could draw all of these logos pretty well with Illustrator, but couldn't just sit down in a text editor and make these logos with CSS.
In theory, yes, in practice I don't know if such converter exists. But SVG should be a better option anyway (it doesn't work in <IE9, but on the other hand, this probably won't either).
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry! It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post…
It's also completely and totally useless Not really. A CSS logo would be useful for performance issues and overall page rendering speed. A CSS animated logo, such as the Atari example, even moreso than a Flash / JS counterpart. CSS renders more quickly than images, and definitely more quickly than embedded Flash.