It's important to note that Google does give it's developers the freedom to choose their own tools. If a team isn't excited about Angular or Polymer, it's not forced on them.
If I was building a webapp that was going to have hundreds of millions of users, I'd think twice about grabbing an off the shelf JS library.
I worked for a Swedish company. Because of holidays, vacation leave, maternity and paternity leave, and sick days, there were employees of the company that I never saw. I'm not saying it's a bad thing, but it took quite a while to get used to it.
A friend of mine was in a similar situation as Reay. He had no addictions, and no psychological problems, but ended up homeless.
He used his remaining 2k to purchase a 1 year membership at Chelsea Piers sports club. It turned out to be the smartest way he could have used that money. Chelsea Piers is an enormous facility with 20 showers, locker room, huge lounge area with Wifi and couches. He hung out there for most of the day, worked out, learned php, took some freelance web development gigs, got enough experience and knowledge to eventually move on to a full time programming job. In a few months he saved enough money for an apartment in Queens.
I would really like to see those studies, and a link would be great. Our company is on Slack and while we all work hard, we take some time during the day to spontaneously crack jokes and send interesting articles around.
I can't speak for everyone in the group, but I feel a little recharged after a flurry of funny gifs or esoteric programming jokes.
It's browser vendors that are bearing the torch of interoperability and standards compliance. Unfortunately, most vendors are companies with their own agenda. To add to that, all companies and people interpret standards differently. Given this, it's no wonder we don't see consistent api implementation and behaviors between browsers.
The aftermath of all of this falls on the developer's shoulders, which is why so many hours are poured into getting a modern webapp to work across all browsers. Resources are limited, and at some point, developers have to throw their hands up and resign from having support across all browsers.
When you start using a seemingly mature HTML5 api, and find that it doesn't work as expected in all browsers, what recourse does one have? Should we continue to stifle innovation while we wait for the browser vendor to reach compliance? History shows you're going to be waiting for a while, or for ever.
A whinge about nomenclature is what I got out of it. At SimplyBuilt we have staff members that foster communication, provide support, and delete spam/irrelevant posts. In our case (and in most cases I guess) the word 'community manager' would have a high handed sound to it, even though they are technically managing a forum.
Agreed. To add to your point about fewer mistakes, it is sometimes difficult to correlate the picture on the screen with what you are seeing on the actual road, causing you to miss turns.
Agreed, most people won't use them. But that doens't mean more people won't use them. Tools that are easier to use means less technical people can use them. This is why websites like Weebly, Squarespace, and Simplybuilt exist. Technical people who build websites will be recommending these tools to those clients they can't or won't take on.
We prefer hiring consultants who bill us as a business rather than as an individual. It's risky and more costly hiring and paying an individual consultant:
* If an individual consultant gets injured, we'd have to pay the individual's worker's comp/unemployment benefits.
* When it's B2B, we don't have to worry about 'tax nexus'. If we're based in NY and hire an individual in California, we now have to register and pay some tax in state of California. Hiring a business erases that responsibility.
* The consultants who have a business are usually more serious and mature. Invoices are cleaner and the experience is more professional all around. Sounds cliche but it's true.
Not sure if you're trolling, but I'll bite. Agreed that aggression in forums shouldn't be tolerated and aggressive or false comments deleted, but this isn't a case here. The point of a support forum is to provide a platform for getting information about a problem you are having. Legitimate questions and solutions to problems are being actively deleted by Apple and it's clear they are trying to hide bugs in their software rather than addressing it.
It sounds like the single default_card is used for recurring payments, and other saved cards are used for one-offs. No separate card subscriptions yet. Is that right?
If I was building a webapp that was going to have hundreds of millions of users, I'd think twice about grabbing an off the shelf JS library.