iamevn

I can't speak to any sort of scalability but I can definitely say that not everything needs to be built for millions of users. There's plenty of utility in tools you use to help even a single person (even yourself!)

Pebble smart watches are tethered (to an android/ios device via bluetooth), do not talk to a cellular network, and have had an especially good battery life because of that and their low-power displays which are always on and visible with external light, only turning on the backlight when you are using it (e.g. hitting buttons or after giving the watch a little shake). afaik, every Pebble watch has had a significantly longer battery life than all of Apple's watches even though they're always displaying.

The newer Pebbles do have a better battery life, lasting multiple weeks maybe thanks of better battery tech.

Please reread what you wrote and try to see if you can see how it comes off as at least culturally insensitive if not outright racist.

See the `either` function further down

  either some-condition { print "was true" } { print "was false" }

No? I don't think this is the trap you think it is.

I'm in the same boat, recursion tends to be easier for me to reason about because I'm expressing the problem in terms of some base case that incoming parameters are being reduced to rather than some condition that an iterative approach is working towards.

I'm very happy with my Unihertz Jelly Max aside from the camera being not great. I think it's the smallest it can reasonably be (62.7mm wide) while still having its touchscreen keyboard be usable and because it's fairly thick it actually feels good to hold in my hands and I don't need to stick one of those silly pop sockets on the back.

Seems fairly standard stuff for libraries to consider. I was really hoping for some weird stuff like patching bytecode or implementing entire different languages as a python library.

can you not narrow it down further to O(k * nCr(n, k)) (n=size of input, k=combination size) since it does k conses for each of the nCr(n, k) combinations?

(the final filter sums k elements nCr(n, k) times as well)

with N as the length of the subsets and X as the length of input, `combinations n xs` basically walks through list xs and at each element, conses that element onto each combination of size n-1 of later elements in the list then appends those resulting lists together. this is on the order of N * nCr(X, N) aka O(NX!/(N!(X-N)!)) which dominates the overall runtime. the final filter walks through each combination and does O(N) work at each element to find the ones that sum to the desired amount, again O(NX!/(N!(X-N)!))

I don't follow why parser combinators would be a bad tool for CSV. It seems like one would specify a CSV parser as (pardon the pseudocode):

  separator = ','
  quote = '"'
  quoted_quote = '""'
  newline = '\n'
  plain_field = sequence(char_except(either(separator, quote, newline)))
  quoted_field = quote + sequence(either(char_except(quote), quoted_quote)) + quote 
  field = either(quoted_field, plain_field)
  row = sequence_with_separator(field, separator)
  csv = sequence_with_separator(row, newline)

Seems fairly natural to me, although I'll readily admit I haven't had to write a CSV parser before so I'm surely glossing over some detail.

This is probably a really basic question but why does the wizard need to stop being drawn with characters when the sprites move out past the left/right borders? Is this a hardware restriction where those lines aren't able to have text on them when there are sprites on the edges?

This is super frustrating to use. There's a character limit of 30 but it seems like whenever it tries to put a line break in the input it just deletes what I was typing.

Why would people need to invest in a neighborhood? Houses are for living in.