teknopaul

We need one of these for .debs. The answer files are easy to generate after installing once but it would be better to have an HTML ui that catered for every annoying .deb that can't think up sensible defaults for itself.

If you are a white US citizen you have nothing to be concerned about.

Unless you have friends, family or empathy.

Just package node_modules subdirectories as tar files.

I stopped using npm a while back and push and pull tar files instead.

Naturally I get js modules from npm in the first place, but I never run code with it after initial install and testing of a library for my own use.

I don't see why system wide dns caching would be of use?

How many different programs in the same process space hit so many common external services individual caching of names is not sufficient?

Article lists a bunch of fun with systemd running junk in containers that seem counterproductive to me. A lot of systemd stuff seems to be stuff useful on a laptop that ends up where it's really not wanted.

Local dns caching seems like a solution looking for a problem to me. I disable it whereever I can. I have local(ish) dns caches on the network. But not inside lxc containers or Linux hosts.

Don't do this too much.

Your eyes have to focus. For things close enough they can tell from the required small angle of cross-eyed movement, how to focus.

These pictures (and stereograms) disconnect the focus and angle of your eyes. Do it enough and you loose the ability to focus quickly. I found it out playing with steregrams on a 286 pc a long long time ago.

YMMV but I lost the ability to quickly re-focus object that you dont already know the size of; and it's a bitch.

Sad that the US has all these power outages. It comes from rampant capitalism. No obligation to provide redundancy so the cheapest solution it wores on wooden poles and one tree down leads to outages. In every weather event in the US the news reports xxx people without power. In the rest of the world it isn't a stat that makes the news. I presume this is because redundant grids don't often go down and when they dothe places where it happens has bigger problems.

I suspect nobody made xxx vlc plug-in because compiling it is far too hard.

I tried to make a joystick controller for a particular use case on one platform (Linux) and I gave up.

VLC solves a hard problem. Supporting lots of different libs, versions, platforms, hardware and on top of that licensing issues.

P.S. dont blame bash for sed. Once you grok bash, other tools make more sense. If you don't understand bashes escaping rules and options

echo x | sed "..."

Is doubly confusing.

RTFM. I have never met a shell user who has read `man bash` from top to bottom. It's not a hard document to read if you have been using bash for a while. People read bits of it, as you do with other man pages, and get frustrated navigating it. But man bash should be read top to bottom with intent to understand it before complaining about it. It should be given the same attention to details that you give any programming language, not any gui tool (that you can exct to be intuitive) bash is a very powerful language and deserves 1 hour of you time to read the man. It you want to write good scripts

Read Google bash coding guidelines.

Try to write shells scripts that don't fork. That approach really helped me write resilient scripts.

Use

x=`${...}`. Instead of

echo |...

Then you bash starts to improve every day, instead of accepting mediocre all your life.%

I have given the above lesson to a few folk who suddenly found bash fun and a highly productive programming language.

Like all languages get it working first, make it testable and refactor until it's good.

With bash that whole process can take 5 mins for a simple script: and scripts should only be simple

Profit creaming, not good for county even if it seems good in the city.

Everytime there is a natural disaster in the US the press report xxxx houses without power. US leccy firms pride the bear minimum service, always. Profit comes first. Delivery second priority at best.

This doesn't ofter happen in Europe because they dont profit cream and builds reliable redundant grid for almost everone. The grid even extends beyond countries boundaries, with neighbouring countries supporting each other.

Some folk out in the sticks, who you might think don't matter, provide useful services to the city folk. Eg farmers.

I.e. Cost the grid not the city.

You probably are being ripped off in the US, but that's a different story to the one being told imho.

Careful what you wish for.

Not important once has copilot ever suggested a correction, found a bug, noticed a typo, prompted for a better solution, which is what any human pair programmer would do. It's a tool. But thinking ng it's like a "copilot" marketing as such is fundamentally missing the point. It won't get better untill people recognise what it _can't_ do as much as what it appears it can do.

LLMs pattern match, they say something that sounds good at this point but with no notion of correct. copilot is like pair programming with a loud pushy intern that has seen you write stuff before didn't understand it, but keeps suggesting what to do anyway. some medium sized chunks of code can be delegated but everyline it writes needs careful review.

