varsock

I agree with the sentiment but Google is an Ad business. Selling phones by itself does not financially support them.

GrapheneOS on Pixel is the most stable and secure way to have a modern mobile phone that is free of trackers (from google and apple alike).

I can't picture a better way to "stick it to the man" than 7 years of them unable to track and serve you ads

hahaha good point.

That colleague, keep in mind is a bit older, also has Vim navigation burned into his head. I think where he was coming from, all these new technologies and syntax for them, he much rather prefers right clicking in the IDE and it'll show him options instead of doing it all from command line. For example docker container management, Go's devle debugger syntax, GDB. He has a hybrid workflow tho.

After having spent countless hours on my Vim config only to restart everything using Lua with nvim, I can relate to time sink that is vim.

Had a distinguished collegue (from the Bell Lab days) say to me recently:

"IDEs take up a lot of RAM on my machine. Vim takes up a lot of squishy RAM in my head. I need squishy RAM to hold info relevant to problem solving, not options available in my tool chain."

As a former Vim user myself, I have to say I really dislike screensharing with coworkers who use Vim. They are walking me through code and shit pops up left and right and I don't know where it comes from or what it is I'm looking at. Code reviews are painful when they walk me through a large-ish PR.

These days, I tend to bring my vim navigation/key bindings to my IDE instead of IDE funcs to Vim. Hard to beat JetBrains IDEs, especially when you pay them to maintain the IDE functionality.

code is just text, so code editors are text editors.

What sets IDEs apart are their features, like debugger integrations, refactoring assists, etc.

I love command line ± Vim and used solely it for a large portion of my career but that was back when you had a few big enterprise languages (C/C++, Java).

With micro services being language agnostic, I find I use a larger variety of languages. And configuring and remembering an environment for rust, go, c, python etc. is just too much mental overhead. Hard to beat JetBrain's IDEs; now-a-days I bring my Vim navigation key bindings to my IDE instead of my IDE features to Vim. And I pay a company to work out the IDE features.

for the record, I am in the boat of, use whatever brings you the greatest joy/productivity.

wait until Google releases a new pixel this fall, buy "last year's" pixel at a discount and they are supported for 7 (?) years of updates (including firmware).

I would recommend GraphenesOS bc they only deal with android and pixel phones so there is a high level of compatibility and things rarely break. (In many cases GrapheneOS was more stable than Google's android, recently with the multiple profiles and memory bug). They also push fixes and security hardening upstream sometimes.

Anyway, GrapheneOS will support a Pixel for as long as the manufacturer (Google) releases firmware updates. So you have the potential of 7+ years of support from GrapheneOS.

don't insult children like that.

When I was in college, two older classmates whom I respected got into a hilarious argument of why Gnome was awesome and now eats rocks (their views, I had no views).

Their elaborate and very specific descriptions of functions and inconveniences drew up a picture of functionality and a e s t h e t i c I had never experienced on windows. So I proceeded to install a distro and take it for a ride

There is a very effective approach (34:00), that big companies like cloudflare use, to ship a product in a fast and quality way. It bears parallels to what you are describing. In essence engineers should not get hung up in the details to trying to solve everything.

1. Just build a proof of concept
2. Discard the prototype no matter what and start from scratch keeping the initial feedback in mind
3. Build something internally that you yourself will use
4. Only once something is good enough and is used internally, then release it to beta.

So that tedious process in trying to flush out all the details before seeing a product (or open source effort) working end to end, might be premature before having the full picture.

A step in the right direction but until there are more robust privacy laws in place, this will not go away.

If their gov is restricted on buying from data brokers, are other governments, foreign entities?

The inherit issue is the American's data can be harvested and sold. Setting up legal restrictions toward certain entities will just cause those entities to "legally self identify" as another entity. Or do business with an entity that is allowed access to American's data.

i take a Phoenix approach with my dotfiles.

Once a decade when my computer crashes and burns, from the ashes emerges a blank slate of dotfiles that is purged of all unnecessary hacks that have accumulated. With a tear and a hopeful outlook, I rush to set the settings I am actually dependent on.

I really need to take more interest in backing up my dotfiles 😭

I will admit reading the reasons against Linux made me a bit butthurt given how much it has accomplished and the ubiquity of it running on servers that host our services.

However, a (real time operating system) RTOS is distinct from a time-sharing operating system, such as Unix, which manages the sharing of system resources with a scheduler, data buffers, or fixed task prioritization in a multitasking or multiprogramming environment. And a time-sharing kernel is likely not suitable for the demands of real-time feedback that airplanes, especially fighter planes, are under. Admittingly I don't work on the kernels so I might be out of my league talking about it if there are ways to optimize them for RTOS applications. And I also don't work on airplane but hobby learning about them.

In an airplane, the pilots are voting members. If they they are nose diving and tell the airplane to pull up, the airplane will calculate how much of the full range of motion to allow the flaps to "bite" the air so that the plane doesn't desintigrate. This takes into account speed, altitude, air density, load on wings, load on frame, G forces pilots would experience, etc etc.