Whenever you’re creating a new pattern for error handling you’re papering over a deficiency in the language. At the time, this was necessary, we had no other options, but it lead to years of inventing new patterns to deal with errors that never worked well enough.
-
Show this thread
-
Untangling this has been painful. The ecosystem will be untangling this for years to come. It was the right decision at the time, but the future cost should be noted. There’s also holdouts, insisting the old way is best or just not wanting to ditch their old toolchain.
1 reply 0 retweets 13 likesShow this thread -
The more I think about it, the same is true of these type systems. They are papering over a perceived deficiency in the language w/ tooling and whole range of new patterns. They’ve had to invent a lot of new stuff and are starting to feel like a silo, or a fork in the ecosystem.
2 replies 2 retweets 18 likesShow this thread -
Replying to @mikeal
Between the language changes, the ES modules switch, existing baggage of environment incompatibility with the browser, and the development of cloud platforms based on WASM, I have a theory that node is about to see competition from an environment that's based on the Web platform
2 replies 0 retweets 5 likes -
Replying to @pfrazee
I had assumed this would be the case a long time ago and the fact that we haven’t really seen anything, to me, says that there’s something off about our calculation here.
1 reply 0 retweets 3 likes -
Replying to @mikeal
Maybe, but the pain points are getting more piqued (ES modules) while the opportunities are getting bigger (WASM)
2 replies 0 retweets 3 likes -
Replying to @pfrazee
I agree, but the response we’re seeing isn’t a replacement for Node.js but a replacement for npm/webpack. There hasn’t been a serious platform challenge. deno is even *less* web centric than Node.js has become.
2 replies 0 retweets 2 likes -
Replying to @mikeal
I agree about that, and I think if it happens it'll be the "new cloud" projects structured around WASM that lead the way
1 reply 0 retweets 1 like -
Replying to @pfrazee
I’ve seen more people going after the OS layer with WASM than I have the node/browser platform layer :) Exciting stuff, don’t get me wrong, but I’m surprised by the lack of challenge to Node.js.
1 reply 1 retweet 3 likes -
When you ask people about platforms that are challenging Node.js the answers you get are Go and Rust, and those *also* started about 10 years ago, and aren’t growing at a rate that will ever catch even catch up. I want to see more in this space and I wonder what is stopping it.
2 replies 2 retweets 5 likes
Growth isn't a constant tho. I feel JS has almost complete programmer saturation, so the way to grow it is to increase total amount of programmers. Go & Rust have established niches, but if they can figure out how to break into the same space JS holds, their growth will change.
-
-
Where I see JS's strengths as a combination of: - high-performance networking - web / UI (having a complete monopoly on the web) - low learning curve - large ecosystem + easy code reuse - ability to use one lang on both server and client
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Replying to @yoshuawuyts @pfrazee
JS has more developers than economic institutions believe exist ;) JS actually drives developer growth, and Node.js is a part of that.
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.