As an iPhone user I much prefer any payment to go through apple payment UI, it’s just safer and hassle free, I don’t need to worry about scammy payment traps.
As a developer I can see the financial reasoning behind implementing third party payment methods.
yeah, esoteric is bad, whether Rails or others. But that's just my impression with Rails, and I'm much more comfortable using other less magical libraries. I guess Ruby is just too good at making abstractions, and I tend to believe that 'making and using abstractions feel great and productive, unless it's made by others'
I think focusing on the syntax level is a bit superficial. While Ruby (especially in the context of RoR) lends itself very well to making DSLs and making abstractions, and thus writing superficially good looking, concise, easy to follow (on a syntax level) application code, it really breaks down when the abstraction does not work perfectly the way you want it.
If you have debugged a Rails app and tried to find where in the 10 level call stack a side effect is introduced, knowing that at each level a 'method_missing' could've changed things, and thus you're really looking at a non-linear call stack since each function call can branch out, you'll know the beautiful looking syntax is not free and in fact very costly.
And don't get me started on poorly documented (if any) CoC (black magic)..
I wish someday Apple Watch can charge itself by harnessing the power of arm swing. I know some mechanical watches do that. Not sure though if it can gather enough power to sustain indefinitely.
They failed because they were not able to adapt to the Chinese market/have any competitive advantage against alibaba or JD which is the point the article is trying to make. None of what you mentioned is alluded in the article.
Yeah, that’s what companies do : look at the stats. And as long as stats say it’s rare enough, it’s not that bad.
People are boycotting not because there’s a higher chance of being murdered/kidnapped with Didi, but that the company was unresponsive, did not have proper procedure/policy for vetting drivers, and took way too long to get even basic info about the suspect driver.
What the stats say here, higher or lower, is moot. Because the issue is that Didi does not give a shit about passenger safety.
I’ve thought about this and and I think the best thing to do here is to relentlessly keep a long, safe distance from vehicles ahead. There are just things you can’t possibly see that the driver before you can.(a puppy/squirrel/whatever that he wants to avoid killing, you can’t possibly know). You can’t anticipate what a human will do here.
You also give yourself a buffer when vehicle ahead have an emergency stop - imagine there’s a truck behind you.
I guess what I’m saying is these ‘brake checks’ are welcome, even if they only serve to educate people.
Last I checked bash on windows is still segregated from the windows system proper. So you cannot call any windows utility/compilers from windows bash. You cannot write to existing files/directories either, based on WSL docs.
Hopefully these limitations will be removed.
You can still make good abstractions with explicit code, and remove most of boilerplates. But please at least be explicit about the fact you are using that abstraction.
One problem with Rails is that these abstractions are applied implicitly and burried deep in the framework. For DHH it's easy to know what it's doing behind the scene. Not for people who did not create these implicitly applied abstractions.
So.. Either you will have to learn ALL the Rails conventions, or you can create your own abstractions and use them explicitly. Also, it will be easy to put a breakpoint on the call site to your abstraction. Try that with Rails, you don't know what/where to put that breakpoint.
As a developer I can see the financial reasoning behind implementing third party payment methods.