541 karma · joined June 21, 2021
If you're some temporarily embarrassed billionaire, then the startup grindset is quite productive towards your goal.
If filling your life with momentary happiness is your goal, then playing videogames is quite productive towards your goal.
If you're a good little worker bee or someone at the Bureau of Labor Statistics is holding your family hostage, then clocking in 18 hours a day/7 days a week at $BIGTECH is quite productive towards your goal.
If you're religious, then going to church, improving your behavior/mindset, etc. are quite productive towards your goal.
It just all comes down to: What do you want out of life? What do you see as the purpose of life? The purpose of your life? Looking at this problem any other way is just deferring your personal philosophy, beliefs, and values to someone else—someone who probably doesn't care one bit about you and what you want.
You're not going to get fired from Uber for being unable to cover a Friday night shift since you're at working at Lyft Friday night. Can't say the same about McDonald's and Burger King.
Meanwhile, the ECMAScript spec really does not leave very much wiggle room. It (like every other web standard) is almost just documentation or often even pseudocode-ification of an actual implementation... Certainly makes you think.
First, find the docs for ESLint and each of the integration packages that you've installed for each major dependency. Then just set each rule to the strictest setting. Then as you're developing, you'll start running into overzealous rules, prompting you to either disable the rule or write some override/exception.
TSConfig, on the other hand, isn't extensible so you can just throw a couple configs from github.com/tsconfig/bases in your `"extends": [...]`. The base config `@tsconfig/strictest` might be of interest to you.
Where are you getting that from? That proposal is not accepted.
1. are strongly/over-opinionated
2. are power users - most of these design choices are inherently less functional than alternatives
3. understand that these things aren't just "the way they are" but are intentional, explicit things that designers & co. want and will push for over how things used to be as well as the status quo
The obvious is that it requires forward declaration. However, depending on how back & forth interdependence is, it requires multiple "tiers" of forward declaration to effectively iteratively redeclare (or augment? Now that's some added complexity for all parties involved…) incomplete types until you can complete them. It's one thing to have a nice list of "here's what exists", but it's another to manually detangle dependency graphs. It's bad enough in C++ which already doesn't allow very much interdependence, but it'd be completely infeasible for any language more complex than glorified assembly.
Next, how would compile-time execution work? It's one thing to forward declare the existence of something, but how do you execute it without knowing its definition? You literally have to add another pass. Similarly, how do you make an inline function call?
One-pass compilation also relies heavily on searching and referring back to data from earlier in the pass, making it rather cache-unfriendly unless you build data structures as you compile, but now you're using massive amount of memory since you have to build these structures for everything in the entire input. This scales incredibly poorly. If you use one thing from some imported header, you now need to add that header and its entire dependency tree into your one pass. This isn't the 70's anymore; more passes ≠ more slower.
It's actually the compiler and IDE people pushing against this one-pass mindset, because it's "simpler" but just worse for everyone… except maybe the developer reading a header file instead of documentation. And do note that complexity comes in forms other than fancy data structures & algorithms in compilers/tooling. I'd argue that a manual flattening of a real world dependency graph is much more complex and harder to grok & maintain. Regardless, it's the compiler/tool developer's job to take the burden of complexity to better serve their users.
Not necessarily. I've seen far too many cases where GPU acceleration actually made things "slower." Throughput != latency
Says who? Package repo maintainers? -Werror is actually quite divisive.