We've been using zod 4 beta already with great improvements but due to our huge codebase not being able to handle the required moduleResolution settings, we cannot upgrade...
They could at least also publish it as a major version without the legacy layer
EDIT: I've just seen the reason described here: https://github.com/colinhacks/zod/issues/4371
TLDR: He doesn't want to trigger a "version bump avalanche" across the ecosystem. (Which I believe, wouldn't happen as they could still backport fixes and support the v3 for a time, as they do it right now)
Some clubs in Berlin (Germany) already do this for quite some time and the people there are all fine with it.
The vibe is just different, because the people focus more on each other or themself instead of generating content for some online profiles.
Just thought that the `This rework addressed a series of long-standing memory leaks and use-after-free issues in the following APIs that support` part will finally solve memory issues with jest, but Simen Bekkhus already posted that it's still an issue... (https://github.com/nodejs/node/issues/35375#issuecomment-174...)
Yesterday I had the case where I needed to create analytics tables in Clickhouse based on typescript types for around 150 types.
Thought I'd give it a try and gave chatGPT 2 examples of existing tables and the corresponding TS types and asked it if it understood what it should do next.
It explained the existing logic and also 2 edge cases hidden (e.g. if a type was boolean the column was UInt8 (to save 0/1))
Then I pasted all types in batches of 15 in and it generated with only 2-3 corrections needed, probably saving me around 1-2h of manual checking and/or creating. It understood that certain fields are non LowCardinality and therefore not used it.
Their pricing update end of last year was one of the reasons we switched over to Github.
Other reasons were, that most external services had integration with Github but not with Gitlab, or that we didn't use many of the features Gitlab provided but charged for.
If they would provide some lite plans with custom feature addons, we might have kept it, but all in all there was not much difference between Gitlab and Github except for the pricing then
As an app developer I can tell that's nothing unusual, bc most of the attribution user linking happens (or happened) through clipboard.
When you used google/firebase deeplink[1] functionality it was copying a hash shortly before the deeplink, that was then pasted inside the app and could be used to link both web+app sessions together, which was really helpful.
no more paper stuff so rather some software where they have to type all the details into the computer