Yeah, I didn't realize that there's a new sort of verbose mode now which is different than the verbose mode that was included previously. Although I'm still not clear on the difference between "verbose mode" and "ctrl + o". Based on https://news.ycombinator.com/item?id=46982177 I think they are different (specifically where they say "while hiding more details behind ctrl+o".
> To be clear: we re-purposed verbose mode to do exactly what you are asking for. We kept the name "verbose mode", but the behavior is what you want, without the other verbose output.
Verbose mode feels far too verbose to handle that. It’s also very hard to “keep your place” when toggling into verbose mode to see a specific output.
As someone who loves all the non-AI portions of Graphite (the CLI and the reviewer UI) should I be worried about this acquisition? Or will the CLI and Reviewer Ui continue to be be maintained and improved?
> He's also implying that Rails does not use web sockets to communicate with frontend which is not only wrong it should be evidently wrong to anyone who built a Rails app in the last 3 years
Where is the article saying that? I only see " Those things are possible in Rails and Laravel, but they take a bit more effort to set up." which is a very different (and more nuanced/personal take) then what you're stating.
What does bug me is being forced to store all my data on their servers. I'm sticking to v4 until I'm forced onto something else (or I build my own replacement)
I think one of the things that got slack going is that they have an actual free tier. I've wanted to use something like campfire or hipchat among dev teams before but I wasn't able to get someone to sponsor the lowest tier so we could just try it out. Also the devs were reluctant because everyone was in the same office.
I think he's referring to real-time enterprise collaboration. Things like Slack and Hipchat (and maybe Google Wave, but obviously that wasn't successful).