HN user

jle17

286 karma
Posts0
Comments92
View on HN
No posts found.

The Mario franchise has two distinct logo styles. The first began with the Mario Bros. arcade game and is mostly used for side-scrolling Super Mario Bros. games, though not all of those games use that style. The second is a multicolor polygonal style, and though it’s primarily used for 3D Mario adventures now, it was introduced with Super Mario World.

I believe the polygonal logo style was first used by super mario bros. 3 (at least for the shape, it didn't have the alternating colors yet as it was all blue). It isn't on the nes boxes but it is on the title screen and on the famicom box.

It's also important to consider how what you view as a bug might not be one from the point of view of the person treating your issue. It is so, so infuriating to receive a "bug" report asking you to "fix" something that is in fact a feature request for something that is not implemented yet.

Even if you get an error from the software, consider that you might not be using it as intended or setup properly.

There is definitely a tendency to authoritarianism and confusionism from the current government, directed at political opposition.

"Security" laws extending the powers of the police and creating new ways to criminalize protest have been passed at a constant rhythm over the years since Sarkozy's time. After the state of urgency of 2015, part of the dispositions where simply put into law permanently.

Police has been increasingly violent during protests, bringing back old forbidden tactics and squads formerly dissolved for their violence (voltigeurs).

While there has been no dissolution of leftist movement and no political violence from the left since "action directe" in the 80's, there have been multiple ones (or attempts) in recent times, like the one from yesterday of an ecological movement.

Anti-terrorist laws are used to detain ecologists or protesters indefinitely, like in the case of the "8th november" affair from this topic, which has seen a person kept in solitary (hence, tortured) for 16 months without even being convicted.

System D 3 years ago

There is a "Système D" DIY magazine here in France, since 1924. I don't know if it is predated by the term or originated it. I remember that there is a big pile of old issues in my grandfather attic.

Towards 2014 or 2015 my previous work (some hosting company) had some AIX, Solaris and SCO, as well as some IBM i (aka OS 400) which isn't a Unix. AFAIK they were used because of choices of slow-moving/risk-averse big corps, mostly to run some java software or oracle/postgres/sybase databases that could just as well run on Linux.

My take on each of the OSes was:

AIX and the associated IBM stuff is kind of a mess. I encountered a bug where /etc/filesystems (fstab equivalent) was parsed differently during boot than when using the mount command manually. The focus seemed to be on the use of the menu-driven smit utility as the primary admin tool, with automation of admin tasks an afterthought. The builtin commands are often not very practical, requiring multiple steps to do things that you're used to do in one on Linux. Installing some open-source tools is essential to sanity. Some of IBM's own tools are using expect on their own software (looking at you lpar_netboot).

SCO is clearly unmaintained stuff that looks like it dates from 30 years ago. At least it's simple to use.

Solaris had some nice features, like Zones or ZFS, but much to my dismay I couldn't play with them as I was made to install an old version of the OS as the newer version wasn't listed as supported by the version of Sybase that was to be installed on it.

The tight coupling, the non-portability, all of that are technical choices, that can be debated on their own merit without the need to attribute malevolent intentions to the developers.

Projects merged changes because they wanted them, not because their goodwill was abused to make them merge anything. People got systemd on their OSes because they chose OSes whose developers chose to move to systemd.

It's not like Lennart comes to your home with a gun if you install OpenBSD.

I don't trust Poetteringware. Poettering's team has a record of foisting technology on users, resulting in the need for e.g. the Devuan fork.

They have been developing software, that enough people have deemed useful to include it in their distributions. Some have disagreed, and have made other choices. No one was forced to do anything, there have been no "foisting" and the "need" for Devuan is a subjective opinion.

There is really no need to transform purely technical arguments into personal attacks. This just discourages participating into free software development.

Think e.g. one of Loki games like SimCity. The audio will not work (and this will be a kernel ABI problem...). The graphics will not work. There will be no desktop integration whatsoever.

I have it running on an up to date system. There is definitely an issue that it's a pain to get working, especially for people not familiar with the cli or ldd and such, as it wants a few things that are not here by default. But once you get it the few libs it needs and ossp to emulate the missing oss in the kernel, there is no issue with gameplay, graphics or audio aside from the intro video that doesn't run.

So I guess the issue is that the compatibility is not user friendly ? Not sure how that should be fixed though. Even if Loki had shipped all the needed lib with the program, it would still be an issue not to have sound due to distro making the choice of not building oss anymore.

Maybe we should eliminate the Desktop folder completely

Seconded. I'm irrationally annoyed that it gets created and sometimes filled with .desktop files while my DE doesn't even use it.

At the very least, we should get rid of the "Templates" folder. I still have no idea wtf that's meant to be used for.

You can place files in the "Templates" dir to serve as templates for the "right-click > new document" feature in nautilus and some other file explorers.

According to the jargon file, ITS called daemons dragons and SAIL (whatever this is ?) called them phantoms. Add to that zombie processes on Unix and user rights angels from FreeBSD's capsicum and the fact that processes come from executable files in ELF format and have debug infos in DWARF and it is quite the fantasy menagerie.

I suggest Kobold for whatever kind of process we need to name next.

Yeah kinda, but at least it's not every applications doing their own thing, it's the thing that runs applications, so assuming you only run sandboxed flatpak stuff, you end up with only one thing.

I kinda like that flatpak forces application created files to end up in a predictable place. Firefox, like plenty of applications, was doing its own thing despite XDG conventions (~/.config etc and associated env vars) being 20 or so years old, now everything is in ~/.var/app, plus flatpak knows if it belongs to an installed application or not.

Although I would have preferred if the hierarchy was reversed, so instead of having ~/.var/app/<app>/{cache,config,data} for each application, I could have all files of a category in the same place as to be able to manage them more easilly (say remove all the cache, version all the config), like it is now for the applications that respect XDG dirs.

Just looked into this and I think it's worth mentioning that there are two different projects called `yq`. The first one that came up (written in go instead of python) is not the right one and doesn't have the `xq` tool.

I never had a Tamagotchi, but I can understand how the loss of a digital pet could have been quite traumatic.

As a kid I cried when it "died". Taking care of the thing for days, seeing it grow, caring for him when sick, it sure created some attachment even though I knew it was virtual.

And because I couldn't bring it at school, parents had to take care of it sometimes, with the pressure of knowing I would badly react if it didn't receive proper care and died (or became sick).

Not sure this is positive, it could certainly have done without this feature. At least my parents didn't thought that me crying over a piece of electronics was very healthy.

It mostly work though, although it might not be legal, most companies will drop your subscription after some time if you stop paying. You might receive some letters from collection agencies, but as long as the sums in question are an order of magnitude lower than what is worth bringing in front of tribunal, they will stop after some time.

To do that on Windows or Linux (I use Mint in my PC) I think I'll have to print the Image as a PDF and then use some other software to "stitch" the two files together.

Actually the process on Linux is similar. On the PDF file, Right-click > Open with LibreOffice (which I believe is installed by default on Mint), then just drag the image onto it. You don't even have to open it, you can just drag the file. On KDE you can even drag it directly from the screenshot software window to the PDF.

It used to be KDE's file manager and web browser all in one app.

It goes further than that. It's pretty much everything in one app. KIOs accesses stuff and KParts shows it. Since many applications expose their functionality using those, it can show whatever content they support and browse it as a filesystem when it's possible.

Web browsing is just KIO doing http and a KPart showing the page. File management is just the file (or smb or sftp or whatever) KIO and the Dolphin KPart. The Kate KPart is used in both cases to either view local text files or web pages source.

But there are others and you can do any combination, including some cool ones.

You can go to man:// or info:// to view man/info pages.

The Akonadi KIO from the PIM suite can be used to browse remote mail or calendar accounts and extract data.

It even used to be possible to use magnet links in HTML (like in <video src="magnet:...">) with kio-magnet or to browse mysql databases and use applications to edit content in cells with libferris, although I don't think those are currently maintained.

Yes when reading the title I thought of <pwd.h> for reading passwd rather than of the command/variable. Also it's already called cwd in other places (like in /proc, at least on Linux) so that would be more consistent.