[-] brian@programming.dev 0 points 8 months ago

you seem to have added a condescending comment before you understood the goals. 2-5x speedup over rsync (their benchmarks, but still) seems significant on its own, and an interface that doesn't require aliasing to be useful is also nice

[-] brian@programming.dev 0 points 11 months ago

I'm pretty sure it can, it's just been moved to Google maps instead

[-] brian@programming.dev 1 points 1 year ago

I'm not sure if I understand why. I like snapshot testing, but I'm not sure what you gain from using this dsl approach instead of a snapshot library and a more typical test framework, but there are some notable downsides:

  • you have to write typical tests in a different place from your snapshot tests. some things are more complex than "this value never changes", you might just care about a property holding, it produces the same value for several different inputs, etc. properly capturing a big for a regression test is more than a snapshot
  • you lose editor tooling, I can't just send tests to the repl from my editor, I don't have autocomplete, etc
  • need edn serializers for all values you care about. seems easy enough to return a host language object without a proper representation
  • may just be me but I'm not a fan of the added levels of nesting
[-] brian@programming.dev 1 points 1 year ago

it doesn't matter how it was made once it's secondhand since it doesn't support the manufacturer

I suppose there's people that bought the original item since it had resale value, but I really doubt that's significant overall, especially at most thrift stores

[-] brian@programming.dev 1 points 1 year ago

I feel like it's probably not a high priority, but the company I worked at that selfhosted gitlab was also paranoid about dependencies disappearing and so mirrored every repo they had a dep on.

I imagine that's not that rare of a situation and it would have been a nice qol kinda thing if we could have federated with the upstream and gotten a backup of issues and such and could do everything on the one platform. definitely not important and requires upstream to also federate, which will never happen for github so not important

[-] brian@programming.dev 0 points 1 year ago

because with things that the compiler does, like padding for alignment, it frequently takes up more space than that. that was my argument the whole time. what til are you talking about? I'm talking about an extra layer you've decided doesn't count. ofc sizeof bool will be a byte in all of those languages.

a bool taking up a single byte is a fantasy that those languages use because developers generally don't need to think about all the other stuff going on.

[-] brian@programming.dev 0 points 1 year ago* (last edited 1 year ago)

a bool is actually a single bit, the rest is all padding

[-] brian@programming.dev 1 points 1 year ago

why would you need to salt long random strings?

also if you salt them you have to have an id too so you can look up who's api key it is. otherwise you can just look up the key hash to get everything

[-] brian@programming.dev 1 points 1 year ago

it is nice to be able to plug your keyboard into a new computer and have all your shortcuts and layout set up though. I do that so I have the same layout and shortcuts on my personal and work computers regardless of os

[-] brian@programming.dev 1 points 2 years ago

they are the first thing that comes up when searching "cursor" in both ddg and google, so I think they're doing ok

[-] brian@programming.dev 0 points 2 years ago* (last edited 2 years ago)

json is fine as a serialization format for things that need to be text, but it's not great as something that gets edited by hand.

not that I enjoy xml, but writing long strings in json is even worse. xml I can write multiline strings as a first class entity.

I can add a comment to an xml document, json I have to write something hacky like "//": "my comment" and hope whatever is consuming it doesn't care.

there's just as many problems with json parsers, since most but not all of them treat numbers as js numbers, which are basically floats. you can't rely on an arbitrary consumer having support to parse ints above a certain size so you just have to make everything a string and hope.

json allows duplicate keys, but they get overridden by the last occurrence. you can't round trip json without losing something. you can't rely on just seeing a key value in json text and that being correct since there could be another later. doesn't come up often but it's there.

[-] brian@programming.dev 0 points 2 years ago

this is someone that's never dealt with drivers for optimus lol, which I'm pretty sure is the main reason people hate nvidia on linux so much

view more: ‹ prev next ›

brian

0 post score
0 comment score
joined 3 years ago