Live data from Hacker News

I'm leaving Ruby Central

gist.github.com

41–50 of 134 posts

Re: I'm leaving Ruby Central

#41

it was never clear what the niche of Ruby was other than being a modernish scripting language for non-critical web dev. I remember Ruby on Rails becoming trendy for web startups with inexperienced programmers (I was one of them) to prototype things in because Active Record was a simple ORM for its time, outside of that there wasn't much other justification for the stack and since the proliferation of similar easy-to-…

The proliferation of frameworks came about from the ideas and design of Ruby on Rails. MVC and ORM had been around before web apps, but it was not consistently used in a web framework until Rails. Convention-over-configuration, “nested doll pattern”, and Rack protocol were all ideas widely ported and copied into other language platforms and frameworks.

Also, ActiveRecord gained significant capabilities with named scopes, something that isn’t as widely copied.

Finally, Ruby itself lends itself well to writing DSLs, something that Javascript and TypeScript sucks at, but sometimes I still see people try and fail.

To be fair, it is my personal opinion that there has not been anything substantially innovative since Rails 5. The features I have seen since is better done with Elixir/Phoenix, mainly because the BEAM runtime makes better concurrency primitives available.

Re: I'm leaving Ruby Central

#42

Contextually it might be relevant that Ruby Central said they wanted to have a Zoom call today to explain everything, then cancelled it. This was their message. "Hello Ruby Community, We recognize that our originally scheduled Q&A session overlaps with the observance of Rosh Hashanah and may not have been the best timing for many in our community. We sincerely apologize for the short notice of this change, especially…

[deleted]

Re: I'm leaving Ruby Central

#44
post #37

Ruby Central should have been more involved in the development of rubygems (software) in the past and establish a community and contribution guideline, to secure the project, secure funding, maybe separating concerns (infrastructure, conferences, etc.) However, taking away funding as retaliation for a conference talk is offensive, too. In the end facts (money) made the decision. I don't think Shopify has bad intentio…

From my reading it was about rv the new tool that hopes to replace rubygems and the push to remove the competition.

The losing of sponsorships because of the talk is what gave shopify leverage. And they used it.. out of fear over the rv tool.

Re: I'm leaving Ruby Central

#45
post #23

Contextually it might be relevant that Ruby Central said they wanted to have a Zoom call today to explain everything, then cancelled it. This was their message. "Hello Ruby Community, We recognize that our originally scheduled Q&A session overlaps with the observance of Rosh Hashanah and may not have been the best timing for many in our community. We sincerely apologize for the short notice of this change, especially…

Wow. I've seen less corpowashed decision making out of Microsoft. They set their house on fire, its burning down, but spraying water on it would get the curtains wet so we can't do that.

That's hilarious. "Our business decisions are questionable but for religious reasons we can't talk about it right now now"

Re: I'm leaving Ruby Central

#46
post #39

Earlier quoted context omitted.

What I don’t get is, what does Shopify get from this? I’m assuming there’s a ton of reputational risk in this move, and my understanding as an outsider is that Shopify already has a ton of weight in the Ruby ecosystem - they seem to be the one case quoted by everyone as the “proof that Ruby scales”.

There are arguably larger reputational risk issues in a company with significant financial/payment activities not having adequate control of their technology. I'm not saying that justifies anything here as I don't know nearly enough about, but I'd wager that even a minor incident arising from them not adequately controlling their stack would create infinitely more issues than this move.

Supply chain attacks are big shareholder news lately?

Re: I'm leaving Ruby Central

#47

Just a glimpse: > London is no longer the city I was infatuated with in the late '90s and early 2000s. Chiefly because it's no longer full of native Brits [1] [1] https://world.hey.com/dhh/as-i-remember-london-e7d38e64

I am so disappointed by this - thought he was a nice guy.

For some reason I always had a feeling about him. Perhaps I couldn’t understand why a guy that did so well in life like him found so much time to pick fights on Twitter. With the kind of money he had, I’d pay to be anonymous.

Re: I'm leaving Ruby Central

#48
The solution is to design package managers around the uniform resource identifier: a way to locate online assets that is mostly (ignoring DNS) decentralised and better than having one org own all the packages.

Re: I'm leaving Ruby Central

#49
> My critique is directed at the process, not at people.

People are not logs floating helplessly in a river. People take decisions and make things happen. They create and run the process, not viceversa.

The critique must be directed at people.

Re: I'm leaving Ruby Central

#50
post #39

Earlier quoted context omitted.

What I don’t get is, what does Shopify get from this? I’m assuming there’s a ton of reputational risk in this move, and my understanding as an outsider is that Shopify already has a ton of weight in the Ruby ecosystem - they seem to be the one case quoted by everyone as the “proof that Ruby scales”.

There are arguably larger reputational risk issues in a company with significant financial/payment activities not having adequate control of their technology. I'm not saying that justifies anything here as I don't know nearly enough about, but I'd wager that even a minor incident arising from them not adequately controlling their stack would create infinitely more issues than this move.

If supply chain integrity is the issue specifically for Shopify, couldn’t they run their own private, internally facing gem repository and whitelist everything that goes there? It’s not a requirement to use the public rubygems.
Post reply on HN