tomeraberbach

6 ms·

31.
by tomeraberbach 2y ago
The main problem SDKs solve is providing a way to interact with an API without having to worry about nitty gritty details like serialization and deserialization, authentication, error handling, retries, connection and thread pooling, etc. W
32.
by tomeraberbach 2y ago
Hi there, I'm the author. Happy to answer questions if you have any :)
33.
Making Java nullable fields backwards compatible(stainless.com)
6 points by tomeraberbach 2y ago|3 comments
34.
by tomeraberbach 2y ago
Glad you like it! I actually have a TODO for what you're describing haha https://github.com/TomerAberbach/lfi/blob/69cdca0b2ee2bd078f...
35.
by tomeraberbach 2y ago
Some info on this page: https://lfi.dev/docs/concepts/concurrent-iterable Recommend reading it all, but this part is probably most useful: https://lfi.dev/docs/concepts/concurrent-iterabl
36.
by tomeraberbach 2y ago
I think there are two things the library makes easier than what you're suggesting: - Some people like/prefer writing iteration in a functional style, which this library enables - It's pretty easy to create unintentional async
37.
by tomeraberbach 2y ago
Yeah, that's true. I think it just has completely different goals. Read through the home page examples and getting started and you'll see it's pretty different.
38.
by tomeraberbach 2y ago
> But what is it good for? ("What's in it for me?") > What are the use cases? I think the examples on the home page and in the "getting started" answer these questions to be honest. Do you feel it's uncle
39.
by tomeraberbach 2y ago
To clarify, the point of it isn't _just_ performance. It's a combination for writing the iteration code in a functional style, which some people like/prefer, while retaining certain performance characteristics that you'd
40.
by tomeraberbach 2y ago
I'm somewhat familiar with fp-ts, and I think lfi is pretty different. fp-ts seems more focused on "pure" functional programming in the style of languages like Haskell. It's much more opinionated on how you should write
41.
by tomeraberbach 2y ago
Yup, I added it in response to the feedback :)
42.
by tomeraberbach 2y ago
> I believe what you are calling a "concurrent" iteration is one of the use cases for Observables, so would be on the RxJS side (the "parent" project). Ah, got it. I don't think I quite understood the relationshi
43.
by tomeraberbach 2y ago
Thank you!
44.
by tomeraberbach 2y ago
I was not aware of it! As far as I can tell, it has some similar ideas (and seems pretty nice!), but I noticed the following differences: - I don't _think_ it supports "concurrent" iteration [1] - It doesn't have a &quot
45.
by tomeraberbach 2y ago
Actually, looks like HN doesn't allow me to update the HN title at this point. Sorry about that
46.
by tomeraberbach 2y ago
That's fair! Agreed it would be good to mention on the home page :) I did mention in the HN post description, but probably should also say so in the title
47.
Show HN: Lfi – a lazy functional sync, async, and concurrent iteration library(lfi.dev)
98 points by tomeraberbach 2y ago|48 comments
48.
New document tabs in Google Docs provide a better way to organize your documents(workspaceupdates.googleblog.com)
3 points by tomeraberbach 2y ago|1 comments
49.
by tomeraberbach 2y ago
Hey folks! I appreciate all the comments. Some of them made me realize I had some mistakes in the article. I went ahead and updated some of the content, and also added some notes explaining what I changed. Thanks for the feedback :)
50.
The 1 Hour per Year Bug, but only in Pacific time(tomeraberba.ch)
76 points by tomeraberbach 2y ago|61 comments
51.
by tomeraberbach 2y ago
No worries! Glad I could send some new knowledge your way :)
52.
by tomeraberbach 2y ago
Link _references_ must be enclosed in brackets. Only _inline_ link URLs use parentheses See https://daringfireball.net/projects/markdown/syntax#link
53.
by tomeraberbach 2y ago
Should be rolled out to everyone by sometime next week See this heading: https://workspaceupdates.googleblog.com/2024/07/import-and-e...
54.
by tomeraberbach 2y ago
Should be updated now
55.
by tomeraberbach 2y ago
Import supports links via upload Export outputs base64 encoded image URLs. We use Markdown reference links to place the large URLs out of the way of reading at the bottom of the file
56.
by tomeraberbach 2y ago
We export to the closest available thing (e.g. file chips become links, people chips become mailto links, etc.) or drop the content entirely if there's truly nothing it can be converted to (rare case)
57.
by tomeraberbach 2y ago
I can confirm it wasn't an intern project (I implemented it and am not an intern haha)
58.
by tomeraberbach 2y ago
No, this feature doesn't affect the preview. We don't convert a Markdown file to a Doc unless a user initiates it
59.
by tomeraberbach 2y ago
This will be supported by the Drive APIs
60.
by tomeraberbach 2y ago
I can't speak to the reasoning for announcing before 100% rollout, but I can say that the slow rollout is for safety. That way if there's a severe bug, then we can catch it while it affects a small number of users, instead of all

More ›