https://github.com/gabemart/hipku

demo is long since dead but the lib is just a file, should still work

edit: demo - https://jsfiddle.net/wyf9zmk4/

Comments URL: https://news.ycombinator.com/item?id=23592346

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=19019636

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=17449835

Points: 14

# Comments: 18

https://asoftmurmur.com/?v=003a6400000e00000000&autoplay=1

I used to do this, but I find it really confusing having dozens of files all called "index.jsx". I eventually moved to './ComponentName/ComponentName.jsx' in my personal projects. It's a bit more verbose, but I find it makes everything else do to with navigating and finding files easier.

> I think that describes code perfectly.

I wasn't very clear here: what I meant was that exchanging a single word even for its closest synonym will always change the effect of a passage to some degree, because the intrinsic aesthetic qualities of the word inevitably alter the effect of the word.

This isn't true for code, where refactoring a line of code might change how readable that line is, while conceivably having an identical effect when the line is interpreted, compiled or executed.

Literature operates by an intractably complex interaction between the words written on the page and the mind of the reader. Exchanging a single word for another may totally alter the effect of a passage, based on factors like the meaning of the word, the associations the word has for each reader, and the aesthetic appearance and sound of the word.

Moreover, we have no objective way of measuring the effect of literature. We don't have a test that can measure how much more empathetic I become after reading a novel, or how much more I understand the human experience.

Computer code typically has measurable outcomes. While "readability" may still be a relatively subjective measure, we can at least say "these two versions of this function are equivalent" if the outcome is the same - the array is sorted correctly, the transaction amount is calculated correctly, the graph is rendered with the same pixels.

This means that editing computer code is nothing at all like editing literature. The cliff-notes version of Macbeth can never produce the same effect in the mind of the reader as reading Macbeth -- but a function that is subjectively easier to read can be shown objectively to produce the same effect as the original function.

That wasn't my reading of the parent at all.

Snow White the animated film wouldn't have been made if copyright was perpetually inherited and some distant Grimm relative refused to give Disney permission to make the film. This is relevant to your original point - that "I find complaining about someone’s artistic endeavors not being free to be absurd in it’s own way." You may find it absurd, but if it were not so, a work you seem to admire might never have been produced.

There is a cultural component to art. It draws from the culture and gives back to the culture. Long copyright terms - and I find current copyright terms very long - prevent future artists from drawing on the culture to produce new, transformative works.

Disney was able to draw on cultural material from the prior 100 years to make Snow White. But if the current copyright-extension-cycle continues, it seems plausible that Disney films - and all works created in the same period - may never fall into the public domain in the USA, and future artists will not be able to enjoy the same free use of cultural source material as Disney itself has done.

My own needs are modest, but I have provisioning scripts that create and destroy DO droplets on-the-fly from the command line.

But the OP is talking about running dozens of servers, not hundreds or thousands. My own modest apps have held up to the traffic from being #1 on reddit and not fallen over, never been null routed or nerfed by DO, and served hundreds of millions of requests and hundreds of TBs of data. I have nothing but good things to say about DO.

I have no experience running apps at the "millions of requests a second" scale, and I'm willing to accept DO might be a bad choice at that level. But what percentage of apps will ever reach that scale?

Distribution is another matter entirely of course!

I'll experiment with moving the email form to under the results, or putting it behind a button. I was trying to make it low friction, but I think I might have gone a bit far.

Thank you for sharing your experience, it's really interesting to hear from other people interested in this space and I haven't had a chance to do so before, so I appreciate it.