mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

12K
active users

#programminglanguage

2 posts2 participants0 posts today

"[Rust is] Technology from the past come to save the future from itself.

Many older languages [are] better than new ones. We keep forgetting already-learned lessons."

- Graydon Hoare, during Rust's initial release

Replied in thread

@serge That said: I now predict that #COBOL will make a comeback.

#GCC 15 integrated a COBOL frontend,¹ and #GNU COBOL 4 seems to make the performance no longer atrocious² compared to the damn expensive proprietary COBOL compilers.

And that’s likely a game changer for many huge, mission critical codebases.

¹ gcc.gnu.org/gcc-15/changes.htm
² sourceforge.net/p/gnucobol/dis

gcc.gnu.orgGCC 15 Release Series — Changes, New Features, and Fixes - GNU Project

TypeScript is dogshit

I’ve been meaning to get this off my chest for a while now — TypeScript sucks.

I know this will hurt many passionate opinionated snowflakes out there, but there, I said it. Fuck TypeScript. You love TypeScript? Great. Good for you. I hate that so much of the frontend tooling has migrated over to it.

TypeScript has singlehandedly ruined my love for frontend development. There’re already hundreds of tools for the frontend development experience (DX). Adding one more isn’t the problem. The negative impact it has on the DX is. The extra compilation, the general vibe of coding in TypeScript, the added mental load when starting new projects, the extra language on top of something you could totally code in etc.

If TypeScript were a language by itself, I wouldn’t mind it. I’m ok with the language. But…it’s a language that compiles to another language and that language is what gets used in the browser. Don’t give me the “why bother writing C? Why not just write Assembly?” argument. Shove it up your ass. That’s one of the dumbest, ill-informed arguments ever.

First it was CoffeeScript, then Babel, then TypeScript. They are all different, but have a lot of similarities. One main trait they all have in common is the degraded DX. IMHO, Babel did a lot good in pushing JavaScript and helping keep up with the latest syntax and other good stuff.

TypeScript is more focused on types in JavaScript, but it does add several other language features. Picking up TypeScript is quite straightforward. Barely a few minutes, really. But the dev overhead, my goodness. It’s no fun.

Simply put, it lacks taste.

I 100% agree with DHH on his views around TypeScript.

For me, TypeScript doesn’t spark joy. It sparks darkness, misery, self-loathing, and depression. I have to use it at work, so I’ll use it. In my personal projects though, I just won’t.

I've finally done it. I have designed my own programming language (it was only a matter of time). After almost 3 months, ProtoGraph, a language that compiles into ProtoFlux on Resonite is finally taking shape.

It's in beta, and I'm sure there is a ton of work remaining to make it lovable, but I'm quite satisfied with the progress so far. If you play Resonite you can check out the world showing some examples at
ProtoGraph v0.10.0.

I also have a wiki documenting the language:
ProtoGraph Language Introduction

#Resonite #ProtoFlux #ProtoGraph #programming #ProgrammingLanguage

While it has its own issues, there are several good reasons why my favourite #ProgrammingLanguage in the real world is #C

Why not #Go?
Because it's from #Google.

Why not #Csharp or #Fsharp?
#Microsoft.

Why not #Rust or #Zig?
#LLVM (aka #Apple & friends).

Ultimately, most of languages I avoid like the plague are controlled by #BigTech one way or another.

C is simple enough to get several alternative compilers based on useful standards.² ³


¹ In theory I still prefer #Oberon07, but when I want to code something useful I still use C instead to lower the entry barrier for other devs, because there are too many incompatible implementations of the compiler and "standard" library.

² Ok, #Python, #Scheme and #Lua have similar qualities, but for the tools I write I usually prefer binary executables with no runtime.

³ No, #C++ is not an option. 😉
harmful.cat-v.orgBjarne Stroustrup: "I Did It For You All..."

I think a lot of my issues learning other languages are because I'm so used to how simple the syntax in #C is that any other #ProgrammingLanguage looks so syntactically complicated that I don't know how the fuck anyone gets anything done I literally jumped ship from #Java super early in my learning programming because I hated that every.Single.command.wasA.fucking.DotReference.withArbitrarycasingToo

And I think that's a big part of my woes with the #Rust compiler. Even if I didn't have problems with the occasionally misleading wording, it's so gods damned verbose and there's so many warnings that are literally just you doing styling things it doesn't like that I have to scroll through multiple pages. I had a error on a fucking Hello World programme that was five lines long and implied a syntax error when it was an issue with how I installed it.

If there was a Yet Another C Killer that didn't throw errors because your one-word variable isn't snake_case (this actually happened to me the time before last I tried to learn Rust and appears to have been patched since then, but the fact that this was a warning that was enabled by default with that glaring of a readability issue baffles me given how big the project is) and didn't need five lines for a basic syntax error, I'd start learning that now.

There has to be a better way than:

ERROR: we expected there to be a semicolon (this symbol: ";") at line 420, character 69
But there was none!

Hint: add a semicolon to line 420, character 69, like so:
println!(" The classic print to console to make sure the function ran...");
^ this thing right here

Could we not just have:

ERROR on 420:69, missing semicolon. Maybe you forgot one?

I wanted to know if I could still program in languages I haven't used in 10+ years, so I found a tech test on Glassdoor and did it six times... in six different languages.

🔗 More: danq.me/lru-cache-challenge

Here's what I learned:

🧠 Programming MORE languages can make you better at ALL of them

👍 With solid fundamentals, you never truly forget a language

😵‍💫 Switching between some pairs of languages causes brain-gearshift problems

Dan Q · I Wrote the Same Code Six Times!Could I rock an interview tech-test in a programming language I haven't touched in a decade? I wanted to know, so I found a tech-test... then solved it in six different programming languages in a single sitting.