ragingrobot

My intent was not to advertise this as an alternative, and I do not see how you came to that conclusion. I was pointing out that this is not unique to the freight railroads to intimidate employees into coming to work on a regular basis.

Quite a few applications do this.

For something like the mentioned oh-my-zsh, it can be safely assumed the user is not a novice in most cases. Having to install in this manner may in fact deter the user, as they'd be suspicious. A well written README would be the better route.

I'm not even going to say which is worse, they both suck equally in my view. The problem with articles like this, as they (purposefully, perhaps) make no mention of such employer tactics. So, I guarantee most readers are saying or thinking "greedy union workers."

"Total Comp", which typically is more than wages. This includes health benefits, which can be a significant part of the figure. So like another said they get the bare minimum but these figures seem inflated and make the employees exactly as said, "overpaid." So, all the public sees is "130K," with no clue where it all comes from.

As well, I have no clue what their benefits are like. It is quite possible they contribute to their benefits as well as most people do, which means their take home may be even less than you'd expect. I for one have employer provided health coverage where the employer contributes, as well as a portion comes out of my paycheck, with co-pays upon an office visit.

Hey, something maybe for one here I can shed some light on, for those who want a little more than the article gives. ;)

I am a supervisor on a commuter rail, and in this respect they operate in a similar fashion.

Like any other business, profits are key. Someone figures out staffing. Pretty much cut and dry. For a line from terminal A to B, there is one train per hour in each direction, 48 trains in a day. We need for example a supervisor at each end, and one engineer and conductor per train. So, say that gives us 48 train crews, and 6 supervisors per day. So, we hire 6 supervisors, and 51 train crews - in case someone calls out sick.

What happens if someone calls out sick? A supervisor? We keep costs down there by requiring the on duty supervisor to stay an additional shift. A crew member? We have that extra crew. If we have too many people call out sick, we force on duty crews to stay on overtime. We don't want to be doing that, now do we? That affects the bottom line.

If no crew is available at all, then the train doesn't run. This is also bad, as it upsets the customer.

Running with a "skeleton crew" ensures we are not spending more on labor than we have to. This is because in some markets, paying fewer workers overtime still comes in at less than having more people to whom benefits are paid.

So, the employees are intimidated into coming to work every day.

What the freight railroads are doing here is forcing the employees to use their vacation pay when they are sick to discourage them from calling out sick at all, in effect penalizing them for calling out sick. That vacation you had planned with the family? Either lose a day (which may require you to cancel altogether), or come to work sick. If they have paid sick leave, they'd use it when sick rather than showing up to work.

