Hey, fun to see my fun little project showing up on HN!
Yes, aliasing the CLI command to a remote script is not exactly best practice. My casual question to myself when I made it was … what’s the literal easiest way I could get this to work on someone’s computer with as few dependencies as possible? This was the solution I came up with. (And in my defense, it is similar to how you install homebrew … `/bin/bash -c "$(curl -fsSL https://xn--rvg)`, but I get that most wouldn’t trust a somewhat random GitHub account like this.)
If you have any questions about this, let me know! My website (https://jamon.dev) runs on it (in a DigitalOcean droplet) and I’ve enjoyed the experience.
I love this so much. I got my start on QBasic and made hundreds of games between 12 and 19 years old. I eventually left it behind, but always had a fond spot in my heart for it.
Last year, when I was going to rebuild my personal website, someone on Twitter challenged me: “Build it in QBasic, you coward”. I was like “haha…wait, can I?”
And I did! It runs on QB64 on a DigitalOcean droplet.
This is one of the big problems App.net always had, in that it wasn't at all intended to be a "Twitter alternative". Alpha was supposed to be an example of what could be built on the platform, not the entire product itself.
At Infinite Red we chose React.js over our previous choice of Ember not because it was objectively better at web, but because it lowered the context switching when our devs would switch between mobile and web projects. We have many devs who only handle web or only handle mobile, but for the ones who can do both, it's well worth it.
React.js being superior/inferior to Vue.js or others isn't very relevant unless the gap is huge, which it's not.
I should also mention that we've found React Native to be far more productive to use than Appcelerator or Xamarin. Not sure what the author used to determine those charts near the bottom.
Complaining about longevity of React Native and then recommending two proprietary, non-open-source competitors is, frankly, absurd. If Facebook ever abandons React Native we have all of the code and can continue to support it ourselves. If Microsoft or Appcelerator ever shut down their platforms for any reason, we're SOL.
While there are some valid concerns with using React Native, the productivity gain and community make it a more than worthwhile trade off.
One of the slides shows "Rails is still the best choice for entire classes of apps."
"Best" is of course usually subjective, and this could spawn huge internet arguments back and forth about the relative merits of various solutions. But I think there's perhaps an objective argument to be made that this isn't true now, and won't be true with Rails 5 and beyond.
I own a web + mobile app dev shop (Infinite Red). Our background is Rails, and some on our team have been using Rails since pre-1.0 (Steve Kellock, for example wrote the first Rails guides, and his name still appears on the website). We have loved Rails (and Ruby) for a long time.
But the concurrency and scalability difficulty of Rails isn't just an opinion. As we've built larger and larger applications on Rails, the amount of effort put into making Rails scale gets disproportionately high. Not to mention server costs.
Yes, it's totally possible to scale Rails. No, not every Rails app needs to scale to Twitter-level. We get that; we've been doing both for years.
When we discovered Elixir/Phoenix [cue the groans, sorry] it felt like we kept the magic of Ruby on Rails while (in a single stroke) we also made a giant leap forward in concurrency, scale, and reliability. In my opinion, this is the direction the Rails community would be better off going. We felt so strongly about this that my partner Ken Miller wrote a piece titled "Phoenix is Rails 5". https://shift.infinite.red/phoenix-is-rails-5-f6d28e57395#.1...
We don't need Ruby on Rails to be great again. It's done its job and we're all better for it and grateful for it. We don't have to become Node.js developers and abandon all the things we love about Ruby and Rails. We have a better alternative: Elixir/Phoenix.
Rarely are we in a position to "accept" or "deny" changes in language. They just happen, with or without our consent. All we can do is try to keep up and make some sense of the current state.
Makes sense. For the record, I don't know much about the issue at hand, was specifically talking about one-word contributions (which I encourage on my project).
@buckbova, what's wrong with one-word changes? I run a semi-popular OS project and accept them all the time. It makes the newbs feel good and encourages them to explore further into the source code.