|
True
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
... because most still don't torque wheel nuts right (the mechanic or the tool?). You need a breaker bar to loosen them.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
FoxPro... starting from v2.0 for DOS all the way through v2.6 for Windows. 
|
|
|
|
|
I worked on the worlds largest and longest running ( to date ) liquidation for 21 years, all the claim handling and payment systems where written in Foxpro for DOS. It performed brilliantly and never let us down.
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
gwbasic, as it is better than python 
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Gee Wiz basic
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
Better than Phyton, innit?
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
honey the codewitch wrote: Do you secretly love Perl?
Certainly not ashamed about it.
But I don't expect anyone else in the group to use it or even understand it. If I must create a tool for others to use then I extensively document the usage.
And I comment the code extensively too. Not just why the code is doing something but explaining what the code actually does (the sort of comments that should not normally appear in code.)
|
|
|
|
|
jschell wrote: (the sort of comments that should not normally appear in code.)
Hey, if it doesn't bother you that it's necessary to do that with Perl, far be it from me to judge.
Every time I even read Perl I feel like I need a shower. 
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
I recently wrote a script to reset and fix the display layout when I switch between laptops using a KVM switch and multiple USB hubs. I wrote one version in Perl and one in PowerShell. I like the Perl one better.
I'm definitely not ashamed to say I still like and use Perl. 
@x=qx{pnputil /enum-devices /problem};
for(@x)
{
if(/Instance ID:\s+(.+)/)
{
system qq{pnputil /disable-device \"$1\"};
system qq{pnputil /enable-device \"$1\"}
}
}
pnputil /enum-devices /problem|select-string "Instance ID"|Foreach-object {$_ -match "Instance ID:\s+(?<root>.*)";$x = $matches['root'];Invoke-Expression -Command "pnputil /disable-device ""$x""";}
modified 3-Nov-23 20:25pm.
|
|
|
|
|
honey the codewitch wrote: if it doesn't bother you that it's necessary to do that with Perl
I know C#, Java, C++/C. And have delved into many others like assembler, Pascal, Fortran, Basic. I have looked at even more than that.
When I choose Perl it is because it is going to be better for the job. I could do it in some of the others but it would take longer. Especially when I present it as a solution that others will need to use I consider the tradeoffs very carefully.
|
|
|
|
|
As long as I'm a user of a language, which pays my salary, and not the creator/designer of that language, there's nothing to be ashamed of. Each language has its own beauty and ugliness, and everything in this world is like that, isn't it?
|
|
|
|
|
I was able to achieve "flow" with COBOL, so no.
PERFORM VARYING ... FROM ... BY ... UNTIL ...
versus
for (int i = 0; i ..) or
while ( ... )
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
It's ancient and dated, but I still have a fondness for hpl, Hewlett Packard's custom language for their early desktop computers. There was a lot that it couldn't do, but there were a couple of things it could do that made it perfect for its intended application. Back in the day, when we had RAM measured in kbits, programs had to be very short. In hpl we had the command chain that would save the program state and start a new program where the first left off. This essentially allowed programs to be written that were far larger than the machine could accommodate, up to the limit of the disk space available.
A second feature made my in-house reputation as an engineer soar; the keyboard key, store was storable, and could be executed at runtime. Since I was developing automated missile test software and hardware meant to be used in a noisy factory environment, ambient electrical noise was a constant problem. I wrote a code block that I used in almost all applications that would measure the local noise, run an FFT on the samples, create a custom filter subroutine to remove that noise, then add the resulting filter program to the actual test program as a pre-processor on the measured data. The accuracy of testing was vastly improved.
Sadly, hpl met with an untimely death, like all good things, it seems. Unlike every other popular language at the time, its instruction set was entirely lower case, which mainline programmers couldn't accept. If it wasn't written in capital letters, it couldn't possibly be any good. By the time HP introduced the HP9845 desktop computer, hpl became optional, and HPBasic replaced it as standard. Things kinda went downhill after that...
Will Rogers never met me.
|
|
|
|
|
I am NOT ashamed of this language it was my go to for my Palm Pilot
NS Basic
I often wonder if anyone here ever used this dialect of Basic ?
|
|
|
|
|
VB6 and VBA, have actually created some really cool apps for automating hardware tests, real time fft displays, animated data plots, etc. My former employer still uses VBA code I wrote nearly 20 years ago in Excel as convenience apps for myself as part of new product performance validation for FDA approvals. 
It was broke, so I fixed it.
|
|
|
|
|
|
I loved MS Visual Basic v3.
It was my first exposure to GUI programming. VB was the gateway drug of coding.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
honey the codewitch wrote: For me it would definitely be VB6
Upvoted for being courageous enough to admit this here or on any coder's forum! 
I agree 100% with you. VB6 might be old and ugly but as long as MS is shipping the runtimes with the OS, those executables will live on and some developers will continue to support those products/projects.
I came back to programming in the late 90s and got my first job doing VB6/Classic ASP development. To keep a long story short, I am still at that company and we still lots of active VB6 projects. (likely > 1M LOC across 2 largish apps and 100 or so 'add-on modules') Those apps are getting migrated as time allows which means very slowly!
In the past I've hired 2 jr. developers for migration only, but neither worked out. Perhaps I just haven't found the right one...or I'm impossible to work with.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
If you're still using VB6 and you want to make your apps pretty check this site out
vbAccelerator.com - Advanced VB, C# and VB.NET Source Code and Controls[^]
He produces some quality controls for VB6 with professional look and feel. It's aces. I learned a lot back in the day from just looking at his code.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Windows Batch.
It's my dirty little secret.
cheers
Chris Maunder
|
|
|
|
|
I loved Visual FoxPro. Fast, easy to use, great community.
MS killed it to force VFP developers to move to SQL Server.
Good business move for MS. A shame for everyone else.
|
|
|
|
|
I liked the language of FoxPro 2.6 for DOS. Unfortunately it died a lot with "corruption detected" on a network where Clipper 87 marched like a Roman legion.
|
|
|
|
|
Why and for what should I be ashamed here? I've been able to pay my bills and live a good life with it all these years.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
