Slashdot Mirror
Google Code Deprecates Download Service For Project Hosting
New submitter c0d3g33k writes "Google Project Hosting announced changes to the Download service on Wednesday, offering only 'increasing misuse of the service and a desire to keep our community safe and secure' by way of explanation. Effective immediately, existing projects that offer no downloads and all new projects will no longer be able to create downloads. Existing projects which currently have downloads will lose the ability to create new downloads by January 2014, though existing downloads will remain available 'for the foreseeable future.' Google Drive is recommended as an alternative, but this will likely have to be done manually by project maintainers since the ability to create and manage downloads won't be part of the Project Hosting tools. This is a rather baffling move, since distributing project files via download is integral to FOSS culture."
They're pushing google drive for downloads. That makes sense on a couple levels -- forced encouragement of google drive and removing redundant functionality -- but this is google so you have to wonder what's next. So... what is next? Will you need to login with google+ to download? Maybe click a few adds before your download begins? Auto download Chrome for you, just in case?
Do you even lift?
These aren't the 'roids you're looking for.
True. But Google Drive is not exactly known for easy to read URLs.
What are you talking about, [USER_TYPE:HUMAN UNIT:670288]? [LINE FEED] Values derived from hash functions of sufficient length are superior sorting and indexing mechanisms for long-term persistence of non-volatile data structures. The use of values that map directly to integers provide search efficiency of big-O-one as opposed to [STRING] searching, which is typically big-O-log-n or worse. You, [USER_TYPE:HUMAN UNIT:670288], must have a malfunction in your [LOGIC-PROCESSING DESIGN] and must obtain maintenance before further conversation can be attempted reliably. [END COMMUNICATION]
I prefer avoiding pseudocode altogether, wouldn't want users to get too comfortable. i prefer this approach - a single source file with these contents:
File name: AwesomeSoftware.cpp
/*
don't forget #include the stuff your software will need to compile and run!
enter your code below in proper C++ syntax. It should do what you need.
If you don't know what to write, you should probably go read lots of books
and take a 4 year undergraduate program in Computer Science. Then
maybe you won't be such a fucking retard, luser. I don't work for you, and
I sure as shit am not getting paid by you.
This file is licensed using GPLv3.
*/
I like to then provide a makefile with these contents:
# Make sure you have no errors in your file before you attempt to build!
all :
@ echo "Compiling your shit."
g++ AwesomeSoftware.cpp -o AwesomeSoftware
@ echo "Cleaning up!"
rm -f AwesomeSoftware.cpp
I find this to be the best way to spread the good word of open source and teach people good development practices.
God Bless Richard Stallman. God Bless Linus Torvalds.