71–80 of 134 posts
> 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.
[0] https://press.uchicago.edu/ucp/books/book/chicago/U/bo252799...
Earlier quoted context omitted.
[flagged]
[flagged]
Because of this they lost a 250,000 sponsorship from sideiq which then gave leverage to shopify to takeover the community because of a fear of this rv tool.
In the end their communities purity tests lost them everything.
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
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 sco…
> MVC and ORM had been around before web apps, but it was not consistently used in a web framework until Rails. WebObjects and EOF were the MVC and ORM frameworks powering Disney (Go.com) almost a decade before Rails existed.
A decade before Rails puts it in 1995. Do you have some resources on this? I like looking into the history of tech.
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-…
> it was never clear what the niche of Ruby Ruby on Rails Chef --- Some of the largest websites in the world run on Ruby: GitHub and Shopify.
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.
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.
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”.
They are a multi-billion company that is highly dependent of RubyGems and a breach could ruin their business. So they have intrinsic reasons to support anything that keeps Ruby and Rails floating.