• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Do you use G languages when coding?

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.
 
The only graphic language I use is "// COA", short for "Cover Our Asses".

I find it's a lot more humorous if you find ways to be just as foul as you would be using 4-letter words without using those words.
 
G languages? Are there XXX-rated languages for coding porn sites and G languages for coding kid-oriented sites now? 😉
 
I use the resource editor for VC++ work, which is visual form layout though only the skeleton of visual code generation.

"G languages" have been being promoted for "writing programs without wriitng code" for at least a decade now (probably a couple of decades), but they've only ever been practical for very narrow problem domains like "visual database design," in other words as not much more than a front-end to a fairly constrained special-purpose app or engine.
 
Originally posted by: DaveSimmons
I use the resource editor for VC++ work, which is visual form layout though only the skeleton of visual code generation.

"G languages" have been being promoted for "writing programs without wriitng code" for at least a decade now (probably a couple of decades), but they've only ever been practical for very narrow problem domains like "visual database design," in other words as not much more than a front-end to a fairly constrained special-purpose app or engine.

In my case (instrument control, measurement systems, graphing and some number crunching) it is really great.
Development time is low compared to VB which they use to use. But the tools are relatively expentive compare to traditional compilers and libraries.

I say :thumbsup:
 
I've used G in Labview before. Hey FrustratedUser, if there are any job openings in your workplace for a G programmer, let me know.

"G languages" have been being promoted for "writing programs without wriitng code" for at least a decade now (probably a couple of decades), but they've only ever been practical for very narrow problem domains like "visual database design," in other words as not much more than a front-end to a fairly constrained special-purpose app or engine.
I have to disagree. I think graphical languages have failed to catch on simply because few people have ever tried them. Talk to 10 programmers and you'll have spoken with 10 people that have never tried a graphical programming language. They're not a panacea but they certainly could have a bigger role than they do.
 
Originally posted by: zephyrprime
I've used G in Labview before. Hey FrustratedUser, if there are any job openings in your workplace for a G programmer, let me know.

"G languages" have been being promoted for "writing programs without wriitng code" for at least a decade now (probably a couple of decades), but they've only ever been practical for very narrow problem domains like "visual database design," in other words as not much more than a front-end to a fairly constrained special-purpose app or engine.
I have to disagree. I think graphical languages have failed to catch on simply because few people have ever tried them. Talk to 10 programmers and you'll have spoken with 10 people that have never tried a graphical programming language. They're not a panacea but they certainly could have a bigger role than they do.

Agreed. It is a completely different way of thinking.

If I see any job opening I'll let you know.
 
Sorry I can't help. When I did LabView stuff (7 years ago) I don't think G was around (or maybe my mind is just going).

Dave
 
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.
 
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?
 
Originally posted by: FrustratedUser
Originally posted by: Apathetic
Sorry I can't help. When I did LabView stuff (7 years ago) I don't think G was around (or maybe my mind is just going).

Dave

LabVIEW is in the G group.
😉


LOL - that tell's you how much about it I remember! It's been a long time and I only used it for about a year. We eventually decided not to use it as it was too expensive to license (we were writing training simulations and would have had to pay large royalties for each copy of the software we sold).

Dave
 
Originally posted by: GhettoFob
I thought this thread was about coding in ebonics..

😀 :beer: Me too.

void main_fool(int wassup[brotha])
{
check_dat(wassup[fugga])
{
if(wassup[capped_in_da_azz] ain't hoppin)
get_the_fvck_out();
}

check_ya;
}
 
My e-commerce class made us use VS.net to produce our commerce sites to interact with an MS SQL db. What was really sad is that all the code-behind functionality of the page, we ended up doing by hand because the drag and grop functions it built were crap and didn't work the way they should have. It was a pain...about the only cool thing it did well was make the definitions for on-event handlers. That's about it. I feel like I can accomplish more coding it myself, not the drag and drop way. Just MHO.
 
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.
 
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%.
 
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.
 
Back
Top