Do you use G languages when coding?

[MrSmithers]

Originally posted by: Ameesh

Originally posted by: FrustratedUser

Originally posted by: Ameesh

Originally posted by: FrustratedUser

Originally posted by: Ameesh

Originally posted by: FrustratedUser
I develop exclusively in LabVIEW for our measurement systems.
The code is close to as fast as compiled C/C++.

If you do use graphical languages, which do you use?
If not then why and what do you think about them.

no i don't use graphical languages because the software i develop is more mainstream and performance sensitive. I think graphical languages are good for somethings but lame in general because they don't give the developer enough control of the inner workings of systems. You are fundamentally limited to the types you have at hand and the types you can build using composition. Basically its good for n00bs and very specific tasks.

LOL
What do you mean by 'inner workings of a system'?
Basically WTH do you mean?

I mean stuff like, pointers and memory, thread pools, file handles, interupts, cache optimization, network protocols, vtables, inheritence, etc.

With graphical languages most everything is abstracted from you and you get these nice little objects that someone wrote for you and you basically connect the dots. The guy who wrote the compiler and the IDE for your G language set is programming, you playing connect the dots is not.

I don't fully agree with you here. First of all I do not want to now about pointers and memory, I wan't to get a product done. The code runs as fast as any other compiled code but I get it done faster.
Second, I have plenty of control over network protocols, databases or even memory if I want to.
Saying that I am not coding is not true. The same rules of design apply to me in every way.
I get what you mean but do not agree 100%.

Its nice that you don't want to know about pointers and memory allocation, but those are the fundamentals of software creation. The fact of the matter is that pretty little gui you are using and the backend software that generates the code that you run from your pictures is most likely all written in C/C++, those little objects you drag and drop from the toolbar are objects that are being built up in some language that does care about memory allocations , the very task of dragging and dropping involves interputs, pointer arthimitic, user mode kernel mode bridging, etc. thats where the real programming is going on. kepp in mind i am not saying that the work you do is trivial, it maybe difficult in its own right but its definetly not programming it just seems like it.

Ameesh, how is that any different than saying that you coding in Java/C/C++/whatever isn't really programming. In order to have maximum control over things, and be able to have to power to code things with maximum efficiency we would have to code in a machine language. It seems that at some point, a compromise has to be made in the form of usability vs. power/speed. It is just that different people choose to make that comprimise at different points along that curve.

Smithers

 

I code all my high end applications in QBASIC

btw, am i the only tard here who gets ameesh and electric_amish mixed up?

 

[Brutuskend]

I do.

"G, I have NO IDEA what I'm doing..."

 

[dighn]

probably good for specialized purposes like instrumentation and measurement in the case of labview. i doubt it's as flexible as a non-G language.

 

[FrustratedUser]

Originally posted by: Ameesh

Originally posted by: FrustratedUser

Originally posted by: Ameesh

Originally posted by: FrustratedUser

Originally posted by: Ameesh

Originally posted by: FrustratedUser
I develop exclusively in LabVIEW for our measurement systems.
The code is close to as fast as compiled C/C++.

If you do use graphical languages, which do you use?
If not then why and what do you think about them.

no i don't use graphical languages because the software i develop is more mainstream and performance sensitive. I think graphical languages are good for somethings but lame in general because they don't give the developer enough control of the inner workings of systems. You are fundamentally limited to the types you have at hand and the types you can build using composition. Basically its good for n00bs and very specific tasks.

LOL
What do you mean by 'inner workings of a system'?
Basically WTH do you mean?

I mean stuff like, pointers and memory, thread pools, file handles, interupts, cache optimization, network protocols, vtables, inheritence, etc.

With graphical languages most everything is abstracted from you and you get these nice little objects that someone wrote for you and you basically connect the dots. The guy who wrote the compiler and the IDE for your G language set is programming, you playing connect the dots is not.

I don't fully agree with you here. First of all I do not want to now about pointers and memory, I wan't to get a product done. The code runs as fast as any other compiled code but I get it done faster.
Second, I have plenty of control over network protocols, databases or even memory if I want to.
Saying that I am not coding is not true. The same rules of design apply to me in every way.
I get what you mean but do not agree 100%.

Its nice that you don't want to know about pointers and memory allocation, but those are the fundamentals of software creation. The fact of the matter is that pretty little gui you are using and the backend software that generates the code that you run from your pictures is most likely all written in C/C++, those little objects you drag and drop from the toolbar are objects that are being built up in some language that does care about memory allocations , the very task of dragging and dropping involves interputs, pointer arthimitic, user mode kernel mode bridging, etc. thats where the real programming is going on. kepp in mind i am not saying that the work you do is trivial, it maybe difficult in its own right but its definetly not programming it just seems like it.

I see where you are coming from but in my case there is no time in the project to have to worry about that very low level time consuming stuff. For me it's like building your own lawn mover before you cut the grass instead of just buying one and cut it.
If there is something really really time critical I could code a dll and use that instread. I've not been needing to do that yet.