From what I can see about similar movements in my country is that these people have a right-wing view on issues as identity and immigration, but mostly a left-wing view on economic policies.
At least to Reddit's credit the possibility of downvoting eliminates the most obvious cases of trolling and flaming.
Most posts are downvoted simply because they present a different opinion, reinforcing the echo chamber.
I like to learn things, and have my opinions challenged in a constructive way. Reddit sucks for that. I can either pick a group of people who completely agree, or a group that disagrees. Both cases are rather pointless.
> Well, you sure as heck don't want to use something like R for that, the class would be too easy
You say that like it's a bad thing. If people solving real life problems use 'R', then it should also be used in the classroom. If that makes the class easy, then give them more advanced problems.
Looking at some other tasks state involves two context switches - to that other task and back to the current.
Looking at another task's state means making a copy of the state, a snapshot if you will. As soon as you make a copy, you now have two versions. Right after you make a copy, before the 2nd task can even examine it, the original state can change again.
To be efficient on a large server, it obviously has to support many parallel threads of execution - but should still be a single memory context
Yes, that's very efficient. That's what a monolithic kernel does.
Of course I do. The key feature of a microkernel is that it uses different access spaces. with protection barriers between them. In contrast, a monolithic kernel has shared access spaces, so different tasks can modify the same data and keep common state synchronized.
After all these years, there has been ample opportunity to optimize microprocessor design to make a better microkernel CPU. There is generally just too much cost involved in the constant context swaps for a desktop OS
The reason that microkernels suck has nothing to do with context swap inefficiencies. The biggest problem is trying to maintain a synchronised state between the different tasks across different memory protection areas.
A simple example is a file system. Imagine a dozen different tasks, all working on the same file system, As soon as one task makes a change (say, delete a file), all other tasks are working with an outdated snapshot of the file system state. Unless notified of the change, this will lead to corruption. And notifying all tasks of every little change would be hugely inefficient, not just because of all the overhead of sending the messages, but also because tasks would need to be made with frequent check points. In the end, it would do nothing to simplify the overall system, because you'd basically be implementing a virtual shared memory, and you'd have to deal with exactly the same issues as with a real shared memory.
The tradition solution in microkernels is to have a single task running the file system. This may be a practical idea on some small scale single user systems, but it's totally unacceptable on a larger server, say a big web server with a few hundred simultaneous connections.
When I was a kid, I had both lego bricks as well as Fischer technic. I wouldn't call any of them superior. They both stimulate your brain, in different ways.
It isn't about being as good or better than humans, it is just because of the serious consequences that occur when a 4500 pound machine makes a mistake in traffic.
The consequences are not less serious when a human makes a mistake driving that 4500 pound machine.
A robot could also measure objects (lamp posts, buildings, signs, etc) on the side of the road, and use a detailed map to figure out exactly where it is. That way you could drive even if you're the first on a completely snow covered road.
The beauty of robot cars is they are always entirely predictable. The outcome may not have been what you intended, but computers only ever do exactly, to the letter, what they are instructed to do.,
With self-learning networks, nobody knows exactly what the computer is instructed to do. And we certainly cannot predict what they'll do when they get live inputs instead of training data.
Why settle for 6 when you can have 8 with only minor disadvantages ? There's a huge amount of trade going between The Netherlands and Germany. Not just trade between the two countries, but also goods transported through them. Having 33% more overlap in business hours is huge.
The US is too big for just one timezone. Ireland is not. Surely, it's possible to make things work across timezones, but it's much easier if you don't have to.
Slashdot Mirror
They called it "Unite the Right".
From what I can see about similar movements in my country is that these people have a right-wing view on issues as identity and immigration, but mostly a left-wing view on economic policies.
I have a casio from around the same time that's still running on its original solar cell.
At least to Reddit's credit the possibility of downvoting eliminates the most obvious cases of trolling and flaming.
Most posts are downvoted simply because they present a different opinion, reinforcing the echo chamber.
I like to learn things, and have my opinions challenged in a constructive way. Reddit sucks for that. I can either pick a group of people who completely agree, or a group that disagrees. Both cases are rather pointless.
Fuck it all, we're doing 18" screen in a 5" chassis. And we'll have a second aloe strip that lathers.
> Well, you sure as heck don't want to use something like R for that, the class would be too easy
You say that like it's a bad thing. If people solving real life problems use 'R', then it should also be used in the classroom. If that makes the class easy, then give them more advanced problems.
How can we fix the broken economics of free developments in mathematics ?
Renounce citizenship
If you can afford the $2350 per person.
If we can prevent an atrocity, shouldn't we?
And who will we put in charge to decide what things are atrocities ?
the majority of people would choose not to aid NAZI Germany.
While not getting an absolute majority, they were the biggest party in the 1933 elections, with over 40% of the votes.
Common sense therefore dictates that the ICE needs to do their job.
Looking at some other tasks state involves two context switches - to that other task and back to the current.
Looking at another task's state means making a copy of the state, a snapshot if you will. As soon as you make a copy, you now have two versions. Right after you make a copy, before the 2nd task can even examine it, the original state can change again.
To be efficient on a large server, it obviously has to support many parallel threads of execution - but should still be a single memory context
Yes, that's very efficient. That's what a monolithic kernel does.
Of course I do. The key feature of a microkernel is that it uses different access spaces. with protection barriers between them. In contrast, a monolithic kernel has shared access spaces, so different tasks can modify the same data and keep common state synchronized.
That's the only really important difference.
Start by treating the worst diseases, and we'll find out. I'm sure we'll be able to find volunteers.
After all these years, there has been ample opportunity to optimize microprocessor design to make a better microkernel CPU. There is generally just too much cost involved in the constant context swaps for a desktop OS
The reason that microkernels suck has nothing to do with context swap inefficiencies. The biggest problem is trying to maintain a synchronised state between the different tasks across different memory protection areas.
A simple example is a file system. Imagine a dozen different tasks, all working on the same file system, As soon as one task makes a change (say, delete a file), all other tasks are working with an outdated snapshot of the file system state. Unless notified of the change, this will lead to corruption. And notifying all tasks of every little change would be hugely inefficient, not just because of all the overhead of sending the messages, but also because tasks would need to be made with frequent check points. In the end, it would do nothing to simplify the overall system, because you'd basically be implementing a virtual shared memory, and you'd have to deal with exactly the same issues as with a real shared memory.
The tradition solution in microkernels is to have a single task running the file system. This may be a practical idea on some small scale single user systems, but it's totally unacceptable on a larger server, say a big web server with a few hundred simultaneous connections.
Best way to deal with used plastic is simply burn it, and generate some electricity.
When I was a kid, I had both lego bricks as well as Fischer technic. I wouldn't call any of them superior. They both stimulate your brain, in different ways.
They are doing it because of marketing. They're trying to sell more toys by pretending to care about the environment.
I wanna see these things take icy turns at reasonable speed, and avoid skids better than humans and recover from them better than humans.
Low level vehicle control on icy roads is a fairly easy problem to solve for computers.
It isn't about being as good or better than humans, it is just because of the serious consequences that occur when a 4500 pound machine makes a mistake in traffic.
The consequences are not less serious when a human makes a mistake driving that 4500 pound machine.
A robot could also measure objects (lamp posts, buildings, signs, etc) on the side of the road, and use a detailed map to figure out exactly where it is. That way you could drive even if you're the first on a completely snow covered road.
The beauty of robot cars is they are always entirely predictable. The outcome may not have been what you intended, but computers only ever do exactly, to the letter, what they are instructed to do.,
With self-learning networks, nobody knows exactly what the computer is instructed to do. And we certainly cannot predict what they'll do when they get live inputs instead of training data.
Why settle for 6 when you can have 8 with only minor disadvantages ? There's a huge amount of trade going between The Netherlands and Germany. Not just trade between the two countries, but also goods transported through them. Having 33% more overlap in business hours is huge.
The US is too big for just one timezone. Ireland is not. Surely, it's possible to make things work across timezones, but it's much easier if you don't have to.
Problem solved.
Except for the fact that offices with 9-5 schedules in both countries now only have 6 hours of overlap, which makes business much less efficient.
Simple solution is just to ignore leap seconds.
Without authority, who decides what's getting done ?