In the short term that would impact their stock price way too much; I don't think they would pull that trigger.
In the long term this stance will become untenable if other regions come to the same conclusions. Anti-competition investigations against Apple are currently running in:
Yes, that feature is called "Collections". An item (login, card, secure note, etc.) can be shared into multiple collections (only within one organization). For each collection per user permissions (none, read, write) can be set.
Your argument against serverless functions holds for AWS Lambda, but this Gitlab feature is based on Knative. That's an open source serverless platform based on Kubernetes.
I think all money Amazon is throwing at serverless is to build a foundation to ultimately transform all their "managed" services into a serverless form. They already released serverless RDS (https://aws.amazon.com/rds/aurora/serverless/).
Good to know that it's open source. I should have looked it up first.
My understanding of Serverless was that it was synonymous with 'Functions as a Service'.
What Knative seems to be doing is more like 'Backend as a Service'.
I guess it's good to know that these two very different approaches are now both labeling themselves as 'Serverless'.
I guess Knative is just hitchhiking on top of Amazon's marketing success around the 'Serverless' term.
I'm fairly certain that under the hood serverless RDS is just "intelligently and dynamically adjusting the instance type with zero downtime" though, not really technically interesting compared to Lambda-serverless.
Is there a 'Material Design' recommendation towards mutating icons? I would guess not, because the sorts of tangible things in which it finds its inspiration don't mutate in place. (They might slide in/out/over/etc.)
update: I did find a suggestion that such mutations can be 'delightful details', at http://www.google.com/design/spec/animation/delightful-detai... – seems a bit of a stretch to me, a subtle, non-'material' UI change that's quite pretty but perhaps easy-to-miss or prone-to-user-error. I suppose as long as it's confined to toggles, as in the page's examples, the flourish is low-risk.
Or if you're already in the process of minification you can also fix these injections automatically, with a simple regex or https://github.com/btford/ngmin.
Interesting software stack running this registry: Wordpress on Apache/MySQL to serve the website and Node.js with SQLite to automatically add content using the Wordpress API.
https://github.com/jquery/plugins.jquery.com
Wordpress is good at serving essentially static content so that part seems reasonable. The jQuery team is good with JS so node makes sense for building backend services. The service itself is not complex and probably doesn't have huge scaling concerns. Essentially performs a git pull when triggered by a webhook.
Wordpress is good at serving static content? Web servers are good at serving static content. Wordpress is a huge, monolithic CMS with vulnerabilities appearing frequently, thus I would call it rather bad at serving essentially static content.
"It is a kind of demoscene contest, where beauty come first. You do not have to produce a one-on-one copy of the painting. The jury rates on quality and creativity of the used algorithms."
In the long term this stance will become untenable if other regions come to the same conclusions. Anti-competition investigations against Apple are currently running in:
- US (https://www.justice.gov/opa/pr/justice-department-sues-apple...)
- UK (https://www.gov.uk/cma-cases/investigation-into-apple-appsto...)
- Japan (https://english.kyodonews.net/news/2024/06/bc2d7f45d456-japa...)
Australia (https://www.accc.gov.au/media-release/new-competition-laws-n...) and India (https://www.reuters.com/technology/google-amazon-apple-lobby...) will follow soon.