@danjac I still have a couple of SPA’s to manage that are about 9-10 years old. Written in #CoffeeScript 1 (not too bad) and #BackboneJS with a #Perl #Mojolicious backend.

Getting to run the JS dev stuff and keeping it up to date, or rather working with a newer Node version is challenging. Looking back it being a SPA doesn’t do much for 85% of these apps. I should’ve used some #jQuery instead for the interactive parts. That way I could’ve moved to #htmx without any issue.

Another cool presentation from TPRC. Ingy talks about a #coffeescript style destructuring syntax for #perl which he hopes to introduce as a core language feature: https://youtu.be/ifoYsubNRj4

Destructuring allows you to dereference and assign elements of a data structure in one go. Rather than have multiple assignment statements, you can reference key names and apply names to array elements by appropriately structuring the LHS clause of a single assignment statement.

WIP: https://metacpan.org/dist/assign/view/lib/assign.pod

Can anyone recommend a good #RubyLang #SDK for working with #GoogleAppsScript? I'd prefer to avoid working directly in #JavaScript, but transpilers like #CoffeeScript and others have their own problems.

Back when Bruce Tate was inviting people to learn a programming language per year, I thought it was silly, but seeing people getting stuck in a single ecosystem, I can see the point.

I'm primarily a #Scala dev, as I love the language & ecosystem. My profile usually doesn't say that I've also worked professionally w/ #Python, #Ruby, #PHP, #Perl, #CSharp, #JavaScript, #CoffeeScript, #TypeScript, #CPP, #Bash, others.

It's in the job description 🤷‍♂️

Just learned about #civet (aka #CoffeeScript for #TypeScript, https://civet.dev).

Haven't formed an opinion on it but once I figured out the origin of it's name I burst out laughing 😂

I unabashedly loved CoffeeScript and still do. I even had a little fork of CoffeeScript 2 where I integrated a rejected PR for CS 1 to add the pipeline operator, but they were all just impractical fun compiler exercises. So imagine my surprise when I saw that someone had reached up inside my brain and pulled out my worst fun idea, and made it a reality. Behold #CoffeeScript for #TypeScript with a pipeline operator and everything else you could want!

https://civet.dev/

#CoffeeScript but for #Rust

@triptych
#CoffeeScript was the community way of sprinkling syntactic sugar all over JavaScript.

Thinking on it, sass is starting to feel like #coffeescript did a while back: loved it, it pushed things forward, but the bits I loved are now mostly available in the language itself, and its time has passed.

「 However, despite the large wave of criticism in 2011, CoffeeScript was one of the most followed projects on GitHub. At that time, it enjoyed relatively high popularity in the Ruby-developers community. A large part of CS supporters said their code ran faster and was three times shorter than JS code 」

How CoffeeScript Got Forgotten
— Staszek Zaczek

#CoffeeScript #JavaScript #ES6

「 CoffeeScript began as a fantastic idea (making it easier to write JavaScript code); ultimately, however, it didn’t stand the test of time and was pushed out by JavaScript. Currently, hardly anyone remembers it. Most new people in the front-end environment don’t even know such a language existed. Instead of being included in lists of the most popular new programming languages, it takes top spots on the lists of the worst languages to learn 」

#CoffeeScript #JavaScript #ES6

「 There were many indications that CoffeeScript would be with us for a long time, but a lot changed to its disadvantage in 2015 after the introduction of JavaScript’s ES6 — which actually was an implementation of CS solutions into the language from which the story began. In ES6, JavaScript also added many interesting new features the CoffeeScript team’s engineers didn’t think about 」

How CoffeeScript Got Forgotten
— Staszek Zaczek

#CoffeeScript #JavaScript #ES6
https://betterprogramming.pub/how-coffeescript-got-forgotten-812328225987?utm_source=pocket_mylist

「 Well, in 2009 Jeremy Ashkenas (now a writer for the New York Times) came up with a rather interesting idea. His idea would embellish and increase the readability of, in some cases, quite complicated JavaScript code. Drawing inspiration from Python and Ruby, Ashkenas created a programming language that compiles into JavaScript called CoffeeScript 」
📍 How CoffeeScript Got Forgotten
— Staszek Zaczek
#CoffeeScript #Javascript #Webdev
https://betterprogramming.pub/how-coffeescript-got-forgotten-812328225987?utm_source=pocket_mylist

「 Well, in 2009 Jeremy Ashkenas (now a writer for the New York Times) came up with a rather interesting idea. His idea would embellish and increase the readability of, in some cases, quite complicated JavaScript code. Drawing inspiration from Python and Ruby, Ashkenas created a programming language that compiles into JavaScript called CoffeeScript 」
📍 How CoffeeScript Got Forgotten
— Staszek Zaczek
#CoffeeScript #Javascript #Webdev
https://betterprogramming.pub/how-coffeescript-got-forgotten-812328225987?utm_source=pocket_mylist

Duelyst — a turn-based card battler — has just been open-sourced. Surprised to see that it's a web-first game! Even has some #CoffeeScript in it. ☕️❤️

https://www.youtube.com/watch?v=h3Cuz6d_7x0

Like I said, this stack of #perl, #Mojolicious, #MySQL, #CoffeeScript, #BackboneJS and #Bootstrap has served me well this past decade. I've got several business critical webapps running in it.

The backend stays. The frontend gets replaced by mostly plain #HTML with #htmx and #TailwindCSS. This makes development a lot faster: less context switching as most of it is done inside HTML templates. Added but very nice bonus: less complicated and error prone build pipeline!

END

The thing is, having to render all the HTML client side with #JavaScript (#CoffeeScript compiles to JS) and adding all the behaviour takes a lot of effort. There are also too many moving parts involved.

Last year I thought about replacing the frontend with #React and even using #NextJS came to mind to replace the backend (not the JSON API). But React is just a different way of doing the same.

I also despise dependency management with JavaScript. Stuff breaks, what worked today doesn't tomorrow

Trying to add some new stuff this week made me realise: I don't enjoy working on this. It has nothing to do with the backend though. I'll always love #perl and #Mojolicious. Both very stable and this past decade I had very little issues with upgrading if any at all.

The part of the stack that needs replacement is the frontend. It's one big #SPA (single page application) which means a bunch of HTTP JSON endpoints and #Backbonejs + #CoffeeScript + #Mustache taking care of the client side.

The webapp is written in #perl with #Mojolicious for the backend powered by #MySQL.

For frontend I went with #Backbonejs and #CoffeeScript. The state and support of modern #JavaScript features was limited back then, dare I say cumbersome. I also enjoyed CoffeeScript, even though I don't like #Python ;-). To make it look half decent I went with #Bootstrap as a CSS framework, but hardly any customisations.

For development I used #Vagrant with #VirtualBox, but since 4-5 years I moved to #Docker.

Programming Languages that will be outdated in 2023

👉👉👉Read more: https://bit.ly/3WOjCbt
Well, don’t worry, I have got you covered with all the necessary information you need. In this blog, I will be mentioning the top 10 programming languages that will be outdated by the year 2023.

#programminglanguages #outdated #copperchips #information #CoffeeScript #Ruby #Scala #ObjectiveC