Noob

So in your head, people are rich because they throw away their money?

Nothing says “cheap” more than clothes which are pretending to be expensive. If you’re going to dress up, wear your better clothes that are in your normal style.

Personally I wouldn’t bother. Just wear what you normally wear. Not everyone is interested in clothes even if they have money.

Part of it might be that I’m often having similar arguments with the team I run about introducing dependencies.

Engineers have a tendency to want to use the perfect tool for a job at the expense of other concerns. It could be ease of maintenance, availability of the skill-set, user experience, or whatever. If there’s pushback it’s normally that they are putting their own priorities above other people’s equally valid concerns.

Often I’m telling people to step-back. Stop pushing, listen to the resistance and learn from it. Maybe I’m on a bit of a crusade when I see similar situations in open-source.

I think for python tooling the choice is Python Vs Rust. C isn’t in the mix either.

people like and want to program in rust

I think there’s a survivor bias going on here. Those that have tried rust and stuck with it, they also like it. Far more people in the python community haven’t tried it, or have and not stuck with it. I like and want to program Haskell. I’m not going to write python tools in it because the community won’t appreciate it.

Tools should be maintained by those that use them. Python doesn’t want to rely on the portion of the venn diagram that are rust and python users because that pool of people is much smaller.

Those languages bring different things though:

• Python is the language the tool is for

• C is the implementation language of Python and is always going to be there.

• Cython is a very similar language to Python and designed to be very familiar to Python writers.

• Fortran is the language that BLAS and similar libraries were historically implemented in since the 70s. Nobody in the python community has to write Fortran today. Those libraries are wrapped.

• Rust is none of the above. Bringing it into the mix adds a new barrier.

I don’t think it’s a dream of “everything in python”, but “python tools for python development”. It means users of the language can contribute to the tooling.

How about “To learn it to that level will take 10,000 hours I don’t have”? Does that make more sense to you?

“learn Rust” in this case is learn it to a level where all of the little behaviour around cross language integrations are understood and security flaws won’t be introduced. Expert level.

It’s not “I did a pet project over the weekend”.

equivalent to one in every £3 spent.

Why not just say that ⅓ of money spent was on contracts that had red flags? That’s what they mean, but they’re trying to make it sound more damning and speaking nonsense.

Journalists and numbers is a bad mix.

On the topic of the actual story, I’m not surprised. When are we going to bring a case?

I’m trying to understand Git, but it’s a giant conceptual leap.

To start with, start with just using git locally. Don’t worry about GitHub or similar. Then git and SVN will work very similarly. The main difference is that you need to git add files with changes inside before you commit them.

Once you’re comfortable with using it by yourself, then I suggest running something like forgejo locally to be your own code server. Then you can play and learn how the two parts work together.

Generally, you need to give yourself a little time. You need to do the work. Be efficient…sure, but don’t try to force it to be quicker than the time you need to learn.

Right, so you just have a single step and then hand over to a proper script. I’ve seen many people try to put much more complex logic in there before handing over to a proper language.

Config is fine, but Yamls biggest problem is people use it to describe programs. For example: playbooks. For example: CI steps.

If YAML wasn’t abused in this way it would have a lot less hate.

Sometimes your longest serving engineers can be your biggest anchor. Good engineers are (justifyably) highly opinionated about what can be done, but sometimes it turns into “what I do works, so all other ways are wrong”. At that point the best move for them might be to go learn how somebody else does it. Wish them well, and back a different horse.

Often the money if far more than the individual realises.

1. Depending on the country, there may be taxes or other benefits which rise to the same degree or more.

2. Members of the team or grade need to be paid amounts which are within some range so that everything is fair.

You may feel you’re worth more than the majority of others, but it’s rarely the truth.

A VP was brought in at the company I used to work for that claimed “I need to offer candidates substantial increases or else I won’t attract top talent”. He started hiring people at a significantly higher rate. (I left at this point) Soon, the other engineers found out and all hell broke loose. They demanded equal pay.

The company is currently in financial difficulties. The salary bill got too big. They’re now struggling to complete the projects underway because they’ve had to cut staff and the 40yo company is probably going to be swallowed up.

Bad Britain has 4 countries thank you very much.

Op was listing different Lsp servers for things like jedi, pyright, etc. All of those things should really integrate with a single server.

Ticketmaster have been price gouging events for decades. This was just where they ended up because regulators have let them get away with it.

Shrinkflation is smaller quantities

Yes

and/or higher prices.

No. That’s just normal inflation.

Sounds like things are going very wrong in lsp land. The point of a language server is to support lots of types of tools through an abstracted server. Not to have one server per tool.

Otherwise, just use fly-checker. It can even get information from multiple tools at once.