Someone needs to figure out medium range charging and sell a unit to every home, coffee shop, airport, airplane, etc. Let us never be powerless or tethered or docked again!
You’re limiting your view of feature flags to a subset of their potential. Also, authorization schemes like attribute based access control (ABAC) can use any arbitrarily dynamic values from the current context. The two concepts overlap immensely.
I’m curious about why people dislike this question. This is a specialized library; it should be testing everything including crazy edge cases that most of us haven’t even considered. Also, someone stated that there have been several URL-related security vulnerabilities in curl.
It’s not only about being able to operate disconnected for long periods it’s also about handling network partitions and being able to achieve consensus without a single source node.
I was a Rails, Sinatra, Ruby dev for years and I’ve been work with Go for years too. I’m struggling to understand your perspective because I’m no less happy coding in Go.
Imagine trying to reign in spending without a budget by drinking lots of water to avoid buying starbucks and other similar indirect tricks. Without the budget you’d easily overspend. This is how I think of calorie counting as the only proper way and other diets as inefficient indirections.
ISO 8601 was designed as a standard format for conveying date/times from the Gregorian calendar. The Gregorian calendar divides time into days, months, years which are units chosen based on Earth rotation around its axis and its orbit around the star Sol.
I don’t see why it would make sense to include points outside of Earth in that system, as I think you’re proposing.
Regarding the other part of your proposal to include locations: ISO 8601 purposely excludes those because converting a location to a UTC offset is a political process that requires lookups for historical changes to that conversion.