|
You'll certainly have a rich supply vein to choose from!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I read your comment on my phone, and have sprayed beer out of my mouth onto the steering wheel
|
|
|
|
|
Sorry, but you shouldn't drink and drive 
|
|
|
|
|
Kenneth Haugland wrote: you shouldn't drink and drive
and he shouldn't play with his dammed either!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
The sole reason, I ditched all Desktops I had. I had a bunch of them at home and at work. I just hate fiddling with this particular issue. Sheer time waster. I started disliking Desktops very much, long ago.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
I've got a rumbly in my tumbly 
|
|
|
|
|
There was a time when Christian was the single highest poster in this forum, with a stellar reputation. And he had nothing but problems in his life and online - the world was out to get him. I'm seeing some parallels here.
This space for rent
|
|
|
|
|
|
That's even weaker than my wives old dell desktop. She bought it because it was no hassle... 
Then she found it wasn't good enough for her games she wanted to play so I got a GPU since it only had integrated. Then there was the little problem of lacking connectors of sufficient size of the psu. Was a 350W but only had a few 4pin connector and I think I needed a 6 or 8.
200W isn't even half a HP. You should get at least 800W psu because more HP = more speed which should result in better overall performance and speed of your work? ![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
Lloyd working at MNET in Brisbane here!
For whatever reason an internal new product I am working on must use the database server in Adelaide! 
(Only 6000 km away!...)
Today our sales people are demoing this new product to a bunch of government people.
For some reason, let's call it Murphy's law, the Adelaide IT people apparently decided that today was a also good day to shutdown the database server VM my new application is using....
The rest, as they say... is (unfortunate) history... 
|
|
|
|
|
Picture[^]
William : Lets do the scene where Luke finds out who his real Father is
Harry : F*** off William.
modified 19-Apr-16 20:24pm.
|
|
|
|
|
Is it just me or does the garage at Windsor Castle look a little rough?
There are two types of people in this world: those that pronounce GIF with a soft G, and those who do not deserve to speak words, ever.
|
|
|
|
|
Such a surreal scene. All it needs is Ricky Gervais smiling in the background.
|
|
|
|
|
Harry would kick Will's ass all the way to Jericho, Star Wars or not.
|
|
|
|
|
Took them 10 years to write.
|
|
|
|
|
Good God!
Their documentation is actually readable!
They must be cr@p programmers, then.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
You must not be familiar with plain English programming. Where the code can also be the documentation.
|
|
|
|
|
Kidding, right?
Back when I was a COBOL wallah, my code read like plain English.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
|
Yes, I got an edgy feeling from the way he immediately jumped on the "plain English" bandwagon.
However, it's a topic worth discussing, so I'll reply to you and totally deaf him/it (it's not a "her") out.
The problem with the plain-English brigade is that they don't seem to realise three things:
0. Code that reads like English is no help to anyone, because it still has to have syntactical boundaries, which will have to be exponentially more complicated than those of "normal" coding -- e.g. there will still be syntax errors, but they'll be an absolute sh1t to track down, because, well, it reads OK, doesn't it?
1. Being able to read the code like normal language doesn't help you code things, and is in no way a replacement for documentation -- i.e. by the time you've read through seven million lines of code and still haven't found the function that you need, you'll be begging for documentation. It will, however, make developers even lazier, when it comes to writing documentation ("Hey, just RTFC*, you dumbass!")
2. To create a truly effective plain-language interpreter/compiler will take tens of millions of man years -- but most of those man years won't be spent by people who are trying to make a plain-language interpreter/compiler. Classes/Interfaces/libraries/frameworks will be written for other purposes, and can just be imported, so the guys who are involved in plain-language coding development have Really got to learn to play nicely with the other kids, which they Really don't do now.
* "Read The appropriate portion oF the Code")
[edit] fruggin' typos!
I wanna be a eunuchs developer! Pass me a bread knife!
modified 19-Apr-16 14:48pm.
|
|
|
|
|
I'd agree with you - but most of the problem is that English (and French, German, Spanish, Chinese, ...) are "natural languages" - i.e. they weren't designed but evolved through use; as a result they are spectacularly redundant, inefficient, and imprecise. The exact opposite of what you need for a programming language!
In addition they are for separate functions: natural language conveys meaning between two equal (or roughly equal) intelligence sapients - programming languages are about instructing only, without any sense of the "meaning" of the instructions being imparted.
While you can instruct in a natural language, it takes a huge amount of "code" to get anything done - unless you have already installed the subroutines into the target individual via training (which takes forever!) 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Precisely!
The variations that have to be built into the syntax make it a minefield of "incorrect syntax" notices, because how the Hell are you to know when you're going wrong, when you're told "Just do English"?
And, as you say, making it multi-lingual would be a nightmare -- e.g. the Dutch conditional term (the English-language "if") translates to "when", but "when" would used for something else. And there would be millions of such "natural" errors.
And the worst part about English is that, although it seems that there's lots of redundancy, because it has lots of synonyms, each synonym for each word has nuances and/or usages that the other synonyms don't have, and many of those nuances/usages would have to be built into the "plain-English" language, so that'd be another minefield, where you can't know if you're using the right synonym unless you read a couple of million lines of the base code.
Still, our little friend should have realised by now that he's trolling people who know what they're talking about, so I'll quit the thread -- unless, of course, real people find it an interesting or fun thing to talk about.
I wanna be a eunuchs developer! Pass me a bread knife!
modified 19-Apr-16 15:21pm.
|
|
|
|
|
Clapclap won't clap anymore. He's gone for good.
|
|
|
|
|
He'll be back...like a nasty smell.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
