PureBasic Forums - English

GedB wrote:Well, there is BackColor

I don't get it. What's wrong with this one?

Fred:

Not exactly a spelling mistake but...
Forever is one word, so shouldn't it be "Forever" instead of "ForEver" as it is 8O?

heheh

-Shopro

Color is the American spelling.

The correct English spelling is Colour.

Still, Fred is not alone. The Miriam Webster dictionary describes 'colour' as a 'British variant of color'.
How can you have a 'British Variant' of English? Can you have a German variant of German or a French variant of French? Surely the English spoken by the English is the original, not the variant!

I'm in one of those moods this week.

Go for it, GedB!

Imagine:

or (our)
hor (hour)
flor (flour)
sorces (sources)

hehe.

And to go completely OT on this misplaced thread:

http://www.kuro5hin.org/story/2004/2/15/71552/7795

The spectrum was better than the Commodore 64.

The Amiga was better than the Atari ST.

PureBasic is better than DarkBasic.

... but these are all obvious facts, GedB -- what was your point?

GedB:

See the history in the help file:

4 April 2002 : Version 3.00
- Changed: Renamed BackColour(), FrontColour() and TransparentSpriteColour() to BackColor(), FrontColor() and TransparentSpriteColor()

See, it was like that in the past... and changed.
Guess why? No computer language names it's commands after the brittish spelling

Timo

.. which, in fact, tells you more about the poor state of the English grammar in the world, than the (programming) languages itself... :p

In this case neither is right or wrong - they are just different. Grammar isn't in the word itself, but in how you use it!

I've been speaking and writing English (American) my entire life and I still suck at it!

Com'on... DB has it's place too, seriously it does.. it's the prime example to both Mark & Fred of, a ) what happens when you screw it up, b ) how _NOT_ to do things , it's also a good grounds for finding out about either language, that being Pure or Blitz, that's how I found out about blitz actually.

Timo,

Now that is funny.

Now I've got to get back to writing my programmes.

GedB wrote:The Miriam Webster dictionary describes 'colour' as a 'British variant of color'

Miriam? Do you mean Merriam?

GedB wrote:I'm in one of those moods this week.

So am I

Inner has a point.. Fred and Mark should use DB as a reference..
Give a link or something, when they want to show ppl how *NOT* to do stuff..

I really like PB and am a registered user.

I am at a crossroads where I will be deciding what technologies to use for the Version 2.0 product my company produces.

I would like to use PB for key components of the next version of the software my company develops. The existing version is built mostly in VB6 and the extreme bloat of the .net framework kind of makes me feel sick so I would like to avoid the .net option. (Java is also a contender.)

From a purely technical standpoint PB is a great choice for the product.

This is a real bet the company/bet your job type decision.

My concerns with PB are as follows:

1) A sustainable business model, in other words (flamesuit on) I think the existing customer base who wants to see PB continue to be developed could buy Fred a pizza once or twice a year. (i.e. annual or semi annual donation/support fee of 20$ or some other reasonable amount.)
I would be more than willing to give Fred $20 once or twice a year to ensure that the time I invest in coding in PB will be somewhat protected.

2) OS insurance. In other words I would feel much more confident about choosing PB if I had a high confidence that the code I write will continue to be useful under WinFX (Win32 successor) and or Linux if that where to become a major player on the desktop.

3) Summary

Advantages:
PB - Speed, Size, Distribution, Community
Java - Platform Insurance
.Net - Longhorn / Microsoft Insurance

Disadvantages:
PB - Small company, Longhorn Uncertainty, Financial Uncertainty
Java - Dependant on Sun (Future uncertain), bloat /performance issues?
.Net - bloat/performance, Microsofts noose around my neck.

I would appreciate any thoughts that might help me to make my decision.

code I write will continue to be useful under WinFX (Win32 successor) and or Linux if that where to become a major player on the desktop.

The next Windows will have to have some sort of backward compatibility, or it ain't going anywhere... in other words, I can't imagine PB stuff is going to stop working on it...

Well I think there is a full demo of the language isn't there? Just like any of these other languages if you try it and its not complete and you buy it, your the only one to blame.

How can you try out a product when you pre-order it before a demo version is out you moron! If you bothered to read my post you would see i had it delivered on release!

Like I said, I answered the perons question at the begining of this thread. Thats all I was trying to do, but unlike Kale here I don't go over and make entire new threads of flames out of nothing.

I have been complaining about DB over at their forums and by email for about 1.5yrs because due to false advertising and false product description i have lost both money and time! I feel i am entitled by right to do this!

If Kale put all that destructive energy into putting out docs instead of making new threads just to flame a product that he didn't have sense enough to try in the first place, we could have some very well documented functions and code that many of us including me could use in our own programs.

Hardly destructive! and whats all this about me and docs? i'm not involved in any writing. BTW What have you done to help the PB community?