aard @ aard @kyu.de

Posts

5

Comments

493

Joined

2 yr. ago

On a real UNIX (not only AiX) killall is part of the shutdown process - it gets called by init at that stage when you want to kill everything left before reboot/shutdown.

Linux is pretty unique in using that for something else.

I guess it depends on how you are using your phone. If you're mostly using it between charges (possibly replacing other devices) it indeed doesn't matter. If you care about standby time, or use it as music player or similar tasks more than active use it does matter.

The same people who, in my field (software engineering), don’t know the difference between Java and JavaScript

The same people who don't understand that zip codes are not unique to a country, and do a zip code search on recruiting platforms without also setting a country. And then offer you to move to their country (at your expense) when you explain them the concept of zip codes and countries.

On a phone the additional power draw of larger modules can be an issue - plus phones are designed to freeze background apps to conserve memory, so you can get away with less.

I currently have 6GB in my phone, which mostly is fine. In a few situations I'd have preferred having 8, though. 4 or less hasn't made sense for a few years now.

RAM is cheap, and even if you're just doing absolute basic shit your current PC will work better with 16GB of RAM (also looking at you here, Apple). If it's not a phone you're buying don't get anything with less than 16GB.

Wall is a linguist, which influenced several of his design choices. You have a wide variety of expressing what you want in perl, just as with natural languages - some ways are maybe a bit harder to read for newcomers, while others are not worse than something like python. Typically you'd have coding guides for projects.

I did a webchat in perl in the 90s, and eventually rewrote it in php3 - php was easier to manage properly isolated between users than perl via the CGI interface, so it became popular with hosters very quickly. I went back to doing all my web scripting in perl once I started hosting my own servers,though.

For an inkjet printer with paper feed issues pulling it through a few times might actually fix those - the print head should be far enough away from the paper that it will not get damaged, and there shouldn't be other parts close enough. I've prolonged quite a few inkjet printers life in the 90s by just sanding the rollers a bit (in some cases you could even get maintenance kits from the manufacturers - which just would be an overpriced tiny piece of sandpaper).

In a laser printer I'd be worried about some of the internals, though.

You'll get different results depending on the printer type, though. For example, that kitchen paper would work in a inkjet printer (as in, would get pulled through, but you couldn't read the result), and work perfectly in a dot matrix printer. I know the latter as I used to print, err, learning aids on paper handkerchiefs with my dot matrix printer in the 90s. A few times teachers were suspecting something, in which case I'd just use it to clean my nose, and toss it. Nobody ever was curious enough to continue their investigation afterwards.

Make sure you use a long extension cord to a fuse without RCD for the hair dryer, though - otherwise the constant resetting of the breaker will eat up all your time savings.

That's pretty much the "we should all put PoE everywhere" debate, and I don't think that'll happen (or is a good idea) - and that's coming from me as someone with switches providing 1.5kW of PoE power budget in the garage.

The alternative would be a shared conductor like we have now - and while that is working will in data centres doing a conductor in the required dimensions for that would be too big, and potentially dangerous, so that'll happen even less.

It mainly depends on the space available in the case of whatever you want to convert. If there's a lot of space you just get a larger USB-C PD converter board with nice soldering points for the cables. The less space available the smaller the module you need to get, up to worst case trying to do your own.

Older notebooks, battery chargers, PMR radios, pretty much everything taking less than 100W DC current.

I'm in my 40s and therefore generally in the "get off my lawn, kids" age.

But I totally agree with that article. I've converted quite a few legacy devices with barrel jack to USB-C - and got rid of a huge box of junky old power bricks. Especially for devices I only use occasionally I don't want to search for the matching power bricks - I just want to plug it into one of the 4 USB-C PD sockets I have installed into my desk.

Here in Europe the 4 months she was at would be somewhere mid to end of the trial period, during which you can be let go without having to provide a reason on relatively short notice. This is also pretty much the only chance you get to easily let go a specific individual - so if there are indications it'll not work out doing just that is a good idea.

But having that done by arbitrary HR drones is just crazy, and obviously you'll be entitled to unemployment benefits or other social benefits after that.

A major difference is how they interact with feedback - the main reason I never did my own mastodon instance is the developers attitude. "We're not interested in helping you because you didn't set it up exactly as in the guide" was (and maybe still is) all over the mastodon bug tracker.

That was the first thing I looked for when lemmy became popular - and found they were taking deployment issues to even the most absurd system seriously.

Additionally they treat suggestions seriously - even if they personally think it is stupid - and even implement some of that. Pretty much no chance of anything of that happening with mastodon.

Thanks to more and more languages supporting full unicode for symbols this will eventually be a thing of the past, fortunately: we can just switch to functions and variables being named only with one or more descriptive emojis.

It generally doesn't have a high opinion of translators (note that the emojis here are inserted as path markers to help with prompt debugging - but everyting else is from the LLM):

I wasn't quite sure what to think about this, so I've asked my local LLM. Seems it is fine.