Rémi Quenin @azagoth - Twitter Profile

@cyberkm @ChristerEricson If you're saying ui "text and filenames" 👍 Else, if "ui text" and "filenames", for runtime, I would argue that even filenames should be replaced with IDs in your archive 😁

1

0

Rémi Quenin @azagoth

over 5 years ago

@ChristerEricson *if

0

Rémi Quenin @azagoth

over 5 years ago

@ChristerEricson Think about threading from beginning of applicable

1

2

0

Rémi Quenin @azagoth

over 5 years ago

@ChristerEricson Limit as much as possible external dependencies, and don't let them spread through your API. And think about your API sooner than later. Clean, simple, dependance-free API are a breeze to use.

0

4

0

Rémi Quenin @azagoth

over 5 years ago

@ChristerEricson When applicable, separation between runtime and edition data structure/serialization/code: this ensure performant, compact, and tight runtime, while keeping good user experience (content people AND progs) with adapted tools/edition code/data structure

0

5

0

Rémi Quenin @azagoth

over 5 years ago

@incomputable @lefticus I was mostly trying to enhance the dramatic effect by being categorical, but after all, maybe not. I've been fooled in the past by being sure that this O(n!) algo was the problem, only to discover by profiling that a container was passed by value.

0

Rémi Quenin @azagoth

over 5 years ago

@incomputable @lefticus All performance claims must be profiled

1

6

0

azagoth retweeted

Alexandre Ganea @alex_toresh

over 5 years ago

@azagoth @sheredom @Ca1ne @olson_dan We do have a team indeed, and we’re looking to scale it up! 😄

0

3

1

0

Rémi Quenin @azagoth

over 5 years ago

@sheredom @Ca1ne @olson_dan @alex_toresh

1

0

Rémi Quenin @azagoth

almost 6 years ago

@wadetb Well, again, I'm no expert, but to my understanding, it is just a proxy with a cache... We're using ngnix servers, and it's pretty light. Priming this cache depends mostly on the amount of data, and the quality of the link, not the server software.

0