The problem is that there are many email addresses that are valid but are likely just abusers. An email address entirely of * and 200 chars long is valid in the RFC, but clearly not a human.
It's simply because they have zero realization, that's not what the title means. Also evident in the article, they're clearly clueless.
What you're seeing in Thailand is respect for Buddhism itself, and a way to keep people interested in Buddhism. In Buddhism there are levels of realization, and a monk is a zero on that scale. Not sure how else to clarify. There are other titles, normally translated as Venerable, which should indicate at least some modest level of accomplishment. But to cite a monk as having any idea at all is fantasy, you just put on a robe, and anyone is suddenly a monk, no education or knowledge required, let alone realization.
I've often used Jenkins for this use case, and really appreciate how it scales to teams too. While it works well, there are lots of pitfalls in it too, logs filling up disks, lots of configs to tweak. I think you've just gotten past those issues so it's stable for your use case.
Good point. Amaranth is used in Mexican cuisine, such as tortillas, so it's well established already.
I think mass market appeal needs to be based off of dishes people already know, vs. a blow of random ingredients with whimsical names. Another poster mentioned impossible burger, which seems more realistic.
We've been doing tests in GCE in the 60-80k core range:
What we like:
- slightly lower latency to end users in USA and Europe than AWS
- faster image builds and deployment times than AWS
- fast machines, live migrations blackouts are getting better too
- per min billing (after 10mins), and lower rates for continued uses vs. AWS RIs where you need to figure out your usage up front
- project make it easy to track costs w/o having to write scripts to tag everything like in AWS, down side is project discovery is hard since there's no master account
What we don't like:
- basic lack of maturity, AWS is far a head here e.g. we've had 100s of VMs get rebooted w/o explanation, the op log ui forces you to page through results, log search is slow enough to be unsuable, billing costs don't match our records for the number of core hours and they simply can't explain them, quota limit increases take nearly week, support takes close to an hour to get on the phone and they make you hunt down a PIN to call them
- until you buy primare support (aka a TAM), they limit the number of ppl who can open support cases, caused us terrible friction since it's so unexpected esp. when it's their bugs you're trying to report and they can mature from fixing them
I think the difference is in other languages I don't have to think about these things any more than I think about what IRQ my sound card is on.
In the CPAN case, if cpanminus is the "good one", then it should be installed by default and CPAN.pm needs to tell you to use that instead or just be deprecated. I don't want 5 choices in package managers, I just want the good one. :)
I recently had to maintain some new perl code. I didn't think it would be a big deal, but found a number of things I take for granted today that perl hasn't kept up with:
1) The perl cpan module doesn't resolve dependencies
2) The cpan module has parsing errors when passing in a list of CPAN packages
3) You have to manually grep your perl code to see what modules it depends on
4) Module installs take a long time since they can compile and unit test the code, unit tests can even make connections to the internet or try to access databases and fail, so you just have for force them to install
5) Non-interactive installs of CPAN modules requires digging in the docs and learning you need to set an env var to enable
6) CPAN modules aren't used that heavily and can have bugs that would be caught in wider used modules. (e.g. the AWS EC2::* modules don't page results from AWS so results sets can be incomplete, whereas the wider used boto lib works correctly and is better maintained.)
7) Perl devs don't think twice about shelling out to an external binary (that may or may not be installed)
8) Even if regexs are not needed, inevitably the perl dev will use them since that's the perl hammer, and it's hard to know what the intention is with regexes or what the source data even looks like
9) You have to manually include the DataDumper package to debug data structs
10) You have to manually enable warnings and strict check, it's not on by default.
Anyhow, I think we've made a lot of progress since the 1990s. :)
A little birdy told me that if you find a bug in GCE's live migration they'll buy you a bottle of scotch. Apparently the team gets blamed a lot for problems that turn out not to something else. :)
I'd recommend making your pricing model simply per GB and then on a rate tier, don't play games with your customers. The quota system ends being a game, and simply ends up wasting management's time trying to ensure the company isn't either getting charged for overages or not using up the quote they have. I'd quite frankly not recommend companies like Sumologic solely based on the massive amounts of time they waste with these things.
So AWS has had a ChinaNet partnership for years. And Tencent's CDN supports HTTPS today. Not getting what's so new here. Ideally, we need a CDN that allows you to manage China just like any other edge, that's the holy grail.