throwaway76543

The article you linked shows that more people moved to the upper bracket than the lower (5% vs 4%).

In relative terms the earnings growth was even more dramatic -- the upper class grew 27% larger whereas the lower class only grew by 14%.

There are more people moving up than down.

There are existing prototypes of laser systems for killing fast moving insects such as mosquitos. Imagine a device on a fence pole covering the surrounding acre.

There are plenty of slow moving pests, weeds and the like as well.

Scooters don't have pedals.

If your opinion isn't informed by data then what value could it possibly have?

Sure thing!

/sbin/init is pid=1, the single process that the kernel starts when a system boots. It typically runs a command to kick off bringing up userland to the correct runlevel, maybe something like "/etc/rc.d/rc 3". It doesn't do anything more than just execute this command.

The command is part of the RC system. Typically written in shell, it handles walking /etc/rc.*/ and running the scripts contained therein to configure and invoke the various services for a particular runlevel.

You can boot linux using your own init and skip the rc system. From grub, add "init=/bin/sh" to your kernel parameters and you will get a shell as pid=1 and no other processes -- from there you can run commands as you wish to bring your system the rest of the way up. If you were to run "/etc/rc.d/rc 3" by hand you would invoke the same scripts that normally run on bootup to runlevel 3.

You could also delete all these shell scripts and replace them with your own code for configuring the system.

Where are you getting 50kph from? Nowhere did I suggest that was a safe speed for daily riding.

We've been talking about 35kph, or 20 miles an hour, which is a perfectly reasonable speed for a bicycle. You're unlikely to be seriously injured if you crash at 35kph. People regularly ride 35kph throughout parts of their ride. It's normal, common, and entirely legal.

Your comments about "sticking to the speed limit" make no sense whatsoever. We're talking about speeds far, far below the speed limit even on residential roads.

I'm flabbergasted that you're having such a freakout over a bicycle going 20mph. I'd hate to see your reaction to an actual gas powered motorcycle or scooter.

That appears to be a ride where they've deliberately set a slower pace for a ride based around socializing. 12-13 mph is about right if you're going to be leisurely carrying on conversations with fellow riders. Any faster and wind noise becomes an issue. I can't talk to my fellow riders at 20+mph.

"lycra clad racing-bike riders" ride far faster.

Capping a vehicle at 15mph means you'll be constantly getting passed on trails. I have ridden a 15mph capped scooter, I was one of the slowest vehicles in my local area that day. I returned it.

I teach unix internals to engineers as part of my job and I've found most engineers aren't intimately familiar with the distinction between the RC system and the init system at all. I agree there isn't widespread understanding of this distinction but I think it is because most engineers simply don't know how any of this works.

The reason to keep these things modular is flexibility and ease of analysis and improvement. The major criticism I see with systemd is that has undefined operational scope and unbounded feature creep. It has no stable interface between components and changes behavior in incompatible and difficult to predict ways fairly regularly. From a systems perspective it's a big ball of mud and the lack of a formal interface makes it prohibitively difficult to change or replace its subsystems.

I don't like that systemd performs ANSI animations on my machine's serial console, for example. Have you seen the "marquee" animations it does when certain services start? I sure would like to force it to print sequential lines of text instead, but I can't.

I don't like that when systemd updated basic utilities like "reboot" I lost the ability to use them in a chroot. Even "reboot -f" which does not need to talk to init. I had to write my own one-liner to call reboot(2) myself not too long ago.

System components need to be well scoped and replaceable. There's a major design problem brewing in this area.

I spoke of the ground being a stationary object (the most common one anyone will encounter, as I put it). I did in fact fall onto the ground.

Crashing into stationary objects is indeed a much greater danger than a fellow cyclist riding with a 10kph speed differential. That was my point, which you are now re-stating.

Hope that clears up any confusion!

Yes, without question. Systemd provides me absolutely no benefit when running a server and adds considerable complexity and fragility in a critical component.

A traditional SysV init is just fine. Want orchestrated service invocation on startup? Run it from SysV init instead of replacing SysV init.

There is no need to conflate the "sysv rc system" with "sysv init." They are entirely separate things.

I think you might be confused. We are talking about the danger involved with two bikes going the same direction with a 10kph speed differential (25kph / 35kph). When crashes like this happen, people fall off their bikes.

I mentioned that I have fallen off at this speed with relatively minor injury. People generally do not die from falling off a bike at 35kph.

Nowhere did I say anything about being hit by a car at 35kph not being dangerous. No one is saying that.

We're talking about two vehicles colliding with each other. The mass of the vehicle is absolutely relevant.

Crashing a bike at 30mph/50kph is not as dangerous as you suggest, you can find plenty of higher speed bike crashes on youtube with no fatalities. Road rash and broken bones are the most likely outcome. I've crashed at this speed and I walked away with road rash only.

There is an enormous difference between a bike crash which results in sliding along the pavement and a car crash.

Are you thinking only of riding on roads? I often ride on paved bike trails. They're usually maybe two meters wide with mixed pedestrian and bike traffic.

