Now #golang has a supply chain security problem.
Github actions, terraform, go.... hmm, what do we got in common here.. treating git endpoints as trusted. But git endpoints can't have any central authority to check for malicious code! At least at #pypi you can report a package as malicious.
https://www.youtube.com/watch?v=EyO_SMl2YBk&ab_channel=CodeHead
Ok, it was easier to find modern programming practices for bash than for #GnuCOBOL - maybe it is more fun with the paid versions of COBOL.
- lint? compiler warnings
- unit tests? Sort of? Couldn't get 'em to work
- package management? where?
- "awesome cobol" directory? more like awesome 404s
Now for the same app in #golang
- it is so fast
- syntax is nice
- format, lint, docs are built in
- modules and packages ... they still don't click with my brain
- can implement a richer game for the same effort than cobol or bash (and I'm not even writing the code here)
And now for #ruby!
<insert I don't know I'm doing dog here>
I'm convinced I didn't set up a venv correctly and I just installed all the dependencies to the system ruby interpreter.
Everything else was easy and modern feeling.
And now for cpp (pain!) using #clion (nice) and cmake (pain!)
C++ is the COBOL of 2024.
- unpleasant
- still relevant because of legacy code bases
- would be laughed off the stage if introduced today
I couldn't figure out how to run cmake from the terminal. I think I'd have to write a CMakeCache.txt by hand (that finds the toolchain) and not clear it works with git-bash.
Alright, moving along & being more careful about how I tag my posts (It appears a tag means, "I want to fight with strangers, anything critical is actually an insult to you & your ancestors")
**Vanilla Javascript! **
- It is less painful than it was in 2013. Sort of. Took a few tries to get modules right.
- Packaging *a website* is still adhoc
- jest with JS made me miss TypeScript because mocking seemed to just work with TS, but not for vanilla js modules
- live demo!
We're up to Angular! The build script is not done, but no one is paying me to finish it,
- Typescript is good. The Vanilla JS people are wrong.
- Bots have a hard time with Angular because it is fundamentally LOTS of pages.
- Feels like the componentization is a lie. All the parts need to know about each other.
- Uh, it is snappy.
- Helps pay the rent and mortgage for people on my team
Now for #rustlang
- batteries included (format, lint, package mgmt)
- bot needed two tries get borrowing & ownership right
- wait, what, already done?
Unlike a certain other language/build system I won't mention because they'll hound me in the comments...
Rust doesn't feel like you are getting continually punched in the face by a developer that hates you.
After this experiment, 95% of my native coding effort is going into rust & go. (not c/c++). Devex matters, huh.
https://github.com/matthewdeanmartin/isopod_rust/blob/main/isopod_adventure/Makefile
#chatgpt I had Assistant write me a bunch of console fish tank apps & the #Golang
worked the best.
An emoji fish tank needs
- work on windows
- handle 2-byte emojis
- fast & low-level helps prevent flicker
Honorable mention to
- python
- ruby
- JS/HTML.
Dishonorable mention to
- c (unicode support is crap)
- lua (no batteries included)
- bash (is this even a language?)
- powershell (Assistant wrote bad ps1 & I couldn't fix it)
I suspect Rust would have done well for the same reasons as Go (modern native code) but I ran out of time to learn how to compile & run it.
Calling #golang from #python is a no-go. It can be done but requires go->cgo->c/c++->cython->python and you still need to have excellent knowledge of c & c++ type systems.
And for all that effort, it is slower than a python-only solution.
https://www.youtube.com/watch?v=ILfPgkqdSYc
FYI- The hash tag for R is #rstats , for C# #csharp for C++, #cpp , for C? Dunno, #clang means something else. Go is #golang F# is #fsharp