Sorry about that. It should be live again. Not sure for how long though... We (studiomoniker.com) are quite busy with other projects and we don't have to time to properly support this project. Hopefully we can make it more HN proof in the future. The project definitely deserves it!
One of the creators here: we were very much caught by surprise by the sudden interest in this project. (A year after launch) We are currently counting stock and updating our shop for a better experience (like not defaulting to an out of stock color for a product)
Interesting! I hadn't found anybody else doing this back when I "typeset" my thesis in a subpixel font. I even build my own tool in Processing for designing the font. A part of my graduation was making an installation of our thesis for the exhibition so people could "read" my thesis. I build an installation with a LCD screen, a USB microscope and a projector. You can find it over here: http://www.thomasjonas.nl/project/a-new-aesthetic-for-text (sorry mobile users)
The thesis was about how the aesthetics of tools/technology can influence the aesthetic of art, so I thought this installation was a pretty fitting idea.
I really hope it won't happen and we've learned from the past, but is it possible we'll soon be transpiling for different browsers and using conditional comments for loading the right version?
I was just going through the list of possible interview questions (http://www.frontendhandbook.com/practice/interview-q.html)... Am I the only (mediocre) Front-end dev that has problems answering these questions? I always start doubting myself when I don't know the answer to basic questions like "Are there any problems with serving pages as application/xhtml+xml?". All these questions ring a bell somewhere, but I have no idea how to turn that into a good answer at an interview... Whenever I run into problems I just try to fix them... I'd like to think that's more important than this factual knowledge.
> "Are there any problems with serving pages as application/xhtml+xml?"
That was more relevant when XHTML was still vying to be the future of markup on the web. The issue was that the XHTML content type mandated a strict XML parser that hard failed if your markup wasn't well-formed, whereas HTML is more lenient. With XHTML, it was easy for a single stray closing tag to kill your entire site. This was an especially common concern if you allowed markup in, say, comments.
Nice way to learn React! For me the tasks could be a bit more clear, especially the first time when I was looking for what I had to do. But I'll definitely try to learn some React this way!
I've always had problems with focusing on application windows. Recently I started using Better Touch Tool to fully maximize windows (when clicking the green button), but that might be a bit of a overkill on a 27" iMac. Maybe this app will work better. Thanks!
Very nice to see more projects where algorithms and art come together. This post also reminded me a bit of this project where a face detection algorithm and a psuedo-genetic algorithm are combined to create faces out of noise: http://lbrandy.com/blog/2009/04/genetic-algorithms-evolving-...
