Manicode is really awesome, did some actual dev for live apps and it does work.
You must though, learn to code in a different way if you are not that disciplined. I had excellent results asking for small changes, step by step and committing often so I can undo and go back to a working version easily.
Net result was very positive, built two apps simultaneously (customer side and professional side).
If card networks, issuers, acquirers, processors and gateways used bitcoin as their settlement layer, most of the current issues would be automatically solved. They could focus engineering resources on creating better user experiences, anti-fraud, etc.
Consumers can keep using their tokenized credit cards, debit cards, etc, but their money would be moved using the bitcoin time chain, instead of hundred of CSV files.
Why haven't the W3C participants even mentioned bitcoin for standardizing web payments? I believe it's because of politics and business. Bitcoin can't be controlled and manipulated and it's not an easy truth to swallow. I hope this changes.
I believe this is a hit piece. The author uses the word "controlled" in a misleading way that leads readers to think that the value offer of bitcoin decentralization is not true or worst, whatever product that builds on it is deceiving their customers. Talks very poorly of the author and everyone else involved.
This is just a list of links with no context or real technical analysis. I guess you are comparing LN to something else, in that case you should too make a list of links of the problems and fraud issues with, for example, fiat based payment networks or as another example, real adoption issues for things such as bcash.
And if your objective is to discard LN because of those issues, those same issues do not seem to matter in the real world where people are actually using LN for real transactions every day all over the world. This is public data you can check yourself.
Anyways, I think this list of links is biased and doesn’t add value to someone trying to understand modern payment networks.
Hi! Looks pretty good! Please, check the pricing page, the "Prime Account" box has a higher top margin than the others, I think its an error. Really like the website.
I believe the title of the article should be "AWS Services You Should Avoid if you don't need them or if they are not the right fit for your specific application, for example, if you need social login you are better off with other alternatives more fit to the social login use-case; or for example, if Lambda is not the best fit for containing and deploying my code given my architectural decisions at the moment of this writing".
I have to admit this sounds awful but true. I'm not going to be hypocrite and claim to have read the Facebook terms of use but I have never really expected those to be in my favor in terms of privacy.
Society and regulators should treat the social media industry like we do with tobacco and firearms.
Yes, we use several Lambda for different kinds of backend and user-facing services. We pay $60 to process ~1M requests per month.
Consider the following:
1. It's pretty useful for fast prototyping (lots of demos, codes, etc. available).
2. Write clean code. Develop your logic totally separate from Lambda, you should be able to test it without it. Use Lambda + API gateway basically as an app/web server.
You must though, learn to code in a different way if you are not that disciplined. I had excellent results asking for small changes, step by step and committing often so I can undo and go back to a working version easily.
Net result was very positive, built two apps simultaneously (customer side and professional side).