And that compatibility still is important today. For one thing, APIs can be written in C (starting with the POSIX API) and be used by programs written in either C or C++ or in language X, or language Y, or language Z.
FTFY. This is due to calling conventions, not due to a 'language compatibility'
Here's an idea: if you don't know shit about C++, don't post shit about C++?
Here's an idea: If you don't know shit about the basics of programming, don't post, like, at all. Especially avoid calling others idiots when you're at the same time making clear you're even less competent.
I like how they call the bash vulnerabilities``Linux shell vulnerabilities''. Like that was somehow Linux' fault, or any other shell was affected. 0/10 wouldn't read again.
Disclaimer: I run a BSD and my bash sure as hell was affected.
Its detractors rarely comment on technical merits/shortcomings, 99% of the time they only throw "pid1", "monolitic", "poettering blight", "binary logs" and "they took our jerbs^wkludgy init scripts!" around.
So..in your world, pid1 bloat, monolithic design, binary logs and getting rid of simplicity/flexibility achieved by shell scripts are/not/ technical shortcomings. Aha. Face.. meet palm.
You're talking about the most outer frill of the most outer presentation layer of the most outer shell...
Which, because the basic stuff is done so badly, is a nightmare to implement.
You're either trolling or absolutely clueless to a degree which isn't even funny anymore. To stick with the example of how the timezone is set, it's a file. It's called/etc/timezone. It contains a string like ``Europe/Berlin''. That's it. It can't quite get any simpler.
The rest of your comment is equally dumb:
I suppose real users do their 3D modelling or photo editing on the command line rather than using Fisher-Price graphical utilities.
Here's some rare insight: For inherently graphical tasks, a GUI is appropriate. News at 11.
Slashdot Mirror
And that compatibility still is important today. For one thing, APIs can be written in C (starting with the POSIX API) and be used by programs written in either C or C++ or in language X, or language Y, or language Z.
FTFY. This is due to calling conventions, not due to a 'language compatibility'
Here's an idea: if you don't know shit about C++, don't post shit about C++?
Here's an idea: If you don't know shit about the basics of programming, don't post, like, at all. Especially avoid calling others idiots when you're at the same time making clear you're even less competent.
...which hasn't been the case in a long time.
/* correct C, incorrect C++ */ /* correct C, incorrect C++ */
Pulling two examples out of my ass:
int *foo = malloc(sizeof *foo);
and
int bar(void);
C++ and C are two different, incompatible languages.
until the Systemd fiasco blows over.
Not going to happen.
If only there were sane and well-designed OS the developers of which actually think about the consequences of what they're doing.
Oh, wait. there are.
tely agree
You need Adblock Plus?
Seriously dude, try this and this and this
I like how they call the bash vulnerabilities``Linux shell vulnerabilities''. Like that was somehow Linux' fault, or any other shell was affected.
0/10 wouldn't read again.
Disclaimer: I run a BSD and my bash sure as hell was affected.
Its detractors rarely comment on technical merits/shortcomings, 99% of the time they only throw "pid1", "monolitic", "poettering blight", "binary logs" and "they took our jerbs^wkludgy init scripts!" around.
So..in your world, pid1 bloat, monolithic design, binary logs and getting rid of simplicity/flexibility achieved by shell scripts are /not/ technical shortcomings. Aha.
Face.. meet palm.
For anyone truly looking for a secure, minimal and clean *nix system as a replacement for Slackware, I can't recommend NetBSD enough.
Seconded that from my NetBSD machine.
You're talking about the most outer frill of the most outer presentation layer of the most outer shell...
Which, because the basic stuff is done so badly, is a nightmare to implement.
You're either trolling or absolutely clueless to a degree which isn't even funny anymore. /etc/timezone. It contains a string like ``Europe/Berlin''. That's it. It can't quite get any simpler.
To stick with the example of how the timezone is set, it's a file. It's called
The rest of your comment is equally dumb:
I suppose real users do their 3D modelling or photo editing on the command line rather than using Fisher-Price graphical utilities.
Here's some rare insight: For inherently graphical tasks, a GUI is appropriate. News at 11.
No, is monolithic Note the part where he repeatedly gibbers about that stuff is impossible to separate.
Leave room for a sleeping bag
And place earplugs somewhere around that spot.
If we could get our homes switched to DC, then we could have these without the extra electronics in them.
Nah. You'd still need a constant-current source, LEDs aren't Ohmic.
Eh, except that 2035 is 20 years away. Nice try, though.
provide everyone with a circa-2010 American standard of living
You can't be serious. This isn't desirable at all.
Love from Europe
It's the right attitude even when there are other options.
Yes.
Am I the only one who thought this was about a software vulnerability? Warping. War-Ping. Ping of Death style.
I want my good old times back.
Now get off my lawn.
the hell is initd?
s/now/nor/
I was talking about a trivial pipeline involving ps, xargs and kill, mainly. Which is neither systemd now sysvinit specific
Ehm. Yes?
Wait for jessie
Like that wasn't trivial to achieve already with the existing tools.
Doesn't matter, as long as it's SomeThingCamelCased. /me pukes
This being modded +5 Insightful is truly pathetic.