aashcan's comments

aashcan | 6 years ago | on: Disable new Slack WYSIWYG editor with this bookmarklet

Just got another note from them:

  We really appreciate your feedback, and we hear your frustration. 
  We're sorry for the impact this is having on your ability to communicate with your team and on your overall productivity. 
  We made a mistake by forcing everyone into this feature without providing an opt-out for customers like you: people for whom the existing behavior was working just fine.

  We've started working on a preference that will let you return to the previous message composer. 
  We don't have a specific release date to share right now — it's this team's top and only priority, however, and we expect to have it available on the desktop within a couple of weeks, with Android following shortly thereafter.

  We will follow up with another note when this option is available to you, and we'll include instructions on how to enable it.

  Again, we're sorry for the disruption and we're grateful for the feedback. 
  We missed the mark on this feature! We will do our best to learn from this and avoid similar mistakes in the future.

aashcan | 6 years ago | on: Slack’s new WYSIWYG input box is terrible

Just wrote in,

  Thanks for sharing your experience with our new formatting UI. I'm sorry to hear it's been a little disruptive so far.
  There isn't a way to revert to the old formatting method, I'm afraid. 
  We don't currently have plans to make the new formatting configurable 
  though we are carefully considering all our customers' feedback.

aashcan | 6 years ago | on: Async-await on stable Rust

Could you share some resources? I'm trying to move a Hyper + Tokio-core + Futures project to the newer versions and am struggling..

aashcan | 7 years ago | on: Atom 1.36

Still stick with Atom as my main text/code editor here. I started out with it mainly to write LaTeX, but since do most of my code editing also in Atom. I looked at VSCode back in '17 but found it quite clunky and not as intuitive as Atom. Things like changing key-binding based on a profile for example needs a quick Google - or maybe I am just slow!

I keep going back now and then to VS Code especially when I need to use the debugger to step through some code. But otherwise, my workflow since has evolved around the little niggles of Atom(like having to open separate terminal windows) so I don't feel the need to switch.

aashcan | 7 years ago | on: Atom 1.36

>The fuzzy finder’s project crawling performance has been improved dramatically by switching to a ripgrep-powered backend. This is most noticeable in projects with large numbers of files - for example, we measured a 14x speed boost in a project with 270K files.

Another leaf out of VS Code's book?

page 1