shrikrishna
Joined 14 years ago
Joined 14 years ago
If you’re running Sidequest entirely on your own infrastructure to orchestrate jobs across your backend, you’re not distributing the software at all, you’re providing a service. The tight coupling does not itself trigger extra obligations. What matters legally is distribution, not architecture.
Edgecase is if you give your software to a customer to run on their own servers (self‑hosted deployment/docker image shipped to customer). In those cases, you would need to allow them to replace Sidequest.js (ie, not obfuscating it away).
Someone more knowledgeable can correct me, if I'm wrong
Ex: Could I have a store of articles and run NLP tasks against it?
I have been following your blogs and zines for years now. Keep up the good work and vibes. Peace.
There are some series they sometimes do, which are entertaining to follow. I also enjoy things like Journal club, where they pick a paper and deep dive into it. The audience also participates, in a way, where they pick the questions/comments from the previous video and answer them.
However, it's not all academic either. There are some running jokes etc, which keep the content entertaining, while being informative, a format that I see common in some of the best Youtube channels.
However, since we started using Yarn workspaces (for JS), I've needed to switch to VSCode because its auto-import is just so much better, and it's one of those things that's hard to go back from, once you're used to it. Sublime text already indexes my code for search, which can probably be used for path suggestions / automatic imports without affecting performance too much maybe? I dunno.
I wouldn't mind it being a plugin either (before Yarn workspaces, I'd use FuzzyFilePath plugin which worked pretty well). But native support would mean the performance would be on par with what I've come to expect from Sublime Text :)
1. Ecosystem. You _will_ need help
2. Friendly (to you) syntax
3. Target to achieve (in your case, it would mean a language that is frequently used in distributed system/data engineering)
Regarding "I find myself going through the crazy articles comparing languages and lose focus and give up.", I hear you. I've been there. Pick two and run with them. Once you start learning a language, stop reading articles on what other languages you can be learning. There is always something better down the corner. That doesn't mean you lose focus and drop whatever you're doing midway. Persevere, and you will prevail.
Finally, my recommendation, based on your requirements would be
1. Python (for data engineering - numpy, scipy, tensorflow, pandas and whatnot)
2. elixir (for distributed systems)
Hope that helps. Good luck!
Currently building https://sigalrm.io
Email (I'm not looking for a job!) : shrikrishna DOT holla AT gmail DOT com