Crazy tech, but companies are just wring to be trying to use LLMs as any kind of source of truth. Even Google is blind enough to think that aí could be used for search results, which are memes they are soo bad. And they won't get better. They just become more convincing

My two penneth: I find the replacement part the easiest and escping all the characters which mean something in regexp to be the most annoying part.

Adding a new char to be escaped seems like another annoyance.

I try to avoid tools that make the hard bit harder, and the easy bit easier

I moved to Debian for servers. Ubuntu is no longer the easy option. Ubuntu has forced upgrades more often than any other platform.

Added "Security" that breaks users workflows is crap. You have to trust the code on your pc. Spend effort making it good, rather than jailing it in case it's bad.

Yep, if you package your own code or scripts, deb is easy.

Just FYI.

I know a few others who have suffered the same from this company.

I'd say the same. But 90% of my time not writing code. It is mostly time wasted with github and k8s build issues.

I could have told you that voicing deamons in your head gets rid of them 20 years ago. A bunch of my friends know this trick too.

I have successfully used this in therapy, i.e. helping friends on many, many occasions.

Strange that this is news in the psychiatric world: we "discovered" it by caring, and listening, and trying stuff out.

If psychiatric community is not listening to patients and conversing with them and their demons, and trying pills as a solution while knowing this doesn't work, it should be considered malpractice.

No wonder everyone hates psychiatrists.

Calling themselves doctors and the humans in front of them patients, is probably the root cause.

alt="Windows user discovers beauty of Unix ;)"

You have to define "desktop" as not being a phone or tablet for that stat to be sane. I would argue the desktop itself changed.

A wooden desk with a PC, a keyboard, mouse and monitor is likely to run Windows: until it's replaced by someone who isn't at a desk.

I have a chart I call "the Ballmer peak" which is the huge trough in earning that accompanied Ballmer's time at the helm.

He was impeached, and every single politician voted on party line, the whole GOP is 100% corrupt (if you agree he clearly did do it) impeachment is not a useful tool in this situation.

To solve this problem recently, I just defined -1% as 'not at all' and 101% as 'all of it' .

But then, I'm a Unix hacker. ;)

If the devs indicate that they aren't going to fix it, raising a cve is

- Rude - Counterproductive - not going to result in a fix - not going to help users

If someone does that in the full knowledge that it will cause a DoS on inocent party's build processes and their ability to shift fixes. It could be validly considered a deliberate denial of service via a supply chain attack.

Maybe that should be policy, so these security bods are forced to accept responsibility for the work they cause.

That would look good on their CVs.

Don't see the problem with ssn as I'd. People have two, get two rows in your database. Not the end of the world often. database it's a tool thus limitation is not an error. E.g. maybe trans peeps want to forget their old ID, maybe not. your own key has no chance of reflecting any reality in the world.

No shit sherlock

Imho Presume 8 bit, encapsulting 7bit usacsii. That includes utf8 and many many other encodings.

Don't interpret user supplied strings at all. Defines max lengths as byte lengths.

Remain agnostic of encoding. Especially in libraries.

It's easier than people think it is thanks to some very clever people's work a long time ago.

I suspect the author does not about the first bit being 1 thing.

utf8 is magic.

You can assume US ASCII for lots of very useful text protocols , like http and Stomp and not care what the variable string bytes mean.

Soooo many software architects don't grok the magic of it.

You can define 8bit parser that check for "a:"(some string)\n

and work with a shit load of human languages.

The company I work for does not realise that most of f the 50 year old legacy C it has is fine with utf8 for all the arbitrary fixed length or \0 terminated strings it stores.

The term ludite indicates that is nothing new.

IMHO this is not about tech being too good tho: it's about new tech being worse.

Much tech _is_ getting worse. Particularly AI, much is about cheaply making a bot that works x% of the time, it's cheaper to piss off a few customers and pay no-one, than to do a good job.

No one likes that, it's cheap and nasty hackery.

People like tech that works 100% of the time, and keeps doing it. Stuff that could not be done before that can now.

People don't like churn. Constant upgrades. Built in obscelecense. AI that work 95% at best. Maps that make different decisions each time. UI fads. Framework wars. Google buying and killing services. Clis that are not automatable.

"The only thing that is constant is the rate of chane" is an observation that tech is not providing what was promised: automation.

Cheaper nastier flakey versions of what worked fine should get a boo.