That is indeed the argument and I don't think it is necessarily a bad one.
Academic papers are both jargony and written in specialist notation and are not generally accessible to lay people without background in the field. I don't see how it is really much different.
> SVG graphics are clean, result in NO blur at all. They don't even need any Truetype-style hinting. You've probably looked only at early non-conforming implementations using bad approximations.
This huge wall of text but apparently you don't understand the subject matter all that deeply. Why wouldn't SVG need hinting? Truetype needs hinting and it's a vector format as well.
(Philippe always posts walls of text, even on the SVG mailing list; seems to be their thing.)
Hinting as done in TrueType is probably overkill for most purposes. But icons are often not displayed in arbitrary sizes, but rather in one of a few known-in-advance sizes. It's not hard to tweak the paths and shapes to fit to the pixel grid for all those. Also, as you approach higher pixel densities, it becomes much less important; basically you may just have to make sure that the smallest sizes fit on whole pixels and that's it.
Long ago I've automated asset generation in different sizes from SVG for an Android app I worked on and even without caring (much¹) about a pixel grid the results were good enough not to need tweaking.
_______________
¹ When hand-writing SVGs I tend to care about integer coordinates simply to not lose my mind.
Don't forget better UX. The whole practice of UX is utter hogwash. Comparisons between 3 or 4 (or 100) solutions that are shitty at baseline is not honest at all.
I have NEXUS and I agree it is worth it. But the relevant question is that TSA pre is not difficult to get. If someone (US citizen or PR with relatively clean record) wants to blow up a plane with themselves on it then I don't see how TSA pre stops them.
Yes, all you're saying is it is possible to make shitty native apps too. So that would explain your results. Native isn't a magic wand, but except for the simplest of things web will not be as good. The cracks still show in things like Google docs and sheets and overall those are pretty good as far as web goes.
I have no idea where this incredulity even comes from you tools, nor the claim from TFA which was patently absurd. Pretty much everyfucking major language not listed has green threads if not built into the core (Python, Ruby) provided as a well known library (Java, C++). And any new language it's pretty much table stakes.
The article claim is so ridiculous it's not even wrong and you go on to snark about a Haskell counterexample. What a complete asshole.
If you have excellent credit you can simply not pay and make them do the work. I had a $1500 dispute. I was getting tired of wasting time. When it went to collections I drafted the standard leave me alone. The funny thing is now the collection company has screwed up twice on some things. It is their prerogative to sue. I doubt they will. If they do it, it will be annoying but I can respond in kind with a countersuit. Oh and the credit score? Dropped about 40 points into the upper 700s. Annoying, but not worth just rolling over and paying.
Agreed, this is just part of business for hospitals. We as honest people feel ashamed if we cannot pay bills. But I make an exception medical bills and other unpredictable broken industries (if any).
If someone bought a car or house, they knew their obligations exactly. If they declare bankruptcy, I would lay some fault with them, if not all.
But with medical billing, you cannot get a straight answer. If they cannot tell you what a simple procedure would cost you, then you don't owe them anything.
Also hopefully if enough people don't pay surprise bills, then medical industry would have motivation to simplify their systems.
You'd hope they would simplify their systems, but instead they just throw it into higher risk pools and raise prices for everyone to cover the non-payments.
Deployment of cell sites at events like stadiums for sporting events and outdoor music festivals is pretty common for years and years. Unless you're a hermit you almost have certainly seen a COW at one point or another. Cf Wikipedia mobile cell sites, especially COW.
I've seen them around alright, just not realized how common or easy-to-set-up they might be for an event like this, or how they work from an inter-provider standpoint. Do they not cost a whole ton for the organization setting up the event, and wouldn't every provider (T-Mobile, AT&T, etc.) be required to set one up? It seems like such a massive headache and cost for something like a Pokemon-catching crowd that might not even generate much revenue(?) that I'm confused how everyone is saying "just deploy extra capacity". Like do providers just follow crowded events for free and put antennas wherever people are as if it's no big deal?
20k is actually not that many people as far as these things go. Over 50k in that confined stadium area and you really start hitting some hard limits with current cell tech. 20k should have been no problem with careful planning.
>20k is actually not that many people as far as these things go
20k people in close proximity uploading and downloading constantly without breaks? What specific event is that comparable to? Music festivals don't have all attendees constantly using their data network.
The point is, there are many places in the world that draw large crowds into a tiny area on a weekly basis, and the cell networks will fall over and die without special measures.
Did they do anything at all to anticipate that load? It seems not. "We tried and failed" is understandable, but simply inviting 20k people and expecting them to play a mobile game is monumentally foolish.
Wikipedia: "The size of the byte has historically been hardware dependent and no definitive standards existed that mandated the size – byte-sizes from 1[3] to 48 bits[4] are known to have been used in the past."
Academic papers are both jargony and written in specialist notation and are not generally accessible to lay people without background in the field. I don't see how it is really much different.