My agency uses a different tactic, just as effective in the employer's view, but no less exploitative of the employee. When an employee calls out sick, a Special Inspector may be sent to their home to check if they are really sick and at home. If the employee doesn't answer the door (They're sleeping and don't hear the door? Doesn't matter), they're charged with falsely calling out sick, and face suspension or termination.

Edit: This industry can be very time sensitive. It may not seem to you a big deal if say a train is late, but cargo is critical or a passenger gets to work late, that is not a good thing. The shipper may take some action if it happens enough. That passenger may start driving.

I didn't disagree with you at all. I was just providing some more substance, beyond the charging and durability factors. I mentioned flooding as one factor. When the remnants of Ida hit last year the entire transit system shut down due to flooding - for hours. Had they still been running diesel powered buses with less sensitive components, some service could have been provided.

As far as the load however, higher speeds aren't required, and they can maneuver like rhinos and it's OK. NYC Subway cars do pretty well hauling loads, the most powerful motors being ~160hp (unfortunately torque ratings are impossible to find), with the car body itself being over 40 tons.

> I understand the use of EV's for passenger cars, but transportation isn't a one size fits all.

I agree fully. Right now all this is a money grab because it's being thrown around in the name of climate change.

I am of a sort of mind where tech should have limited use in the transportation space, where reliability should be primary. Our subway trains and signals routinely have some sort of computer related issues where implemented. The older tech tends to have fewer issues when maintained properly.

The use case for a bus differs from a pickup, though.

As far as the battery, at least in NYC there was talk of having quick charging stations at the end of each line. However the typical driver layover time is on the order of twenty minutes, so they'd have to be real quick charging.

Never mind vandalism of charging stations, and that areas of NYC flood easily. I lived in an area where it floods easily in a moderate rain storm. The arrival of hybrid buses years ago also saw the arrival of "No service due to road conditions."

Many are stuck in this mindset "OMFG! The world is going to end literally, TOMORROW, if we don't stop global warming!" and providing knee-jerk responses. Corporations have no problem cashing in on it.

That's assuming they get close to the contact transfer limit. A lot of theoretical numbers are stated. Now that it's in use, maybe we'll get some practical numbers. Perhaps they never will get near the contact data limit, so it's not to be a concern.

It's possible they don't "catch up" for a while, getting a few extra bits and pieces over the next several contacts, not just at the contact following that missed.

They are indeed an abbreviation for "change". change {root,own(er),mod(e),gr(ou)p}...

I am one of those who say "c-h-..." as well. For some reason I find it less awkward to say than "shroot."

Perhaps the first thing I think of with "ch" is the hard C or K, like "character." That sound wouldn't work in those cases. 'Kroot', 'kown', eh... no, so "C-H-..." it is.

On that note the page mentions"char" at the top, lists "care" and I more frequently hear others use "char" as in to burn. In my groups I think I'm the only one that pronounces it as first syllable of the actual word.

If there are no severe restrictions or limitations on what Linux applications under Rosetta can do, that makes WINE a great possibility, at the least.

> The way I see it, the period from 1945 to 2020 was the exception, not the norm. Apart from that period (in the Western World), humans have been facing more difficult times than 2020-2022 through most of history. Still we have surivived, and at times, prospered.

Now you got me thinking about this. Perhaps that period was a technological "sweet spot." Technology assisted us in our tasks. It wasn't too primitive where it hindered us like the periods prior. On the flip side, we were not overly reliant on that assistance like perhaps we are now (think chip shortages disrupting nearly every facet of life).

Also, population growth. The planet is significantly more populated. For example, had this baby formula shortage happened during a period of less population, could it have had less of an impact? Even if the same proportion of the population were, it may have been not so great of a stress as supplies may have stretched longer.

Right before the 2008 downturn, I had an ING Direct (now Capital One) savings account, at that time with an APR over 8. At once point in the early 2000s it was doing a hell of a lot better than that.

It never recovered. I never saw that rate go above 1% ever since.

Why high? Someone else in the thread made a remark about the insinuation of a "phone in front of my face" but in fact this could very easily happen by a sober person just simply not paying attention, and that is fairly common.

> You can break parts that are expensive to replace.

Both in the process of tinkering, and out of frustration when stuff goes wrong. So, also developing a bit of anger management skill. :)

Technology in late model cars makes tinkering more difficult as well. Back when our parents were tinkering, you didn't have to reprogram a computer when changing heads or a cam. All you needed was hand tools, for the most part. My toys are an '88 and a '90. Both would require creating a new program for major changes- requiring EEPROM chips and a programmer. Newer cars are simpler, but not as simple as needing just a screwdriver to tune a carb. Quite honestly it does take some of the fun out of it.

They ditched the concept about ten years ago. Being out of the loop I had to look up if APFS even supported them anymore, and in doing so, found opinions on two ends of the spectrum: the concept was the best thing ever, or one of the most detestable features. I guess no one really understood how to use them anymore and added to it's demise.

Last I was past the area, they had stuck a JetBlue ad on the Pepsi one. Not huge, but probably noticeable across the river.

Shame we allow this to landmarks. Granted it was temporary, but... eh... kind of tacky.

https://libn.com/2019/08/22/jetblue-addition-to-pepsi-sign-l...

Interesting, I have never seen such a thing. Perhaps it's more for comfort than mechanical reasons?

Everything's on the up.

I'm an omnivore, and use tofu for meals on occasion. On my trip to the Asian market yesterday (cheapest price around), tofu was 50% higher than what I paid last trip two or three months ago (was $1.39 for House Foods 10oz - a common brand around here, now $1.99). Nothing's safe.

