295 karma · joined August 4, 2023
It uniquely seems to be fragmented and messy compared to most other parts of the software industry,(not sure why, just saying what I observe.
So the market situation looks very different to the ones that the DOJ was going after (like Google in ads,if Wiz was a big ad company then maybe the government would be more interested in trying to block it). Wiz isn't even close to having some kind of insurmountably dominant market share in their specific area of expertise either.
That being said, one of the reasons these things sell is that the majority of people sitting behind computers in large enterprises absolutely DO NOT have any idea what they were doing.
Once you get to a certain scale, the idea that you can "just be competent" and maintain high standards and configure your boxes the right way the first time every time btecomes logistically impossible.
Liability and insurance also is a big concern for large companies. The ability to blame somebody else for your security failings and check off all the silly boxes is pretty valuable. I'm sure consumer windows antivirus software would become a big hit again if you were for all intents and purposes being legally strong armed into purchasing it.
The whole thing reads like all the dozen or so "cloud security" plays out there.
Either I'm missing something big, or their products are outrageously far ahead of all the other similar sounding products out there.
I've been known to roll my eyes at a lot of these sorts of product catalogues in the past though and so I'm definitely biased and not the target audience for their marketing.
Some CIO out there probably really does think that their security problems will finally be over once they purchase another half dozen dashboards click through and look at.
All I'll say is that the recruitment process alone, if it's still as bad as it used to be, is a major red flag and deal breaker w.r.t what it says about the overall culture.
Maybe things have changed and so people should really take my opinions about them with a grain of salt.
It's rock solid AND comes with relatively new packages, AND they are close to stock. I also appreciate their willingness to put themselves forward and show leadership when it comes to adopting (or creating) new technologies that can make the platform better. I think most professionals can agree at this point that despite little qualms and some early hiccups here and there, technologies like systemd and wayland (and others) were probably good ideas in the long run, and Fedora was consistently way out ahead in promoting and adopting them.
I also tend to trust Red Hat (and yes even IBM) more than I do Canonical for a number of reasons.
The existence of a package manager causes a social problem within the language community of excessive transitive dependencies. It makes it difficult to trust libraries and encourages bad habits.
Much like Rust has memory safety benefits as a result of some choices that make it difficult to work with in some context, lack of a package manager can have benefits that make it difficult to work with in certain contexts.
These are all just tradeoffs and I'm glad "no package manager" languages are still being created because I personally enjoy using them more.
I would agree with you if we were talking about a customer facing webpage or something. But an app for say an accountant? That should be a TUI or as fast as a TUI. The workers are literally hired to get over the learning curve and become fast with the app, so it's not as big a concern if first-use is more difficult. You arent trying to sell them a product and drive higher percentage click through.
I 100% agree with you for applications for say online shopping. Those should prioritize new user experience over long time user efficiency probably.
I've seen a lot of failed projects for data entry apps because the experienced workers tend to prefer the terminals over the web apps. Usually the requirement for the new frontend is driven by management rather than the workers.
Which is understandable to me as a programmer. If it's a task that I'm familiar with, I can often work much more quickly in a terminal than I can with a GUI. The assumption that this is different for non-programmers or that they are all scared of TUIs is often a mistaken assumption. The green screens also tend to have fantastic tab navigation and other keyboard navigation functionality that I almost never see in web apps (I'm not sure why as I'm not a front end developer, but maybe somebody else could explain that).
I'll defend green screens all day long. Lots of people like them and I like them.
Everything else you listed I would agree with you about being terrible and mostly hated though.
I do find it slightly offensive that you would insinuate that hiring in Texas is solely about less worker protections and not that we have plenty of skilled workers in one place and with a lower cost of living.
I'm a worker not an owner,and I prefer living in Texas at this stage in my life and have turned down offers to move back to California.
Working in tech in a big Texas city easily puts you in the top 10% of the cushiest jobs in the US. Based on how I've been treated here, I really doubt that worker protections (or lack thereof) is the real driving force behind more tech jobs moving here. We are far from being oppressed here.
The most likely driving force of tech moving to Texas is that mid career professionals like myself don't see a future in California due to the insane cost and bad vibe of raising a family there. It's a great place for people just out of college, but Texas is a better place to settle down unless you are pulling an outrageous salary. The other big advantage California has is VC and startup networks being located there, which is also something that primarily benefits early career people rather than those of us that need a stable job at an established company.
It's also worth pointing out that Texas has long had a large technology industry presence. The dominance that California experienced during the early 2000s through to mid 2010s is an outlier and it shouldnt surprise anybody that things are evening out.
If I write a script using BSD esque tools I can be reasonably sure they will work on any Unix-like, whereas if I write/test my script on a machine using GNU utils, I'm fairly likely to accidentally use a GNU extension that would cause the script to fail on an older Unix-like OS. For instance, I do a lot of work migrating code off of AIX,and I need the scripts I develop to work on AIX when I'm gathering environment information from customers. I can't just assume they will have a ~2020+ implementation of Unix userland tools with all the GNU extensions and nice features. Sometimes the machines have been sitting quietly in the back of a data center not being updated for quite a while and will have more "90s style" of Unix tools.
I have to work with old machines and legacy operating systems quite a bit in my day to day and I always am going to prefer something lighter and with less ways to shoot myself in the foot w.r.t. POSIX compliance. MacOS is Unix certified so I appreciate them being somewhat reserved in the features they add on top of POSIX.
Modern GNU userland utils are nice and fun but if you are looking for compatibility it's best not to use them. Consequently, the MacOS situation doesn't bother me especially given you can install more up to date tools if you want. I think keeping the defaults older and more compatible is a good thing.
Going the other way, you can safely take desoxyn orally at a therapeutic dose and mostly it is like adderall, and you will avoid for the most part the bad effects that occur at recreational doses of smoked street meth. That's why desoxyn isn't schedule 1.
So I dont think it's particularly misleading to say that this guy was basically taking meth and experiencing a lot of the side effects that would be experienced had he been taking street meth. The two chemicals have similar enough effects, and when taken at recreational dosages they can both have the bad effects we would typically associate with meth abuse. It's good to make this clear to people getting treatment for ADHD (or college students popping pills illegally for a cram session) so that they don't get the erroneous impression that because it isn't meth, they don't have to treat dosage and dependence as seriously as they would have to if it were actually scary street meth with all the scary imagery that comes along with it. It's good that we draw parallels and are clear with people that it's a very serious drug with potentially meth-level side effects if abused.
I sympathize with you in the sense that I don't want to make it harder for people to get their prescriptions, but on the other hand I think it's just false to say they are totally different due to the addition of the methyl group.
TLDR: it is absolutely possible to abuse oral pharmaceutical grade (not meth)amphetamine to the extent that you have stereotypical meth head type side effects. And it is absolutely possible to take pharmaceutical grade methamphetamine at a therapeutic dose and have it be a lot like typical therapeutic (non meth) amphetamine use. There isn't that big of a difference.
That's just how programming on teams and trust and teamwork actually works in the real world. Especially on a deadly serious not-hobby project like the kernel.
Sometimes you are gonna have to do work that doesn't excite you. That's life doing professional programming.
Everything Ted Tso recommended is just common sense teamwork 101 stuff and it's just generally good advice for programmers in their careers. The inability of rust people to follow it will only hurt them and doom their desire to be accepted by larger more important projects in the long run. Programming on a team is a social affair and pretending you don't have to play by the rules because you have such great technical leadership is arrogant.
I'd be suspicious these guys aren't in it for the long haul if they don't get their way and will leave the Rust they shoved in the kernel to bit rot if things don't go their way w.r.t enough rust adoption fast enough. "If you don't let us add even more rust, we will resign from the project and leave you to maintain the rust that's already there and that we added, and that you said you didn't want to add because you didn't trust us to not resign".
Rust 4 Linux people just proving the points of the maintainers scared of abandonment.
The rust 4 Linux people unfortunarely give the impression of caring more about rust than about the kernel, and it's clear that many are willing to make that perfectly clear by abandoning the larger project.
The whole thing needs to be scrapped and rethought with better and more committed leadership. This past 6 months to a year has been embarrassing and done nothing but confirm the fears of anti rust people.
I think the situation (loosely, wasting time spinning your wheels by modernizing things that are actually fine the way they are and may be made worse by adopting "hot new thing") looks worse when you see it through that lens than it actually is throughout the industry as a whole. There are plenty of opportunities for modernization and doing some of the things described in this article that actually make some sense when applied to appropriate situations.
In other words, I totally understand the vibes of this post, it's one of the reasons I don't work in the parts of the industry where this attitude is most prevalent. I would never feel the push to write a post like it though because the poster is I think being a bit dramatic. At least that's the case looking at the industry from my (id argue broader) vantage point of being an expert in and working quite a bit with "legacy" companies and technologies that maybe could stand to have a new UI implemented and some tasteful modern conventions adopted at least as options for the end users.
California and Texas have a lot more in common than people who've only lived in one or the other think. Texas just happens to be growing very quickly and is in some ways more geopolitically important at the moment (energy and exports and semiconductors and finance), which (besides less business regulation) is a big reason for the outflow from Cali and other states to Texas.
That's what growing conservative "anti globalist" movements backed by national security elements are really about. Not ultimately immigration or racism or tax cuts (that's how you get the tubes on board), but about how the inability to keep civilians out of information conflicts has made running countries incredibly difficult.
This is one area where China absolutely has the right approach and we need to wake up about what it means in the public rather than complain that we can't scroll silly waste of time videos all the time. The US public is incredibly uneducated about this concept and why it poses a threat, so the discussion needs to be had.
I think we should be far more critical of American internet companies as well and quite a few of them should probably be banned because they are creating the same sort of problem w.r.t how we can practically organize a functioning society. That's the unfortunate thing, is a bunch of libertarians in silicon valley a while back decided to invent a business model that could cause a global war.