No, they’re banned because the people who decided the ban disagree with content that questions their political ideology. For example, this includes a lot of books on racism.
Are you aware of what's available on the thing you're posting this comment through? You can't even make a book with content close to as graphic as what's available here. The kids are fine, it's the fascist adults we need to be concerned about.
The problem is that it is impossible to create an engine that will run on synthetic fuels, but is guaranteed to never run on fossil fuels even if modified / hacked, because they’re chemically identical for all practical purposes. There might be some type of DRM-like solution, but given the economical incentives involved, that will be circumvented by car owners. The whole thing is an incredibly stupid idea and will probably lead to the ICE ban being ineffective.
Right, the way you solve this isn't by regulating the cars or their engines themselves (beyond certifying tested performance on synthetic fuels) - instead, you simply regulate the sales of petroleum derived fuel and only allow the sale of synthetic fuels.
In 2035 cars from 2015 will still exist and need to be fueled, let alone cars from 2034. And people driving 20 year old cars can't afford to spend 6x the price for synthetic fuels.
JIRAs growth strategy was based on developers adopting it without having to talk to their bosses first because it was cheap enough to do so. Nowadays, this probably works differently, but that’s how they initially gained traction.
I'm just saying that Sweden, Norway and Finland together would make an awesome couple; given how they overcame legislative issues and how they modernized their countries against all odds (with all that happened after 1808).
From a political perspective they're quick to adapt to a changing landscape.
Apple has a 100% monopoly on the market for iOS app distribution, which can be argued is bad for the customer because the 30% revenue share they take is inflating app prices.
People keep saying this but in an antitrust case you cannot simply declare the narrowest market that fits your argument and expect the court to accept it. The court will examine the market reality and examine how consumers actually behave to determine what the actual relevant market is, and it's unlikely that a court would find "iOS app distribution" to be a separate and relevant market for antitrust purposes. I've explained why in detail elsewhere [1], but in short, the US legal system generally does not consider an aftermarket consisting of a single brand's product to be a relevant product market unless specific rules are met:
> Because it would be inappropriate to punish a firm for its natural monopoly in its own products, courts embraced a sweeping prohibition against analyzing alleged anticompetitive activity by focusing on single-brand relevant markets: "[A]bsent exceptional market conditions, one brand in a market of competing brands cannot constitute a relevant product market." [2]
For a much more thorough explanation see my linked comment below.
Unfortunately, PHP doesn't ship a tool for this (and it’s hard due to the way autoloading works). So PHP's typing is slightly less useful than e.g. TypeScript.
They do static analyses that go beyond type checking. I have not tried phan and psalm, but the last time I used phpstan its type analysis threw false positives because it was using incorrect assumptions. So my impression is that phpstan lacks the rigor of a true compiler‘s type checker phase.
In my opinion, the PHP distribution shipping an official type checker which does nothing other than verify type correctness based on the information in the code would be much more useful. Kind of like `php -l`.
Tooling is not the issue here, nor is autoloading.
ISO C and C++ doesn't provide tooling, nor should any language. Tooling is better handled by third parties and implementers. Language should be focused on application and execution of the language. Unfortunately for PHP the language and implementation are tightly coupled as is Java and Swift.
A well constructed modern PHP project using composer has the tooling needed to statically validate. Personally I use PHPStorm but I also use IntelliJ for Java and Android. There are others out there as well.
Autoloading used correctly is no more than Java using a package line or namespace.
I find no problem with TypeScript and others. I however have a 10+ million line code base of PHP that predates TypeScript and others and needs to get a viable transition path. This gets things closer with real type errors at runtime. That is way better than my mainframe COBOL counterparts who have no path forward at the level of modern code.
Tooling inside IDEs is somwhat useful. But being able to just run a compiler-like CLI tool to tell you if there are type errors in your program is much more useful still, since you can run it in pre-commit hooks and on the CI. As far as I know, a tool which can do this _without_ requiring extensive configuration and without throwing false positives does not exist yet for PHP.
As for the "language shouldn't provide tooling" argument: You picked C / C++ as a positive example for this. Those are standardized languages which evolve at a glacial pace. For most of their use cases, this is a good thing. But I'd say PHP's faster evolution over the last decade was the right thing for that language. Other modern language projects seem to follow a strategy of a single standard implementation with extensive tooling pretty successfully (e.g. Go, Rust, Swift, ..).
There are phan, php-stan or psalm tools from third parties which add this functionality to PHP. All three of them are very good and actively developed.
When I want to buy cherry tomatoes in German REWE, usually half the varieties have their unit price listed in €/100g, while the rest is in €/1kg. While metric does make converting in your head easy, I bet this still throws off a lot of the non-mathematical people and is done very much intentionally.
> * Checkm8 doesn't bypass the protections offered by the Secure Enclave and Touch ID.
All of the above means people will be able to use Checkm8 to install malware only under very limited circumstances.
> * The above also means that Checkm8 is unlikely to make it easier for people who find, steal or confiscate a vulnerable iPhone, but don't have the unlock PIN, to access the data stored on it.
„Under a second“ might be ok for websites, but doesn’t cut the mustard for web applications. People expect highly dynamic user interfaces which react almost instantaneously.
