You might want to actually read that wikipedia post.....
"The slang term Guido is used in American culture to refer derogatorily to an urban working-class Italian or Italian-American male who is overly aggressive or macho with a tendency for certain conspicuous behavior.[3] It may also be used as a more general ethnic slur for working-class urban Italian Americans.[4]"
Okay? Strawman much? I'm not arguing that anyone do anything about it. I'm just telling you objectively what it is. The Wikipedia article YOU cited disagrees with you...
I’d guess so that ticketmaster etc. can’t identify which tickets are being sold via StubHub. If the domains were identifiable, ticketmaster could block the transfers.
Yeah. That's a slightly more expensive endeavour. The question is is they can scale enough the number of domains and connect to send emails. New domains + not known can have not so good sending reputation.
If they use low number of domains, Ticketmaster could start blocking new domains with more than average number of ticket purchases.
Totally just guessing: Maybe to reduce inbound spam that's forwarded to the buyers? If it was one central email address, spammers could just send a ton of images/PDFs to all known prefixes of that central domain, but needing to guess the prefix + right domain adds a layer of indirection? They may not do much validation on the forwarded tickets, just store it for disputes
Ejecting is an outdated concept when it comes to Expo for the past two years or so. The eject command in the cli is just an alias for the prebuild command even.
The way Expo builds your app these days let's you add native code as you want, modify your Gradle and pods files as needed, and you can still be on their managed workflow where you don't ever need to have Android and iOS folders in your repo. It's a really great time to be using Expo.
Depends on the specific experience you're trying to create but there are fewer and fewer cases where what you want to achieve with a mobile app cannot be done with the mobile web. I can only think of one case in my career where native was actually necessary and not the vanity of the manager having an irrational disdain of the mobile web.
Or stated differently: unless it can be articulated why mobile web/PWA/hybrid cannot work for a specific technological reason, starting with PWA/hybrid is always the best approach. If it needs to be native then go with the vendor-recommended manner of development (unless you love painting yourself into a corner 95% of the way through the project -- been there, done that, don't want to go back).
Exactly, the one thing I oft think is when I hear about some metro, such as bart, or MUNI, or some other big-USA-city-metro woes, like NYC subway etc... complain that they need more money to handle efficiencies or some stupid shit ;
I always think that every single USA-based transit administrator, or even train conductor, should be forced to do an internship in Tokyo, Singapore, Hong-kong, shanghai beijing etc...
You want to know what VALUE YOU SHOULD BE _PROVIDING_ then go find a rail/transit system that fn works, is clean, is on time, isnt a crippling financial bullshit on the people... go do some transits in these countries to see what a shameful position USA is in this regard. And you - specifically and personally who work for these transit orgs in the US and are too stupid to even see the simple truth of how Fd the US is in this regard.
