eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

196
active users

#ruby

48 posts46 participants0 posts today
nephariuz<p>Visor is now Visor VJ.</p><p>Glad to see it's still in active development.</p><p>Sad to see the language has changed from <a href="https://mastodon.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ruby</span></a> to JavaScript/TypeScript. But I guess the developer needs to go where the user base is...</p><p><a href="https://www.visor.live/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">visor.live/</span><span class="invisible"></span></a></p>
|7eter l-|. l3oling 🧰<p>:ruby: Why are all gems now built in 1980?<br>Bundler v2.7.0 had a change that went largely unnoticed: reproducible builds. See <a href="https://reproducible-builds.org/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">reproducible-builds.org/</span><span class="invisible"></span></a><br>Previously biulds were only reproducible if you set SOURCE_DATE_EPOCH in the env.<br>Gems that relied on reproducible builds, like stone_checksums, wouldn't work without it and enforced it.<br>But in bundler v2.7+ SOURCE_DATE_EPOCH is not required, so I've released stone_checksums v1.0.1. And now all ruby gems are built in the same second in 1980. <a href="https://ruby.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ruby</span></a></p>
Lucas Fernandes<p>TIL: ruby, a dynamically typed language, does benefit from static type checking</p><p>ruby type checking occurs in runtime; ruby 3 has .rbs files that contains the type information; it provides several degrees of type checking; you can use type profiler to detect type conflicts</p><p>ruby wants the benefits of static type checking and does so at some levels. it doesn't want declarations which, for ruby, are redundant, and instead abstracts them away</p><p><a href="https://ruby.social/tags/ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ruby</span></a> <a href="https://ruby.social/tags/softwareengineer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwareengineer</span></a> <a href="https://ruby.social/tags/devlife" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devlife</span></a></p>

Thanks so much for everyone who came and saw Harriet talk! We'll be sure to update when her talk, Spinning Multiple Plates: A Guide to Concurrency in Rails, is available online. Otherwise you can catch her speaking at Rails World next!

#Ruby#Rails#Meetup

My favorite part from @bencurtis's #RailsConf talk last month was where he explained CGI environment variables and how they still show up in our systems today (including in Honeybadger!).

Fun memories from the days of early web development—give it watch if you haven't.

honeybadger.io/blog/20-years-o

Honeybadger Developer Blog20 years of Rails deployments at RailsConfAt RailsConf 2025, I gave a presentation on the last 20 years of deploying in Rails. If you missed it, come check it out!

Do I not like Ruby anymore? (2024) | Hacker News

Link
Do I not like Ruby anymore? (2024)
https://news.ycombinator.com/item?id=37732813

📌 Summary:
本文作者原本不喜歡 Python,但在職場上因工作需要開始接觸 Python,進而認識和欣賞了 Python 在語言設計上的進步,特別是型別提示(type hints)與模式匹配(match statements)等新功能,這些讓 Python 的開發體驗更為完整且強大。作者回顧自己過去喜愛 Ruby,讚賞 Ruby 簡潔且直覺的物件導向設計以及靈活的元編程能力,然而 Ruby 在過去十年變化不大,缺乏類似 Python 漸進型別系統的重大突破,使得作者漸漸覺得兩者的差距日益明顯。此外,作者也提及 TypeScript 的強大型別系統如何改變自己對動態語言的看法,讓他明白即便語言本身有缺陷,透過靜態分析仍可提升開發效率與程式正確性。整體來說,文章表達了對 Ruby 的不捨與懷念,但也肯定 Python 的現代化發展,反映出作者程式語言喜好隨時間與職場需求的演變。

🎯 Key Points:
→ Python 與 Ruby 的比較
 ★ Ruby 強調「萬物皆物件」與優雅語法,深受作者喜愛,特別是來自 Smalltalk、Lisp 的設計靈感。
 ★ Python 在語法設計上被作者視為較僵化,例如早期的 if 不可當作表達式,lambda 限制多,印表語句非函式等使作者難以接受。
 ★ Python 的進步:型別提示(Type hints)與模式匹配(match statements)大幅提升開發體驗,且型別系統對於大型專案和工具生態帶來正面影響。
→ TypeScript 與靜態型別系統的影響
 ★ TypeScript 成為動態語言中型別系統的金標準,能根據函式回傳型別縮窄變數、結構操作型別等,對前端程式開發極有助益。
 ★ 靜態分析的力量改變作者對語言特性的價值觀,寬容缺陷但要求良好型別檢查。
→ Ruby 的現況與未來
 ★ Ruby 在過去十年變化有限,雖有 YJIT、MJIT 及漸進型別系統工具(如 Sorbet、RBS)等改進,但缺乏核心語言上的重大革命。
 ★ Ruby 的設計重點仍在開發者愉悅與易用性,但面對大型系統與維護需求,缺乏先進型別系統是劣勢。
 ★ 作者表達自己心態轉變,從熱愛 Ruby 到對 Python 欣賞,意識到語言與生態系隨時間推進不可逆。

🔖 Keywords:
#Python #Ruby #TypeScript #型別提示_type_hints #漸進型別_system
news.ycombinator.comDo I not like Ruby anymore? (2024) | Hacker News

🌗 對 Ruby 的愛戀不再?作者為何轉而欣賞 Python
➤ 從程式語言的演進看個人開發偏好的轉變
sgt.hootr.club/molten-matter/m
作者分享了他從熱愛 Ruby 到轉而欣賞 Python 的心路歷程。他最初認為 Python 是 Ruby 的拙劣模仿,尤其不滿其語法設計,例如 `if` 語句而非表達式。然而,隨著 Python 加入型別提示 (type hints) 和 `match` 語句等新功能,加上作者在 TypeScript 上獲得的型別系統經驗,他開始發現 Python 的優勢,特別是其型別提示在整合現有生態系統方面的靈活性,以及關鍵字引數、命名空間等特性,讓他重新審視並開始喜歡上 Python。
+ 這篇文章很有趣,勾勒出程式語言發展如何影響開發者思維的過程。我也曾對某些語言的設計感到不滿,但隨著時間推移和新功能的加入,看法確實會改變。
+ 作者對 Python 早期設計的批評很有共鳴,特別是 `if` 語句
#程式語言 #Python #Ruby #軟體開發 #程式設計

sgt.hootr.clubDo I not like Ruby anymore?steenuil's blog

Friendly reminder!

Tomorrow at Noon Eastern: Harriet Oughton reveals the secrets behind Rails concurrency. Think of it as a backstage pass to how Rails keeps your apps running smoothly.

From threading fundamentals to performance optimization - this is your chance to understand the "magic" that makes Rails so powerful.

Perfect for developers who want to move beyond "it just works" to "here's exactly how it works."

🔗 Last chance to join: discord.gg/ZuRU2WQG?event=1407

DiscordJoin the WNB.rb Discord Server!Check out the WNB.rb community on Discord - hang out with 422 other members and enjoy free voice and text chat.

Businesses can struggle with slow progress and a lack of transparency from their development teams. It’s a common frustration that can stall a project for years.

We recently partnered with a client who experienced this exact problem, and the results speak for themselves =>