Androider

The docs are definitely copyrighted. Same as if you wrote a blog post and they copied it, it would be copyright infringement.

Otonomo sounds like a deeply unethical and shady company. If I was doing any kind of business with them I would not continue to do so. While it would be hard to sue them, hopefully when you Google them in the future the fact they ripped of Smartcar will be one of the first results.

Really looking forward to your Xero integration, that's currently a must for us (daily sync so we can reconcile customer invoice payments) otherwise Mercury looks great. The Big Bank we use right now don't provide sending ACH or wires online, you have to call them and they give you a confirmation call back about an hour later. It is a giant pain in the behind and completely ridiculous in this day and age.

Once you get automatic Xero sync working we'll be there!

It's pretty clearly meant to be tongue-in-cheek. In "researching" power vests she wore a L.L.Bean fleece vest from 1995, I wouldn't exactly call it overly subtle. Maybe a bit of introspection about why you found the writing upsetting instead of funny is in order?

I find the opposite true. Components based routing is fine for small applications, but in a sizable application you will inevitable end up with several things that doesn't fit nicely into the simplistic router component model, and now you're shit out of luck and have to try to jimmy-rig in some escape hatch.

It's a much more flexible model to have the router update your state in Redux or whatever, and then you take care of all the rendering and component hierarchies yourself.

Thank you, this looks excellent! Finally a router that doesn't force you to define your UI by splitting everything up into their top-level view components. I want the router to give me the state, and then get the hell out of the way so I can fully manage the UI myself.

I've had a look at react-router multiple times over the years, and the best thing going for them seems to have been that they managed to squat that generic name early on. From the docs and GitHub, it's always been abundantly clear that the "current version sucks, mistakes were made, next version will totally fix everything" again and again.

This isn't going to bring any new local games to Linux, rather it "solves" the gaming problem by simply making these streaming games playable on Linux with Chrome, same as on Windows, Mac, on your TV with ChromeCast, tablets, phones etc.

Much like web apps, YouTube, Netflix etc. today already work flawlessly on Linux, so will gaming too with this development. For most people, the browser is already the only "native" desktop application they use on their computers.

Web apps and web video finally made the Linux desktop viable, but also irrelevant in the bigger picture.

Slack doesn't provide a self-hosting option at any tier. This allows you to host the encryption key in your own AWS account's KMS service, which Slack then (running in Slack's own AWS account) then queries.

It's a large market for both sides, but Brexit will hurt one much more than the other.

The UK exports ~50% of its goods and services to the EU. The EU exports 8% of it's good and services to the UK. The latter is in absolute terms the larger amount of goods and services, but the former is just a massive portion of total trade to have to suddenly replace or re-negotiate.

Think about it this way: SMB company A has to suddenly replace 50% of its customer base. Enterprise company B has to suddenly replace 8% of it's customers. I know which one I'd rather be!

The chart shows Instacart receiving the most VC to date. Now there's a company with a business model completely ass-backwards (in-store isle walking), a terrible customer experience (regularly out of items you order since there's no backend integration) and disappointment all around (swapping out products for vaguely related 5x pricier ones, or arriving with about half of what you needed to make your dinner).

When that company rightfully craters, the blast zone is going to be spectacular.

I also received images from my previous apartment for the new tenants long after moving (yes I did file a move notice with USPS). But then I also keep receiving the physical mail for the previous tenant at my new apartment even 6 months after moving, despite crossing out their addresses and dropping it in the mailbox, and even talking to the postman (didn't help, it's always a different person). That seems like a bigger problem.

It gives access to your name, email and profile picture (if you have one). I don't consider it any different than if the same was asked with a signup form.

Having implemented Google Logins in the past, I always choose that option on sites I see: The site doesn't need to store any kind of password for you. This site also appears to be using the new Google "Cross Account Protection" feature, which will for example automatically log you out of the third party site if you report to Google that your account is compromised.

"We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary."

