7 more posts in this thread. [Missing image file: Linux_sucks.gif]
Right now FOSS is suffering from three MAJOR problems, which seriously hamper progress. If these problems were to be soled things would be a LOT farther along.
1.- The "Taco Bell" problem. This is where limited resources are squandered on the illusion of choice and ego stroking and its a serious issue. How many distros on distrowatch fit this description? "Its (insert Ubuntu/Debian) with (insert KDE/Gnome or derivative) along with (insert LO/FF/Gimp/Chromium) and just enough changes to make things incompatible"? Probably a good 90% at least. If this ego stroking illusion of choice were removed and that effort instead put to use fixing issues with one of the big three? It would go a LONG way to fixing the second problem.
2.- The "busted shitter" problem. You ask someone to paint you a picture or write you a song for free? You'll have plenty to choose from,many of which might even be good. Ask them to fix your stinking shitter for free? Better get used to pissing in the sink. All the "easy and fun work" in Linux is pretty much done,while all the nasty work, regression testing, documentation (how many place holder help files are in your average distro?) bug fixing, drier testing, application compatibility testing, all the nasty work that really adds polish to an OS and make it shine? Too much of it simply isn't getting done. For proof go look at any distro's forums after a major release and how many "update broke my driers" posts you see. More importantly look at how many of these are involving the "bog standard" hardware, the Realtek and Via sound, Realtek and SiS networking, the major wireless chips, things that should frankly NEVER be allowed to break because of the number of people using those chips...yet they are crapped on constantly. It doesn't matter how well your OS looks, the second it starts crapping on bog standard hardware it looks Mickey Mouse.
0 more posts in this thread. [Missing image file: python-logo.png]
Hey /g/ wondering if you could help a python noobie out.
So what im trying to do here is send a UDP message to a server that contains the clients name IPaddress and port (the port that is passed is used as a welcoming port for all income transitions from the server to client) Now i need to send out this message to the server then wait 10 seconds, listening to the welcoming port for the server to send an ack, after 10 seconds i then need to send the message again and wait 10 more seconds. i need to do this 3 times. So i can send the server the info, get it to send the ack back and i know im listening to the right port, but the problem is i dont know how to make it reset the request after the first 10 seconds past.
here is my code
while i < 3:
message = 'REGISTER '+ userID + ' ' + userIP + ' ' + userPort
## port we send it form, just a random one)
clientSocket = socket(AF_INET, SOCK_DGRAM)
## newsocket that the ack should be coming from
welcomeSocket = socket(AF_INET, SOCK_DGRAM)
## where i have my issues, after the first 10 seconds the program just ends because the socket died.
message, serverAddress = welcomeSocket.recvfrom(2048)
if message != None:
i know the code is super sloppy, im winging socket programing in python with absolutely no experience in python, all coding i have done this far has been in C++, C, and some assembly
26 more posts in this thread. [Missing image file: build.png]
Hey look at that, yet another build thread.
Tell me if there is something wrong with this build. Used for hardcore gaymen, softcore gaymen, and just general usage.
Will be getting within 3 months. Probably just a single/dual Dell U2412M setup. Trying to keep the Red, White, and Black look of it.