bulleyashah
Is there a setting in Firefox that allows me to invert colors without a plugin or javascript? The default Black on white is too painful for eyes.
For example, mathematics is not mystical. Philosophy is also well argued.
And secondly, not everything might be definable with data. For example, how should one treat others is not a purely scientific question.
Having said that, what would you like to know?
I understand that transistors amplify current but how do they amplify voltage (like in CMOS)? Isn't voltage going to amplify current also?
I never understood this.
And I agree, most of it can be summarised as "life is a complex system. You can't marry any kind of ideology if you want to achieve any goal, but instead keep listening to feedback and tune accordingly"
But I see what you're saying. Some combination of voting and randomness might br worth it. Also, another thing is maybe some sort of sentiment analysis can help (abuse mainly comes from trolling, virtue signalling etc).
I don't know, if ther was a way to figure out what value a comment adds (or inverse), then that, combined with voting and some sort of randomness might make the system fairer and better?
What a great idea. I have myself disabled colors on the screen to avoid those addictive contrasts.
I also try to do a phone fast every Sunday, where I give my phone to my wife and just live without it for a day. It's amazingly rewarding. You should give it a try :)
I don't use Twitter that much but I hear that twitter is really toxic. Assuming some part of twitter tweet section is random, does that inspire confidence that such a system might work.
Imagine a discussion on Linux and Torvalds comments on it. But due to randomisation, it doesn't get enough traction. Note that this problem will become bigger the more top level comments you get.
This is the same problem with democracies also. Everyone gets to vote but the outcome might not be the best.But the alternative of randomly selecting people to govern also has its problems.
Do you know any platforms which have successfully done the randomisation thing?
You might shoot yourself in the foot by optimizing only for single servers because eventually you'll need horizontal scaling and it's better to think about it in the beginning of your architecture.
I realized this one day when I was drawing some nice sequence diagrams and presenting it to a senior and he said "But who's ensuring the sequence?". You'll never ask this question in a single threaded system.
Having said that, these things are unavoidable. The expectations from a system are too great to not have distributed systems in picture.
Monoliths are so hard to deploy. It's even more problematic when you have code optimized for both sync cpu intensive stuff and async io in the same service. Figuring out the optimal fleet size is also harder.
I'd love to hear some ways to address this issue and also not to have microservice bloat.
And secondly, if you do end up with q distributed systems, remember how many independently failing components there are because thag directly translates to complexity.
On both these counts I agree. Microservices is no silver bullet. Network partitions and failure happen almost every day where I work. But most people are not dealing with that level of problems, partly because of cloud providers.
Same kind of problems will be found on a single machine also. Like you'd need some sort of write ahead log, checkpointing, maybe optimize your kernel for faster boot up, heap size and gc rate.
All of these problems do happen, but most people don't need to think about it.
Secondly, I don't know why you say "distributed systems are an active area of research" and use this as some sort of retort.
If I say "Is a monolithic app running on two separate hosts a distributed system or not", if your answer is "We don't know, it's an active area of research" or "It's not. Only microservices are distributed"
I understand your point. You are using distributed in the sense of "how is one big work distributed", you probably also hate overly "Object Oriented code" for similar reasons.
But distributed systems is a well understood thing in the industry. If I call you and you tell me this, then you're directly responsible for hurting how successful I would be by giving me a misleading sense of what a distributed systems is.
Adding network is not a limitation. And frankly, I don't understand why you say things like understanding network. Like reliability is taken care of, routing is taken care of. The remaining problems of unboundedness and causal ordering are taken care of (by various frameworks and protocols).
For dlq management, you can simply use a persistent dead letter queue. I mean it's a good thing to have dlq because failures will always happen. About which order to procese queue etc. These are trivial questions.
You say things as if you have been doing software development for ages, but you're missing out on some very simple things.
Also, Pinker wrote a book on how the mind works, which is very very wrong (my wife, who's a psychologist absolutely hates it). She asked me to read a small article called "That's not how the mind works" by some guy at MIT to explain.
Then I've also read his book on "How to write" and as an avid reader, I'd say we'd not have had Shakespeare if we followed his advice.
And now you're telling me that his other books are also very shallow? Does he not realize it?
Don't like End of Universe? Create your own big bang.
What do you mean it's impossible? Stop this learned helplessness.