post: add js-ipfs 0.35 release post #234
Conversation
alanshaw
requested review from
hugomrdias,
jacobheun,
achingbrain and
vasco-santos
ghost
assigned 
|
|
||
| Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started: | ||
|
|
||
| - Check the issues with the `help wanted` label at the Ready column in our waffle board - https://waffle.io/ipfs/js-ipfs?label=help%20wanted |
There was a problem hiding this comment.
Since Waffle is shutting down, should we start linking to GH issues instead?
E.g. the super-memorable https://github.com/ipfs/js-ipfs/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22
There was a problem hiding this comment.
Yes, this needs a PR to https://github.com/ipfs/js-ipfs/blob/master/RELEASE.md also ipfs/js-ipfs@2b1095a
content/post/80-js-ipfs-0.35.md
Outdated
|
|
||
| One of the biggest goals for JS IPFS is to enable the distributed web in the browser. Part of that is being a good web citizen and minimising the amount of code we ship, to ensure IPFS downloads quicker, `npm install`'s quicker, loads quicker and utilizes fewer resources. It's especially important on resource constrained mobiles and IoT devices. | ||
|
|
||
| The good news you want to hear is that we've now chopped around **26%** off the bundle size of JS IPFS since 0.33, that's a reduction of _over_ a quarter of the code we were previously shipping! This is an amazing improvement and a great reason to upgrade. |
There was a problem hiding this comment.
Maybe this should include the reduction since 0.34.0 too as it's the last release?
There was a problem hiding this comment.
@hugomrdias started work on it when we were at 0.33, so it feels right to compare it against that version. We got some of the benefits in 0.34 but didn't shout about it as it wasn't finished.
/cc @dirkmc @vmx