1. They used the same state emblems to create a completely different design.
2. Doesn't mean other people can use their "old" logo (which they're currently still using).
FWIW, I'm no fan of MOS (one of the reasons I posted is because they're notoriously litigious, even suing Spotify over the order of user playlists), but I'm also no fan of design work being so blatantly ripped off, particularly by companies that can easily afford to hand work to a real designer.
Ironically, the completionist in me would be stressed out knowing there's new content waiting for me everyday. I'd feel compelled to listen to the day's new audio track before it has a chance to pile up over a week, which makes for good business, but would personally stress me out and ruin the whole point of Calm and similar mindfulness services. I'm probably just a weirdo edge case, though :]
You're definitely not a weirdo edge case, I think we all feel something like that around email, facebook notifications etc, and it's something we very consciously want to avoid in our product.
Each Daily Calm session is available for that day only, so you either listen to it or you don't. If you do come back to the app every day there's something fresh for you if that's what you'd like (you can of course to a regular session too). If you don't use the app on any particular day, no big deal, there's no backlog of content for you to stress about catching up with!
It's a time-consuming but relatively harmless foible.
I guess it's partly FOMO, partly habit, and partly the slightly positive aspect of following a routine. There are the odd days when I just skip them all, but it does leave me slightly irked.
All in all, it's not the worst thing in the world, although I wouldn't be upset to grow out of the habit.
I quite agree. I like the repetitive edge of Headspace. Although I have to say that I don't feel compelled to do all of it. I know it's not a test and if I push myself to do things then it lessens the benefit.
> I removed comments from JSON because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn't.
I'd say "for reasons" not necessarily "good" ones. In particular, I think the jury is still out. The hacks that people have done to get comments into npm files are really quite illuminating.
It's funny. He says use a preprocessor to remove comments. Thus not using JSON. It's almost a joke. Except Microsoft does exactly that in their hip project.json format.
Double quotes everywhere are more annoying to read than end tags. If we're going to invent nonstandard formats, why not remove the redundant tag name in the XML end tag. Problem solved.
It allows optional quotes and comments, plus trailing "," and element type specifications. I think it's easier to read and hand-write, as well as write a parser/generator.
Looks like a good take. Your readme would benefit from an example of what luxem looks like, ideally the first thing I'd see, below a short tagline, rather than having to read a lot of text and try to picture what you're describing.
What good reason? Many programming languages have tools that parse comments for various things. With that 'good reason' we should remove comments from all programming languages.
Comments wouldn't be usefull (mostly) for data sent on the wire --and JSON is quite good for that-- but for configuration files, they're indispensable. INI (like git's) is way better of a configuration format than JSON. Easier both to read and to write.
For sending things over the wire, a few way more efficient formats exist. JSON's appeal was simplicity and human-readability. The first goal is achieved OK; the second, so-so.
But I think geography could be referring to the next disruptive technology, or how the existing tech centers are strangling their young and forcing new tech companies to move where it’s more affordable. Different types of geography.
We're looking to hire an awesome engineer to lead development of our website, calm.com. Ideally you're a generalist with a passion for the frontend and great eye for beautiful designs and interfaces. As lead engineer on the website you'd get to decide what technologies are appropriate going forward, and have a huge amount of influence over both the technology and product direction of the website. Your influence will extend beyond just the website though, and as an early engineer at Calm you'll have get to have huge impact on the company. Email ben@calm.com if you'd like more details!
They do click on the ad, and then they buy something. The parent is saying they don't care how many people click, they only care how many people buy (a subset of those that click).
All advertisers want to maximize ROI. Ad displayers want to maximize CPM. It's a mistake to focus on one specific metric, because they all multiply to form the actual metric you care about.
