Hjertnes.blog

#

March 01, 2018

Yawn

#

March 01, 2018

Hot tramp, I love you so! 🎵👩‍🎤

#

March 01, 2018

Testing out Firefox, for the first time since the Chrome Mac Beta. It’s fast, but damn it is ugly.

#

March 01, 2018

Dear designers: can you please stop hiding the fucking sign-in button.

Thanks.

#

March 01, 2018

Gnu Artanis. A Web Framework for Guile (the GNU Scheme implementation).

#

March 01, 2018

Three things I want from a future X-Pro 3:

  • In body stabilisation.

  • Larger battery

  • Quieter shutter.

When to do client side and when to do server side

March 01, 2018

When you are doing a web project in 2018 you have the choice between doing most of the heavy lifting server side or client side. The former means that you render most or all of the HTML before it reaches the browser, while the latter means that you only send a minimal HTML file from the server and the browser will use API’s and Javascript on the browser to produce most of what the user end up seeing.

There are pro’s and con’s to both approaches, and there are times when one is better than the other.

If you are developing something where the content is in focus, in other words where the user of your web site are primarily consuming the content like for example a blog then doing more of the work server side is the better approach. Because it will load faster and less resources have to be transferred to the client.

But, if you are developing something where there either is a combo or where user interaction is the primary thing. What we call a web app. For example Gmail, Facebook or Twitter, then doing more on the browser is better. This is because it enables us to do more advanced functionality that in the past was reserved for native apps.

Like always, it depends on what you are building. I see a lot of people bringing in huge frameworks using for example Angular or React when it is unnecessary and the only difference between that and doing it with some backend language like Python or PHP + some plain JavaScript is a lot more JavaScript assets than needed.

Just because a modern framework is there, doesn’t mean it is the right thing for everything. Or for all parts of what you are building

Why I shoot film

March 01, 2018

I shoot both film and digital. And I use them for very different reasons.

When I want to make sure that I end up with some good images I always bring my X-Pro 2. I can shoot duplicates and make sure that I at least have some good images at the end of the day. No matter how the lighting conditions are. But I often bring my 35mm camera instead if I just want to shoot for fun.

If you go for a film camera you can more or less anything. I personally prefer very manual cameras, but you can also get something that are more like a modern DSLR or a point and shoot. The reason I prefer manual cameras is that they just work, even without a battery. And you just expose and shoot. This process is a very useful to really understand how light and the different settings on your camera works together.

The reason people shoot film vary. Some do it because they like the process, others like the simplicity and some because of the look of the films they use.

I shoot film because I enjoy having some stuff in my life that don’t require me to re-charge the batteries all the fucking time. And I really enjoy how the images look. Good black and white film looks much better than anything I have ever gotten out of a digital camera. And I really love how goofy Fuji Superia colour film look. Some do it with filters, I personally prefer to go back to where the Instagram filters or Lightroom Presets go their looks from in the first place.

#

February 28, 2018

Working on a Wordpress XML-RPC compatible server that you can use with Hugo etc.

#

February 28, 2018

Oldpub. I just completed the first “working” version of my Wordpress XML-RPC server. It is far from perfect, and far from complete. But it works with MarsEdit for plain text posts.