Try using Zoom client with screen sharing. Doesn't work and so on many applications limited by functionality. People say its year of Linux 2026 and xorg is dead. But its not even close to make it work for basic functionality. You can blame on vendors but as long as user functionality is not working, its never a working solution
Yes, it now works in Zoom, but not in Webex, unfortunately. That's been a big obstacle for me. I'd need to be able to share individual windows with audio.
This is outright stupid to believe. I have been working for past 15yrs and worked across startups to Top 5(FAANG), and never seen or gone through this.
Happens in consulting more often than you think. Product firms run different or at least that's what I assume. I haven't worked in FAANG but have worked in the Big4s, and a couple of Fortune 50 manufacturing firms. The experience I talk of has to do with the Big4.
In all seriousness they mentioned India not mango fango. That said, my xp has been the same as you. Only time top performers get nixed is if a whole arm gets nixed and they get caught in the crossfire.
OP said "do well", not top performer. Thinking you're a top performer isn't the same as the company thinking you're a top performer. I've never seen someone put on a PIP that didn't deserve, even if they thought differently.
Most people struggle just to keep their head above water nonetheless come up with elaborate conspiracies of sabotaging other peoples careers. No one is thinking about you that much.
I suspect the root of the problem is an unwillingness to take ownership for their action (or inaction). I've never been on a PIP. Even when I've given my employers reason to give me a verbal warning, their response has been: "that's not like you, don't let it happen again," and it hasn't happened again. I suspect that is true for most of those who have never been on a PIP.
Now I'm on the flip side, in a place where I may have to put someone on a PIP. What can be done has been done. There is only so much support and positive guidance that can be offered before you have to provide them with a plan backed with consequences for not following through. It is an employee that I don't want to lose because of their contributions, but it is also an employee that I can't afford to keep because (without changes) they are a liability. Unfortunately, previous interactions suggest that I will have to cut my losses. Yet the ball lies entirely in their court at this point because they are the one who has to take ownership for the issues they create.
Yeah, that slows down typing a lot. Luckily people on a laptop can use the touchpad which lies just below the space bar. I have a laptop with physical keys around the touchpad so I even have a button to paste. No need to tap, double tap, etc. I think that I never used a mouse in the last 20 years.
You can cut/paste within your editor just fine. The subject at hand is window-system level clipboard/selection interaction, and in particular the presence of standard key bindings for them in various environments. While some terminal and editor apps do have keyboard bindings that interact with the OS clipboard, none are standard.
Basically, yeah: you had to use the mouse to select it in the first place. Using the mouse to paste it is easier, not harder.
Look at how fanatic the compatibility actually is. Building Postgres or MySQL is conceivable but probably will require some changes. (SQLite compiles and runs with zero changes right now.)
SQLite runs about 5 times faster compiled with GCC (13.3.0) than it does when compiled with FIL-C. And the resulting compiled binary from GCC is 13 times smaller.
Interesting! I guess that's from your standard benchmark setup. Please note that Fil-C makes no secret of having a performance penalty. It's definitely a pre-1.0 toolchain and only recently starting to pick up some momentum. The author is eager to keep improving it, and seems to think that there's still plenty of low hanging and medium hanging fruit to pick.
It does (or did, at some point) pass the thorough SQLite test suite, so at least it's probably correct! The famous SQLite test coverage and general proven quality might make SQLite itself less interesting to harden, but in order to run less comprehensively verified software that links with SQLite, we have to build SQLite with Fil-C too.
If you run Nix (whether on NixOS or elsewhere) you can do `cachix use filc` and `nix run github:mbrock/filnix#sqlite` and it should drop you into a Fil-C SQLite after downloading the runtime dependencies from my binary cache (no warranty)!
The other way to look is why adding NS label is causing so much memory footprint in Kubernetes. Shouldn't be fixing that (could be much bigger design change), will benefit whole Kube community?
Author here: yeah that's a good point. tbh I was mostly unfamiliar with Vector so I took the shortest path to the goal but that could be interesting followup. It does seem like there's a lot of bytes per namespace!
You mentioned in the blog article that it's doing listwatch. List Watch registers with Kubernetes API that get a list of all objects AND get a notification when anything in object you have registered with changes. A bunch of Vector Pods saying "Hey, send me a notification when anything with namespaces changes" and poof goes your Memory keeping track of who needs to know what.
At this point, I wonder if instead of relying on daemonsets, you just gave every namespace a vector instance that was responsible for that namespace and pods within. ElasticSearch or whatever you pipe logging data to might not be happy with all those TCP connections.
>you just gave every namespace a vector instance that was responsible for that namespace and pods within.
Vector is a daemonset, because it needs to tail the log files on each node. A single vector per namespace might not reside on the nodes that each pod is on.
I think DaemonSet is to reduce network load so Vector is not pulling logs files over the network.
We run Vector as Daemonset as well but we don't have a ton of namespaces. Render sounds like they have a ton of namespaces running maybe one or two pods since their customers are much smaller. This is probably much more niche setup then many users of Kubernetes.
(Which is technically in line with you saying “17 series”, since there’s no number in the Air’s name. But your comment makes no sense unless you thought the Air was included in that, and so…)
Out of curiosity, why not release BIOS mod with a fix? Atleast personal laptops (out of warranty) can benefit out of it until Asus fixes their sht.
People blame Windows being slow and etc but most of the times hardware manufactures don't even get into this level to make best out of thier hardware. This is the reason why Apple is so successful, they control hardware, software while in open world, software like Linux/Windows is written by someone while hardware is designed by someone else.
Right, and Windows probably has something similar (maybe it requires loading a driver). This is BIOS-style code interpreted by the OS, so you can patch it at the OS level.
Maybe the risk is too high ?, bricking UEFI means time for soldering/reflowing, because you won't be able to software-recover it(unless it has dual bios mechanism).
If you've ever traveled abroad and replied to a work email or worked on anything at your hotel there's a chance you violated visa rules in some form. Very easy to find a violation if you want to find one, following the letter and not the spirit of the law.
It was an ESTA, and yes, technically working from the US with an ESTA isn't allowed. I'm not invited to the CES since I've left the first company I worked for in 2020, but I definitely would have cancelled all my plans to do so until this is clarified. If I needed a full visa to get there, I probably wouldn't have.
Also that's not what happened. The ones responsible for the breach, IE Hyundai execs and management who took care of the visa waivers and asked their employees to setup production lines were not arrested, only the people who had little to say about capital allocation were. In a way, Hyundai investors would have been a better target than their workers since they choose the execs who chose to build in the USA.
Same here. No other font comes close to it in terms of readability.
I really don't care about what each font claims about in terms of achiveness. As long as it's not pleasing to me, its not worth for me.
