alextingle

Try cutting down your caffeine really slowly. I did it by gradually cutting caffeinated coffee with slightly more decaff, over months. Eventually I was 100% decaff. Never had any withdrawal (the headaches, and energy slumps you mention).

And now I no longer have any of the bad symptoms caffeine was giving me: nervous tick, wildly fluctuating energy levels, random extreme emotions.

Back when I was younger, caffeine had none of those bad effects on me. But as I grew older, they started to ramp up. Because coffee was such a constant in my life, it took me many years to realise the cause.

Just take a look at the heap, and see what's there. If an object is leaking then the heap will be full of that kind of object. If it's a problematic leak, then the excess pointers will be easy to spot.

I think you watch too much far-right nonsense on YouTube.

Couldn't he just sell it in two volumes on Amazon, and charge $7.50 for each volume?

If your editor just blithely replaces tokens in code, then your alignments are going to be wrong. We write code in monospaced fonts for a reason.

> Even allowing comparison operators like ≤, <, ≠ and = that align > consistently would be a useful start.

Every text editor that understands Unicode already allows for that. If you want to use ≤ rather than <=, then you need to alter the language, not the editor.

Does this mean LCD displays are going to get a lot cheaper? That would be nice.

What? You sound like someone who's complaining about all the "pointless" semi-colons in C++ code.

If you can't be bothered to learn the basics of the language, your criticism isn't going to be worth much.

First you have to appreciate that Make isn't as bad as you think it is. If you want to improve on it, then first you will really have to understand it.

That's the pitfall that so many would-be build system authors fall into: _Holy crap, why is it so complicated? Surely something simpler would do the job... [YEARS LATER]... Shit, my build system is so ugly because of all those damn real-world edge cases I've had to fold into it._

I've written Makefile for FORTRAN. Dealing with modules added about 6 extra lines. That was one of the more complex rules. Does that count as "special magic"?

He thinks he needs a shell script to do automatic dependency management with Make. Obviously he's not presenting himself as a Make expert, but that's hardly rocket science.

I don't see anything in there about efficacy. Did it actually work to combat obesity?

Isn't the possibility of side-loading one of the main things protecting Google Play Store from being hammered by the Digital Markets Act?

Came here to post that. Danke!

That's absolutely not the case for everyone. Dismissing all treatment for psychiatric disorders as "always worse for the patient" is dangerously ill-informed.

> None of that happened, and not because all the bugs were fixed.

No one is in a position to assert that. We have very little idea how fragile our civilization is. Perhaps it's pretty robust, and networks of interconnected problems (like Y2K) stand no chance of snowballing out of control. Or perhaps it's really, really fragile, and surprisingly little stands between us and a profound collapse.

It's very difficult to be certain, because it's such a complicated system, and one that we can't really test to destruction.

Would all the Y2K bugs have caused a widespread systematic failure if they'd gone un-fixed? Probably not... but maybe? Just like all low-probability, high impact risks, it's very hard for us to reason about.

How much money is it wise to spend on averting the risk of giant asteroid impacts? Hard to say. Probably more than you think, though.

Having inputs look consistent between applications is a core plank of usability. Rolling your own custom widgets is just spending a lot of time and effort making the UI worse.

> It's got a lot of warts.

Really? Seems pretty elegant to me.

The problem with Make (or any build tool) is that few developers care about how their project is built. They want to focus on writing their code, push a button, and get into testing it. That's a fair enough attitude.

But the problems with build tools are insidious. It's basically trivial to build a small project, so to start with, everyone assumes it's a nothing problem, and spend no effort on it. Then as the project grows, over months and years, the problems slowly accumulate. Each time some feature or corner case is added, the build gets slower, more complex, and cruftier. Eventually someone decides to take a look inside, and recoils in horror...

But it's not Make that's the problem (or any build tool). It's just the fact that building big projects is a tricky problem, and requires just as much effort to solve elegantly as any other tricky problem.

I worked at a big bank that had a problem with their Make-based build system taking multiple hours (sometimes days) to build some of their projects. They spent millions on trying to replace it with some Java monstrosity. I spent a few months rewriting their Makefiles, and the build times shrank to less than 1% of what they had been.

Make was the best tool for the job, because the job was vast, and had many, many corner cases. Make is a general purpose language, and is fairly unopinionated about how you use it to solve problems. All the "Make replacements" I looked at were far too opinionated to be elegantly bent to the task at hand. They were designed to look simple. That's great when your problem is simple, but big builds are not simple.

> it's obviously easier through a web interface

Why? Typing "wc file" seems infinitely easier than navigating through some web interface. Care to explain?

You think Germany has a monarchy??

What's the solution to his problem getting printf() to work?

That does sound like a PIA.

> It is also within their prerogative to dismiss employees who protest company policy.

If they are performing their duties adequately, then that's absolutely wrong.

It's also utterly stupid. Employees who think about what they are doing are far, far more valuable than mindless drones.

> it's straightforward to change the default.

Care to share? Looking at https://systemd.io/TEMPORARY_DIRECTORIES/ and I don't see any description of how to change the default behaviour dictated by systemd.

How do I disable the automatic file reaping? How do I configure the maximum age of temp files? Neither are mentioned. The bulk of the page is just a long list of passive-aggressive suggestions about how users are doing things wrong.

Plenty of new Chinese EVs driving around here in the UK.

An update bricked my Ulephone after 3 months. Not going there again.

Love the bait and switch where you are invited to upload an image, THEN asked to create an account and provide an e-mail.

No.

It you start out that manipulative, then I can't be bothered to engage.

If you require account creation, then be honest, and say so upfront.

> Indeed, one reason to outsource stuff to a handful of giant providers is that they do a much better job of security overall.

Is that really true?

Shifting infrastructure to the cloud makes it cheaper, it reduces the incidence of security problems, but it magnifies the impact of security problems when they do occur.

Is that a "better job". How do you measure that?

No. You were clearly insinuating that illegal immigrants are likely to commit crimes.

That subreddit is basically just an ad for various crappy US brands. There is zero interest in discussion of actual BIFL products, or practices.

Make works just fine on Windows.