Explore tweets tagged as #coffeescript
🚨 Offering $1,000 Bounty to Rebuild This App in Next.js + shadcn/ui I’m looking for a developer to fully rewrite Reddit Music Player (old CoffeeScript project) using a modern stack: - Next.js 16 (App Router) + shadcn/ui What it needs to do: - Browse subreddits → fetch posts -
142
66
413
you know a js library is REALLY old when it uses coffeescript in the readme
1
0
18
0
2
9
最近はCoffeeScriptにハマったのでCoffeeScriptの復権を目的として(無理)、Viteを参考にした"milkee"というBuilderを作成している 名前はCoffee(Script)にミルク混ぜて(利用難度を)マイルドにしようという意で v2でプラグイン突っ込めるようにした https://t.co/7eckO7Cev3
1
1
5
TypeScript, CoffeeScript and Go walk into a bar and end up having an all-night bender which results in an ugly child called Rust. Yes, it’s Omarchy. Yes, on a Beelink SER 8 Yes I know you can’t have more than two natural parents — unless you’re a cat. Yes, the syntax is the
0
1
0
@iamdevloper the spirit of CoffeeScript is still alive
1
1
6
I’m really enjoying writing python. It sucks that I never worked as closely to it until now. Maybe if I started with it I wouldn’t have hated coffeescript so much 😆
0
0
0
Maybe Gemini 3 is better, but for this task, Claude Code still reining! Recreating a basic version of Framer Studio from back in the day ;) Coffeescript Livereload etc.
0
0
1
@iamdevloper My Post about Coffeescript's Stupid Scoping killed it https://t.co/BW2gxF9IbZ
1
0
6
Random JS Thing — TypeScript wasn't the only dialect. CoffeeScript predates me, but as I understand it, it was supposed to be JavaScript with more functional components to make the code more readable. Here's a thread of all the random ones I know about🧵
1
0
1
Name a day when you were most excited to be in web dev. I'll go first: December 2009, when I first heard about CoffeeScript 🤩
2
0
2
おはようございます☀️ 昨日、TypeScriptが誕生するまでの歴史を読んでいたら、CoffeeScriptの存在を知って面白かったです！ 今日も勉強とバイト頑張ります✊🏻
0
0
13
old article. indeed. TypeScript Will Kill CoffeeScript and Dart (2012) https://t.co/7fSMknz4jn
0
0
0
mizchiさんが先日からずっと同じこと繰り返し言ってるけど、coffeescriptやprototype.jsの後始末とかやったことある人にしかこの感覚って伝わらんのではって思ってる。タスクベースでは最適だけどそれをボトムアップで積み上げていくとプラットフォームの進歩と変な角度で衝突するやつ
Tailwind が悪いのではなく諸悪の根源はCSSそのものであるというのはみなさん同意できると思うんですが(※議論が進まないので合意したことにする)、その上で Tailwind は問題の一つ(HTML/CSSの分離不可能性)に富豪的な解釈をしていて、この世界観だと次の解が出た時に身動きできないって話よ
1
54
242
2
0
20