Sure and android is a small part of Google. Everyone in ads, search, cloud are still predominantly c++ (or something higher level like Java). Rust is gaining momentum but overall it's still small.
While certain teams within Google are using rust by default, I'm not sure rust is anywhere close in scale for new lines of code committed per week to c++.
Sharing a session is independent of the terminal emulator itself. Use tmux for that. There are a handful of good terminal emulators. Weztern, alacritty, and kitty are popular. I use. Tiling window manager so I prefer to avoid tabs and use alacritty for that reason.
Why do you think trippling the memory usage of a program is an acceptable tradeoff? It's not just GC pauses that are problematic with gc languages. Some software wants to run on systems with less than 4GiB of RAM.
So anything that uses a less popular language is considered over engineering? Distros support lots of different languages already and there are likely other packages built with zig already.
Google runs everything on their tpus which are substantially less costly than to make and use less energy to run. While I'm sure openai and others are bleeding money by subsidizing things, I'm not entirely sure that's true for Google (despite it actually being easier if they wanted to).
Just because you can use it from C doesn't mean it's a C ABI. You can do almost anything from C, but the semantics of the APIs require additional work in order to use correctly. Just because golang can interface with C doesn't mean C APIs have a golang ABI right?
It's all about where the stable ABI exists. You can do anything in practice, but if you stray off the happy path it will result in pain. On PC OS, everything used C (or in Linux, syscall) ABI. On android the ABI is java based, and on iOS it's objc/swift based. These are deliberate choices and while they make some use cases more difficult, they are optimized for the use cases the companies care about. I'm personally preferential to a language agnostic IPC boundary being the abi, but that has its own cons as well.
The best of both worlds is hosting the binary independently of git in some cloud storage and just have a script that fetches it (and set it in .gitignore). git itself doesn't like binaries very much and it will bloat your git clone speed/size if you update the binary ad it will effectively store all versions.
I think this is happening by raising the floor for job roles which are largely boilerplate work. If you are on the more skilled side or work in more original/ niche areas, AI doesn't really help too much. I've only been able to use AI effectively for scaling refactors, not really much in feature development. It often just slows me down when I try to use it. I don't see this changing any time soon.
ABI is a far larger concept than the kernel UAPI. Remember that the OS includes a lot of things in userspace as well. Many of these things are not even stable between the various contemporary Linux distros, let alone older versions of them. This might include dbus services, fs layout, window manager integration, and all sorts of other things.
If you are just a lower level IC, your influence is small. However if you can climb to higher level 7+ or enter management you will have a lot of control of roadmaps you own. If you're trying to influence organizations you're not in you're also going to have quite limited influence, but participating in dogfooding programs and filing bugs is still more influence than you would have externally.
I do agree that it's not easy even given the correct conditions.
Big tech companies are large. It's very possible to be working on things that are generally great for society while others in the company are not. Fighting from the inside for the behavior you want to see gives you an outsized influence on the outcomes you want to see.
One of the hardest parts of writing an os is learning and understanding how to make the toolchain work the way you need it to. I wouldn't consider that a negative to spend time discussing it in such detail. Otherwise you have no idea how to even apply the high level concepts.
Unless it comes down massively in price, it's not going to displace manual driving for anything other than Uber/taxi. It's far cheaper to drive your own car in most of the us. If parking lots disappear and the parking that remains becomes similar in price to that of major cities and insurance rates skyrocket, then maybe that will change, but only by increasing the overall cost of transportation.
Google has been actively trying to diversify away from being dependent on just ads for a very long time. The other ventures are certainly not side projects in terms of investment, and pretending revenue sources are equivalent to the only source of motivation is over simplifying how large companies operate.
No. Iced has no accessibility support built in. It's a pretty hard thing to do, so it's not surprising that something more hobby driven doesn't have it.
Plenty of people take risks even with obligations. I am risk averse, and like to ascribe much of that to my obligations to keep my family happy, but really I've always been this way, and would act pretty much the same without them. On the other hand, I've seen folks go to the brink of poverty to start businesses even with small children to feed. They are far more successful today than myself.
15 years ago, it was incredibly common to see folks texting things like "c u ltr". It made its way into instant messaging (where folks had a keyboard), but slowly disappeared once everyone had smartphones that autocorrected everything. I don't think it's strange to see that people prefer it stylistically. Text has very little in the way of showing emotions or intentions, so everything you can do to alter that is something to be used. People want to be less formal sometimes.
If it exists, it's probably not at all related to Gmail or only used for testing. I don't think Google reuses a lot of third party code in its first party server software.
And it shows how silly the idea is. gcc still sees plenty of forks from vendors who don't upstream, and llvm sees a lot more commercial participation. Unfortunately the Linux kernel equivalent doesn't exist.
It's makes the worse case sufficiently bad and unfair such that it makes things worse overall. If the lock is contended by a thread with higher priority, then that blocking thread will have its priority increased. Now if the ends thread to get the lock is one spinning on it rather than actual high priority one, then this will repeat, leading to large latency on front of the high priority thread and a lot of misaligned CPU utilization by a lower priority thread.
Spinning on a CAS is far more expensive than spinning on most other instructions as well as it affects all core that may try to access that cache line, which may include things other than the lock itself.
Also consider how the system acts under high CPU load. You will end up with threads holding locks when not running leading to the majority of the time you miss the lock you spin all 100 times. This just exacerbate the CPU load issues even more. Hybrid locks are only helpful under lower CPU load.
And I think it'd a poor choice that causes worse system performance. Android's bionic doesn't spin, nor does Windows or Fuchsia. Avoiding the syscall overhead is generally detrimental to overall system performance especially when the CPU load is high.