Very neat, love it. Few things--
1) Recommend this install line (for those of us on mainline/standard who've never used a different toolchain) cargo +nightly install nu
2) Things like ls | where readonly don't work as expected-- readonly should be a bool, shouldn't it?
3) How do you paginate? ls | less doesn't work
Speaking to the business model, in my midwestern city a few coworking spaces popped up only to go broke within a few years. The only one to last is funded by VCs and mostly as their incubator. That VC one is thriving because the rents are heavily subsidized. If they ever rose prices, I doubt their membership would have any problems getting up and leaving as they don't have ties there by the nature of "coworking." It's the Uber/Lyft problem-- easy to switch between 2 competitors offering a commodity service. Good luck ever becoming more than marginally profitable. Heck, they're a real estate business, and they can't take advantage of deductions as effectively as LLCs or individuals can. As this realm matures, and they spend money and effort vetting markets, enterprising partnerships can swoop in offering localized services for cheaper.
I've tried exactly that. Most of what I got back was questioned looks followed by something like, "you mean where do I work?" Maybe I'm around different people.
As a small-timer I don't think I'll ever cloud up. Managing a few servers isn't too bad, is easy to maintain (from both a developer and "dev-ops" standpoint).The cloud abstractions would have been great before Ubuntu's LTS 8-10 year schedule, Nginx and Systemd. But now it's just so simple using those and my existing architecture to launch new web services.
My (naive?) view is that Nginx caches static files by default after the first hit so the inconvenience isn't worth it in my web apps. Would I really see an improvement switching to a SQLite-esque file system?
Their notification was fine. The tweet was vile and full of expletives. You'll have trouble finding any business or institution that tolerates speech like that. This isn't the censorship hill anyone should want to die on.
"Why go public if you literally say you won't make money?"
Because you can get rewarded heavily for it.
They have $88 million in working capital as of June 30, 2019 and are on track to lose another $40 million before the end of the year, so they need more capital. With $330 million carrying value of preferred stock, I think it's go public, somehow issue 100s of millions of dollars in debt or die.
I'm not sure that's any safer. It should protect you from the automated prompt-response systems, where an absolute match is required. But call-center workers see those answers in plaintext. Eventually an attacker will probably reach one where answering, "It's a lot of random letters and numbers. I forgot what they were but the real name is Smith!" will be enough to pass.
Another short, controversial news article with plenty of possibly good points but no actual data. For instance, home ownership is down? Okay, tell me how much and in what areas. Is it mostly densely populated areas that are running out of space? Or is it everywhere? Are there other explanations (like older first-age of childbirth?
QE is unprecedented. If you look at the absolute yields, we're talking about rates below inflation (1.8%). It's an inversion but the magnitude is so low it's hard to compare it to past inversions.
Equity valuations are pretty much in line with earnings with the S&P 500 index as a whole trading around 20x earnings. Considering how low the risk free rate is (US treasuries), that's not a booming valuation and is probably undervalued if interest rates stay this low considering most of these companies return at least 10% on tangible equity.
Unemployment is low right now, but so are wages and so is inflation so it's not like we're booming there either.
Oh wow. At some point I've thrown up my hands and just used Pcg64 because people I trust but can't possibly verify recommended it. Your post reaffirms that that was the right decision (trusting others).
The paper extrapolates from its survey questions about developer time to loss profitability so I think it's fair to discuss risk as more than just developer time. Even so, the developer time risk of poorly maintained packages is enormous (and not just security-related). Consider the time loss from a security issue in a package you have to replace, fix yourself or wait for someone else to fix. Not to mention the non-time losses. The npm ecosystem has thrived despite this and other risks-- if you want developers to adopt your software, make it interesting, easy to talk-about, frictionless to get started with and shiny. Time is a logical consideration that takes a backseat.
npm is full of packages (developer tools and libraries in general) popular with developers but that carry enormous risks-- like short support cycles, breaking changes, security issues, packages that themselves depend on packages with similar problems, among other things. You don't have to let a paper define how you evaluate risk, but even if you co-opt their definition of risk as loss profitability, npm's popularity is at odds with "minimizing risk."
Doesn't pass the sniff test. By developer use, npm, for all of its security issues and orphan packages is the most successful package ecosystem of all time.
Google's AlphaStar StarCraft bot did just this under different accounts. Along with some other fingerprinting, many of the accounts and replays were found by the SC2 community.
FYI, even if you had broken your finger the treatment is almost always splinting and time. Most doctors wouldn't do an x-ray or a vibrating test. Does it hurt? Splint it, come back in a week. Next.
Very few people would happily train someone to take their job. And, some of those people will be vocal about it. The midlevels do the same thing in reverse. It's a stretch to extrapolate this to all "providers" and call that the "core problem" of health expense. How much of your bill do you think goes to the "provider" anyway?.
The west's current monetary policy very much hurts retirees living on dwindling fixed incomes. There ought to be at least some reward associated with savings, even without taking a risk to the principal.
Getting back on the topic of backdooring chips, the US has a strong track-record lately of leaking secrets. You can take some solace in the fact that anything the US would try in that arena has a much higher chance of being leaked compared to authoritarian regimes.