hopsoft

7 ms·

1.
by hopsoft 2y ago
SOS mode in Utah also.
2.
by hopsoft 5y ago
As far as security is concerned, it's the application's responsibility to properly scope websocket connections... if and when that's appropriate. This is true of any websocket connection, not just those used by StimulusReflex
3.
by hopsoft 5y ago
I recently Dockerized a Rails development environment for working on an M1. It’s gone well so far and may provide some guidance for other development workflows (YMMV). https://gist.github.com/hopsoft/c27da1a9fda40516999
4.
by hopsoft 6y ago
I think the much touted "NEW MAGIC" will be the thing that does the automatic content refresh.
5.
by hopsoft 6y ago
This is exactly what CableReady was built for... to update the DOM from any Ruby process (in the request cycle or not). It was designed from the beginning to update the DOM from out-of-band non-request based workflows like background jobs.
6.
by hopsoft 6y ago
Just saw that this is on HN. Happy to answer any questions.
7.
by hopsoft 7y ago
> the DOM was often used to store state. And this just isn't a very efficient approach. StimulusJS is a modern approach that uses the DOM to manage state. In my experience it has proven to be quite simple and performant. https:&#x2
8.
by hopsoft 8y ago
Interesting point about grassroots vs top down. I think that definitely plays into the equation. Another big part of it is that developers seem to a unique class of workers that don’t seem learn much from those who preceded them. We love to
9.
by hopsoft 8y ago
I'm not sure any other technology stack would have fared much better. Consider that 6 years, 2 months, and 20 days passed between Rails 3.2 and Rails 5.2. That's quite a bit of time for the framework to evolve. Then factor in the
10.
by hopsoft 8y ago
You’ve setup a false dichotomy. Servant leadership can & should be decisive.
11.
by hopsoft 8y ago
Rails (server side rendering) + Heroku.
12.
by hopsoft 9y ago
Our tools & materials are constantly changing... not to mention that every project is different in various ways (though many developers delude themselves into thinking their project is unique i.e. the snowflake effect). I've found
13.
by hopsoft 10y ago
What about Traveling Ruby? I've never used it, but it looks promising. https://github.com/phusion/traveling-ruby
14.
by hopsoft 10y ago
Sounds like Stripe may be a large service oriented system written in Ruby but not Rails. https://www.quora.com/Why-did-Stripe-choose-to-use-Ruby-for-...
15.
by hopsoft 10y ago
> Don't confuse your job with your family. Reminds me of this terrific article from David Brady. https://heartmindcode.com/2013/08/16/loyalty-and-layoffs/
16.
by hopsoft 11y ago
I wrote a script to benchmark some of the diff strategies for anyone curious. https://gist.github.com/hopsoft/ae361319c54bbcb4f8e2
17.
by hopsoft 11y ago
Why? Genuinely curious.
18.
by hopsoft 11y ago
Conway's Law & micro-services help maintain flatter organizations at least in tech focused companies. When disagreements arise & consensus is hard, the various parties can simply introduce a new service boundary & go their
19.
by hopsoft 11y ago
I do like the access-granted DSL. It seems to address some of CanCan's problems on larger more complex projects. Also... if you prefer a more OO style, I wrote a 50 line authorization lib that has proved workable on some of my larger p
20.
by hopsoft 11y ago
Here's a very similar tool in Ruby. https://github.com/hopsoft/goldmine
21.
by hopsoft 13y ago
I built a small testing framework with a pry workflow as one of it's goals. It's possible to run the tests in pry mode which drops you into a pry session on test failure. I've used it on several small libs & the test+pry
22.
by hopsoft 14y ago
Removing the ability to run code on gem install would be quite disruptive. I think that establishing a universal gem signing policy and/or some form of whitelist/blacklist strategy would be a better solution. Consumers need to be able to tr