You need to only deposit 12,500 € in the bank account of the GmbH you want to create as capital (Stammkapital). The founder (Gesellschafter) have then an obligation to pay the GmbH the other 12,500 € at a later date. The CEO (Geschäftsführer) can request that the Gesellschafter pay the rest of the capital.
The CEO can use the capital to establish the business. It can be used to pay wages, buy hardware etc.
Of course there are obligations for the CEO to not let the GmbH go bancrupt.
> Maybe you may also want your tool to serve your workflows and not the opposite.
This sounds like you claim that pijul serves all workflows well, which would contradict my own experience. I'm so used to think in branches / PRs (to display a history and showing lineages), that I find the current way of handling channels/patches of pijul alien. Right now I would need to break my workflow in my daily operation to use pijul.
Isn't your comment then very specifiy for that installation of yours? When you use MS Teams in a "normal" O365 environment, then every feature you described for IRC is possible with weebhooks and the cards API. Simple CURL based integration.
Only if you define "undefined behavior" as in a very constraint sense (as in "the language specification doesn't specify the behavior").
But CPU architectures also have undefined behavior. ARM for example calls these "UNPREDICTABLE" and "CONSTRAINED UNPREDICTABLE". Have a at the Armv8 architecture reference and grep for those. Lot's of ways to write programs in pure assembly with undefined behavior too!
x86, 6502 and Z80 etc all have undefined / unpredictable behavior too.
6502 is extra fun, because it has "unstable" instructions, whose result would be dependent on specific chip, temperature, and other factors. I can't find the article that dissected some of them anymore, but as I recall it was because of stuff like an (internal) bus conflict with multiple drivers enabled (EDIT: close, but it's even wilder than that).
There is a writeup in PDF here
https://csdb.dk/release/?id=198357
about what actually happens on all the unimplemented instructions that still "run" parts of the CPU, some with decent results, and some with less.
And for the last part of your sentence, it depends on what address you run some of the instructions from, since they take a byte out of that in account when doing the weird operations, so some bad instructions can be used, if you are running from $fe00 - $feff because it takes the high byte ($fe), adds one to it, then ands something else with it and lastly produces a result that leads to a usable instruction, but only if the and is with $FF so it doesn't drop bits on you. =)
Thanks, but I meant something even more unpredictable, which is hinted at in your document: "ANE [...] is chip- and/or temperature dependent" and "can not be reproduced in visual6502, which hints on it being some analogue side effect that the simulation does not cover".
It's a shame that I cannot find the other article, because I remember that the author actually had looked at the individual transistors, and figured out the bus conflict or whatever it was, which pretty exactly described what happened, and maybe even why some bits would be more "weak" than others.
EDIT: Oh, hah! Your PDF actually links to it in the same section. The wiki seems currently down, but here's an archive.org link of the page that describes the unstable opcode in great detail. So thanks a lot! https://web.archive.org/web/20210405071521/http://visual6502...
Yeah, 96kHz/24bit is only really useful for production, since it makes it more foolproof and harder to mess up your recording.
But storing music over 48kHz and 16bit for comsumption is really just waste of storage space and pure snake oil. 16 bit give a dynamic range of 96dB and I'm not aware of any recording outside of experiments that take advantage of it. Even the most expensive speaker / headphones will distort terribly if you play them on the loudness level where this dynamic range would matter...
And most "high quality" recordings with a high frequency range (96kHz+) only really add ultrasonic sound and mostly noise artefacts that don't correlate to the music recorded (and that no speaker / headphones can even reasonably, without high distortions, reproduce, if they even pass the LPF of the reproduction chain).
So yeah, I also think that 48/16 is all we need for optimal consumption. If the format is lossless, it's also nice for archival reasons.
I think your retrospective is very Dattebayo centric and distorted.
Most big fansubbing groups hated CR back in the days when CR started, since CR took their fansunbs to fuel their business.
Once CR started to make/pay for their own translations (also hiring translators from some groups in the background) the situation got better, since then a clear, legal path was visible for the community.
I don't know anything about any of these groups (I do like anime), but they had to know from the beginning that voluntary subtitling would never make any money. Even if copyright law were intended to help regular people rather than giant corporations, their work was entirely based on material they had questionable "right" to use in the first place. They scratched their own itch, and later CR had an itch too. It could be that Dattebayo always had a more complete understanding of the situation than other fansub groups had.
> but they had to know from the beginning that voluntary subtitling would never make any money.
Exactly zero of the fansubbing groups ever did it to make money. For most people, they were in it for the community, which included things like the prestige of having your name associated with a popular/successful project. The reason the fansub community was upset at CrunchyRoll was because not only did they take the content, they edited it to remove the intros and other forms of attribution to the original fansubbers.
If they had left in attribution, nobody would have cared, and CrunchyRoll would have been treated like any number of other torrent to streaming sites that existed.
> Most big fansubbing groups hated CR back in the days when CR started, since CR took their fansunbs to fuel their business.
I mean, Dattebayo definitely criticized CR at first. But by the time Dattebayo closed shop, they were highly supportive of CR. That's why its important to remember the names of these groups. Do you remember the large-fansub group and/or which anime you're talking about?
Its hard for me to think of a bigger group than Dattebayo back then. Dattebayo covered Naruto and Bleach subs, as well as a bunch of lesser known anime.
Funny that I'm nobody again. I work for a big german retailer. A big part of my work includes simplifying and refactoring code, so that we have lower maintenance cost and can move faster as a organisation unit. This was also a big factor in my last promotion.
We also increased profit by lowering our runtime cost by some of those optimizations.
If I were a betting man, I would bet that the main reason why you're allowed to do that is because you lowered runtime costs by some of those optimizations, not because of the cleaner code you can move faster.
? not parent, but I am really surprised by that mindset.
A large part of my career has been telling my boss "we should invest 5h of cleanup time here to make sure that in the future we won't have those 5h worth of obstacles here before building a new feature on top of it".
In industries where requirements change on a weekly or monthly basis, agility is worth a lot.
I completely agree. My bet would be the bosses usually don't. So in a lot of places you need another "excuse" (or as another poster mentioned, spend the time saved to invest more into maintainability but cover it up).
Thanks! That's what I seem to be seeing elsewhere now too, although the main site is now down (for me), so I haven't been able to confirm as much as I'd like.
The CEO can use the capital to establish the business. It can be used to pay wages, buy hardware etc.
Of course there are obligations for the CEO to not let the GmbH go bancrupt.