You can achieve your share option in iOS using shortcuts. If you make a shortcut that sends the content of the share (like the URL of the article) to an arbitrary URL.
I did this with a tiny service I run on my home network that just calls yt-dlp on the passed URL and puts the result in a samba share that Emby uses, works amazingly well with all the services that yt-dlp understands.
I wouldn’t describe myself as a photographer so take with a grain of salt. A combination of iCloud and self hosted PhotoPrism [1] is perfect for me. My phone automatically backs up everything to both locations so I’m not worried about loosing anything and both do a good job of organizing by date/location/event. I can happily take photos without worrying that I’ll need to sift through them all at a later date. When I happen to use a camera that isn’t my phone (Mavic Mini being the most frequent), I can add the photos to both locations from my laptop. Apple does a great job of packaging and presenting ‘memories’ at a later date.
Others have already mentioned good pens to start with, but I want to mention that the paper is equally important. Clairefontain makes great notebooks for fountain pens that won’t break the bank.
The reason for this has to do with paper composition and weight and how free flowing (liquid) ink interacts with the paper fibers. [1]
+1 for Wave. Have been using it for my needs over the past 12 months with no major complaints. It appears their business model is based on getting you to accept payment for services through their automated invoicing, which they take a percentage of[1].
If you have the time to join groups that you find interesting, but are not directly related to your topic of study, do it. You will spend the rest of your career increasing your skill set in the domain you chose, but university can be a unique chance to get to learn from all the other domains. In my experience, and your milage may vary, nobody asked about my grads after I graduated. The skills I gained by joining groups outside of CS helped me go much farther than spending that extra time studying I think ever could.
For my use cases, Lightsail containers are far over-priced when compared to the smallest virtual server (which can run multiple small containers). $3.5/month for 1vCPU virtual server or $7 per container for 0.5 vCPU.
There is certainly value in the service offered, but 4x/vCPU worth? That I am not sure of.
lightsail seems to be aimed at smaller deployments, so measuring the cost difference as a ratio probably isn't as relevant as the absolute difference - this is probably worth $7-14/mo for the user who's only running a couple of small containers.
As someone who only had just gotten into front end programming after years of backend work, npm has been a nightmare. I haven't experienced the same level of frustration with other package managers (pip, cargo, go mod, etc) as I have with npm.
Is yarn the better option? What is our path forward?
I think the problem is not really NPM it's the way that mainstream frontend development requires very wide and deep dependencies. If you stick to using smaller frameworks and libraries without heavy build tools then it's not much of a problem.
I basically do no frontend development, partly due to tools npm and the current frameworks, I simply cannot wrap my head around it. I do help run a few modern javascript application however. Even a minimal app will pull in 1000+ dependecies, and I think that’s the problem.
It simply don’t happen in Python, Go or Rust (or even Java) because the languages comes with a rich standard library. Javascript comes with just the basics, everything else is a dependency. It’s not uncommon for people to audit their dependencies in Python or Go, but you pull in maybe 10 or 20. A basic Javascript app easily pull in 100 times that, how are you suppose to deal with that?
This has not been my experience at all. Most Rust developers unfortunately seem quite happy to adopt modern programming bad practices. (There are many exceptions, of course.)
Example: I went with the first Rust program I could find installed on my computer, tealdeer. It's a dead simple program: run `tldr progname` and it will print a handful of examples of how to run `progname` in your terminal. Run `tldr --update` and it will download the latest version of the database containing these examples from a web server.
To build this extremely basic CLI program, I need ONE HUNDRED AND NINETEEN distinct crates.
I think that there's difference between Java and JS landscapes.
Java has rich standard library. Some would say - too rich. But anyway - very few people would need customized collections, standard library covers all the needs. And where it does not cover all the needs, there are few commonly accepted additions like apache-commons or google guava. So that one solves `leftpad`-like issues.
Another difference is that Java is old. Most needs were covered by many libraries and few libraries survived which are good enough. It's again some commonly accepted wisdom, so you don't really need to search for many options. You have one good enough option that you'll use and move on.
So it's not about maven/gradle vs npm, it's more about ecosystems. I don't think that porting maven to JS world would change anything.
