I guarantee that there are a ton of sites out there not monitoring their certs.

Including Microsoft, Starlink, Github, Cisco:

* https://www.keyfactor.com/blog/2023s-biggest-certificate-out...

"A ton" being a misspelling of "the vast, vast majority".

A discussion on licenses will go sideways very quickly. GPL does limit the adoption of software in certain environments. So it really depends on your goals. Do you want an OSS project that will be useable by everyone (including corporations) or do you want to guarantee that the software will always be OSS and guarantee that Corporations can’t benefit from it without contributing back (potentially requiring them to open their own proprietary code).

There’s a lot of moral perspective that people apply to this decision, but not all developers have the same goals for their software. MIT is more flexible in its use than GPL, but doesn’t help ensure that software remains open.

> MIT is more flexible in its use than GPL, but doesn’t help ensure that software remains open.

Sure it does. The original software will always remain open. It isn't like people can somehow take that away.

GPL is copy left, it has a stated goal of encouraging more software to be OSS, including new contributions. That’s what I meant by software remains open. MIT on the other hand can be used in closed source situations. While the original code will remain open, future changes are not required to be open source.

They can use it on locked devices where you cannot replace it though. And then what do you do with the source? Print it and appreciate its beauty?

I found the title for this post misleading. To clarify it a bit, AI has only improved productivity by 10% even though 93% of devs are using it.

Yeah, the title may suggest that productivity is still 10% out of 100% after CEOs fired half of developers believing that the rest will do all the job with the help of AI.

This is ultimately the thing that needs to be fixed. The exemption for small trucks was stupid, and it should have been reserved for literal farm equipment (as that was intended). The fact that SUVs slip by on this now has created such a dumb market.

The OBBB Act passed by Congress last year eliminated the financial penalties associated with violations of CAFE standards, so there’s presumably no reason why automakers have to abide by them anymore, except possibly for concerns about future legislation.

> I need that little bubble that separates me from other people.

I get the same independent feeling from others you describe while riding my bike (not a bubble, but that’s a false sense of security in a car giving the 40kish car occupants who die every year in the US). In fact, I generally enjoy that bike experience more than I ever do driving because I never get stuck in car traffic, never get stuck behind a line of cars at a traffic signal. Never need to work about parking, other than finding a secure place to lock up (which some destinations lack). I used to love driving, but I started commuting by bike for work and realized over time that I enjoy biking so much more that I go weeks at this point without ever driving.

FWIW I live in a smaller American city of about 120k people, but is part of a greater metro area.

I really like this advice, but aren’t these two examples the same, but yet different advice?

// Good? for walrus in walruses { walrus.frobnicate() }

Is essentially equivalent to

// BAD for walrus in walruses { frobnicate(walrus) }

And this is good,

// GOOD frobnicate_batch(walruses)

So should the first one really be something more like

// impl FrobicateAll for &[Walrus] walruses.frobicate_all()

I suspect that Mark Twain would even greatly appreciate the humor in referring to it that way.

He once said he would, in fact!

;)

Is Mark Twain still alive? I heard they exaggerated his death...

The American Heritage Dictionary is far better than Merriam-Webster in my experience.

Rust pretty much nails all of those.

Not really. By default allocators will panic if there isn't physical memory available. Recursive functions can cause panic at certain depth. Code generated by macros isn't very visible for the developers and recursive macros are very common. Return types are checked only if the developer adds #[must_use].

You can overcome lot if you invest a lot for type system, but that depends on the developer.

“The tea bags used for the research were made from the polymers nylon-6, polypropylene and cellulose.”

They aren’t pure plastic.

Those were three different bags, not all in one.