Even in a bike lane you're still passing stationary objects. You asked "when would there be any" and then immediately gave one of the most common examples. An even more commmon example, of course, is the ground you're riding over. You have a 25kph speed differential to the earth.

There is no serious threat to your life from a bike going 35kph. I've crashed at that speed or faster numerous times on downhill courses. No need to be so melodramatic.

No they don't. The Oxford Cycling Club claims an average of 17mph -19mph or 27-30kph: https://www.britishcycling.org.uk/club/profile/7892/oxford-c...

"The average speed can vary according to weather conditions and ability, but expect an overall average of around 17mph -19mph for a ride of 60 miles"

Furthermore, an average speed will have significantly faster and slower portions along the ride. The OCC will drop to far slower speeds uphill and will ride far faster on the downhill.

25kph is a meandering speed for an adult on a road bike. 30kph is quite common and 35kph isn't unusual. I regularly ride paved commuter trails with bikes doing all of those speeds and it really isn't a problem.

The idea that a 10kph speed differential between vehicles is a problem doesn't make any sense considering you have a 25kph speed differential with stationary objects on your commute. Or 50kph if you consider two 25kph bikers passing each other.

It's really a non issue. 25kph is an unreasonably slow limit. The energy levels involved in a bike crash simply don't compare to the potential for damage in a car crash, in part due to the lack of mass.

No, the data is not up for sale. As the article you linked clearly states the data is anonymized and cannot be tied to individuals.

It's simply not a thing. It would violate PCI-DSS.

I'm not sure what you mean with the first bullet point. All banks which do payment processing do lending. It's inherent in the nature of the service, that's what the above article is about.

Using credit cards at thrift stores cannot affect your credit score. That article is poorly written and is discussing impact to credit issued by the credit card issuer. It may impact models run by the bank which issues your credit card but it will not impact lending from any other source and will not impact your credit score.

No one can share individual purchase data with other lenders, that sort of data sharing is prohibited.

Yes, with a per capita expenditure of $700 it's safe to say they aren't covering any serious illness. "Our costs are low because we have a healthy lifestyle" -- more like the costs are low because no one has any serious illness like cancer.

I'm looking for more than a strap and a seat. I'd like the entire interior space to be repurposed to absorb impact energy.

Honestly what I'd like is a safety oriented cabin designed to minimize whiplash. Restrain my head and neck, surround my body with impact absorbing material and put a screen in front of my face and a keyboard within reach of my hands and we're done.

I don't want a large void space inside the passenger area of my car at all.

Would you care to elaborate? I'm finding your opinion rather odd myself.

The vast majority of people never freeze their credit and never have to expend any energy on the issue of credit security at all.

Most people have their credit run a few times a year, when they sign up for a new service, new credit product, raise a limit, buy a new vehicle, what have you.

On the contrary, credit card theft is one of the most common forms of identity theft.

As I said above, it is far, far less time and expense to follow up to actual fraud with a police report than it is to freeze-unfreeze your credit every time you want to pass a credit check.

As I said above "No one is talking about totally ignoring fraud and allowing a default judgement to occur"

You are discussing something entirely different, unrelated to the point I made above.

The vast majority of people will spend less time as this is a rare occurrence.

Freezing a credit report is not going to prevent someone from getting ahold of your information. It will prevent someone who already has your information from running your credit and opening new lines of credit -- which doesn't matter much. It is completely ineffective for the vast majority (90%+) of identity theft.

It will not protect you from someone stealing your cards or checks.

On the contrary, it works even better if you regularly use your credit report because you don't have to deal with the absolute pain in the ass of freezing and unfreezing it constantly. Time is money and that's a guaranteed loss of both.

The kind of identity theft involving use of a credit report (as opposed to a stolen bank instrument) is relatively rare. Most identity theft involves a stolen credit card and freezing one's credit report offers no benefit in that scenario.

I am absolutely not wrong, the vast majority of people take a passive approach and are fine.

I don't know why you're talking about "getting your money back," this kind of fraud doesn't involve any loss of money from anyone other than a bank. There is no way at all that I can put my own money at risk by not freezing my credit. No one is talking about totally ignoring fraud and allowing a default judgement to occur -- I am talking about not paying upfront fees to micromanage access to pull credit.

It does not matter very much at all.

Just file disputes, it'll get removed. Disputes are free and with a police report in hand they will go through.

I'm suggesting you should not pay upfront to help curate this data, to pay to micromanage access to a credit report to protect other lenders.

You could just do nothing. That's what I'm doing. I care very little if someone defrauds some bank using my identity to open credit cards. I won't be paying for it. It's the bank's problem, not mine. I'm under no obligation to expend effort to maintain their security and datasets.

The more you let this kind of thing be pushed into your lap, the more it will be.

It's not reliable enough now, sure.

Similarly, my 6 year old is also not reliable enough to pilot a car.

Both will change as they mature.

Self driving cars also have prior experiences and a sense of what other drivers are doing and why. That's sort of the point of machine learning.

In fact, they will have a lot more prior experience than any human driver in the world.