Hi, I've done Android development professionally for many years, over multiple apps. I don't know anyone who uses the x86 simulator for anything except out of curiosity to check it out every couple of years if it's still completely worthless. Android developers develop with an ARM phone attached by USB, and it's still an abysmal experience compared to iOS.

Who's going to make the "develop on x86, deploy on server-side ARM" experience smooth? It certainly isn't today. Who has that kind of control of the entire stack top to bottom? Amazon is the only one that comes to mind... but I wouldn't bet on it.

Of course I can, but the question is why would go out of my way to do any of that?

I was interested in trying the state of server-side ARM for my mostly-interpreted language, and I pretty much immediately found that it doesn't Just Work. I had a vision of spending many hours searching, creating and +1:ing GitHub issues and tracking discussions around "why package X doesn't work on ARM" and the developers saying at best "happy to accept patches" (which btw is the mantra for why "why package X doesn't work on Windows", and why you don't want to develop with Node on Windows to this day despite all of Microsoft's ecosystem work). Nope, not worth it.

I'm not interested in supporting ARM just for it's own sake. A 30% discount on the cloud instances is also not nearly enough for me or my team of developers to be spending any significant amount of time on this, solving problems unrelated to our core business.

Let's see again in a few years. Of course, if ARM development machines become mainstream by way of Apple, then the calculation changes completely.

When developing for iOS you typically interact with the iOS simulator on your desktop, which natively compiles your app against x86 versions of the mobile frameworks. True native iOS development is pretty rare, and more painful. Overall, iOS development is a delightful experience because there's a singular hardware target and Apple pretty much nails the execution.

For Android development on the other, you don't have a good simulator, and the out-of-the-box dev experience relies on an x86 emulator of the ARM environment. In practice this means that in your day-to-day Android development, you're running the compile-run-test cycle by looking at your actual ARM device all the time, because the emulator is dogshit. I wouldn't really call it cross-platform development in any traditional sense, it's more like remote development, and a bad experience.

On a related note, if Apple does switch to ARM chips for their laptops, that will make mainstream ARM server-side development more viable than any cross-platform story ever can. Or kill the Mac desktop. One or the other :)

Node and Ruby applications do fail on ARM though, when it comes to native libraries and extensions. And now your whole distro is different than your development machine, which adds complexity.

Do I really want to be debugging why node-gyp fails to compile scrypt on the ARM distro on the new Amazon A1 ARM instance (which it did in my case)? And if I solve that, what about the other 2451 dependencies? Let's pessimistically say there's a 1% failure rate, I'll be stuck doing that forever! Nah, I'll just go back to my comfy x86 instance, life's short and there's much code to write :)

I think I'll side with Linus on this one. I saw first-hand how non-existent the x86 Android market was, despite Intel pouring megabucks into the project. If the developers don't run the same platform, it's not going to happen, no matter how great the cross platform story is in theory. Even if it's as simple as checking a box during upload that "yes, this game can run on X86", a huge chunk of the developers will simply never do that.

So the ability for your own constituents children to stay in their own home state given choice and opportunities is now equivalent to Amazon bringing in 25K out-of-state employees. Gotcha. That is about as direct a FU from the "I got mine" boomer crowd and politicians that nixed this deal to the next generation as you can get.

It's second, but I do think it's weak relative to the size of the city and the unfulfilled potential of what it could be.

The NY metropolitan area is ~20M people, but it's clearly much weaker when it comes to tech than the bay area at only ~7M people (I'd say, a magnitude less in number of tech startups alone), and somewhat stronger than the Boston metro area at 4M but not significantly so. Having lived in all three (and now living in Manhattan for 4 years), I don't think for example there is significantly more tech meetups (maybe even less?) or startups (definitely numerically more, but not of better quality) than in Boston, while by numbers alone it should be a whole magnitude greater.

