You mind find inspiration from http://passwordstore.org
307 karma · joined August 9, 2013
I'm asking genuinely here. Is Servo expected to be have a much better performance?
I think Elm is to address the issue that JS is the only thing that runs in a browser. With that said, I suppose you could use it with Node as well.
I'm wondering how long does it take to execute the ES refresh on a search query when the Shard was marked as dirty?
If the search requests are mostly real time, I suspect this is really short, but if the Shard ingest new messages for a while (let's say 50 minutes) and it's marked as dirty, a search query would ask ES to refresh 50 minutes worth of documents before running the actual query.
As it shown to be a problem? Is the refreshing time growing along with the number of documents inserted since the last refresh?
Or maybe they should be and out implementation of feature flags should always take the current customer into consideration...
In my experience, it's relatively easy and clean to work with `if(feature) this else that` in a simple backend application (a service that pulls from a queue and maintain a state, for example).
The problem arise when you start working with more complex applications. Specifically application with complex UI where you have to check the state of the flag at multiple different places in the code. You end up adding branches all over the code, branches that will be removed once the feature is fully deployed and known to be correct.
It adds a lot of overhead, the code is less readable.
There must be a way to do implement feature flags in a smoother way.
Canada
Sure, it can be hard to read because you can write the same thing in tens of different ways and some people abuse it, but if you don't and your team does not, you end up with a beautiful code base.
``` SERVER=http://localhost APPID=test SECUREKEY=key curl "$SERVER/app/$APPID" \ -d "{ \"secureKey\": \"$SECUREKEY\" }" ```
It's more concise and still provide the braces safety.
I'd like to see if a something like DeepFreeze could help here (there are probably alternatives here, DeepFreeze just came first in my mind).
> Traditionally, goods are subject to the first sale doctrine--once I buy a shirt, it's my property, and if I want to sell or rent it, I can. It's mine.
> But software is licensed. When I buy a piece of software, I'm actually paying for a limited and revokable right to use someone else's property. And now companies are putting software into more and more goods.
That's a pretty good summary.
I will really try it out. Thanks!