Pages: 1 [2]   Go Down
Author Topic: Parallel LCD display  (Read 2342 times)
0 Members and 1 Guest are viewing this topic.
Central MN, USA
Offline Offline
Tesla Member
***
Karma: 72
Posts: 7171
Phi_prompt, phi_interfaces, phi-2 shields, phi-panels
View Profile
WWW
 Bigger Bigger  Smaller Smaller  Reset Reset

Quote
boy, was I wrong about that

You are not wrong at all: we all use products from a multi-billion company founded on BASIC.

Magic of licensing. Don't ever sell!
Logged


Dallas, TX USA
Offline Offline
Faraday Member
**
Karma: 63
Posts: 2649
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

Quote
boy, was I wrong about that

You are not wrong at all: we all use products from a multi-billion company founded on BASIC.

Well... Yes and No. The underlying code needed to actually implement the BASIC interpreter
was not written in BASIC.

Even more comical is that in the late 80's and early 90's when NT was being developed,
it was done in C, using GNU tools running on MIPs UNIX machines.

--- bill
Logged

Georgia, US
Offline Offline
Jr. Member
**
Karma: 2
Posts: 84
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

WOW! after those previous comments, I feel like I've been chastised and redeemed at the same time.
So what do yall think of someone who took RPG instead of Pascal?
Logged

Offline Offline
Edison Member
*
Karma: 116
Posts: 2205
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

I wouldn't worry too much about that.

The key is if you can write superior code.

Some people mistake using good tools for writing good code (the "C worshipers"). For those people, no amount of good tools can compensate for their inability to write good code.

Logged

Dallas, TX USA
Offline Offline
Faraday Member
**
Karma: 63
Posts: 2649
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset


The key is if you can write superior code.

Actually, I think it is more about the design and algorithms in the overall system
rather than the coding itself.
And design/algorithms are completely independent of the language used.

Coding is a very small part of an overall project and
IMO the actual language used is pretty irrelevant.
You can have brilliant, excellent, fast, and superior code within individual components
but put the pieces together in a poor design and the system will not work very well.

I used to have a saying, I used quite a bit in the past:
"Better algorithms, beats faster code every time".

i.e. a much better algorithm or system design written in interpreted BASIC could potentially
outperform a poor design written in assembler.

The moral is spend time up front to examine the system as a whole
and deal with things at a system level (before coding)
rather than try to optimize things down at the function/coding level.

Sometimes there are unknowns where some experimental trial/error coding is necessary
but those are often not the norm.

--- bill
Logged

Pages: 1 [2]   Go Up
Jump to: