Fortran is still a good language for some purposes I think.

And I feel the same way, C++ tries to solve the problem of having too many features by adding more features.

I'd rather believe it's a bunny than acknowledge snails that large exist.

When I think of a tech worker union my thoughts first go to standardizing everyone's pay and limiting what I can earn myself. I've probably fallen to anti-union propaganda.

A tech worker union that says nothing about pay could still do so much.

A union could ensure that the company's incentives are aligned with worker's incentives around things like on-call.

I'd love a union that forced a company to give all on-call workers compensation. Something like:

1. If you're woken up in the middle of the night, you automatically get 8 hours comp time (time off), plus 2x the time you spend on-call during off hours.
2. Accrued comp time over 20 hours must be payed at 10x normal pay if the employee leaves the company for any reason. The idea here isn't for employees to accrue comp time, but to give the company a strong incentive to ensure employees use their comp time.

Basically, if a company is having lots of on-call alerts, or the company is preventing employees from using their comp time, you want this to be directly painful to the company. Incentives should be aligned, what is painful for the worker should be painful for the company.

Or, regarding "unlimited PTO". I'd love to see a union force companies to:

1. "Unlimited PTO" policies are fine, but they must have a guaranteed minimum amount of PTO specified in writing. So none of this "yeah, we heave 'unlimited PTO'; oh, we're really busy this quarter, so can you wait to take PTO until next quarter?".

Tech workers have it good compared to a lot of workers, but there are still plenty of abuses a union could help with, even if the union never even mentions pay.

This is how companies that don't have competition act. This is how most companies act. We need more anti-trust enforcement.

It seems the people who are the most staunch defenders of capitalism and free markets are the most resistant to the capitalist and free market solution.

Clean air (or rather, air with normal levels of carbon) belongs to the public, and anyone who wants to take it away should pay the public.

If ByteDance is a normal company they will seek profits and sell for as much as they can.

But if TikTok is a Chinese psyop, they'll just use any of the many legal tricks we allow to change the "owner" while China still retains control. Companies do this all the time, look at shell companies and such. It's super easy for China to mask the true owner if they decide to.

This is why we should make broadly applicable regulations instead of picking on one specific company.

No real use you say? How would they engineer boats without floats?

I get so aggravated by video games with weak flashlights. Like, we live in an age where my keychain flashlight can light up the nearest mountain.

Are we going to clutch our pearls over work-from-home inequality while we ignore the even greater inequality of pay differences?

Jobs are different. Pay is different. Those who can work from home should have an option to; this will help them, and the environment, and those who do have to travel to work. If I have a job that requires me to travel, such as physical maintenance, working in retail, etc, I welcome a smooth commute because half the people are working from home.

To avoid running code that might steal your data for profit, only run official code that will still your data for profit.

Shorter code is almost always better.

Should you use a class? Should you use a Factory pattern or some other pattern? Should you reorganize your code? Whichever results in the least code is probably best.

A nice thing about code length is it's objective. We can argue all day about which design pattern makes more sense, but we can agree on which of two implementations is shorter.

It takes a damn good abstraction to beat having shorter code.

I've come up with the following rules for my own relationship with Reddit.

1. I will avoid posting on Reddit.
2. If I do post on Reddit, I must make a similar post on another forum, maybe Lemmy, maybe somewhere else.

Number 2 is important because it helps other small communities grow.

It's not a problem if a lot of people post on one forum, but it is a problem if a lot of people post only on one forum. I wont allow myself to post only on Reddit.

That said, I haven't posted on Reddit since June.