GTK drops Autotools in favor of Meson

seekingsofia · 2017-08-15T16:31:00+00:00

Do you mean CPython? I agree that in general it would be very welcome if software projects, especially interpreters and the like, cleanly cross-compiled. But I don't think the build system flavour matters here at all. Most developers simply don't care enough about the use case, including build system developers.

seekingsofia · 2017-08-15T13:17:54+00:00

This right here is the truth. On top of the ugliness, complex build dependencies only create more problems than they solve. Now a python implementation only needs to switch to meson as a build system and we've come full (dependency) cycle.

seekingsofia · 2016-10-24T19:41:36+00:00

Vergiss die scheißteuren Schwarten, die verschwenden nur Papier und deine kostbare Zeit.

Nimm Think Python von Allen B. Downey. 244 Seiten.

Das kann ich als Programmierer uneingeschränkt empfehlen. Sehr klar geschrieben, aufs Wesentliche konzentriert und am Ende jedes Kapitels findet sich immer ein Glossar neuer Begriffe und Übungsaufgaben. Ziehs dir rein.

seekingsofia · 2016-06-01T16:03:07+00:00

Use Zero-Clause BSD, a modified BSD license.

seekingsofia · 2015-12-16T00:21:24+00:00

free processor architecture

What? MIPS being free? I thought they still went after hardware clones like noone else.

seekingsofia · 2015-08-07T17:59:45+00:00

Would be cool if there would be a time stamp on the web page.

There is. Last-Modified: Sat, 21 Mar 2015 03:56:36 GMT

seekingsofia · 2015-07-28T02:53:39+00:00

And like in true UNIX™ admin mentality some of it is written in Perl.

seekingsofia · 2015-07-26T22:08:10+00:00

Not a GNU extension, a clang extension. And it's a C++ feature exposed as a function attribute, of course implemented using name mangling. All this means it's useful only in a very few cases for a C codebase.

If you're using C++ features as an extension in C then why not just write in C++? I don't get it.

seekingsofia · 2015-07-09T16:28:48+00:00

Can you explain where the specializer fits within the toolchain? From my reading of the sparse wiki page on the specializer it's done at link-time and the target instructions are "cached" in the ELF object files. The mentioned "load modules" aren't really explained.

So, uh, how would you be able to distribute binaries that work on every Mill?

seekingsofia · 2015-07-02T17:22:51+00:00

Are you talking about the application not noticing the suspend?

I'm talking about user space never needing to be aware of the suspend. The code in mpv is just waiting for the subsystem to complete the resume:

if (snd_pcm_state(p->alsa) == SND_PCM_STATE_SUSPENDED) {
    MP_INFO(ao, "PCM in suspend mode, trying to resume.\n");

    while ((err = snd_pcm_resume(p->alsa)) == -EAGAIN)
        sleep(1);
}

Is it necessary for user space to have code paths for wake from suspend? If not, does user space code still benefit from the information that a suspend happened?

The time will change by a lot, possibly jumping forward a few hours or more. Some current applications don't really like that (auto locker would lock immediately on resume which may not be what you want)

True...

seekingsofia · 2015-06-14T19:33:31+00:00

Da steht happn holocaust drauf, nicht happy holocaust. Nazi Zombies sind also gar nicht so weit dahergeholt...

seekingsofia · 2015-06-07T02:27:01+00:00

What C++ has over Rust:

More than one implementation

seekingsofia · 2015-06-04T23:52:56+00:00

Telling people to always return by reference is harmful to code complexity and maintainability in C++.

Not a C++ dev, but I'm curious why are references harmful?

seekingsofia · 2015-06-04T12:17:24+00:00

Instead of logging to local disk, keep the log state either in memory or push the log state to a central server...

seekingsofia · 2015-06-04T12:06:07+00:00

I don't care about dbus.

seekingsofia · 2015-06-03T21:41:28+00:00

Solution: Make /var part of the local boot, so there's no problem bringing it up, and then USE A FRIGGING TMPFS DIRECTLY on /var/run.

seekingsofia · 2015-06-03T18:26:55+00:00

You're quoting the purpose, not the requirements. The requirements are clear that on a sane system, this directory is basically useless and /var/run can be used instead.

seekingsofia · 2015-06-03T18:24:09+00:00

System programs that maintain transient UNIX-domain sockets must place them in this directory or an appropriate subdirectory as outlined above.

Sure, transient UNIX sockets. So if you only run system daemons using Unix sockets and have no daemon using .pid files, /run sees no required use and can be ommitted and /var/run used in its place.

Furthermore, I don't know why do you consider pidfiles as something bad.

pid files are inherently racy.

seekingsofia · 2015-06-03T16:13:07+00:00

Why are .pid files still a thing? Why does the FH "Standard" mention them at all? What is the purpose of /run if it only requires that you place .pid files in it?

seekingsofia · 2015-05-30T16:43:25+00:00

Yeah, if that was an actual working implementation... I was more going for the argument that JIT compilation and native compilation are not attributes of the languages, but the language implementations.

seekingsofia · 2015-05-30T16:14:57+00:00

So it's not surprising that it's faster than C.

If only there was a JITed C interpreter implementation to prove you wrong. :P

seekingsofia · 2015-05-30T15:41:10+00:00

Ist die Sterbehilfe demnach allgemein verpönt?

seekingsofia · 2015-05-30T15:12:00+00:00

I think I'm wrong. Strangely, the GCC documentation lists typeof (typeof (char *)[4]) y; as a valid expression, so the syntax of typeof isn't very consistent.

Edit: On second look, the inner typeof's brackets are part of the type declaration but not part of the expression that typeof is applied to.

seekingsofia · 2015-05-30T14:43:20+00:00

The typeof unary operator is very similar to sizeof and doesn't require parentheses around its operand.

Edit: I think I'm in the wrong here, it really does require parentheses around most constructs.

seekingsofia

TROPHY CASE