As an Australian, I struggle at times with Europeans et al who attach so much importance and stress to such insignificant things. Hence, she'll be right mate.
139 karma · joined July 11, 2018
As an Australian, I struggle at times with Europeans et al who attach so much importance and stress to such insignificant things. Hence, she'll be right mate.
I first found out about Kalman Filters when looking up how large ships use software to remain stationary in the same geographical location even whilst surrounded by crazy waves.
The word 'each' conveys the intent of this code way more explicitly.
As a quick example, the Svelte 'ecosystem' is simply the Javascript ecosystem, which existed well before React. You can import any npm module to a Svelte app. Outside of the React-specific packages (which I argue are overkill), such as Redux or Redux-enabled form libraries, what are you missing? Pre-styled components like calendars, modals, popups, are available in a range of vanilla-JS packages. Anything more than that and it's possible that React thinking has over-complicated your approach.
https://support.apple.com/en-us/HT208108 https://support.apple.com/en-au/guide/security/sec59b0b31ff/...
From my understanding, you've got Docker for defining your app's services, you've got Kubernetes for orchestrating them, you've got Terraform et al. for defining/configuring your infrastructure, and now you've got CNAB/Duffle to bring all these tools and configs together under one umbrella.
> Does it run on Linux?
From the article[1] posted above:
> By design, it is cloud agnostic. It works with everything from Azure to on-prem OpenStack, from Kubernetes to Swarm, and from Ansible to Terraform. It can execute on a workstation, a public cloud, an air-gapped network, or a constrained IoT environment.
[1] https://open.microsoft.com/2018/12/04/announcing-cnab-cloud-...
> ...but not annoyed by errors they don't care about. Telling which from which is highly contextual, and the language rarely has that knowledge.
Isn't this where the programmer's knowledge + a little thinking come into it? With experience you come to understand what kind of errors certain functions will return and then you spend a little time thinking about the context this error may appear. With this you determine whether the error has to be handled or can be safely ignored via a '_'.
That sounds more like laziness on the part of the programmer, rather than the language design.