shwetank
It's not an either/or thing. Why not both?
It's a leadership development platform, aimed at new managers who want to do it right. I'm solo bootstrapping it.
It has a combination of learning resources (courses, research paper insights etc) and tools.
While the learning resources are for helping you with knowledge, the tooling aspect is for developing the right habits for staying a good leader.
You can still find those types of sites if you want.
>These days the signal to noise ratio is so far tilted the other way with people obsessing too much about contributing what they think people want read or boasting about stuff they feel is boast-worthy that it almost completely drains out the purist content from people who just post stuff that genuinely interests themselves.
With more people joining the web, that will be a side effect of it. On the flip side, there has been so much massive positive change on the web too. Online transactions, many government services becoming online (many times reducing corruption), email and IM connecting people around the world in a way never before, and many many more things. Just focussing on the negatives by commenting a few types of sites like fb, insta, twitter etc is fainting a very one-dimensional picture.
>The only good thing about the modern web is that while the barrier for entry writing a website has gone up, inversely the barrier for entry publishing content has gone down dramatically
I actually think that is a bad thing, not good. What made the web the web was the low barrier to entry. Also, if you think that is the only good thing about the modern web, then I really don't think you truly realize the scale in which most people take the web for granted nowadays in their everyday lives, which affects them in a positive way.
The web was far more useful for you. I, for one, am glad the days of IE6 and the lot are over.
No. Only the user allows it.
>FFS. This is like the battery api. Too much time spent on "can we", too little time spent on "should we".
The battery API can be tremendously useful on mobile if used effectively. For example, disabling certain animations and high end GPU intensive effects if the battery is less.
So can you think of use cases for using ML in an app (native or desktop?) Many of those would be good to have in the browser as part of a web app too.
Also, I see a lot of people use Whatapp to send/share actual hindi (written in devnagari) instead of hindi written in roman alphabet. I would say the latter is still more popular, but the former growing quite a lot.
Another thing I see is people use whatsapp to bypass typing altogether. Since you can share pretty much any media easily on whatsapp and other messaging serivices, I've seen some people leave short voice messages instead of typing text.
Overall, some of the solutions for payments and banking being implemented in some developing countries is quite different than what most people in the west are used to. M-Pesa is one of them, but in countries like India, online wallets are starting to gain traction too.
Most people in developing countries don't have credit cards, let alone being comfortable using them online. So a lot of people in India still use the 'Cash on Delivery' model, which isn't very much prevelant in the west, and other solutions like 'Netbanking' (in which the shopping site redirects you to your bank provider's site, you log in, and through the bank provider's site you do the payment, and then it redirects to the shopping site's payment confirmation page ; In other words, you haven't used a card, you've just paid directly through the bank) are also there.
I think now the time is right to take a look again at NEX https://dev.opera.com/blog/introducing-nex/ and standardising core parts of browser extensions.
Electronics for the JavaScript Developer Using Wi-Fi and Bluetooth LE
Also, compare this to the number of people who are just using JS normally worldwide, then we'll have perspective of just how many more people are just fine with JS Vs the people who feel the need to make these.
My guess would be that the number of people who like JS and use just normal JS in their projects is far far greater in number than the people who use compile-to-js solutions. So in comparision to the former, the latter group could be called as 'few'.