The complexity in twitter is that you have one channel per user, so you want to scale the "personnalized timeline". Whereas telegram/discord have clear channels.
>
This is an implementation of the "Learning Everything about Anything" system. The system
is implemented in MATLAB, with various helper functions written in Shell, Python, MEX C++
for efficiency reasons. For details about the method, please see [1].
This readme contains instructions on using the code, as well as accessing/using already
trained models for various concepts.
The software has been tested on Linux using MATLAB versions R2011a. There may be compatibility
issues with older versions of MATLAB. At least 4GB of memory (plus an additional 0.75GB for each
parallel matlab worker) is assumed.
Well you'd have to build a probabilistic model for each concepts, whether on pixels or on features, and you could use it to generate images randomly. It might show up some good shapes.
(Disclaimer: I am not an native english speaker)
The title of the article and of the algorithm (learn everything about anything) is a bit misleading. You might believe that it learns everything, period. Actually it's more about finding every variation of a "concept", I quote their website:
"a fully automated method that given any concept, e.g., horse, discovers an exhaustive vocabulary for it that explains all variations (i.e., actions, interactions, attributes, etc) that modify its appearance."
I do agree with you speed typing might not be the most valuable skill to a programmer. Being able to type without a lot of typos is a lot more usefull since they can create hard to find bugs.
I'm puzzled, what's the use case for threads in the node asynchronous model ? Isn't the major use of threads is to prevent long running task from blocking the app in synchronous programming ?
It actually seems like an overhead but in reality it's designed to help you maintain your software easier:
Using interfaces makes your software functionnally dependant meaning that it relies on "theorical functions". On the contrary using directly some library makes your software structurally dependant to one's library.
This can be a massive issue if the library you're using is not maintained. If you wanted to switch to another one unless you were using a well defined interface that the other library can implement. You would just have to change a few lines of code vs changing a whole lot of calls to one's lib.
IMO, this is one of the major issue of javascript.
I totally agree. I own a Samsung Chromebook and even if i'm able to get a lot of work done with it and that it's absolutely a blessing to carry around (i'm a CS student) the screen isn't suited for long work session unless you want to go blind...