Why Nostr? What is Njump?
2023-08-16 02:09:41
in reply to

A13cui on Nostr: npub17esnv…kclcm "Wanna know the ancient secret of not having concurrency issues? ...



"Wanna know the ancient secret of not having concurrency issues? It's called not having shared mutable data in the first place. And for a library that is supposed to provide pure functions, none seems required whatsoever."

you've skipped about a couple of lemmas in your argument. who said they're providing pure functions? I again did something that you can't do (along with engaging with what I said): looking at the source code and how the library is used. while looking through it, I noticed that it looks like only C++ needed to implement sync since Java and JS seem to handle it just fine (not like you'd care about actually looking at the code since you're set on disagreeing with me). it seems perfectly content with either sync or async contexts (although async would definitely be preferable for, you know, the case when you're in a fucking Android dialer and need to format phone numbers in real time). also that data is there just for convenience, you can... just... regenerate it if you really need it. I would argue that they should've used protobufs by now especially since they were around before Google bought Android (this library was made specifically with it in mind), it would've been more efficient, but I'm not the one making the rules.

https://github.com/google/libphonenumber/blob/master/FALSEHOODS.md btw, yet another piece on why programmers like you oversimplify phone numbers. I bet you check emails using regex considering you oversimplify and ridicule this problem, huh? fuck you, I'm not engaging with you since you're clearly bad faith and spent essentially no thought on looking for a couple of minutes on what this library actually offers. don't @ me ever again, you're as bad faith as I perceived you to be in your wayland discussions, go sugma.

EOD.
Author Public Key
npub1gykyxa0f5e96pelee3spdvxhet9r0aeky05dfl9apjal4wym346q9rd8w8