Let’s say you have an object in an S3 bucket which is set to be private (i.e. no anonymous access). Then you want to share
it with people who have no AWS accounts, for example, subscribed visitors to your website. This can be a video course
that only paying users can access, or an EBook that requires subscription.
Mixed content happens when some resource on a page is loaded via HTTP, while the site itself uses HTTPS. It’s a problem
because that means there are files requested on an unencrypted channel, which breaks the consistency guarantees of
Why some projects are clean, easy-to-read, and performant, while others a convoluted mess? Why, when making a modification, in some codebases everything falls into place immediately,
while in others it’s more like walking on a minefield?
As WebPack 2 barrels forward, Tree Shaking — or more technically, the removal of unused exports using static analysis — is finding its
way to the mainstream. Developers are putting their hopes high, as it promises to solve the pressing problem of bloated packages. Usually,
only a fraction of code is actually needed from each dependency but their entire codebase is bundled, increasing the size.
There’s a lot of buzz about JVM optimizations and how it makes production code perform better
thanks to the Just-In-Time (JIT) compilation and various optimization techniques.
A lots of excellent research materials are available,
but I wanted to see for myself how these apply in practice,
so I decided to dig deeper and play around with some measurements.