Careful with Cloudflare, they don't let you change nameservers[1]:
> Registrant agrees to use Cloudflare’s nameservers. REGISTRANT ACKNOWLEDGES AND AGREES THAT IT MAY NOT CHANGE THE NAMESERVERS ON THE REGISTRAR SERVICES, AND THAT IT MUST TRANSFER TO A THIRD PARTY REGISTRAR IF IT WISHES TO CHANGE NAMESERVERS.
So it's a no-go if you want to use Route 53 or something like that.
They could switch your A records and still MitM your whole site. Granted I’m sure that would only happen if their CEO was really mad, but it just requires too much trust for my comfort.
Atomic CSS sounds great until you actually try it on a big project and you run into all sorts of issues. Mostly that your html ends up looking like a total mess which slows down the rest of your work, and that it's not flexible enough.
In practice, DRY in CSS ends up making code very hard to maintain. It creates ghost side effects where you change something on one page and break something on another page unknowingly.
With the exception of a few elements that don't really change at all from one page another like buttons, doing a little bit of copy pasting or search and replace between files is easier.
Sure, you might forget to update one page or component here and there, but at least it won't be broken. Better a component is inconsistent in style but functional than broken.
Using a few variables for things like color and spacing can also help minimize this problem.
Keeping most of my CSS components encapsulated and "namespaced" has worked a lot better in practice than trying to make everything reusable and coupled together in ways that you'll forget about when you have to come back to that project a few months later.
Couldn't agree more. I finished some refacotring of a CSS done with the DRY mantra and there were so many hidden gotchas. When I changed one thing it would end up breaking a number of unrelated things.
The only advantage Braintree has is Paypal support.
I haven't checked on Braintree lately, but the few times I've had to talk to the Braintree support or sales team, they've been very unhelpful.
If your business is not the size of AirBnb they make it clear they don't really care about having you as a customer. And that's even if you process a few millions a year.
If you're outside the US, have fun signing up and jumping through hoops. If you're building a marketplace, your users will have to jump through the same hoops just to start accepting payments.
While Stripe isn't perfect either, they are a lot friendlier and helpful when you speak with them. They also have Stripe Connect and self-signup which makes it much easier to build a marketplace.
I'd rather use Stripe for credit card processing, even if that means dealing with Paypal's bottom of the barrel APIs directly to add Paypal payments. That's how bad Braintree support is.
Maybe they've gotten better and this is out of date, but based on past experience, I don't really care to find out.
Google has some of the worst UI/UX. For all the other great stuff they do, this is one area where they really shouldn't be teaching others but learning from them.
From the barely usable Gsuite admin console to the indecipherable API docs (and developer console), I can't think of a single product where I can intuitively find the setting or option I'm looking for.
Not to mention they often miss the most important thing to the developers: what the developers can do with the exposed API. The Google Plus API was super locked down, for example, you could only post actions from your app from some pre-approved list. That's very limiting. If a developer came up with something cool, like say trading cards, there likely wouldn't be a verb for them. Facebook was much better in that you could post anything, but had to go through app approval.
I don't think the article's methods would be very good re fixing this since when they asked developers to accomplish goals with the API and tracked them, they already decided what would be written.
Maybe it was just my friend group, but I feel like Facebook had a nice period shortly after it switched from profiles to walls, but people actually thought about what they were posting instead of spamming it constantly. Then between the spam from inane facebook games (via the API access you mentioned, I think I have ~100 of these blocked still because of how they gobbled up the whole feed at the time) and now the giant number of content farms, the news feed is attention grabbing yet useless for anything actually social.
Someone please steal this idea:
- Social network where you get 1 post per day. Text status, link, photo, whatever.
- You have a couple of free "bonus posts" each month for when you really want a second post.
- Monetize by selling additional posts, but the cost ramps up exponentially.
I'm sure it's not destined for facebook-level gajillions of dollars, but there's got to be some market for a sane social network that you can actually keep up with, right? Instagram is working for me right now, but maybe only because I don't know that many people on it. I've tried FB and twitter and basically checked out of both.
I have to agree, but some products are still really great and have only improved over time. Gmail and Search come to mind.
Material design, while pretty, doesn't hold up usability-wise for all applications. It's a case where the consistency of switching between Google products is improved but at the cost of usability and UX of each individual product.
