RonSijm

joined 1 year ago
[–] [email protected] 5 points 1 year ago (1 children)

What we have is machine learning, just an algorithm that takes input and gives you output. It can’t act on its own.

Isn't that basically what "real learning" is as well? Basically you're born as a baby, and you take input, and eventually you can replicate it, and eventually you can "talk" for example?

But in the training data something was off, suddenly your AI is racist and gives every black person a lesser amount.

Same here, how is that different from "real learning"? You're born into a racist family, in a racist village where everyone is racist. What is the end-result; you're probably somewhat racist due to racist input - until you might unlearn that, if you're exposed to other data that proves your racist ideas were wrong

If a human brain is basically a big learning computer, why wouldn't AI eventually reach singularity and emulate a brain and beyond? All the examples you mentioned of what it can't do, is just stuff it can't do yet

[–] [email protected] 3 points 1 year ago (3 children)

How do you handle the existential crisis of our works being digital and transient versus having an actual, physical product?

Well this topic is very subjective, but I'll chime in...

"You have a right to perform your prescribed duties, but you are not entitled to the fruits of your actions." -

Basically: You should be programming because you like programming - Not because you like that people like your program, or that it might immortalize yourself somehow - Or because people might use your program forever and will remember you by it

You can say the same for every profession: You're the best doctor in the world and you healed millions of people. Great. 100 years later all those people are still dead anyways. What was the point?

Basically everything is temporary in the end, and everything is going to be forgotten. Seeing your job as a programmer as part of your identity and your applications as proof of your existence or digital legacy is pretty much pointless

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

Don't think the size really matters... an IP is 4 bytes, and the port another byte, plus lets say 4 bytes for the UserId. So with some overhead, you can practically put about 100k addresses in 1 MB.

With that many addresses, you should probably be more concerned about the lookup than the storage. I'd probably put then in a Dictionary[UserId, SocketData].

Websockets don't usually stay alive for long periods, so there's not much point of storing them in a database. Unless you're building something serverless, but then I wouldn't build something myself, but just use Firebase Cloud Messaging instead

[–] [email protected] 1 points 1 year ago (1 children)

Personally I don't have any problems with it (if that was directed at me) - I've added 418 as "unhandled exception code" response to a bunch of applications, so I can easily differentiate whether my application is throwing an error, or whether it's some middleware gateway AWS io-thing

I was just curious what OP thought about it, since in the early days it wasn't uncommon to add goofs or easter-eggs into software, but nowadays not done so much... and apparently the "HTTP Working Group" doesn't like it either... So I was curious whether OP though in hindsight whether it should've been added or not

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (7 children)

Do you regret adding it, or with the knowledge you have today, would you still add the 418?

Since a bunch of languages have not implemented it, or/and has long discussions about it:

https://github.com/dotnet/runtime/issues/15650
https://github.com/golang/go/issues/21326
https://github.com/nodejs/node/issues/14644
https://github.com/psf/requests/issues/4238
https://github.com/aspnet/HttpAbstractions/issues/915

view more: ‹ prev next ›