165 karma · joined January 9, 2017
And also - vram is a moat that keeps the cost of "professional" cards absurdly high without making them actually faster than consumer cards.
What i'm saying is that most of us are willing to give up a bit of security for repairability and saving the planet. Phones and laptops are expensive products in terms of resources used to create them. We're definitely not paying the full price for them. Imagine how much would it cost to extract every microgram of precious resources and capture all pollution and co2 emitted in the supply and distribution chain. Instead we're lining the pockets of megacorps that use every trick to enrich themselves while slowly destroying the environment, the same corps that gives access to your data to the government if need be. I'd say the chance of a sophisticated hardware hacker implanting a rogue chip in your phone is somewhat smaller than the chance of your phone's screen or battery dying in the next year.
I find it amazing how the proteins not only have to create the shape in the end, but they also need to be able to snap together in the right conformation and avoid snaping together with other molecules that happen to be around there. And they must evolve that function in the first place. I intuitively have a hard time grasping what simple processes repeated an inumerable amount of time can produce in the end. And yet here we are.
Ofcourse, in our foolishness, we could create an ai with the goal of survival and replication at the expense of everything else. Or self optimisation could inadvertedly do so
[1] https://www.planetanalog.com/signal-integrity-challenges-set...
- Denial - This should be pretty easy, just put types everywhere!
- Anger - But my code is correct! The damn compiler doesn't understand what I mean!
- Bargaining - Can't I just use any?
- Depression - This will take forever to figure out and I have a deadline :(
- Acceptance - It's a tool like any other, it's a hassle, most of the time is useless but sometimes it saves you from bugs and makes collaboration easier.
You just have to accept that the type specification in typescript is a whole separate language that you have to learn, that takes time to write correctly.
In my experience that's at least 30% more than writing js when you know what you are doing, more when you don't. Adding the linter and tests you end up spending more time on these correctness checks than actually writing code, and that is ok, or not, depending on the project goals.
When you are writing library code this cost goes up, WAY up because your library will be used in multiple ways by different people so you have a combinatorial explosion of cases that need to be handled.
I don't understand where this expectation that writing typescript should be as easy and quick as writing js.
IMHO the typescript docs are one of the best resources (just compare them to python docs...)
How big is the risk of a child being groomed through these electronic means? Is it comparable to being struck by lightning? What is worse weighted by probability: being sexually assaulted as a child or being suspected and having your life turned upside down for years by these algorithms. We already see these things happen with relatively minor things like having your google account closed by an algorithmic mishap.
How was this 10% number of false positives determined? Is this only an expectation of false positives or an actual statistic. What does 10% mean in the context of mass surveillance?
It might well be that millions of children are groomed and assaulted every year through chats. I don't have the data so i cannot say. I was under the impression that most sexual assault cases happen in the family and not by strangers.
What's worrying though is that these decisions are taken behind closed doors without any oversight, on the hope that they might save a child and possibly putting our lives in the hands of algorithmic justice.