grumps

I finally caved and switched to Wayland 6 months ago or so. Things just work so much more smoothly.

I love uv, the why not works great if it’s your machine but in places without your machine uv is just another step for a customer.

`sh` is nice but it requires a dependency. No dependencies is nicer IMHO. uv makes this way easier but for low dependency systems, or unknown environments stdlib is king.

Fair enough w.r.t to how it works in the EU. I sort of knew that the legal system there was not as easy to bring suits etc.

As you said reaction is based on my personal experience in the US. However at times the US does pickup ideas and concepts from the EU, specifically California.

Because lawyers and courts become involved. They don't understand software or anything related to it.

A law and regulation is written one way and interpreted a different way by the courts. In the USA it's all about case law.

Hypothetical:

I write a nifty alarm clock app. To cover some costs I charge a nominal fee. Some unknown condition occurs a user misses a flight and loses their job.

According to your position I should be sued.

Why should I be held liable?

Daniel Stenberg has a blog post somewhere about all the hate mail he gets over the fact that curl is bundled in some software. You don't think some litigious person won't attempt to go after him over it?

My family has personally impacted by a dumb lawyer trying to subpoena information incorrectly. Dealing with this was 7k in lawyer fees, covered by an insurance policy. Technically he could legally held for this terrible usage of the courts but it would have been an even bigger mess.

This is outrageous and ridiculous.

Cool, don't use my code if you're in Europe or within Europe.

We will need amended licensing for denying use within Europe.

How in the world is this good for devs? It's terrible. Do you really think that "big corp" will not figure out how to pass the liability directly to the author?

What will happen the opensource world once you're held liable for some moron who uses some software I wrote for myself? or incorrectly uses it?

do you really believe the curl should be held liable because some POST failed and a user lost something over it?

what about my old backup scripts? I need to remove them from my repos?

please provide a link to all your software, so I can find bugs and then sue you for everything you have.

I rarely comment here on hackernews. I've also seen several flame wars over pipenv. I also believe that python packaging and pinning is nothing but a mess. Recently I started using Pipenv and suddenly I've been having horrific issues with python to the point of me almost giving up on the language itself. I believe the issue is a mix of Pipenv, Pip and Debian. I don't have full scope view of the issue yet but without evidence I believe the issue is how Debian uses Pip at the system level, and in pip 9+ an API used by Debian changed. Pipenv seems to greedly somehow upgrade my pip and thusly hoses everything and I find myself reinstalling everything. All three are making me consider making changes to my entire stack and setup that I've been using daily for the past 5 years on many many systems.

In addition when/if I have time I'll further debug and attempt at PRs and issues to help.

I almost _never_ write comments, but I had to write here and say that despite having almost all the Boynton's books we own memorized that I still enjoy reading them for my 18 mon old.

edit: clarify I don't have ALL Boynton books.

They're are many downfalls with working remote. In the past year of being remote I've found that it can be very difficult to pick up on the attitude of a co-worker or boss. It also can make difficult conversations not go so well. People will also avoid having to have face to face conversations because they don't like confrontation. I like working remote, but I also think it's important that a "connection" be built with your co-workers and sometimes that just only partially happens over chat and hang outs.

Hey PM here - once you go PM it's going to be harder to back to DevOps if you want to.

Small sites may not have been hit if you turned it off soon enough. Quick tips:

* Look through the menu_router table for suspicious looking entries. * Look at users & user roles, anything new? * Look for scripts and executibles in your public and private upload files directory.

If you really don't know drupal and it's a new project, start from scratch (New Database but you're code should be safe assuming your repo isn't stored on the same server and there's no write to repo access on server)