The waterfront is slowly getting nicer, but as soon as you go even a few blocks inwards it's still sketchy and/or industrial. An anchor like Amazon HQ would have had a ripple effect of improving the whole area (like maybe we could finally get a decent grocery store? It's cheaper to take the train into Manhattan and go to Whole Foods than visiting the local LIC Food Cellar and Key Food markets!), especially the more eastern neighborhoods within walking distance, which really aren't seeing much of any development today.

Literally tens of thousands of students graduate each year from NYU (16K alone) and other colleges in the area. You're right that skilled workers don't sit around waiting for jobs to show up. They'll go to where the jobs are, which for tech still largely means the West Coast. And I say that as a NYC resident and tech entrepreneur. The tech scene in NY is weak, and non-existent across the river in LIC. Having an Amazon HQ in LIC would have been a great anchor around which to build a stronger startup scene: If your startup fails, hey, there's always Amazon to fall back on (instead of just the financial sector).

But I'm sure the students are actually grateful that they were spared from Amazon and living close to home, and that the Bay Area residents will continue to welcome each new batch with open arms!

It's easy-peasy once you get the general algorithm down:

1. Is there a Stack Overflow CSS snippet you can use as-is that solves your problem? Score!

2. No? Fiddle with random bits until it looks OK in your browser of choice (Chrome). Display: block and position: absolute are great time savers, slap that on most things.

3. Ship it! Onto the next feature!

Pro-tip: Pixels totally work and you should just stick to that everywhere. The browsers and device manufacturers have kindly taken the necessary steps to make it Just Work no matter what the medium.

In case you think I'm being sarcastic, only half. Nobody cares about your beautifully cascading, resolution independent em's and semantically beautifully structure. The whole thing will be run through an uglifier anyway and probably you should just have used JS for your runtime generated layout anyway if you have any kind of dynamic behavior.

Louis CK has a fantastic bit about this:

"When you're broke, the bank starts charging you money... for not having enough money. If you have a lot of money, they give you money. Because you have a lot of money! You have so much money that we should give you some! Because you have a lot, you should have more! Here, take more money! Take this guy’s $15, fuck him, you should have it!"

Like the article says, class boundaries are also knowledge boundaries. Because you don't know of any alternatives, you bank at the local BoA and get taken advantage of to the tune of $15/month in perpetuity with a low balance, or even pay a percentage at the corner check cashing place. Or you can get free banking and around 3% APY today if you have savings, know how and where to bank and how to structure a 12-month CD ladder. It's expensive to be poor!

You've got it backwards. The output of the product and marketing team is expertly tailored to target the amateur. Don't for a second think they don't know exactly what they're doing.

Fuchsia is to Google as Tizen is to Samsung... something keep in the back pocket for a worst-case legal total war, but unlikely to see any real world use.

I had a yellow cab driver claim just last month that his credit card machine was broken, after a ride from the airport into Manhattan. I told him too bad, plastic is all I got, and wouldn't you know it miraculously the machine worked when he tried it (with a sour face). As a cherry on top he then tried to charge me more than the fixed rate set for the airport fares. So taking a yellow cab in NYC still absolutely sucks in 2018 and you'll get swindled if you're a tourist.

Uber doesn't have much of a moat or lock-in effect. I just switched one day from being a frequent Uber rider to 100% using Lyft, simply because I don't like Uber's behavior as a company. The prices are so close it doesn't make any practical difference to me.

Anecdotally, among my friends I also see Lyft becoming the default, and sometimes price-checking with Uber. If Waymo or whoever came out tomorrow with a cheaper/safer driverless car, I'd just as likely drop Lyft in a heartbeat.

Because they're not paying you in bitcoin or by brown paper envelope. There's federal, state & local city tax reporting for each employee, W-4's to fill, W-2's to mail, health care providers to setup (different in each state even within the same company), 401Ks etc. Unless you're going underground not only from your employer but also the tax authorities.

Now if you maintain your high-cost address but go tripping around the world, perhaps they wouldn't find out for a while.

And then the same seller will pop up a day later under a new name.