- 125 points
- In the first segment of the very first episode of the Abstractions podcast, we talked about Google killing its goo.gl URL obfuscation service and why it is such a craven abdication of responsibility. Have a listen, if you’re curious:
Overcast link to relevant chapter: https://overcast.fm/+BOOFexNLJ8/02:33
Original episode link: https://shows.arrowloop.com/@abstractions/episodes/001-the-r...
- Benefiting users is definitely not Ollama’s first priority, as seen when this pull request was summarily closed: https://github.com/jmorganca/ollama/pull/395
Those README changes only served to provide greater transparency to would-be users.
Ulterior motives, indeed.
- These comments would carry more merit if they weren’t coming from the very person who closed this pull request: https://github.com/jmorganca/ollama/pull/395
Those rejected README changes only served to provide greater transparency to would-be users, and here we are a year and a half later with woefully inadequate movement on that front.
I am very glad folks are working on alternatives.
- Integrating ripgrep-all with fzf makes for a powerful combination when you want to recursively search the contents of a given directory.
I have been using a shell function to do this, and it works wonderfully well: https://github.com/phiresky/ripgrep-all/wiki/fzf-Integration
The built-in rga-fzf command appeared in v0.10 and ostensibly obviates the need for the above shell function, but the built-in command produces errors for me on MacOS: https://github.com/phiresky/ripgrep-all/issues/240
- Having owned countless Mac notebooks over the last 30 years — starting from the PowerBook 140 up through the M1 MacBook Pro — I can tell you with confidence that Apple has made the same sleep change shenanigans mentioned in OP’s article.
It used to be that you could count on a sleeping Mac to stay asleep until you explicitly woke it up by opening the lid, pressing a key on the keyboard, or pressing the trackpad (or separate trackpad buttons — yes, those used to exist). Perhaps more importantly, you could count on the sleep function to have barely any effect on the Mac battery.
I don’t recall when, but at some point over the aforementioned three decades, Apple started changing the terms of this sleep contract.
It seems Apple decided that some functions should still be available when the Mac is “sleeping”, with no way to restore the previous behavior. As a result, random wake-ups are the new normal, replete with unexpected battery drainage.
I have seen modern MacBooks go to “sleep” with an 80% charge at night, only to be rendered dead with a 0% battery level by morning. Does something this extreme happen often? No. But it never happened before. And moderate battery loss while sleeping? That happens very often on today’s MacBooks.
Your mileage may very. And Apple probably continues to implement better computer sleep behavior than competing vendors. But I would argue that people who think MacBook sleep behavior is excellent… have never experienced how it behaved in the past. That behavior was superb.
But sadly, I imagine most people have never experienced that excellence.
- As the maintainer of the Python-based Pelican static site generator for over a decade, I can say with confidence that my experience has been nothing like what is described in this article.
Most of Pelican’s code was written by other people, and yet I have spent almost zero time debugging that code, much less my own. After taking advantage of Pelican’s rich plugin ecosystem and adding a handful of useful plugins, I continue to be amazed by how much time this publishing system saves me, and how little time I must spend to keep everything running smoothly.
What it would take to accomplish this by writing HTML by hand instead… I simply can’t fathom it. But once again, that’s just one person’s experience, and YMMV.
- Sorry for the confusing language choice on my part. I just meant that I think it's great that your project supports JMdict. I think how you are using JMdict is indeed totally okay! :^)
- As a credited contributor to the EDICT[1] Japanese/English dictionary, I am very pleased to see its successor JMdict[2] actively supported by this project. Bravo!
And as someone who now also speaks Italian, I am even more pleased to see that Italian support will be added tomorrow.
It is wonderful to see such a useful tool released as an open-source, self-hosted project. (^_^)
[1] EDICT: http://edrdg.org/jmdict/edict_doc_2009.html
[2] JMdict: https://en.wikipedia.org/wiki/JMdict
- 1 point
- Python 3.12 is now available via asdf [1]:
[1]: https://justinmayer.com/posts/homebrew-python-is-not-for-you...asdf install python 3.12.0 - Quite true. I actually submitted a pull request [1] over a month ago to make it clear to potential users what will happen when Ollama is launched for the first time, but based on the complete lack of response from Ollama developers, I get the distinct impression that they are reluctant to draw attention to these important details. Unfortunate.
- If you use Fish shell and Python, my project VirtualFish can make managing virtual environments a lot easier and more fun:
- This project is not open source but instead uses the “Business Source License”. I only mention this in case open source is something that is important to you.
- A interesting option I haven’t seen mentioned here is Beeware, an open-source (MIT) project with this summary:
“Write your apps in Python and release them on iOS, Android, Windows, MacOS, Linux, Web, and tvOS using rich, native user interfaces. Multiple apps, one codebase, with a fully native user experience on every platform.”
Source: <https://beeware.org>
- I use and really like Gitea: https://gitea.io/
You could also have a look at a recent Gitea fork, with a very unfortunate and cumbersome name: https://codeberg.org/forgejo/forgejo
- The README in the GitHub project repository says:
> “This application is in maintenance mode.”
Source: https://github.com/kanboard/kanboard
I think there are better open-source kanban-style applications out there that are also actively maintained. For example:
- Frustrated by expensive per-seat pricing and unfriendly contract terms, we looked for PagerDuty alternatives and found a fantastic open-source project called Uptime Kuma: https://github.com/louislam/uptime-kuma
Uptime Kuma is one of the few open-source projects that feels like a commercial product: polished user experience, frequent release cadence, and a rich set of features including monitoring PostgreSQL servers, Docker containers, and so much more. Its list of supported notification services is so long that I don't even recognize half of the options available. Truly impressive.
Side note and shameless plug… We love Uptime Kuma so much that we made it one of the cornerstone applications provided by Fortressa, which we think of as the “App Store for Open Source”: https://fortressa.com/
- Carrying out the original intent (going on the run), even in a lesser form than the ideal (going slower than usual), helps to reinforce the habit. Ultimately, this is about mastering the art of showing up.
This concept is closely related to the “Two-Minute Rule” proposed by James Clear, of Atomic Habits fame. Showing up consistently, even in small ways, helps build momentum and leads to significant accomplishments over time.
I have not yet tried either one, but here is the other project for those who want to compare and contrast them:
https://github.com/manaflow-ai/cmux