lomereiter

PocketBook is by far the most hackable, especially their b/w readers, which still run Linux 3.10 because of hardware limitations - for these, getting root permissions is trivial with an old jailbreak script based on Dirty COW. (That said, the hardware is rather slow for the price tag.) Most applications use modern Qt 6 / QML. You won't find much information online, but it's a lot of fun exploring all this stuff with Ghidra MCP and creating binary patches. Shameless plug: I created an emulator so that you can download firmware from the official support web page and try it out on a Linux desktop (https://codeberg.org/datyoma/pbemu)

IMO the actual difference between introverts and extroverts is that the latter use @here and @channel a lot more frequently

...or Korg NTS-1 (or even both together), which is not as modular but fun and hackable in its own way

For some Mini PCs there are fanless cases, e.g. from Akasa: https://akasa.co.uk/update.php?tpl=list%2FCHASSIS+POWER.tpl&...

I've got one of those, and it houses a system with 8 CPU cores, 32 GB RAM (can be upgraded to 64 if need be), 1 TB NVMe and 4 TB SSD - and it's all inside, whereas with an RPi the SSD would have to be external. The only thing that's collecting dust now is the old RPi.

This is even handier: https://github.com/NikolayS/postgres_dba

The community can agree to always call it "Redpanda Connect™ (former Benthos)"

Don't you ever get inspired by reading good books? You can learn new tricks and apply them elsewhere, and it's much easier than actually contributing to a big open-source project.

If this were indeed the average attitude, there wouldn't be this big of an outcry with regards to the move from fully open-source to source-available licenses (Mongo/ELK/Hashicorp/etc.)

FWIW I had decent success with Xpra on Linux, and it's still being actively developed, e.g. the HTML5 client is considered stable now: https://github.com/Xpra-org/xpra/

"Large teams" is the key, there has to be enough services and/or language diversity to justify the extra complexity.

To set up an open-source service mesh, the infra team anyway has to configure a private certificate authority and cert-manager to create k8s secrets for the service mesh components. From there, it's straightforward to extend the common deployment template (hopefully there is one) to mount a volume with an auto-rotated certificate. All an application developer has to do is to use that certificate, which is much less effort than what you are implying.

Reminds me of a Russian joke.

A secretary applies for a job; the interviewer asks her: "In your CV you claim that you can type 1000 characters per minute - for real?!" "Yes!", she replies, then adds in a low voice: "but such nonsense comes out..."

Arrow format is not intended for storage, it's for in-memory data exchange between different libraries and languages.

Glad to see usability improvements here, but I won't be using it until there's a light theme (asking an application to respect the OS theme is apparently too much these days).

You could buy a USB enclosure for an M.2 NVMe SSD - a bit bulkier but still portable and addresses your concerns.

This article was written in 2015, a year before idle_in_transaction_session_timeout parameter was added (in Postgres 9.6) - which is unfortunately still disabled by default, but that's the easiest way to make sure no transaction sits idle for too long.

Yes, you absolutely need to set a reasonable idle transaction timeout to avoid a disaster (bugs in the code happen) - this can also be done globally in the database settings.

Better yet, oauth2-proxy in case of an organization: only admins need to know the secrets, every user simply uses SSO to get access.

We ran into a similar issue once, and addressed it by changing the sorting column from id to created_at which has the same ordering but doesn't have an index on it. Good to know Postgres optimizer can be tricked even easier.

Our industry is so disorganized that after half a century 'Software Engineer' is still not a recognized profession, and there is just as little interest in unionizing. I lack the audacity to make sweeping judgments about it.

Who are these 'we'? It's all up to personal preference in the end. As Github demonstrates by postponing SPA framework adoption, there are enough companies out there that share your desire to keep things simple.

What you describe is solved with GraphQL, which is a very mature technology by now.

You can shift your focus to mentoring your teammates and presenting at developer meetups / conferences. Simply tell your manager that you are greatly concerned about the bus factor (cite the 71% figure), and hopefully you two will figure out how to proceed.

Check out "Hobo: Tough Life", it's at the extreme end of the spectrum, where you have to beg and steal in the beginning.

Why give your money to a manufacturer who explicitly wants you to run MacOS on their hardware, and not to its Linux-friendlier competitors?

If I were a kid, I'd ask my parents to switch to a family plan, and negotiate how I can help with home chores in exchange for those extra $6/month. (Of course, very few kids actually think this way.)

My wild guess is that Putin's goal has always been cleansing the power circles of the oligarchs who got there in the 1990s, and now that he's running out of time as he's getting old, he needs help in that from the West. Now he might be betting that the sanctions will mostly target these oligarchs and make the country _really_ unattractive for them, whereas an average Russian anyway has no assets abroad and doesn't travel much, and therefore won't notice the difference, as energy and food are abundant domestically. If that's his plan, there should be no need to go beyond Ukraine.

How about solving a sudoku? E.g. https://www.nytimes.com/puzzles/sudoku - choose the level so it takes you less than 10 minutes.

You are describing Tidelift (https://tidelift.com/) except the bit where the users would "need to pay" - although that could be addressed e.g. via regulations for enterprises but not individuals.

AGPL doesn't prevent running unmodified software and offering it as a service by large vendors. See the controversy around SSPL and the recent ElasticSearch fork by AWS - I suggest reading Kyle Mitchell's take on this: https://writing.kemitchell.com/2021/01/20/Righteous-Expedien...

That said, I believe SSPL is an overkill, and what's needed for a less known SaaS product is a legally enforceable revenue-sharing mechanism - so it can benefit from being listed on popular platforms.