Deep spread operator (Bilal Abdullah)

Deep spread operator (Bilal Abdullah)

Hello Scripters,

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.

Re: Deep spread operator (Bilal Abdullah)

1. 4 dots are visually almost identical to 3 dots. This could introduce severe bugs because of a simple hard to spot typo.

2. Deep traversing will always have performance problems in some cases. Dealing with circular references can take this issue even further.

I believe such functionality should be used in very specific situations, where object shape is well-known, not very deep and definitely not circular. So, supporting this at the core of the language will probably be frowned upon by the community.

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.

1. 4 dots are visually almost identical to 3 dots. This could introduce severe bugs because of a simple hard to spot typo.

2. Deep traversing will always have performance problems in some cases. Dealing with circular references can take this issue even further.

I believe such functionality should be used in very specific situations, where object shape is well-known, not very deep and definitely not circular. So, supporting this at the core of the language will probably be frowned upon by the community.

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.

1. 4 dots are visually almost identical to 3 dots. This could introduce severe bugs because of a simple hard to spot typo.

2. Deep traversing will always have performance problems in some cases. Dealing with circular references can take this issue even further.

I believe such functionality should be used in very specific situations, where object shape is well-known, not very deep and definitely not circular. So, supporting this at the core of the language will probably be frowned upon by the community.

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.

1. 4 dots are visually almost identical to 3 dots. This could introduce severe bugs because of a simple hard to spot typo.

2. Deep traversing will always have performance problems in some cases. Dealing with circular references can take this issue even further.

I believe such functionality should be used in very specific situations, where object shape is well-known, not very deep and definitely not circular. So, supporting this at the core of the language will probably be frowned upon by the community.

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.

1. 4 dots are visually almost identical to 3 dots. This could introduce severe bugs because of a simple hard to spot typo.

2. Deep traversing will always have performance problems in some cases. Dealing with circular references can take this issue even further.

I believe such functionality should be used in very specific situations, where object shape is well-known, not very deep and definitely not circular. So, supporting this at the core of the language will probably be frowned upon by the community.

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.

Re: Deep spread operator (Bilal Abdullah)

digressing a bit, but once you get used to the idea of deep-copying objects using JSON.parse(JSON.stringify(x)), you also realize web-projects are alot simpler if you keep many non-JSON-datatypes in string-form by default (BigInt, Date, CivilXxx, etc.), since the use-case to copy/serialize data between web-components is far more common than the need to actually revive data for use in low-level business-logic.

1. 4 dots are visually almost identical to 3 dots. This could introduce severe bugs because of a simple hard to spot typo.

2. Deep traversing will always have performance problems in some cases. Dealing with circular references can take this issue even further.

I believe such functionality should be used in very specific situations, where object shape is well-known, not very deep and definitely not circular. So, supporting this at the core of the language will probably be frowned upon by the community.

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.

1. 4 dots are visually almost identical to 3 dots. This could introduce severe bugs because of a simple hard to spot typo.

2. Deep traversing will always have performance problems in some cases. Dealing with circular references can take this issue even further.

I believe such functionality should be used in very specific situations, where object shape is well-known, not very deep and definitely not circular. So, supporting this at the core of the language will probably be frowned upon by the community.

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.

1. 4 dots are visually almost identical to 3 dots. This could introduce severe bugs because of a simple hard to spot typo.

2. Deep traversing will always have performance problems in some cases. Dealing with circular references can take this issue even further.

I believe such functionality should be used in very specific situations, where object shape is well-known, not very deep and definitely not circular. So, supporting this at the core of the language will probably be frowned upon by the community.

I really appreciate everything you all have done for the language and have no complaints over here.
I do have a suggestion though :)

At work we’ve almost got rid of lodash, except we still need it for DeepCopy vs rolling our own.
It’s the same with my side projects. I don’t use lodash because the main times that I need deep copy is when I’m either digging into the Redux store using React, or copying an observable in the Angular world.