I was wondering how much I‘d pay if I used AI Chatbot APIs directly instead of getting a monthly subscription.
So I‘m starting an experiment where I use the APIs for a month using a self-hosted instance of Open WebUI.
I already like having unified access to Claude, ChatGPT, Amazon Nova, etc.
Where's the difference compared to the built-in define word command?
Code written with box characters used on old old software to make fake UIs
You’re still arguing about tabs vs. spaces? May I present…
In other languages you first have to know about the concept of monotonic clocks and then explicitly remember to use them where applicable, while Go‘s APIs just know your intent and do the correct thing.
I‘m fascinated how smart Go‘s time APIs differentiate between telling time using the system clock and measuring durations of time using monotonic clocks.
Stumbled upon this in @willemdev.bsky.social‘s great article „time.Now() and the monotonic clock“:
www.willem.dev/articles/tim...
Does anyone have links to the stories mentioned here?
I recently implemented a custom Flink data source for my thesis.
Implementing the Source interface meant writing implementations for about 10 other interfaces.
Most of my time was spent understanding the purpose of these interfaces. While the functionality and value of these classes is minimal.
For example, why do we have to initiate multiple classes to read data from a file in Java? FileReader, BufferedReader, maybe another one to deserialize the data.
This is interesting since it contradicts the common stance that functions and classes should be kept small.
Additionally, the single responsibility principle seems to lead people to define responsibilities to small an specific.
Just saw John Ousterhout‘s talk on Software Design. He has some really interesting thoughts.
The most important point is probably that he prefers deep classes with small interfaces because they provide the largest amount of abstraction while minimizing additional complexity.
youtu.be/bmSAYlu0NcY
Or at least not automatically submit by sending return at the end.
As a result, I can only select and delete it as a whole. If I copy it into other apps, it‘s rendered correctly.
I wonder what leads to this encoding/rendering bug.
I have a WhatsApp chat where I always receive the 🙂↔️ Emoji as 🙂↔. However, when I use it, it‘s rendered just fine.
I know that this Emoji is encoded as 🙂, zero-width joiner, and ↔.
Additionally, even though it is rendered as it’s separate parts, it’s treated as a single Unicode glyph…
Raycast Wrapped 2024: Extensions screen with tiles containing the following content. 15 total extensions installed. Top Extensions: 1. Emoji & Symbols, 825 opens, 2. Raycast Notes, 382 opens, 3. Dictionary, 135 opens, and 7 more. Supercharged access: 3 hotkeys, 1 alias. 3 Quicklinks. 2 Script Commands. Latest extension installed: Color Picker.
Summary screen with tiles: Most active day: Monday. Top App: WhatsApp. Installed Raycast: 517 days ago. Opened Raycast: 3387 times. Most active hour: 15:00. And more tiles.
Interesting, that I open WhatsApp more often than my browser or terminal. What does your @raycast.com wrapped look like?
Nice, another talk for my watchlist!
Wow, this is super interesting to hear! While Rust has a reputation of being hard to write, this article suggests that its developer productivity is comparable to Go.
However, the learning curve is likely steeper for Rust and the Rust team in the experiment was probably already proficient with it.
This can be true for some tools, however, for tools such as zoxide or bat, even memory usage will be negligible for typical use-cases.
For example, I would have thought that Go is a better fit for CLI tools. The development speed should be faster than with Rust and due to it’s simplicity, it should be easier for people to get into the code and contribute.
Most CLI tools neither need the performance, nor the safety of Rust.
It‘s interesting how so many modern CLI tools are written is Rust. Especially for those, where performance isn’t critical.
Is this because the Rust community loves to rewrite stuff in Rust or is Rust actually nice to use for CLI tools? Maybe snappiness also has a subconscious effect on users.
I‘d like to see more about what you see as human in the loop.
Do you see aggregations of all my posts, like the aggregation, and the tool likes all the source posts, or do the aggregations include posts of multiple users?
How does infrequent posting impact this tool?
Seems to be working again 🎉
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec 08, 2024 - 18:00 UTC Scheduled - We will be conducting a scheduled infrastructure upgrade that may temporarily impact publishing and certain website functionalities. While some features will remain operational, like installations and search, minor inefficiencies may occur. Normal operations are expected to resume following the maintenance window. Dec 8, 2024 18:00-22:00 UTC
Looks like a hickup during some scheduled maintenance. Let's hope that it's nothing too serious.
I already feared that one of the dependencies my project uses got deleted 😮💨
Am I the only one for whom the iPhone keyboard is lagging while voice memos are playing in WhatsApp?
I find that so annoying, especially for an iPhone 13 Pro, which should be plenty powerful…
#apple #iPhone
Oh, and in case something goes wrong, there’s always jj undo!
For the last month I‘ve been trying out jj (Jujutsu) as a git alternative.
While I didn’t see anything wrong with git before, jj makes complex git operations so simple that I don’t want to go back.
Editing history, rebasing, splitting up large commits are all super easy.
As a result, I usually default to using _italic_ for italics and **bold** for bold.
This way, I at least don't write something that was meant to be italic in bold.
now you can run `npm install bluesky-comments` to use bluesky replies as your blog's comment section!
thanks @coryzue.com 🙌
Relevant HackerNews discussion for anyone wondering as well: news.ycombinator.com/item?id=1065...
The original link seems to be dead, so here is an archived version: web.archive.org/web/20170804...
Just learned that there is a term describing that people will rely on any behavior of your API, no matter if it’s part of the contract or not:
Hyrum‘s Law
This can often make it hard to change implementation details, after the API has users and should be considered while designing the API.