I can confirm. Russel group universities will grant masters degrees to people who do not show up for lectures, do not possess functional English, and do not perform the coursework. The exams are dumbed down to ensure a high pass rate. Everyone understands their job and pay depends on the international student fees.
I'm ok with saying that Open Source is now widely understood to mean what the OSI says, that's just a function of how language evolves. But we don't need to re-write history to get there.
Open Source isn't a brand, it isn't a trademark, it was hijacked by OSI to enforce their specific interpretation of a phrase that was already in use. OSI wasn't founded until 1998, over a decade after the term open source software became popular and was used throughout the unix and linux communities and in businesses such as Caldera. Before OSI came up with the OSD many creators of open source software had non-compete clauses in the licence.
"Open Source software" was never a popular term before the OSI promoted it. "Open Source software" is a reworking of the original term "Free software" to be more palatable to businesses. The Open Source Definition is very similar to the older Free Software Definition and virtually all software qualifies as either both or neither.
Likewise I feel like it only became "the common understanding" due to pushing within the past decade. Before that "the common understanding" was what people are only now calling "source available" - which I don't think I'd heard of before just a couple years ago.
This could have been some custom cdk constructs. Then at least you can plug in SQS / SNS / DynamoDB / CW / IAM all in one solution. Flightcontrol doesn't seem to offer these.
I’ve been getting great mileage out of service catalog products. They’re a great middle ground between custom CDK and in-house PaaS. You can even use them as CloudFormation resources so they compose well and users are agnostic to which CDK language (or Terraform even!) that is used to write them. I’m currently experimenting with using them to expose terraform modules as CDK constructs.
Oh interesting, what was your experience with it, out of curiosity?
For my part, there was some initial friction making it usable from the publisher perspective but haven’t really had issues using it from the consumer side.
Anti-meritocracy was in in some CoCs, arguing in its favour was a reason for exclusion from an event / project. Even if the argument happened somewhere else on the internet and not in the project.
Whenever I see someone dying on the hill of fighting for 'meritocracy', in the words of another poster in this subthread, I have found them to be:
> ...a zealot about their cause. Deflecting and uncompromising, very unagreeable. They would be the last persons to know how to make a community comfy.
... And typically with a giant chip on their shoulder. The real world's a little bit more complicated than the spherical cows that the near-religious faith in it requires.
It highly depends on what you understand that word to mean. At first it was just meant to to pronounce fairness. Nothing more to it. It was used in a context to explicitly disregard who people are and focus on what they do.
And of course it wasn't meant as an instruction manual for how to run a society. It was quite explicitly a message that you are not judged by who you are. That is it, there is no ideology, there is no grand idea. That is media garbage that filled your head with a phantom.
And honestly, that did a much better job than most COC I read.
I'm not sure how your comment is relevant. No one is fighting for meritocracy here. Only providing the requested information about a case where CoC pushed a specific political view and excluded others.
The EU did put in regulations, but they did the opposite and essentially mandated DRM. They want to prevent owners from turning off nanny devices or overriding pollution controls.
Could be due to American climate and Leafs getting sold heavily in America. Jeff lives in a place hotter and sunnier than Málaga. Cars can roast in their huge unshaded parking lots with black tarmac.
This is popping up because SurrealDB was found to turn fsync off by default. But there are important differences:
- SurrealDB provides poor documentation about this default
- SQLite is typically run client side, while SurrealDB is typically run as a remote server
- SQLite is actually full sync by default, but distros may package it with other defaults
- SurrealDB explicitly did this for benchmarking reasons (for comparison fairness) while SQLite distros turn off fsync for typically practical reasons as it's run pure client side.
I think there is some nuance needed here. If you ask support to partition your bucket then they will be a bit annoying if you ask for specific partition points and the first part of the prefix is not randomised. They tried to push me to refactor the bucket first to randomise the beginning of the prefix, but eventually they did it.
The auto partitioning is different. It can isolate hot prefixes on its own and can intelligently pick the partition points. Problem is the process is slow and you can be throttled for more than a day before it kicks in.
They can do this with manual partitioning indeed. I've done it before, but it's not ideal because the auto partitioner will scale beyond almost anything AWS will give you with manual partitioning unless you have 24/7 workloads.
> you can be throttled for more than a day before it kicks in
I expect that this would depends on your use case. If you are dropping content you need to scale out to tons of readers, that is absolutely the case. If you are dropping tons of content with well distributed reads, then the auto partitioner is The Way.
Azure functions don't operate in the same way, they are more like AppRunner's architecture. They then layer on the Lambda billing model.
It was typical Azure strategy of rushing out a product to show they have all the same features as AWS. It may have improved since I last touched it in 2018.
reply