1,397 karma · joined March 15, 2015
My posts and comments do not reflect the views of my employer.
I consider software companies to be "tech" companies, but alas.
That said, I still don't like the #. I think that will be the biggest issue with adoption (at least based on feedback on this post). Would the spec have to come up with another symbol if they wanted to implement `protected` behavior?
Alternatively: `this.private.value`, `definitelyNotThis.value`
That said, considering how widespread JavaScript is at this point, I think it is in their best interest to cater to more than one programming style.
Frankly, if this is an issue that you are concerned about, you should really invest the time to learn (and possibly migrate to) TypeScript. Specifically, see their class documentation which already has support for `public`, `private`, and `protected` [1]. (Edit: read @denisw's reply regarding TS. I make this suggestion specifically for TS's compile-time assistance regarding private field access.)
It actually kind of boggles my mind that V8 engineers sat down and agreed that this would be a good design decision. Granted, the article says that they are proposals—is there any way to provide feedback on this? (Edit: https://github.com/tc39/proposal-class-fields/blob/master/PR...)
[1] https://www.typescriptlang.org/docs/handbook/classes.html
Does an extra syllable really cause that much additional friction?
It almost seems malicious, or at the very least anticompetitive. Who has access to such filtering systems already, or the resources to create one?
GRPR regulations, while I absolutely realize their necessity, have made it difficult for me to expand my side business into the EU. This would just be another road block for innovation.
If this topic piques your interest I would also recommend Mathematics for Computer Science: https://courses.csail.mit.edu/6.042/spring17/mcs.pdf
With Today at Apple (https://www.apple.com/today/), they already have the technical infrastructure in place as well.
As a mid-level engineer currently job hunting in NYC, the salary range for most non-FAANG companies (including most start-ups) seems to be $90-150k.
From my experience, the idea of "mid-level" and "senior-level" employees in our industry seems to be skewed to the left. Mid-level employees are generally 2-5 years into their careers, and senior-level can be anywhere beyond that. When you think of senior-level employees in other industries, you generally assume they have 10-20+ years of experience under their belt.
That said, if it were proven that PG&E were directly liable for this fire, how would that play out?
I think that is a much better way of looking at it. Thanks.