swysercoding-blog

[swysercoding-blog]

Mr. Robot.

[swysercoding-blog]

What will you pick for 2017?

[swysercoding-blog]

Definitely the best video about PWAs!

[swysercoding-blog]

Definitely exiting stuff!! So they say it is like Angular 2, but with more cool stuff!

[swysercoding-blog]

Everysoft Corporation by taires http://bit.ly/2fHDdcV

[swysercoding-blog]

The Depressed Developer 2 by dstori http://bit.ly/2gfXMfz

[swysercoding-blog]

👆🐶#programminghumor #programmerlife #funny #dog #badpundog

[swysercoding-blog]

💻🙀#programminghumor #code #cat #programmingfun #cpp #dotnet

[swysercoding-blog]

Now and Then, what it is to learn JS in 2016 by RolandCuley http://bit.ly/2gHdYoz

[swysercoding-blog]

So true...

The 5 phases of software development by Gabr3l http://bit.ly/2fumyYA

[swysercoding-blog]

Yup, it is now my new favourite hobby! Its a thing...

[swysercoding-blog]

Great tool for checking different screen sizes and devices!

[swysercoding-blog]

Soooo looking forward to this being released! Will make every Js coffee converter's life easier!

[swysercoding-blog]

Ever wonder what the hell Webpack does? I know I did...so I found this awesome article that explains exactly what it does and how to use it!

[swysercoding-blog]

Started playing around with Docker, I am so excited I even got VPS hosting!

[swysercoding-blog]

Constants and Object.freeze in JavaScript

Node.js already supports const and most browsers eventaully will, but that only creates immutable variables not objects. For example:

const obj = { property1: 'value1' }; // some implementations will error out, some will just not assign to it. try { obj = { property2: 'value2' }; } catch (e) { console.log(obj); } console.log(obj); // { property1: 'value1' } obj.property1 = 'value2'; console.log(obj); // { property1: 'value2' }

This is where Object.freeze comes in, it prevents the entire object from being modified:

const obj = Object.freeze({ property1: 'value1' }); // some implementations will error out, some will just not assign to it. try { obj.property1 = 'value2'; } catch (e) {} console.log(obj); // { property1: 'value1' }

This is useful for the same reason that const is useful, it makes code more predictable by ensuring that an object’s properties and values can always be relied on once defined. Though it does have a weakness with arrays:

const arr = Object.freeze([{ property1: 'value1' }, { property2: 'value2' }]); // some implementations will error out, some will just not assign to it. try { arr[0] = { property2: 'value2' }; } catch (e) {} arr[0].property1 = 'value2'; console.log(arr);

So it is important to remember to use Object.freeze on each array element:

const arr2 = [{ property1: 'value1' }, { property2: 'value2' }].map(Object.freeze); // some implementations will error out, some will just not assign to it. try { arr2[0].property1 = 'value2'; } catch (e) {} console.log(arr2); // [ { property1: 'value1' }, { property2: 'value2' } ]

Although, this does not seem like something that has good support, it actually works in all modern browsers. Though since Object.freeze is most useful with const and const is still not supported in some environments, you will need another way of generating constants. Finally, frozen objects run just as fast as regular objects. Frozen objects only ran slower in the past due to browser bugs. For example: https://bugs.chromium.org/p/chromium/issues/detail?id=115960.

Github Location: https://github.com/Jacob-Friesen/obscurejs/blob/master/2016/objectFreeze.js

[swysercoding-blog]

Material icons!