> The biggest risk when going with a long established solution is the potential danger of picking something that is on its way out of the zeitgeist.
I long established solutions are likely long established for a reason. And they are also likely protected by the interests of the companies already using them.
I think it's easy to eyeball if an older solution is still actively developed, RoR clearly is. Newer solutions can be very popular and active now, but die within just a few years. Just look at all the JavaScript frameworks we've gained and lost in just the last couple of years.
I absolutely love my Garmin instict. It has an always-on display and a battery that lasts for nearly a month.
I mostly use it for reading my calendar, weather, notifications and time. Occasionally I use it for exercise.
But what it also excels at is GPS. I use it as a backup navigational tool when sailing. It has also prevented me from getting lost when running in the woods a number of times.
In my opinion even the 28x decrease in performance mentioned would be a no-go. Sure the package saves a few bytes but I don't need my entire pc to grind to a halt every time I publish a package.
Besides, storage is cheap but CPU power draw is not. Imagine the additional CO2 that would have to be produced if this RFC was merged.
> 2 gigabytes of bandwidth per year across all installations
This must be a really rough estimate and I am curious how it was calculated. In any case 2 gigabytes over a year is absolutely nothing. Just my home network can produce a terabyte a day.
Because the authors mentioned package, Helmet[1], is 103KB uncompressed and has had 132 versions in 13 years. Meaning downloading every Helmet version uncompressed would result in 132*103KB = 13.7MB.
I feel like I must be missing something really obvious.
I recently wrote an essay about this search engine, and its ranking algorithms.
Initially Marginalia used an interesting variant of PageRank discussed in the original paper, called Personal Pagerank.[1] Currently pages are ranked with BM25.
I think Personalized PageRank is still used for a new feature of Marginalia which is ranking pages based on similarity. I think this is already integrated into the website but there used to only be this testing page:
https://explore2.marginalia.nu/
In any case I have a lot of respect for the creator. Marginalia has seen a lot of growth and it's been interesting reading the blogposts.[2]
I'm using PPR for domain rankings, but it's a very weak factor. It mostly affects the physical ordering on the results in the index, and given that queries have a timeout they'll execute for, it makes it so that higher ranking results are discovered first. Though in general, as I mentioned, this is a weak effect.
Explore2 and the website discovery tools now built into the search engine are using cosine similarity of the incident link vectors. I wrote a blog post about the technique called "Creepy Website Similarity" available :-) https://www.marginalia.nu/log/69-creepy-website-similarity/
If you don't share the task description or other materials provided by your university, I don't see the problem with sharing your essay. (Not a lawyer)
It's a sure fire way to get your uni submission incorrectly flagged as plagiarism. How straightforward it is to prove you're the original author varies by institution.
once the essay is already graded, it should not matter. and less as time passes.
on the contrary i thought any essay, paper or report written for uni or school can be considered for publication in some form. not everything is worth publishing of course, but if it is, talk to your supervisors about it.
> There's something to say for minimalism as a distraction-free mechanism.
I think there's little credit to be given here. A text widget is part of any gui toolkit and there are hundreds of notepad like text editors. I think basically every DE on Linux has their own...
I long established solutions are likely long established for a reason. And they are also likely protected by the interests of the companies already using them.
I think it's easy to eyeball if an older solution is still actively developed, RoR clearly is. Newer solutions can be very popular and active now, but die within just a few years. Just look at all the JavaScript frameworks we've gained and lost in just the last couple of years.
reply