Having a built-in ad blocker doesn't hinder an app from also accepting extensions which block ads.
1,862 karma · joined January 18, 2011
http://colintheshots.com
[ my public key: https://keybase.io/colintheshots; my proof: https://keybase.io/colintheshots/sigs/4YdtDSG8zFyKbYG1bOtsNBIVYkrl26QpnsVA1pT7zqY ]
Having a built-in ad blocker doesn't hinder an app from also accepting extensions which block ads.
As Ricky would say, "It doesn't take rocket appliances."
We already support a very limited set of the WebExtensions API to offer features like Reader Mode. Rest assured that more features will land in the coming months.
If you're a developer and you want to help us, our Github site is at this link. We mark easier issues with a Good First Issue label. We also need help with translations, documentation, and even getting issues filed.
Long press the link.
It's not the same thing, but the built-in tracking protection incidentally blocks a portion of ads.
TL;DR: There was too much cruft built up.
Work should move faster now. We substantially grew our Android team in the last year.
In this case, she's arguing that their insurance partners do not provide voluntary parting insurance. This may be technically correct. However, the way insurance works is you can always go to an insurer of last resort and ask for exceptions. Lloyd's of London will cover race cars while racing or space vessels for accidents, for example, even though those are hardly standard policies. Nearly anything can be covered if you set the premium and deductibles high enough. They have billing codes for some pretty bizarre insured cases.
An entire sharing economy of companies could easily devise an insurance product that meets these needs if they worked to make it to happen. It would be trivial to scare consumers away from competitors that do not provide this.
Tesla isn't having a great look on Wall Street, but that's because investors priced them as a tech company instead of a car manufacturer. They're having demand issues, but they'll adjust and markets will adjust the way they price Tesla shares. They still had no trouble raising funds despite serious new direct competition.
Solar is making huge international wins from cheaper, non-domestic manufacturers, including a few of the first massive installations to come in cheaper than coal.
Immigration is a real issue, of course, but a lot of companies have adjusted by opening R&D offices in Vancouver to be close to the border and the time zone of US tech offices.
https://en.wikipedia.org/wiki/List_of_nuclear_and_radiation_...
The problem with having any discussion of nuclear is agreeing upon the facts. It's crazy hard to find an unbiased source. If you asked a random bystander why we haven't built nuclear reactors in recent years, you might hear "environmentalists." However, the truth is dramatically different. No one will insure a nuclear power plant except the US government. Investors won't invest in nuclear, as there's no appetite for the risks to open a plant and spend over a decade building it when cost overruns are common and it may never actually open.
The reason wind and solar are growing much, much faster than nuclear today isn't because of "environmentalists." It's because nuclear involves far more subsidies and risk.
I'd have them write down the instructions to make their airplanes. Then I'd follow their instructions in the strictest, most literal sense possible, resulting in some lopsided airplanes.
It was a great beginning lesson in algorithms.
The work to make GeckoView offer a full set of functionality in Focus should also help other apps.
Kotlin also works on iOS through AppCode and Kotlin/Native, but that integration is still very young. I can't promise you won't have platform issues along the way.
I've found far too often over the years that companies decide to use a hybrid framework to save time and money and take just as long to write the app with equally as much cost. Then no one wants to maintain the finished product. It requires too many unlikely skill sets and trickier debugging.
React Native isn't automatically cheaper because it's a hybrid. Hybrids work great for trivial apps that look a lot like the examples. A hybrid framework also has to address every new niche the native solution fills or else integrations themselves add up to a massive cost.
Several years ago, I joined a Midwestern startup just before the Series A as one of the first ten employees and the first mobile FT dev. I took a pay cut to join and was explicitly promised ownership and real "skin in the game." Nine months later, when they finally devised an options pool, I found I had been granted 0.065% and left immediately. It was like they'd stolen months of my work. Today, they have over two hundred employees and are probably headed to a large equity event.
Another startup I joined raised a lot of money and paid almost market rates to some of the best developers in town. Their tech was some of the best in the city, but they pivoted and lost most of their developers when they didn't achieve product-market fit. They will probably only ever reach a tiny multiple compared to what their investors desired.
Microsoft explicitly detected DR-DOS and pretended that the DOS crashed instead of starting Windows, which worked just fine on DR-DOS before then. This was ruled an illegal practice even though Microsoft had been far smaller at the time.
In the end, I scored a job with a FAANG company literally because I didn't want to work there. A friend warned me away before the interview for work-life reasons, but I decided to go ahead with the interview anyway as practice and I nailed it. There's no reason to stress if you don't want the job. Another friend who worked there later convinced me to take the offer.
What bothers me is: you're basically the same coder both before and after competitive coding practice. You're only more marketable with the same skills.