samprotas

5 ms·

1.
by samprotas 5y ago
I’ve worked on systems in the past that had different levels of ip geolocation data precision. When the precision was low, they would pick the midpoint of the known area (maybe a whole state) to “fill in” more precise data (ex: the city). S
2.
by samprotas 6y ago
It’s also very directly related the to “effectively standard” (but not included) async library in Haskell. https://hackage.haskell.org/package/async The package description at the top of the link touches on the motivat
3.
by samprotas 6y ago
Zulip is another interesting point in the design space IMO. I think it’s worth a look for its take on the identified problem. https://zulip.com/
4.
by samprotas 6y ago
Having executed several "no-downtime" cutovers between systems via DNS updates, I will warn you that a surprising number of clients never re-resolve DNS, so the TTL is effectively "forever" from their point of view. For
5.
by samprotas 6y ago
Protobuf supports "oneof" which is also cumbersome to implement in these same languages but all of them support it (with some extra LOC and no exhaustiveness checking watching your back). Java/Go/C++ are perfectly capabl
6.
by samprotas 6y ago
I agree that having multiple different types of "object values" share one JSON key with no explicit "type" tag is asking for trouble with extensibility and conflicts. That said, I think the constructive suggestion would
7.
by samprotas 6y ago
The number of comments here specifically upset with this part of the current design is a bit discouraging, but not necessarily surprising. Yes, many mainstream languages have near-zero support for Tagged/Discriminated Unions or Enums w
8.
by samprotas 6y ago
A agree with this sentiment from my professional experience writing Go. This article has some nice specific examples of "Simple" APIs that push the complexity onto the programmer. https://fasterthanli.me/blog/
9.
by samprotas 7y ago
I believe it’s a reference to the dot operator: . The parens around it are Haskell notation for using an operator in prefix position, which is often how operators are displayed in a “standalone” context such as this.
10.
by samprotas 7y ago
https://tech.channable.com/posts/2017-02-24-how-we-secretly-... FWIW they have this post from almost 3 years ago about adding Haskell to their stack. I'm guessing the time for your prediction has come and gone. On
11.
by samprotas 7y ago
FWIW he is listed here https://www.postgresql.org/community/contributors/
12.
by samprotas 7y ago
This is a good point. So maybe my concern is more a verboseness issue rather than expressiveness. That said, it would be nice if there was some commentary on whether an implementation like Swift’s was considered and ruled out for some reaso
13.
by samprotas 7y ago
So I am a bit unclear on this from the proposal. Composing contracts is a slightly more verbose fix for allowing multiple contracts for a given type (just make a composed contract and specify that). Using composed contracts, allowed:
14.
by samprotas 7y ago
"Although functions may have multiple type parameters, they may only have a single contract." Anyone else find this limitation a bit disappointing? Seems like a somewhat arbitrary restriction that limits the usefulness of this fea
15.
by samprotas 8y ago
I find it kind of odd that there are all these comments claiming the article glosses over nuance and therefore its conclusion is baseless when the counterpoints have even less data. Everyone seems to agree successful companies have started
16.
by samprotas 8y ago
This exact same thing happened at DuPont about 5 years ago. I believe there were roughly 80k employees at the time. There was essentially no real work email for most of the day until I believe IT figured out how to add a whitelist for @comp
17.
by samprotas 9y ago
For low utilization low cost continuous applications (think a web socket listener with not much to do) this lowers the entry level cost below a t2.nano it looks like. That’s a win in my book.