The German rail system has also been detoriating in the last decades due to lack of investment of the Deutsche Bahn after being privatized. You don't see it on the main lines, but you see it on the lesser used ones.
750 karma · joined May 28, 2015
The German rail system has also been detoriating in the last decades due to lack of investment of the Deutsche Bahn after being privatized. You don't see it on the main lines, but you see it on the lesser used ones.
Good luck with that.
On most hardware I buy, I can read "compatible with Mac and Windows" on the package, but nobody seems to bother if it's compatible with Linux or not ...
One solution is to distinguish between a "datetime" and a "duration". You cannot convert a duration to days (or really anything). You can add or subtract a duration from a datetime, and you can convert the difference between two concrete datetimes into days.
And that's actually how some libraries already implement it.
So the answer to "how long is a month" is "it depends, and I can only say if you apply this duration to a concrete time".
Systemd has lots of good ideas, and is now mature enough in most places. Unfortunately, the authors of systemd have the tendency to replace virtually everything in Linux with their own version, designed for their own purpose, without listening to how other people use those things.
And you can't really disentangle parts of systemd just using a distro.
So system administrators not using Linux for a desktop got tired of constantly fighting the breaking things, and just threw it out completely.
If systemd only was an init system, and had stayed out of the rest (syslog, DNS, network management, directory layout, you name it), and would just have done the init system job really well, it wouldn't really be controversial. But with the "you need to do it my way, I don't give a shit for your use case is, and I don't give a shit if I break your system" attitude shoving it down the throat of everyone, they didn't really make friends with many people who run more complicated systems.
Then it might be interesting for you that Rust copied this (like a few other things) from Haskell, where they are (somewhat confusingly) called type classes.
The content doesn't matter, it knows who you communicate with and how often, and that's already a privacy concern (wife wants to know if husband cheats on her with someone else? and so on).
But of course the WhatsApp CEO doesn't mention this ... much easier to say "we don't look at your content" to give it the spin they need.
I would be happy if I got to replace the battery, and the SSD. You know, those two parts with a limited lifespan right from the start...
Instead, guess what is soldered to the mainboard in newer Macbooks? Yes, those two.
Nah. Technically, and in terms of manufacturing cost, it would be even easier to make a simpler computer, without all those bells and whistles that can be turned against the user, without the Intel Management Engine, TPM, and what have you.
> That's the type of stuff they sacrificed to make it cheap.
No, it's economies of scale which make one expensive, and the other one cheap. And human greed, and the human need to control other humans.
Still, I visit websites all the time that don't work with Javascript disabled. They don't work at all, or the images don't load, or the formatting breaks down.
None of this is necessary. In principle, static content should work fine with Javascript disabled.
This keeps beeing peddled by the pro-nuclear fraction, but you are comparing apples and oranges: the "large number of people die" is based on "if you burn coal without any filters, in particular if you do it in a little hut in a third world country with no proper chimney, it's really really bad for your health".
Nuclear power plants require modern technology for high safety standards. Coal power plants on anything than a very basic technology level all have filters that scrub the sulphur etc. Outside of third world countries, nobody dies from coal. It's not even a health problem.
The problem with coal and other fossil fuels is that they use up limited resources, and they put back the CO2 into the atmosphere that has been extracted by plans over millions of years, causing global warming.
The problem with nuclear is that when it goes boom (and it has done so about once every 20 years since we have nuclear), it leaves a large area inhabitable for a long time. Which is a big problem in a densely populated country like mine. Also, at least in my country, even though we are using nuclear for about 60 years now, nobody has figured out a safe way to store the nuclear waste - it just gets moved around from one failed attempt to the next.
The "lots of people die from coal" vs. "nobody dies from nuclear" story (which are both distortions, conveniently in different directions to match the ideology of those bringing it up) is a red herring.
But it's a distraction gladly used by those who want to promote more copyright restrictions - everyone learns as a small child "what's yours is not what's mine", and everyone learns that theft is bad.
So calling piracy theft means everyone has the gut reaction that it's bad.
Calling piracy an infringement of a monopoly has a very different flavour to it.
Copyright monopolies do serve a purpose. But one shouldn't try to distract from this purpose by calling piracy theft.
Before "copying" music or books was cheap, the situation was quite different (tunes and books were copied left and right, nobody cared, but you had to pay the musicians to perform a tune, and the scribes to copy a book), but theft still existed, and was punished.
Navigation, ads, etc., maybe, but not the contents itself. Most webpages could be perfectly useful with Javascript completely disabled.
Sadly, many aren't.
You can make music together at this distance (even though it's perceptible).
I always find it funny that people think of Usenet "mainly for file distribution" (though that happened), when I used it exclusively for discussion... long before the News servers had the capacity to deal with all those alt.binaries.* groups.
Containers use Linux namespaces to decouple from the main OS. MacOS doesn't support those, so no matter what you do, you can't run them directly on MacOS. That's why you need a VM, and you need the WSL Windows subsystem for Linux on Windows.
BSD has jails, but they don't have the same functionality. In particular, I sorely miss the network namespace that Linux has on MacOS.
Pure speculation, but for example if they did design a process to enrich their pasta with iron, tested it initially, but then never tested it again (who cares if there's iron in pasta...), and then it stopped working for some reason (or possibly never worked reliably in the first place). And then instead of trying to find out what made this process not work, they just came up with a new process that did work.
As I said, it's speculation.
Another option is of course "I perfectly know, but I cannot tell you, because if I did, we'd be in legal trouble".
It was pretty invasive - I tried to keep using Debian without systemd, but indirect dependencies always brought it in. Until I switched to Devuan.
And the dependencies brought in EVERYTHING. You could no longer mix and match, pick one part from here if it worked for you, and another part from there.
Which lead to the criticism that "systemd is not modular". Which Poettering denied, pointing out that there are modules at systemd-compile time, completely missing the point.
> So, more or less, people resent systemd because it's difficult to find - or build - a distro without it.
And I wouldn't have minded systemd as an INIT SYSTEM - the existing scripts WERE pretty bad. But systemd is like the Borg - it tries to assimilate everything. And it broke quite a bit of existing functionaility along this path.
So it's NOT a runtime error, it's a compile-time error, even though you can assign different functions at runtime.
Prelude> :m Data.List
Prelude Data.List> let f xs = [(head ys, length ys) | ys <- group xs]
Prelude Data.List> f "aaaabbbcca"
[('a',4),('b',3),('c',2),('a',1)]
Of course using the "group" function instead of programming it myself is cheating a bit ...There's an obvious translation from the ladder logic to a MC14500B program, so it's easy to replace those devices with a simpler MC14500B device.
I even think I've seen ladder logic mentioned in some of the MC14005B documentation (but it's been some time since I looked at that).
The result is inferior most of the time.
[1] https://en.wikipedia.org/wiki/City_of_Angels_%28film%29
[2] https://en.wikipedia.org/wiki/Wings_of_Desire
[3] https://en.wikipedia.org/wiki/Vanilla_Sky
[4] https://en.wikipedia.org/wiki/Open_Your_Eyes_%281997_film%29
It's not. The majority is just textual content I want to read. Possibly with a few images.
I don't need Javascript for that. And being forced to use Javascript for it is the exact problem.
For the minority (something clever that requires user interaction beyond reading text and looking at pictures, this "non-standarized", maybe even "proprietary" stuff) Javascript is just fine.
But don't force me to use Javascript for the rest.
The problem is not "people could use that particular Java feature to make code cleaner, but they don't".
The problem is on a higher-level: If you have ever tried to read your way through some library, e.g. Spring, you'll see code spread over hundreds of files, and it takes ages to just find out where that particular bit of code you need is, because it's automatically injected in some builder class which is an inner object extending some other object that implements an interface somewhere.
And then you have several competing abstractions, and sometimes one gets used, and sometimes the other.
IDEs and type hierarchies help, but only to some degree.
And then you are still stuck with an overengineered abstraction that nevertheless does not allow you to do the obvious thing that needs to be done in your particular case. So you need to implement a fragile workaround, for example copying one of the library classes, modifying it a bit, and then injecting it instead of the one from the framework. All of which will horribly break if someone changes something in the library.
"Style" is never the problem.
state what you are doing = what happens automatically if you sit in the same office with other programmers: you know what they are working on, you know if they are stuck with something because they usually just ask aloud, etc.
And given that basically all bigger German companies have a works council [1], this is really really likely to happen.
- newly created account (or, in the more sophisticated variants, an account created some time ago with a few meaningless postings) - ask for help, or ask a question to distract from the actual goal - somewhere in the text, throw in some association that should stick (like "refugees steal", or "refugees sexually assault woman", as a fact that doesn't need discussion) - when confronted, the only answers were contentless excuses, like "but I am really asking this for my mother, who can't use a computer". Never any attempt to engage in actual discussion.
The reaction to these is that people usually address the question, don't address the baseless association, which probably then starts to stick in the unconsciousness of at least some of them.
And on the political side, at the same time there was an increase in support for extremist and nationalist, anti-foreigner parties.
Though of course how much such messages contribute to that is difficult to say.