Yes. That very example shows why itis hard to write fast program in Ruby. It's not even the interpreter (which is slow), but it's that Ruby is pure magic.
I was never able to understand what happens, when I looked at a particular snippet of Ruby code, if it was not me who wrote it. With Go, understanding others people code is a trivial task.
Essence: "A single associate assigned to a specific production line working between the production dates specified (12/14/2020 – 12/21/2020) was found to be using an improper torque wrench technique".
The counterpoint is valid (rising seas don't help), but then we have Saint Petersburg ([1]) that's literally build on top of swamps and occupies multiple islands. It has a first class subway ([2]). It's a little deeper than regular subways, but it exists and works really well.
What are the limits for the number of layers? 176 seems like a large enough number to believe that a few thousands are a possibility. Is the tech any close to a bottleneck, or they will keep growing them up?
That would be up to a specific OS to decide which guarantees on stack size limit would it like to provide. But I agree that it's a valid concern, and not all possible vDSO implementations are reasonable.
vDSO is a good way to mitigate issues like these. It's also a better stable ABI than libc, and easier to maintain than pure kernel ABI (like Linux does), because nobody forbids the kernel to inject different vDSOs to different binaries, if a need arises.
vDSO is also a language independent construct, so there's no special treatment for any favorite language, be it C (OpenBSD), C++ (Windows) or Oberon OS (Oberon).
I've entertained an idea to build a set of tools for contemporary development (version control, code review, CI, etc) which would only speak Gemini. That would be both the UI and the API.
Blockers came fast:
* no way to upload anything that exceeds 1024 bytes,
* escaping is subtly broken and so it would be impossible to review code written in Python or Markdown (triple quotes)
* No text editing capabilities, pretty much.
Which is fine: Gemini is great because it's restricted. It's nearly impossible to abuse. It will find its users, even if it would not be me.
First of all, kudos for trying to find new ways to fund open source. Those are needed.
This approach might work well for issues which require a lot of thought, but produce a simple fix and can be easily merged
This might go horribly wrong if outside contributors try to implement a major feature to a project which they don't have a good mental model for, produce a large patch that may get rejected by maintainers, or end up being rewritten-by-code-review, which would cost such maintainers more time than if they implemented the feature in the first place.
Bloomberg maintains an excellent dashboard that tracks vaccination in the US and worldwide ([1]). It shows that California is one of the slowest states with only 37% of received vaccine administered. Top five states are North Dacota (77%), West Virginia (74%), Oregon (61%), South Dacota (61%) and Texas (60%).
While my account is relatively young (13 days), it's not one day old. You can also look into my comments over this time. So, the accusation is clearly off.
snaps are tied to the proprietary Ubuntu store and they are not available on all of the Linux flavors. For instance, I don't see snapd on Alpine Linux:
I don't believe it's a joke. It still might be a deliberate lie (a random twit is not a real source of knowledge), but so far this is consistent with what we already know. See https://news.ycombinator.com/item?id=25769730
I was never able to understand what happens, when I looked at a particular snippet of Ruby code, if it was not me who wrote it. With Go, understanding others people code is a trivial task.