nateweiss
Like many utilities, there are countless other ways to get to a similar result, but I personally don't want to think through exactly what tools and adjustments would be needed. So, for me, $5/month is a good value to get a task off my plate every once in a while. Thanks for making it!
If yes, you might consider a page or callout about that use-case, as it might attract some additional users. Just a thought.
PS Separately, if you ever felt like it, it would be lovely to have a poster (or similar short thing in your style) about CSS Selectors specifically, to give to our customers. (To use our stuff, it's good to know about selectors but don't need to know about styling/positioning and such.)
There are companies launching on HN and employing people on HN all the time. Those companies may or may not survive the long haul. I don’t see how I can sensibly demand more of a promise from the software and services that I buy, vs. what we (collectively) promise to our own users or customers.
Just FYI, you can touch once in the URL bar to set focus to it (the whole URL will be selected), then touch and hold down on the keyboard (which will then act like a desktop touchpad) to move the cursor around to edit the URL.
I find this handy, though it took me a while to get used to it.
Neither has as wide a selection as GAP, and are more on the casual side, but have stuff that can work as business casual. The latter is menswear only, so if you're female not so useful.
A my-fault anecdote: I submitted a PR for a minor new Fine Uploader feature, and when a few followup questions were asked about documenting the new feature, I never got around to completing the tasks.
So, at least in my case, I intended to contribute and did "most" of the work, but failed to make the time to bring my PR over the finish line. Perhaps there were a bunch of well-intentioned-but-ultimately-not-usable contributions like mine, and maybe they also contributed to the frustration.
I try (but sometimes fail) to remember that so, so much of the stuff I use every day to maintain my livelihood was created by others, for the free use of others. But it's such an embarrassment of riches that sometimes one forgets to be thankful and that's when the feeling of open-source entitlement sets in (at least that's how I see it).
In the past I maintained a bunch of little plugins that got a decent amount of use, but it was a long time ago (1990's) and I think the culture was different. There was some criticism, but most people were very appreciative and if there was something they wanted added etc, they would just solve it on their end without any complaints or drama. There was no PR type workflow, arguments over licensing, or expectation of awesome docs/support for a free thing. I'm not saying I want to go back to that per se, but when I think about maintaining that type of project now, it sounds fatiguing instead of exciting.
Not sure what my point is... I guess just to say thanks and that I can totally understand why you'd want to stop supporting the code. But it is used and appreciated, and the fact that you nurtured it for so long is an achievement on its own. Cheers!
Not a huge problem because there's the cool branch list/switcher at top center, so maybe will find myself working with the Location Bar hidden mostly.
It can be a culture shock though. Even something like Internet access can be very different from what you're used to, in addition to the nature of your relationship to your neighbors and so on. To anyone considering it, I'd recommend trying it first somehow (rent a place for a few months or something, maybe partly during the area's "off" or "shoulder" season if applicable, so you see what it's like when the good weather ends, etc). It may or may not work for you, but if it does it can be a really nice change.
I feel ST could have a checkbox during checkout to add an additional $50 or something in that range. "I'd like to be a supporter for an extra $50". I'm pretty sure I would opt-in to that, but maybe I'm just saying that now because there isn't such an option....
Interestingly, the name Vegemite itself was also originally "crowdsourced" back in the 1920s [1], so the effort had some tradition behind it. Perhaps "Vegemite" also sounded really silly back then.
I think (but not sure) that it's still for sale in Australia... in any case it is/was delicious, regardless of the name.
[1] http://adage.com/article/global-news/crowdsourcing-wrong-veg...
I got a box of pencils that you sharpen on both ends, one end is red pencil and the other is the "normal" black/graphite color. Great for drawing little UI mockups and such.
Edit: Also, we found that our instances were reachable (they mostly provide a JSON-based API over HTTP), in the sense that they were getting the incoming HTTP/HTTPS traffic that they normally do. But the responses were not getting back out to whoever requested them... lost on the way back out or something.
I need to mess around to see if there is a straightforward way I could get a reference to the underlying data item (the row in the .csv for many of your examples, etc) from the context of a callback that fires on say $('bar').hover() or what have you. Will look into it.
Anyway thanks for answering, and nice work.
My lovely neighbors are full of observations and predictions like this, sometimes preceded by references to the Farmer's Almanac... what one could call "country wisdom" with perhaps a smile on one's face... but it really seems like they are usually right about such matters. They were so convinced of the harsh 2013-2014 winter that they decided to leave for two months of it, which they haven't done in like 50 years or something--which turned out to be a great call. Of course it could be coincidence or random chance, and I probably don't hear about or remember the times when the predictions are wrong. But I do love that there are other constructs for measuring and predicting weather other than what we typically hear about from the weatherperson on the news.