Vladimir Klepov
@thoughtspile.bsky.social
Got some kind of a hobby, renovating this apartment. Can't say I enjoy it. But hey, at least it stops me from thinking about programming!
January 19, 2025 at 1:25 PM
Got some kind of a hobby, renovating this apartment. Can't say I enjoy it. But hey, at least it stops me from thinking about programming!
I noticed bluesky removes bot followers, but leaves them in follower count. Wonder if it's a genuine bug, or something they "overlooked" to make the place feel livelier
January 17, 2025 at 2:10 PM
I noticed bluesky removes bot followers, but leaves them in follower count. Wonder if it's a genuine bug, or something they "overlooked" to make the place feel livelier
Ran some vanilla community detection on npm packages, very cool how it discovers e.g. polyfills, or eslint plugins by topology only.
But now a large ecosystem can "capture" generic utilities it depends on, e.g. aws-sdk captures tslib, jest captures chalk. Maybe if I feed it more data...
But now a large ecosystem can "capture" generic utilities it depends on, e.g. aws-sdk captures tslib, jest captures chalk. Maybe if I feed it more data...
January 13, 2025 at 12:04 PM
Ran some vanilla community detection on npm packages, very cool how it discovers e.g. polyfills, or eslint plugins by topology only.
But now a large ecosystem can "capture" generic utilities it depends on, e.g. aws-sdk captures tslib, jest captures chalk. Maybe if I feed it more data...
But now a large ecosystem can "capture" generic utilities it depends on, e.g. aws-sdk captures tslib, jest captures chalk. Maybe if I feed it more data...
My first idea was to group packages by namespace (@angular/*) and prefix (react-dom -> react).
It does find prominent communities, but is very dirty (everything now appears to depend on everything), and does nothing for the "utility swamp" that mostly consists of standalone libs
It does find prominent communities, but is very dirty (everything now appears to depend on everything), and does nothing for the "utility swamp" that mostly consists of standalone libs
January 12, 2025 at 11:42 AM
My first idea was to group packages by namespace (@angular/*) and prefix (react-dom -> react).
It does find prominent communities, but is very dirty (everything now appears to depend on everything), and does nothing for the "utility swamp" that mostly consists of standalone libs
It does find prominent communities, but is very dirty (everything now appears to depend on everything), and does nothing for the "utility swamp" that mostly consists of standalone libs
Working on something fun! This are the top 3000 npm packages and their dependencies. We can see constellations of babel (green "bush" on the right), aws (red / pink blob on top), etc. Wonder if I can scale and cleanup this to see anything useful.
January 11, 2025 at 12:09 PM
Working on something fun! This are the top 3000 npm packages and their dependencies. We can see constellations of babel (green "bush" on the right), aws (red / pink blob on top), etc. Wonder if I can scale and cleanup this to see anything useful.
LinkedIn is not very pleasant, but right now it has the best balance of user base size and a decent algorithm that amplifies your content, even on a free tier, so it's a platform not to ignore.
January 6, 2025 at 11:22 AM
LinkedIn is not very pleasant, but right now it has the best balance of user base size and a decent algorithm that amplifies your content, even on a free tier, so it's a platform not to ignore.
Meanwhile in Javaxir land
elixirschool.com/en/lessons/b...
elixirschool.com/en/lessons/b...
January 3, 2025 at 7:42 PM
Meanwhile in Javaxir land
elixirschool.com/en/lessons/b...
elixirschool.com/en/lessons/b...
State of npm, p3
Publishing an npm package is so easy you can use npm for free file transfer / sharing.
You'll need: email and a package.json with name and version.
Put anything you want (it's funny dogs) to the folder, npm publish, et voila you can npm i it from any machine and get funny dogs.
Publishing an npm package is so easy you can use npm for free file transfer / sharing.
You'll need: email and a package.json with name and version.
Put anything you want (it's funny dogs) to the folder, npm publish, et voila you can npm i it from any machine and get funny dogs.
January 3, 2025 at 8:44 AM
State of npm, p3
Publishing an npm package is so easy you can use npm for free file transfer / sharing.
You'll need: email and a package.json with name and version.
Put anything you want (it's funny dogs) to the folder, npm publish, et voila you can npm i it from any machine and get funny dogs.
Publishing an npm package is so easy you can use npm for free file transfer / sharing.
You'll need: email and a package.json with name and version.
Put anything you want (it's funny dogs) to the folder, npm publish, et voila you can npm i it from any machine and get funny dogs.