C can teach you about navigating pointers and about memory leaks. The point here isn't to create great applications, it's to teach programming. If you start with python, you have no idea what python is doing, either for you or within your programs. Much better to implement hashes, linked lists, etc. before jumping into languages where all that stuff remains magical -- and apparently cost-free -- to the coders without that experience. It has nothing to do with which language is better to write applications with; it's to develop an understanding of what programs are.
I've been using computers for over 30 years and have never once used this keystroke.
Is it telling that I ran across this article twice and both times thought "What's the problem? just hit Ctrl-R and get on with it!"
Now what's this "application" you speak of?
Okay, I'll run with that. So documentation is really just code that we run on users. Suddenly writing documentation has much more entertainment potential.
Also, programmers write software, not documentation.
I've been contributing to a project over the last 20 years (which happens to be a text editor) which has 80+ pages of documentation in texinfo. I'm not specifically recommending texinfo; it's what the project started with and it works. The point is, the build process renders a plain text version of the texinfo documentation, then a script reads the formatted docs to build several of the program source files, including hash tables of the commands, static text for the internal "help" commands, enums (it's C code), etc. You literally cannot add a new command to the program without adding it first to the documentation. It's a slick way to keep the documentation in sync with the code. The same idea could surely be implemented with many other document source formats. It's a step towards Knuth's Literate Programming without going overboard.
Programmers certainly can and should write documentation.
The lower classes (the 98%) don't care about default because they see it as comeuppance for the robber barons who have all the money to lose anyway. It's only a catastrophe for those with something to lose. For the rest, it's an inconvenient equalizer. (Actually probably much more inconvenient than equalizing; hope we don't find out.)
I didn't realize how luck I was that Ubuntu quit supporting non-PAE (i.e. all of my) machines. I was forced back to Fedora/MATE (GNOME was jumping the same shark) and it's nice to just use the machine again. They drove me off before I had a chance to hate Unity. So, thanks for that!
I wonder if this is the same thinking that went into screwing up paging in Evince (a GNOME project). I find lately that middle-click in the Evince scroll bar does nothing, and left clicking causes a jump to that location (like middle-click is supposed to do, and does in other apps) rather than a page forward. And then there's replacing the menus with buttons on the right like chrome. Ugh.
Fortunately, I've moved to MATE (and mate-doument-viewer a.k.a atril).
I wish GNOME would switch to EBCDIC. Then we could finally sweep its dust from the floor and get back to having fun. Bye, GNOME.
I have no problem with licensing of patents. What I find absurd is the notion of transfer of patents. If someone invents something they ought to be able to profit from it even if they don't produce. But what sense is there in allowing trolls to buy innovation rights from others?
"Patents: license them or lose them. No sales or transferes allowed." Soon as they make me king.
It's a state politician screwing up a state law. Do you want federal politicians to be able to overturn state laws on a whim?
Since you mention it, the same Republican legislature (North Carolina) is pushing a proposal to repeal any local ordinances that go beyond federal regulations. This is their broad stroke approach to "doing away with anti-business regulation". This same bunch that's been screaming "states rights" for years is now doing just the opposite now that they've finally gained power.
"Accelerating one ton to one-tenth of the speed of light requires at least 450 PJ or 4.5 ×10^17 J or 125 billion kWh, without factoring in efficiency of the propulsion mechanism. This energy has to be either generated on-board from stored fuel, harvested from the interstellar medium, or projected over immense distances."
Or you can borrow it from the future, where it will be generated conveniently enough in exactly the right quantity by slowing that one ton down. We just haven't figured out how to shift the energy equations in the temporal dimension yet.
So how would his knowledge of passwords from when he used to work there be of any use? Do they not immediately change all the passwords he had when he left the company? Did they let him keep his keys to the building as well? The real villain here is the victim's IT department.
Slashdot Mirror
Reading this on a T42 with a 4:3 1400x1050. Will use it 'till one of us dies. Would love to by the same thing new.
The problem stems from the assumption that everyone surfing the web is a consumer. That is not often the case.
I strongly agree with this approach. Do some (admittedly toy) simple stuff in assembler first.
Then move on to C as their 2nd language.
Their 3rd language... can be whatever they want to implement in C. :)
C can teach you about navigating pointers and about memory leaks. The point here isn't to create great applications, it's to teach programming. If you start with python, you have no idea what python is doing, either for you or within your programs. Much better to implement hashes, linked lists, etc. before jumping into languages where all that stuff remains magical -- and apparently cost-free -- to the coders without that experience. It has nothing to do with which language is better to write applications with; it's to develop an understanding of what programs are.
What about the privacy of the people planning to overthrow the government when it is no longer following the constitution?
This. Or, more to the point, start your own business doing the same job the right way, as you see it. If you succeed, you were right (and lucky).
I've been using computers for over 30 years and have never once used this keystroke.
Is it telling that I ran across this article twice and both times thought "What's the problem? just hit Ctrl-R and get on with it!" Now what's this "application" you speak of?
Sounds like M87's Puppeteers know something and are heading for higher ground.
If that were true then there would not have been 100 million downloads of Apache OpenOffice, would there? Therefore...
Sorry, that was me. I left curl running in a loop on a 56kb dialup and went on vacation. My bad.
Oh yeah, will I'm DEAD and on the no-fly list, and they can't fly my body back to my hometown for burrial. So there!
They lay... power-up eggs that the pac-man vans pick up? This makes no sense.
Okay, I'll run with that. So documentation is really just code that we run on users. Suddenly writing documentation has much more entertainment potential.
Also, programmers write software, not documentation.
I've been contributing to a project over the last 20 years (which happens to be a text editor) which has 80+ pages of documentation in texinfo. I'm not specifically recommending texinfo; it's what the project started with and it works. The point is, the build process renders a plain text version of the texinfo documentation, then a script reads the formatted docs to build several of the program source files, including hash tables of the commands, static text for the internal "help" commands, enums (it's C code), etc. You literally cannot add a new command to the program without adding it first to the documentation. It's a slick way to keep the documentation in sync with the code. The same idea could surely be implemented with many other document source formats. It's a step towards Knuth's Literate Programming without going overboard.
Programmers certainly can and should write documentation.
The lower classes (the 98%) don't care about default because they see it as comeuppance for the robber barons who have all the money to lose anyway. It's only a catastrophe for those with something to lose. For the rest, it's an inconvenient equalizer. (Actually probably much more inconvenient than equalizing; hope we don't find out.)
Your first item of homework is to find out how the proverb "People in glass houses..." ends.
With a period!
I didn't realize how luck I was that Ubuntu quit supporting non-PAE (i.e. all of my) machines. I was forced back to Fedora/MATE (GNOME was jumping the same shark) and it's nice to just use the machine again. They drove me off before I had a chance to hate Unity. So, thanks for that!
I wonder if this is the same thinking that went into screwing up paging in Evince (a GNOME project). I find lately that middle-click in the Evince scroll bar does nothing, and left clicking causes a jump to that location (like middle-click is supposed to do, and does in other apps) rather than a page forward. And then there's replacing the menus with buttons on the right like chrome. Ugh.
Fortunately, I've moved to MATE (and mate-doument-viewer a.k.a atril).
I wish GNOME would switch to EBCDIC. Then we could finally sweep its dust from the floor and get back to having fun. Bye, GNOME.
I have no problem with licensing of patents. What I find absurd is the notion of transfer of patents. If someone invents something they ought to be able to profit from it even if they don't produce. But what sense is there in allowing trolls to buy innovation rights from others?
"Patents: license them or lose them. No sales or transferes allowed." Soon as they make me king.
Since you mention it, the same Republican legislature (North Carolina) is pushing a proposal to repeal any local ordinances that go beyond federal regulations. This is their broad stroke approach to "doing away with anti-business regulation". This same bunch that's been screaming "states rights" for years is now doing just the opposite now that they've finally gained power.
Humor detectors exists though. Most people have 'em. Obviously not everybody though.
Or you can borrow it from the future, where it will be generated conveniently enough in exactly the right quantity by slowing that one ton down. We just haven't figured out how to shift the energy equations in the temporal dimension yet.
Democracy is two wolves and a sheep deciding what's for dinner.
...or as we like to call it, "not-always-on".
Mexico?
So how would his knowledge of passwords from when he used to work there be of any use? Do they not immediately change all the passwords he had when he left the company? Did they let him keep his keys to the building as well? The real villain here is the victim's IT department.