files

My worry is it's going to create VS-specific files, which I'm adamantly opposed to (or any IDE-specific files, for that matter).

You're loading 3 css files and 5 files related to fonts.

Looking naively at github files by type is unreliable, since so many people do things like keep their.vimrc and.vim files on github which artificially inflates the number of.vimL repositories.

We store all of our images, icons and Android OBB files on Amazon S3 and sometimes our bills get totally unmanageable.

Ability to edit very large files with ease was another one in favour of emacs.

Producing some CSV files from a DB is orders of magnitude less work than creating your own analysis front end, so in nearly all cases, this is the solution you're paid to do.

We’re looking for engineers to help us improve the ability to design custom workflows and scale our system to support massive amounts of files.

We like to crunch numbers, log files and whatever else we can get our hands on in Hadoop and Storm.

It's possible to run a macro on a list of files?

I was commenting on his suggestion that everyone start serving their own JavaScript files, and writing custom code to check their sanctity.

I spend most my time doing find-in-files or jump-to-definition or rename-across-this-project.

It's a complex product — job distribution, a revisioned file store with support for large files, containers — so we need people with serious tech chops.

I really don't want you to become the embedded player for.mpg files in all of my browsers, so I'm stuck with a 1"x1" postage stamp on my 26" monitor and no full-screen option).

You could think about: "Oh how can I optimize view rendering in Angular?" "How can I solve head-of-line blocking when using web sockets?" "What is the optimal compression algorithm in order to serve JavaScript files for mobile devices?" I can't imagine a huge number of people think about how to solve these challenges - but I would bet that a lot of people face them.