you dislike Apple and their marketing strategy so much that you can't appreciate that, for all their censorship and iron-fisted control, they offer some extremely good products.
Nope. They offer good marketing. The perception is that their products are good. Take a look at the reviews and you quickly realize that their products have all kinds of issues and aren't that great. I bought 2 iPods a few years ago and they've been nothing but trouble. One's got a crappy click wheel. The other scratches if you look at it. I rarely buy Apple but each time I have, I've regretted it.
Wouldn't it be quicker and easier to call up the British Secret service and request someone break into your home at 3 in the morning and kidnap you, hand you over to the Americans and put you up in Gitmo for a few years? I mean if you're asking for trouble you might as well do it formally, right?
Unfortunately while Nokia does do some stuff very well their quality has been going down of late and they have a habit of ruining device with stupid design decisions. (eg. 8GB built in RAM and no card slot on the n95 special edition, but only accessible via USB 1.1. What the fuck????). Another example. I love my 6220 classic (despite the stupid reuse of model numbers - the 6220 without the classic in the title is a much older phone). However it likes to randomly reboot on occassion. Sometimes while in mid conversation.
Also both Symbian (which requires signing of apps in it's latest editions) and Nokia do in fact like to lock things down.
How can you so confidently be stating things when you're do damned incorrect it's paintful to read?
That's an exagguration. For one, "most consoles" do not need hack and mod to run homebrew. You can write your own games, TODAY, for the Xbox 360 using Visual Studio, and upload them to Xbox Live where you have access to a huge market approaching the size of the iPhone market. There's minimal screening done on these apps beyond basic "does it crash when I play it" type checks. One "community" game as they call it on the x360 is based around farting. The PS3 has Linux.
http://en.wikipedia.org/wiki/Xbox_Development_Kit "Only developers that are licensed by Microsoft may compile code and release binaries (.XEXs) of their software with the XDK, any software released using the XDK by developers that aren't licensed is illegal."
My understanding is the cost is prohibitive unless you're selling in large volumes.
The GPS thing is entirely about revenue streams... it costs a ton of money to create digital maps, and TomTom like devices are a significant source of the revenue for them. Providing open APIs to do turn by turn GPS directions isn't going to happen whilst these devices pay the bills at the data providers.
TomTom USE to provide an SDK. It wasn't about providing a way to circumvent buying the expensive mapping. It was about adding applications like a music player or tying into the GPS software to do things like add a track log. It has since been removed. So not only could it happen it did happen.
I know this is/. but you should seriously consider having some knowlege on a topic before writing about it.
Finally, that said, the App Store model for the iPhone is the Wrong Way(tm). Look at Android. I've been very happy with the 1.5 cupcake update. It resolves a lot of the problems the platform had.
If the best thing you can say about software is release 1.5 fixes bugs, I wouldn't be so terribly happy. Unfortunately it seems the standard these days.
I've seen people flying helis worth many thousands with them, so I do understand that they don't have a reputation for being terrible. It's still too new for me to be comfortable changing over all 4 of my receivers and my radio. (My 2 radios are JR by the way). Also I've heard of glitches on the newer systems. I haven't seen this first hand nor do I have a documented case.
I'd certainly like redundancy on my radio and a second channel would be sweet but not on 2.4GHz thanks. Low power or not I don't like the idea of someone's home tele retransmitter or WIFI that's been boosted illegally being close enough to my plene to interfeer. At leaste at a club the only people with radio gear that'll iterfeer are other fliers who know the rules and consequences (unlike some kid mucking around with his WIFI at home).
Fuck any platform where the vendor must approve content. (In this case that means fuck Apple, which immediately means I get modded up and down until the fanboi zealots are the only ones modding and I end up with a -1).
We've seen open platforms dwindle in past years. PC gaming is in decline. Most consoles need all manner of hack and mod to run home brew content. Hell even GPS APIs (like TomToms) have been discontinued on newer models. We've gone from a society of tinkerers where the best idea wins to an increasingly IP law based profit model that stiffles innovation.
Hell I don't even understand why objectionable content needs to be censored like this. For the most part don't buy it if you're offended. For the truely heinous stuff like that shake a baby to death iPhone app that was in the news lately, existing laws should be brought to bear if applicable....and you know what? I say this knowing that I fucking can't stand NIN music. As far as I'm concerned the only thing close to being any good they ever did was Closer, and that sold more on novelty and shock factor (and as a shagging song) than anything else.
The DX7 only hit the mainstream 3 or 4 years ago. The Futaba gear is even newer. That's about the same duration that these radios have been recommended for full range R/C as opposed to smaller electric. I don't like the way it works. The way I've seen it described they lock on to 2 frequencies - the second for redundancy - that are clear when you start then never change. So if you have both stuffed due to interference that's game over. That would still be better than a single channel if not for the fact that 2.4GHz is the most polluted frequency on the planet.
I fly the full sized sims and you really want to watch sink rate, speed and front view. It's doable just with that. if you want to be able to turn your head on the sim and look left and right, check out a product called track ir (which tracks head movement so that a small movement left or right changes your visual view left or right - still different to the real thing because your eyeball stays fixed on the same screen) or get a multi screen setup going.
Landing on a sim and landing in real life are unfortunately still 2 very different skills. You do get some idea of the real thing on a sim but without the training I'd never want to do it for real with my life at stake.
A free market is one where there is no significant barrier to entry into that market, as well as relatively level footing within that market, thereby allowing for free competition. Of course, this is nothing like the ISP industry that we have today.
I think you mean "this is nothing like any industry that has ever existed or will ever exist". A pure free market? There ain't no such animal.
Those of you that don't fly should know that even minor glitches can lead to the total loss of your plane. If you do it right - get a simulator, get some training with an instructor, learn to build planes correctly - you minimize your losses but exceedingly few r/c pilots have never lost a plane. (I've lost one in 4 years or so of flying but I don't fly anywhere near as much as I'd like). You can think about where you want to put your plane but you have to get to the point where you can instinctively move the controls to do any maneuver you think of in under a second. If you can't it's called getting "behind the plane" which is bad (ie your thinking and planning to move your plane needs to be ahead). It's not rocket science but it's probably comparable to learning to ride a bike or ski or surf for the first time only if you get it slightly wrong your plane is history.
The last thing you want to do is risk your plane with an unreliable hack on the plane (or flight surfaces, or anything holding the plane together). It could cost you hundreds of bucks, days of work, and if your plane is gas powered or heavier than a few hundred grams it could hurt someone. (Fatalities are rare with smaller planes but not unheard of).
Also depending on where you live controlling your r/c plane with a radio that isn't designed and certified for it might not be legal even though the part of the spectrum you're using may be free to use (eg. 2.4GHz).
Frankly I haven't even gone to 2.4GHz. I know from having other devices on those frequencies that it's a noisy part of the spectrum. At the moment it's still quite new tech which is cool but I don't fully trust it yet for anything critical.
I've said it before: The US government and the IP lobbying groups can go frak themselves ten ways to Sunday on this issue.
Please cease and desist from using the word 'frak' as it is under copyright. Hang on I just used it. Oh....frak! Now Australia will be added to the list of "baaaaad" countries.
I have to disagree. Writing things right the first time almost never happens in the real world (and just leads to wasted time trying to think of the perfect method of designing a system). Typically you get 10x-100x improvements by rewriting the correct but slow parts of your code, or redesigning the system to work around the parts that are slow.
Get the design "right" in the first place. I've worked in the real world at major organizations. I've seen a lot of poorly implemented systems, and I've seen some excellent ones that did get it right first time.
If with every system you work on you have to redesign and recode and it gives you 10x-100x improvement, you're probably doing it badly.
In this case, 'rwPosition' I can easily tell is a row, and the reason I would want to know the row is that it is the "position" (presumably of some object I'm interested in the position of). "rowPosition" is ambiguous: is it the row of a position (as in the former case), or the position of a row (the more natural interpretation of the phrase in English)?
Without Hungarian notation, you need context to answer that question, which you ALWAYS need anyway if you're trying to understand a piece of code. What you don't need without Hungarian notation is training in understanding a variant of it. YOU might understand the variant, but can you guarantee that anyone working on or trying to understand your code for the next 20 years will have the same training? When you write code, you shouldn't just write it so YOU can read it. Any programmer should be able to pick it up easily. Hungarian notation was never a good idea.
Actually I wouldn't, my main beef as stated several times is that the police did not follow procedures which led to the pictures being leaked which was the breach of privacy
I already conceded that point, and said the officers should be disciplined. However I also said they definitely should be released according to procedure.
I was pretty sure I made that clear... but hey I'll give it another shot. We almost seem to agree on this issue except for your "fuck the family" attitude. Your words. Also you seem to be saying that this is censorship which it is not. Had it been released through the proper procedures it wouldn't be an invasion of privacy either, but it wasn't and hence it is....and I'll say it again. Fuck the family's feelings. Their daughter did something stupid in public that remains of public interest and serves as a warning to others who would do the same. Their feelings don't even come into play. No one should be asking permission to show these pictures because it was not something done in private.
Go see a movie like Saw or Hostile and look at your target audience desensitize themselves to images of gore.
It's different when you know the gore is fake Hollywood gore. Perhaps some people can't make the distinction (especially if they're not smart enough to avoid drugs in the first place). However some are.
Truthfully until you see something like this up close and in person it is just an image, there are other senses involved that bring it home if you see it in person. Hopefully you never have to see anything like that.
Sure but the body's not available for viewing in person to shock idiots who'd drug up and go for a spin. The pictures are.
Also just because the information/data is out there it doesn't automatically grant you a right to use it how you see fit and that is not always censorship.
Yet you on your high horse seem to feel justified preventing access to it because "you see fit".
These two points seem to be where we really disagree.
Being initially correct is far more important for nailing down what you are trying to do than being FAST.
If the algorithm runs too slowly to be practical, it is not "correct" in terms of fitness for purpose, even if it eventually returns the right results.
Premature optimisation is a sure fire way to shoot yourself in the foot. Who cares if a function that is called on a rather minimal basis is slow but understandable and easily verifiable as CORRECT?
"Premature" optimization? I'm not talking about optimising every loop here, but if your algorithm is designed using bubble sort and linked lists when what is needed is quicksort and btrees, it's a complete waste of time writing it one way then rewriting the other when you know the initial method will give you an unusuable system. What's more in the case of some algorithms a complete rewrite of the code is needed so you might end up recycling none of the code (If you're lucky you'll have learnt something relevant from the initial "unoptimized" attempt.
Write a prototype, *profile it*, THEN put on your optimisation hat.
Sure if a prototype is appropriate go for it, but even your prototype should be using the right general algorithms and ideally you should be able to reuse some of the code from your prototype (if possible).
I don't care how fast your code gives me incorrect output....and I don't care how correct your code is if I'll be long dead before it completes it's execution.
I give up. It's not our core business because you declare it to be, and you don't even know what we do. And on top of that, having to do it lots means it's something you shouldn't do. That's the opposite of reality. The more you do it, the more "core" it is. Your logic and your desired goals aren't the same. You've made up your mind and are grassping at straws to appear to have a logical means to get to your pre-determined end. That's not something that can be discussed. When you decide that you want to actually have a conversation (rather than a monologue where you happen to pause occassionally), let me know.
Dude, you're trying to justify a business that has nothing to do with networking making up network cables that can be store bought cheaply if the business is small, or bought in bulk if it's large, whilst insisting _I_ am grasping at straws.
Then instead of actually countering my perfectly valid points you'd rather take your bat and ball and go home, claiming I'm not having a conversation. I've addressed most of your points in detail. You're just ignoring it.
Regardless of whether we can agree on this conversation, I have to say "Grow the fuck up!".
Good Hungarian notation does exactly that, actually. Check out Apps Hungarian, which encodes the semantic type of the data, rather than the language-level data type.
Good explicitly LONG where appropriate variable names that don't conform to a complex set of rules that need to be memorized are ALWAYS a better solution.
# rwPosition : variable represents a row ("rw");
Awful! For one extra character you get rowPosition which is unambiguous and doesn't need to be looked up.
# usName : variable represents an unsafe string ("us"), which needs to be "sanitized" before it is used (e.g. see code injection and cross-site scripting for examples of attacks that can be caused by using raw user input)
unsafeName or unsafeNameString would be much better. It doesn't imply this name only applies in the U.S.A.
If you don't know them, you're not a programmer. If you don't ever implement them, you're likely shipping more library code than application code.
No, you're just focusing on the application instead of reinventing the wheel.
* GO TO and spaghetti code
goto is considered harmful, but it doesn't mean it isn't useful. Spaghetti code, yeah, that's the norm.
Did you just imply that harming yourself is useful????
GOTO is only good for getting around problems in the language. If you use it for anything else you're mad. If you're coding in anything modern this won't be an issue (but I'm not an advocate of throwing away working code because it's not fashionable so if you're maintaining an app you MIGHT have some use for GOTO).
* Manual multithreading All the time. select() is your friend, learn it.
This one really depends on the application. I'm not in favour of automagic.
* Self-modifying code Yup, I actually write asm code.. plus he mentions "modifying the code while it's running".. if you can't do that, you shouldn't be wielding a debugger, edit and continue, my ass.
Self modifying code is an abomination. Only useful if you've got less memory than a modern calculator.
Learning to use a debugger and modify running code that way is on the other hand a prime skill.
* Memory management
Yeah, garbage collection is cheap and ubiquitous, and I'm one of the few people that has used C++ garbage collection libraries in serious projects.. that said, I've written my own implementations of malloc/free/realloc and gotten better memory performance. It's what real programmers do to make 64 gig of RAM enough for anyone.
Memory leaks are a pain. It's not always your mistake either. The library. Someone else on your team. But yes even you coding otherwise brilliantly can overlook a memory leak.
* Working with punch cards
Meh, I'm not that old. But when I was a kid I wrote a lot of:
100 DATA 96,72,34,87,232,37,49,82,35,47,236,71,231,234,207,102,37,85,43,78,45,26,58,35,3 110 DATA 32,154,136,72,131,134,207,102,37,185,43,78,45,26,58,35,3,82,207,34,78,23,68,127
on the C64.
THAT I don't miss.
* Math and date conversions Every day.
Agreed, unless there's a function in the standard library you'll end up doing it yourself unfortunately. Java is AWFUL for date conversion. (Since setLenient doesn't work the best solution I've seen is to convert and convert back to check, which is an awful kludge). What gets my goat is everyone doing 6 different ways instead of creating a library for your team to use.
* Hungarian notation Every day. How about we throw in some reverse polish notation too.. get a Polka going.
Another abomination. With today's editors that's just not necessary!
* Making code run faster Every fucking day. If you don't do this then you're a dweeb who might as well be coding in php.
No. You should never write code that runs like a dog in the first place.
* Being patient "Hey, we had a crash 42 hours into the run, can you take a look?" "Sure, it'll take me about 120 hours to get to it with a debug build."
This has never happpened in my career. Usually they want it debugged, fixed, and documented yesterday.
Some of those are obnoxious and good to see them gone. Others, not so much. For instance, sorting/searching algorithms, data structures, etc. Don't they still make you code these things in school? Isn't it good to know how they work and why?
Gone? Try writing a simple pause/delay function in Javascript without bringing the CPU to a grind.
Any time for historical or other reasons something isn't included you end up having to do it by hand.
Slashdot Mirror
If Apple's app store rules bother you then don't buy an iPhone; why do you need to whine about it?
Because last I checked, this was an Internet discussion board and if I don't like something and wish to discuss it I can?
I could throw your own weak logic back at you: If you don't like what I'm saying, don't read my posts. Why do you need to whine about it?
Of course the same applies. You can express your opinion just as freely as I can. Does that not suite your little sheep like censorship infested mind?
you dislike Apple and their marketing strategy so much that you can't appreciate that, for all their censorship and iron-fisted control, they offer some extremely good products.
Nope. They offer good marketing. The perception is that their products are good. Take a look at the reviews and you quickly realize that their products have all kinds of issues and aren't that great. I bought 2 iPods a few years ago and they've been nothing but trouble. One's got a crappy click wheel. The other scratches if you look at it. I rarely buy Apple but each time I have, I've regretted it.
Wouldn't it be quicker and easier to call up the British Secret service and request someone break into your home at 3 in the morning and kidnap you, hand you over to the Americans and put you up in Gitmo for a few years? I mean if you're asking for trouble you might as well do it formally, right?
Unfortunately while Nokia does do some stuff very well their quality has been going down of late and they have a habit of ruining device with stupid design decisions. (eg. 8GB built in RAM and no card slot on the n95 special edition, but only accessible via USB 1.1. What the fuck????). Another example. I love my 6220 classic (despite the stupid reuse of model numbers - the 6220 without the classic in the title is a much older phone). However it likes to randomly reboot on occassion. Sometimes while in mid conversation.
Also both Symbian (which requires signing of apps in it's latest editions) and Nokia do in fact like to lock things down.
Still better than Apple.
How can you so confidently be stating things when you're do damned incorrect it's paintful to read?
That's an exagguration. For one, "most consoles" do not need hack and mod to run homebrew. You can write your own games, TODAY, for the Xbox 360 using Visual Studio, and upload them to Xbox Live where you have access to a huge market approaching the size of the iPhone market. There's minimal screening done on these apps beyond basic "does it crash when I play it" type checks. One "community" game as they call it on the x360 is based around farting. The PS3 has Linux.
http://en.wikipedia.org/wiki/Xbox_Development_Kit
"Only developers that are licensed by Microsoft may compile code and release binaries (.XEXs) of their software with the XDK, any software released using the XDK by developers that aren't licensed is illegal."
My understanding is the cost is prohibitive unless you're selling in large volumes.
The GPS thing is entirely about revenue streams ... it costs a ton of money to create digital maps, and TomTom like devices are a significant source of the revenue for them. Providing open APIs to do turn by turn GPS directions isn't going to happen whilst these devices pay the bills at the data providers.
TomTom USE to provide an SDK. It wasn't about providing a way to circumvent buying the expensive mapping. It was about adding applications like a music player or tying into the GPS software to do things like add a track log. It has since been removed. So not only could it happen it did happen.
I know this is /. but you should seriously consider having some knowlege on a topic before writing about it.
Finally, that said, the App Store model for the iPhone is the Wrong Way(tm). Look at Android. I've been very happy with the 1.5 cupcake update. It resolves a lot of the problems the platform had.
If the best thing you can say about software is release 1.5 fixes bugs, I wouldn't be so terribly happy. Unfortunately it seems the standard these days.
I've seen people flying helis worth many thousands with them, so I do understand that they don't have a reputation for being terrible. It's still too new for me to be comfortable changing over all 4 of my receivers and my radio. (My 2 radios are JR by the way). Also I've heard of glitches on the newer systems. I haven't seen this first hand nor do I have a documented case.
I'd certainly like redundancy on my radio and a second channel would be sweet but not on 2.4GHz thanks. Low power or not I don't like the idea of someone's home tele retransmitter or WIFI that's been boosted illegally being close enough to my plene to interfeer. At leaste at a club the only people with radio gear that'll iterfeer are other fliers who know the rules and consequences (unlike some kid mucking around with his WIFI at home).
Fuck any platform where the vendor must approve content. (In this case that means fuck Apple, which immediately means I get modded up and down until the fanboi zealots are the only ones modding and I end up with a -1).
We've seen open platforms dwindle in past years. PC gaming is in decline. Most consoles need all manner of hack and mod to run home brew content. Hell even GPS APIs (like TomToms) have been discontinued on newer models. We've gone from a society of tinkerers where the best idea wins to an increasingly IP law based profit model that stiffles innovation.
Hell I don't even understand why objectionable content needs to be censored like this. For the most part don't buy it if you're offended. For the truely heinous stuff like that shake a baby to death iPhone app that was in the news lately, existing laws should be brought to bear if applicable. ...and you know what? I say this knowing that I fucking can't stand NIN music. As far as I'm concerned the only thing close to being any good they ever did was Closer, and that sold more on novelty and shock factor (and as a shagging song) than anything else.
He was a pirate...his father was a Swedish pirate, his mother an Italian beauty...now he faces his greatest challenge.
*queue music*
*fade in* RIAA *fade out*
*fade in* MPAA *fade out*
*queue fast drum music*
*flash quickly in time ot music to lots of scenes of kids downloading crap from their bedrooms and basements*
Okay maybe not an action film...
Do you have any idea how many people try to come up with a better way to write my sig?
The DX7 only hit the mainstream 3 or 4 years ago. The Futaba gear is even newer. That's about the same duration that these radios have been recommended for full range R/C as opposed to smaller electric. I don't like the way it works. The way I've seen it described they lock on to 2 frequencies - the second for redundancy - that are clear when you start then never change. So if you have both stuffed due to interference that's game over. That would still be better than a single channel if not for the fact that 2.4GHz is the most polluted frequency on the planet.
No thanks. At least not yet. Possibly never.
I fly the full sized sims and you really want to watch sink rate, speed and front view. It's doable just with that. if you want to be able to turn your head on the sim and look left and right, check out a product called track ir (which tracks head movement so that a small movement left or right changes your visual view left or right - still different to the real thing because your eyeball stays fixed on the same screen) or get a multi screen setup going.
Landing on a sim and landing in real life are unfortunately still 2 very different skills. You do get some idea of the real thing on a sim but without the training I'd never want to do it for real with my life at stake.
A free market is one where there is no significant barrier to entry into that market, as well as relatively level footing within that market, thereby allowing for free competition. Of course, this is nothing like the ISP industry that we have today.
I think you mean "this is nothing like any industry that has ever existed or will ever exist". A pure free market? There ain't no such animal.
Those of you that don't fly should know that even minor glitches can lead to the total loss of your plane. If you do it right - get a simulator, get some training with an instructor, learn to build planes correctly - you minimize your losses but exceedingly few r/c pilots have never lost a plane. (I've lost one in 4 years or so of flying but I don't fly anywhere near as much as I'd like). You can think about where you want to put your plane but you have to get to the point where you can instinctively move the controls to do any maneuver you think of in under a second. If you can't it's called getting "behind the plane" which is bad (ie your thinking and planning to move your plane needs to be ahead). It's not rocket science but it's probably comparable to learning to ride a bike or ski or surf for the first time only if you get it slightly wrong your plane is history.
The last thing you want to do is risk your plane with an unreliable hack on the plane (or flight surfaces, or anything holding the plane together). It could cost you hundreds of bucks, days of work, and if your plane is gas powered or heavier than a few hundred grams it could hurt someone. (Fatalities are rare with smaller planes but not unheard of).
Also depending on where you live controlling your r/c plane with a radio that isn't designed and certified for it might not be legal even though the part of the spectrum you're using may be free to use (eg. 2.4GHz).
Frankly I haven't even gone to 2.4GHz. I know from having other devices on those frequencies that it's a noisy part of the spectrum. At the moment it's still quite new tech which is cool but I don't fully trust it yet for anything critical.
I've said it before: The US government and the IP lobbying groups can go frak themselves ten ways to Sunday on this issue.
Please cease and desist from using the word 'frak' as it is under copyright. Hang on I just used it. Oh....frak! Now Australia will be added to the list of "baaaaad" countries.
I have to disagree. Writing things right the first time almost never happens in the real world (and just leads to wasted time trying to think of the perfect method of designing a system). Typically you get 10x-100x improvements by rewriting the correct but slow parts of your code, or redesigning the system to work around the parts that are slow.
Get the design "right" in the first place. I've worked in the real world at major organizations. I've seen a lot of poorly implemented systems, and I've seen some excellent ones that did get it right first time.
If with every system you work on you have to redesign and recode and it gives you 10x-100x improvement, you're probably doing it badly.
In this case, 'rwPosition' I can easily tell is a row, and the reason I would want to know the row is that it is the "position" (presumably of some object I'm interested in the position of). "rowPosition" is ambiguous: is it the row of a position (as in the former case), or the position of a row (the more natural interpretation of the phrase in English)?
Without Hungarian notation, you need context to answer that question, which you ALWAYS need anyway if you're trying to understand a piece of code. What you don't need without Hungarian notation is training in understanding a variant of it. YOU might understand the variant, but can you guarantee that anyone working on or trying to understand your code for the next 20 years will have the same training? When you write code, you shouldn't just write it so YOU can read it. Any programmer should be able to pick it up easily. Hungarian notation was never a good idea.
Actually I wouldn't, my main beef as stated several times is that the police did not follow procedures which led to the pictures being leaked which was the breach of privacy
I already conceded that point, and said the officers should be disciplined. However I also said they definitely should be released according to procedure.
I was pretty sure I made that clear... but hey I'll give it another shot. We almost seem to agree on this issue except for your "fuck the family" attitude. Your words. Also you seem to be saying that this is censorship which it is not. Had it been released through the proper procedures it wouldn't be an invasion of privacy either, but it wasn't and hence it is. ...and I'll say it again. Fuck the family's feelings. Their daughter did something stupid in public that remains of public interest and serves as a warning to others who would do the same. Their feelings don't even come into play. No one should be asking permission to show these pictures because it was not something done in private.
Go see a movie like Saw or Hostile and look at your target audience desensitize themselves to images of gore.
It's different when you know the gore is fake Hollywood gore. Perhaps some people can't make the distinction (especially if they're not smart enough to avoid drugs in the first place). However some are.
Truthfully until you see something like this up close and in person it is just an image, there are other senses involved that bring it home if you see it in person. Hopefully you never have to see anything like that.
Sure but the body's not available for viewing in person to shock idiots who'd drug up and go for a spin. The pictures are.
Also just because the information/data is out there it doesn't automatically grant you a right to use it how you see fit and that is not always censorship.
Yet you on your high horse seem to feel justified preventing access to it because "you see fit".
These two points seem to be where we really disagree.
I suspect we'd disagree on much more.
Will this include XP as a VM for a year as well?
Yeah, that's about how long the poor old Pirate Bay's got left in it.
Your next one will cost kid, but you'll thank me for it later.
Being initially correct is far more important for nailing down what you are trying to do than being FAST.
If the algorithm runs too slowly to be practical, it is not "correct" in terms of fitness for purpose, even if it eventually returns the right results.
Premature optimisation is a sure fire way to shoot yourself in the foot. Who cares if a function that is called on a rather minimal basis is slow but understandable and easily verifiable as CORRECT?
"Premature" optimization? I'm not talking about optimising every loop here, but if your algorithm is designed using bubble sort and linked lists when what is needed is quicksort and btrees, it's a complete waste of time writing it one way then rewriting the other when you know the initial method will give you an unusuable system. What's more in the case of some algorithms a complete rewrite of the code is needed so you might end up recycling none of the code (If you're lucky you'll have learnt something relevant from the initial "unoptimized" attempt.
Write a prototype, *profile it*, THEN put on your optimisation hat.
Sure if a prototype is appropriate go for it, but even your prototype should be using the right general algorithms and ideally you should be able to reuse some of the code from your prototype (if possible).
I don't care how fast your code gives me incorrect output. ...and I don't care how correct your code is if I'll be long dead before it completes it's execution.
I give up. It's not our core business because you declare it to be, and you don't even know what we do. And on top of that, having to do it lots means it's something you shouldn't do. That's the opposite of reality. The more you do it, the more "core" it is. Your logic and your desired goals aren't the same. You've made up your mind and are grassping at straws to appear to have a logical means to get to your pre-determined end. That's not something that can be discussed. When you decide that you want to actually have a conversation (rather than a monologue where you happen to pause occassionally), let me know.
Dude, you're trying to justify a business that has nothing to do with networking making up network cables that can be store bought cheaply if the business is small, or bought in bulk if it's large, whilst insisting _I_ am grasping at straws.
Then instead of actually countering my perfectly valid points you'd rather take your bat and ball and go home, claiming I'm not having a conversation. I've addressed most of your points in detail. You're just ignoring it.
Regardless of whether we can agree on this conversation, I have to say "Grow the fuck up!".
In Vista you can go: Press Start button, type "word", hit enter. And you open MS Word using a CLI-like interface.
On XP try winword instead of word, oh and don't press the start button - try WindowsKey+R
Good Hungarian notation does exactly that, actually. Check out Apps Hungarian, which encodes the semantic type of the data, rather than the language-level data type.
Good explicitly LONG where appropriate variable names that don't conform to a complex set of rules that need to be memorized are ALWAYS a better solution.
# rwPosition : variable represents a row ("rw");
Awful! For one extra character you get rowPosition which is unambiguous and doesn't need to be looked up.
# usName : variable represents an unsafe string ("us"), which needs to be "sanitized" before it is used (e.g. see code injection and cross-site scripting for examples of attacks that can be caused by using raw user input)
unsafeName or unsafeNameString would be much better. It doesn't imply this name only applies in the U.S.A.
I'm old too but...
* Sorting algorithms
If you don't know them, you're not a programmer. If you don't ever implement them, you're likely shipping more library code than application code.
No, you're just focusing on the application instead of reinventing the wheel.
* GO TO and spaghetti code
goto is considered harmful, but it doesn't mean it isn't useful. Spaghetti code, yeah, that's the norm.
Did you just imply that harming yourself is useful????
GOTO is only good for getting around problems in the language. If you use it for anything else you're mad. If you're coding in anything modern this won't be an issue (but I'm not an advocate of throwing away working code because it's not fashionable so if you're maintaining an app you MIGHT have some use for GOTO).
* Manual multithreading
All the time. select() is your friend, learn it.
This one really depends on the application. I'm not in favour of automagic.
* Self-modifying code
Yup, I actually write asm code.. plus he mentions "modifying the code while it's running".. if you can't do that, you shouldn't be wielding a debugger, edit and continue, my ass.
Self modifying code is an abomination. Only useful if you've got less memory than a modern calculator.
Learning to use a debugger and modify running code that way is on the other hand a prime skill.
* Memory management
Yeah, garbage collection is cheap and ubiquitous, and I'm one of the few people that has used C++ garbage collection libraries in serious projects.. that said, I've written my own implementations of malloc/free/realloc and gotten better memory performance. It's what real programmers do to make 64 gig of RAM enough for anyone.
Memory leaks are a pain. It's not always your mistake either. The library. Someone else on your team. But yes even you coding otherwise brilliantly can overlook a memory leak.
* Working with punch cards
Meh, I'm not that old. But when I was a kid I wrote a lot of:
100 DATA 96,72,34,87,232,37,49,82,35,47,236,71,231,234,207,102,37,85,43,78,45,26,58,35,3
110 DATA 32,154,136,72,131,134,207,102,37,185,43,78,45,26,58,35,3,82,207,34,78,23,68,127
on the C64.
THAT I don't miss.
* Math and date conversions
Every day.
Agreed, unless there's a function in the standard library you'll end up doing it yourself unfortunately. Java is AWFUL for date conversion. (Since setLenient doesn't work the best solution I've seen is to convert and convert back to check, which is an awful kludge). What gets my goat is everyone doing 6 different ways instead of creating a library for your team to use.
* Hungarian notation
Every day. How about we throw in some reverse polish notation too.. get a Polka going.
Another abomination. With today's editors that's just not necessary!
* Making code run faster
Every fucking day. If you don't do this then you're a dweeb who might as well be coding in php.
No. You should never write code that runs like a dog in the first place.
* Being patient
"Hey, we had a crash 42 hours into the run, can you take a look?"
"Sure, it'll take me about 120 hours to get to it with a debug build."
This has never happpened in my career. Usually they want it debugged, fixed, and documented yesterday.
Some of those are obnoxious and good to see them gone. Others, not so much. For instance, sorting/searching algorithms, data structures, etc. Don't they still make you code these things in school? Isn't it good to know how they work and why?
Gone? Try writing a simple pause/delay function in Javascript without bringing the CPU to a grind.
Any time for historical or other reasons something isn't included you end up having to do it by hand.