The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)
But there's a shocker in here: Angular.
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.
Maybe: lots of people in 2017 wanted to try Angular, tried it, and almost none of them liked it.
Or maybe: new users are still liking it but old users are churning out?
- Next.js has an enormous "want to learn" pool, great sign for them
- 62% of Meteor users and 72% of Sails users would not use them again, ouch
We need to stop calling Express a framework, it's too big. It's bedrock.
More from Tech
After getting good feedback on yesterday's thread on #routemobile I think it is logical to do a bit in-depth technical study. Place #twilio at center, keep #routemobile & #tanla at the periphery & see who is each placed.
This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.
We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.
Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.
This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile
So I have been studying this entire communication layer as its relevance is ever growing with more devices coming online, staying connected, and relying on real-time communication. Not that this domain under penetrated, but there is a change underway.
— Ameya (@Finstor85) February 10, 2021
This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.
We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.
Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.
This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile
You May Also Like
“We don’t negotiate salaries” is a negotiation tactic.
Always. No, your company is not an exception.
A tactic I don’t appreciate at all because of how unfairly it penalizes low-leverage, junior employees, and those loyal enough not to question it, but that’s negotiation for you after all. Weaponized information asymmetry.
Listen to Aditya
And by the way, you should never be worried that an offer would be withdrawn if you politely negotiate.
I have seen this happen *extremely* rarely, mostly to women, and anyway is a giant red flag. It suggests you probably didn’t want to work there.
You wish there was no negotiating so it would all be more fair? I feel you, but it’s not happening.
Instead, negotiate hard, use your privilege, and then go and share numbers with your underrepresented and underpaid colleagues. […]
Always. No, your company is not an exception.
A tactic I don’t appreciate at all because of how unfairly it penalizes low-leverage, junior employees, and those loyal enough not to question it, but that’s negotiation for you after all. Weaponized information asymmetry.
Listen to Aditya
"we don't negotiate salaries" really means "we'd prefer to negotiate massive signing bonuses and equity grants, but we'll negotiate salary if you REALLY insist" https://t.co/80k7nWAMoK
— Aditya Mukerjee, the Otterrific \U0001f3f3\ufe0f\u200d\U0001f308 (@chimeracoder) December 4, 2018
And by the way, you should never be worried that an offer would be withdrawn if you politely negotiate.
I have seen this happen *extremely* rarely, mostly to women, and anyway is a giant red flag. It suggests you probably didn’t want to work there.
You wish there was no negotiating so it would all be more fair? I feel you, but it’s not happening.
Instead, negotiate hard, use your privilege, and then go and share numbers with your underrepresented and underpaid colleagues. […]