Amazing, history does repeat itself. One of the companies in my batch (S07) was iJigg (https://www.crunchbase.com/organization/ijigg), which had the 2007's version of this interface: single upvote, player, and all. It did well and then petered out as many hyper-niche apps did at that time.
There is also https://hypem.com/, which focuses on music posted by blogs but is otherwise fairly similar. It helped me discover a lot of cool music back in the day :) Nowadays Spotify's music discovery algorithm is often "good enough", though.
If we think about the technology available around 2007, a crowd-sourced music recommendation system is basically what I would expect. No offense, that’s just what we had at the time. The Netflix prize wouldn’t come out until 2008. Pandora’s Music Genome project was perhaps ahead of its time but mostly manual (20-30 minutes per song!).
Today, we would usually use automatic song similarity technologies to recommend songs. The reason is pretty clear: popularity-based systems don’t know anything about the songs they recommend. They don’t know anything about you. They only know metadata about the song, that a certain number of people liked a song, essentially throwing away half of the information in a user-song tuple.
(It re-opens in April, if anyone happens to be in New York and hasn't visited Storm King, I really cannot recommend it enough, it's a lot of fun, Dia too, Earth Room and Beacon are magic but honestly they're all amazing, so fun! https://www.diaart.org/visit/visit-our-locations-sites)
I was thinking more towards the strandbeest series (https://www.strandbeest.com/), although those have entirely too many legs to be spiders and are also not made out of aluminium.
You're not unreasonable for expecting something at least vaguely spider-like. This just looks like a big crane for assembling big wind turbines.
Is the "spider" part supposed to be the web-like aluminum frame of the crane? That seems like a stretch, but it's the most charitable interpretation I've got.
Love this article. I wrote basically the exact same technique almost 10 years ago. At the time I called it `lazy-easy` and still use it today. Sometimes you just want some nice smooth animation without all the state management: https://www.hailpixel.com/articles/lazy-animation-with-lazy-...
The main reason you prepare crêpe batter long before you want to use it is two fold:
1. Allows a bit of gluten development (like cold ferment in bread)
2. And (i believe) most importantly: it allows all the air that was incorporated during whisking to escape, resulting in an even batter
Always wondering if you could just stick it in a vacuum pump...
Honestly, whatever suite of tools allows you to organize your research, thoughts, and easily write text. Remove as much friction as possible. When we wrote The Workshop Survival Guide (https://www.workshopsurvival.com/), we used post-it notes on a wall and google docs. It allowed for a fluid collaboration.
On a more meta note, how you approach writing your book is probably more impactful than your toolchain. If you're working on a book that educates (rather than, say, entertains), I'd like to share the writing framework that my longtime collaborator, robfitz, describes in Write Useful Books (https://www.usefulbooks.com/). Basically, treat your book like a product, find your audience, and test your subject matter with them as your craft your prose.
* Disclaimer: Rob and I run Useful Books, a community and toolset for non-fiction authors.
I love tailwind, and I've been writing CSS professionally since CSS2.1. I have often debated with many developer friends why it has performed so well, and this article really missed some big reasons:
1. It's works extremely well with the current component-focused UI frameworks (react, svelte, etc). Subsequently, the verboseness that is often a complaint isn't an issue at all, but a feature.
2. Does everything out of the box, and very easy to customize.
3. And, most importantly, it allows for easy art direction. Does one button need to be a slightly different size or color for this one specific element? Chuck an extra modular class on it. No need to build a complex cascasding or edge cases. (Shout out to `tailwind-merge`)
Point 3 for me speeds up production work immensely. Also, not being in JS has shrunk bundle sizes by a small amount, which is always welcome in this era.
I agree with all of your points. I am kind of shocked that I had to scroll so far down to see point #3 on this thread at all.
CSS doesn't give the best toolset in order to do styling and organize styling. The locality of HTML structure and styling makes things far easier to work with.
I would also throw in that front end coding feels far more fickle and arbitrary. Tailwind allows me to define a set of rules and then apply them directly. It ends up being more maintainable when used in conjunction with component abstractions.
1. For component usage and in this case only restricted. You can only style the top layer of a component, not each part.
But for component development, tailwind made it complex, e.g. if you want to make it possible to set / add custom styles to each sub-element.
2. Vanilla CSS too.
3. For designers with individual styling of components Tailwind is great, but not for app where elements have the same style or developed at component level.
You prefix the class with hover: or focus: etc. very powerful, although this is where a lot of people start to find it gross especially when you add breakpoints into the mix.
I love that the author shows the whole workflow. It highlights how much tweaking and work it takes to achieve a polished output. Still amazing how easy it was to chain the networks together.
That is spectacular! Keep in mind when watching this that the technology to make this has only been available for mere weeks, and here's a video that would have taken months-to-years to produce using traditional techniques.
These are cool, but I feel like too many of these are just kinda coming up with a simple prompt and letting SD do it's thing. I'm looking forward to more human direction with these videos rather than just "what happens if AI zooms in a bunch?" (the Infinite__Vibes ones are getting there).
You have vastly overestimated how much money that one sale will net me, but I will be donating twenty dollars of other origin to Planned Parenthood, as agreed upon.
Which, isn't even a word, but I enjoy the internet doing classic internet things.
Edit: It is now `no`. Amazing.