Engines are lubricated almost immediately. The oil pump is typically camshaft driven, so it's only a matter of seconds before everything is lubricated. In addition, modern oils tend to "stick" to parts better and don't drain off as easily. It takes quite some time before they're completely dry.

As far as the material, at one time engines had components of various materials. Blocks of cast iron, heads or intake of aluminum. Now as you state, they are mostly aluminum. While it may expand more than steel, the majority of the components are going to expand at the same rate, unlike in the past.

This has not been necessary for quite some time. With modern tolerances in manufacturing, it is not necessary, even wasteful (burned gas and small amounts of wear that add up over time) to warm up a vehicle.

It may have been another story at long ago with larger gaps between rings, differential expansion of materials, newer oil formulations and so on.

With my daily driver 1995 Grand Prix (which just a few weeks ago bit the bullet, non-engine related), I never, even in the coldest weather let it sit idling warming up. Most mornings even around 0F, I turned the key and drove off. It died with ~289,800 miles. It did not consume any oil or coolant, the spark plugs are clean as new.

In fact, driving off easy will warm the engine up faster than letting it idle.

> We've made it through decades without breaking theming, what changed?

According to the GNOME team, application developers were getting bug reports filed against their application about broken interface elements, and GNOME was having bug reports filed for the same. The devs stated it was the fault of the theme being used, and as such it would eliminate a lot of headaches for both if themes were forbidden.

"Independent developers" set out to explain this in more detail. [1] While it is targeted at vendors who created their own themes for branding, it echos the overall sentiment toward theming from GNOME itself.

A blog post from a dev as well. [2]

[1] https://stopthemingmy.app/ [2] https://blogs.gnome.org/tbernard/2018/10/15/restyling-apps-a...

unfortunately using a simple pipe is not going to work, because you're also looking for user input, and you can't do both easily with stdin.

This article made me check out my dict out of curiosity (american). It has words like "zorch". No. Clue.

Perhaps allowing the user to specify a word list, and defaulting to some value would be better than suggesting symlinks.

On Tumbleweed, I have no /usr/share/dict/words, but /use/share/dict/american. Allowing the user to set would also be useful if multiple languages are installed, and doesn't change the number of lines of code.

I changed the first line to:

  words=$(grep -Ex '\w{5}' "/usr/share/dict/${wordlist:=words}" | tr '[a-z]' '[A-Z]')

so I can invoke it

  wordlist=american wordle.sh

You can also replace it with $1 (or any other positional parameter):

  words=$(grep -Ex '\w{5}' "/usr/share/dict/${1:=words}" | tr '[a-z]' '[A-Z]')

And invoke it with

  wordle.sh american

In either case, it defaults to /usr/share/dict/words if no list is given. Personally I'd go with the first as you use $1 for guesses, and higher numbered parameters get messy.

In one side of my mind, I agree with others that such behavior is unprofessional. Then I remember, this is pretty much his project, it may have grown in great leaps but it still started out as his personal project and he gave rules for working on it which were broken.

I haven't been following lately, but last "outburst" I had noticed was two or three years ago. It was pretty mild compared to this, but used some harsh language - nothing at all profane, IIRC he still used terms like "idiot," "trash," and the like. People still had a fit, saying he'll never change.

This is pretty cool. One thing is that it seems to get confused by nearby (smallish?) bodies of water. Near my house there's two creeks, they meet sort of forming a D shape. The traced path jumps across a small land mass once or twice between the creeks. Ultimately the drop would have ended up in the Raritan Bay regardless (although tool says Atlantic Ocean, I guess that's just me being pedantic) as the two creeks merge right before the mouth. Still, pretty cool.

A good pair of walking sneakers. If you're comfortable you'll keep at it. If well supporting you'll avoid pain and injury. Call that ROI or avoiding future loss.

> I'll be at least spending part of the day in the PacNW forests to keep the depression at bay.

Enjoy some of it for me. I will get out there, someday...

I keep saying it, before I visit any foreign country, I'm spending some time in the PacNW.