Top all-time · #566
DockYard
Company blog · dockyard.com/blog · on HN as bcardarellaprogrammingweb
DockYard is the company blog at dockyard.com, writing about programming and web. Since 2015, 104 different Hacker News readers have linked it 158 times, most often “Phoenix.LiveView: Interactive, Real-Time Apps. No Need to Write JavaScript”. It is still writing: the last post was on 2026-06-10, and you can follow it by feed.
Rarely recommended · 2 of 40 sampled comments recommend it?
Why HN links it
DockYard is a software consultancy whose blog is linked in Hacker News threads about Elixir, Phoenix and LiveView, mainly for server-rendered interactivity without writing JavaScript and for Phoenix-versus-Rails comparisons.
- Recommended for · 2 comments
- One commenter called the Phoenix-is-not-Rails post very interesting; another pointed readers to the Phoenix Channels vs Rails comparison as one to check.
Summarised by Claude from a sample of 40 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
We build custom apps and software for Fortune 500 and industry disruptors alike. Our teams combine AI with 15 years of industry-leading experience to build faster without sacrificing quality.
Most-linked posts?
- Phoenix.LiveView: Interactive, Real-Time Apps. No Need to Write JavaScript19 people · 21 mentions · first linked 2018-12-12
- Phoenix Channels vs. Rails Action Cable12 people · 12 mentions · first linked 2016-08-11
- What makes Phoenix Presence special, and a sneak peek10 people · 12 mentions · first linked 2016-03-25
- Elixir Deployment Tools Update6 people · 6 mentions · first linked 2018-02-28
- All for Reliability: Reflections on the Erlang Thesis4 people · 8 mentions · first linked 2018-07-18
- /blog/2020/12/21/optimizing-user-experience-with-liveview4 people · 6 mentions · first linked 2021-01-15
- Phoenix is not Rails3 people · 5 mentions · first linked 2015-11-19
- Announcing Distillery 2.0 – Better Elixir Deploys3 people · 3 mentions · first linked 2018-08-23
- LiveView Native: 100% Native UI framework for building on multiple devices.3 people · 3 mentions · first linked 2024-09-10
- How long it took to convert our team from Rails to Phoenix3 people · 3 mentions · first linked 2015-10-29
What Hacker News says?
Shameless plug; I recently wrote a blog post about suggestions on improving your audio for remote teamwork: https://dockyard.com/blog/2021/02/08/improve-your-audio-to-b... Although I do suggest the Shure MV7 mic, which I use, there are example of really cheap ways to immediately improve how you sound over conference calls. Another tip I talk about us using RNNoise, which does an excellent job at cutting out backgrou…
Comment linking /blog/2021/02/08/improve-your-audio-to-boost-remote-team-efficiency
on “Higher quality audio makes people sound smarter”Submitted DockYard R&D: FireFly Optimizes Your Elixir Compilation as a story · 115 points
HN discussionPersonally, I'm very interested in the possibility of Phoenix LiveView giving us the best of both worlds: https://dockyard.com/blog/2018/12/12/phoenix-liveview-intera...
Comment linking /blog/2018/12/12/phoenix-liveview-interactive-real-time-apps-no-need-to-write-javascript
on “You probably don't need a single-page app”Submitted Phoenix.LiveView: Interactive, Real-Time Apps. No Need to Write JavaScript as a story · 75 points
HN discussionConsider these two scenarios. 1. SPA with asynchronous server communication. A button switches to a spinner the moment you click it, and spins until the update is safe at the server. Error messages can show up near the button, or in a toast. 2. LiveView where updates go via the server. The button shows no change (after recovering from submit "bounce" animation) until a response from the server has come back to you.…
Comment linking /blogs/optimizing-user-experience-with-liveview
on “How we got to LiveView”Submitted Create your first LiveView Native (Elixir) Application as a story · 68 points
HN discussionChris said in a different comment optimistic ui updates already exist… Here’s the link: https://dockyard.com/blog/2020/12/21/optimizing-user-experie...
Comment linking /blog/2020/12/21/optimizing-user-experience-with-liveview
on “How we got to LiveView”Submitted What Is Machine Learning Anyway? as a story · 63 points
HN discussionYou'd use the optimistic UI features that LiveView ships with out of the box to handle the arrow click, and you wouldn't await a server round-trip for each keypress, so again that's now how LiveView form input works. For posterity, I linked another blog where I talk exactly about these kinds of things, including optimistic UI and "controlled inputs" for the keyboard scenario: https://dockyard.com/blog/2020/12/21/opt…
Comment linking /blog/2020/12/21/optimizing-user-experience-with-liveview
on “How we got to LiveView”Submitted What if we could transpile COBOL into Elixir as a story · 58 points
HN discussionThese kinds of discussions miss a ton of nuance unfortunately (as most tech discussions do), so hopefully I can help answer this broadly: First off, it's important to call out how LiveView's docs recommend folks keep interactions purely client side for purely client side interactions: https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html#m... > There are also use cases which are a bad fit for LiveView: > Animat…
Comment linking /blog/2020/12/21/optimizing-user-experience-with-liveview
on “How we got to LiveView”Submitted Phoenix Channels vs. Rails ActionCable as a story · 54 points
HN discussionI wrote my thoughts on the LiveView 1.0 release: https://dockyard.com/blog/2024/12/03/phoenix-liveview-goes-1...
Comment linking /blog/2024/12/03/phoenix-liveview-goes-1-0
on “Phoenix LiveView 1.0.0 is here”Submitted Phoenix is not Rails as a story · 32 points
HN discussionThis might be outdated but should give you some idea at least https://dockyard.com/blog/2016/08/09/phoenix-channels-vs-rai...
Comment linking /blog/2016/08/09/phoenix-channels-vs-rails-action-cable
on “Running GitHub on Rails 6.0”Submitted Building a Nerves Lullaby Player as a story · 31 points
HN discussionElixir. The ecosystem has been steadily growing (and, more importantly, becoming more robust and mature) throughout 2018 with continuously improved tooling, libraries and frameworks. I'm excited for many of the upcoming things [1] in the Elixir world, and how those things can improve the way I build (web) software in 2019. [1] For one example, https://dockyard.com/blog/2018/12/12/phoenix-liveview-intera...
Comment linking /blog/2018/12/12/phoenix-liveview-interactive-real-time-apps-no-need-to-write-javascript
on “Ask HN: What technologies did you learn in 2018?”Submitted Elixir Is Safe as a story · 26 points
HN discussionUntil you have users. :-P For one example, check this comparison: https://dockyard.com/blog/2016/08/09/phoenix-channels-vs-rai...
Comment linking /blog/2016/08/09/phoenix-channels-vs-rails-action-cable
on “Go 1.7 is released”Submitted Lessons Learned – 10 years of running a software consultancy as a story · 25 points
HN discussionI don't know Go, but that probably depends on your goals. To quote myself from elsewhere: > Efficiency in the BEAM is mainly in service of its primary goal of fault-tolerance. If one process crashes unexpectedly, the others should continue. By the same logic, if one process is CPU-intensive or IO-blocked, the others should keep making progress smoothly. And if processes are good for isolating errors and performance…
Comment linking /blog/2018/07/18/all-for-reliability-reflections-on-the-erlang-thesis
on “Achieving 100k connections per second with Elixir”Submitted EXGBoost: Gradient Boosting in Elixir as a story · 18 points
HN discussionDeployments are a significant amount of magic, moreso than with other languages. You're deploying a whole beam ecosystem not just a single app. If you want to do anything remotely dynamic (e.g. using environment variables as knobs a la 12-factor) you'll have to rely on distillery and voodoo. Meanwhile distillery has been broken on FreeBSD for months with no fix in sight and no actual community understanding of how t…
Comment linking /blog/2018/02/28/elixir-deployment-tools-update-february-2018
on “Ask HN: Go-to web stack today?”Submitted Phoenix Channels vs. Rails Action Cable as a story · 12 points
HN discussionI have an app like that, but I found it convenient to use Phoenix anyway as it provides test helpers, a nice router, an efficient template (EEx) compiler with escaping, etc. I just ignore the parts I don't need. Phoenix LiveView looks super interesting for simplifying this further: https://dockyard.com/blog/2018/12/12/phoenix-liveview-intera...
Comment linking /blog/2018/12/12/phoenix-liveview-interactive-real-time-apps-no-need-to-write-javascript
on “Elixir, Phoenix, Absinthe, GraphQL, React, and Apollo”Submitted What makes Phoenix Presence special, and a sneak peek as a story · 10 points
HN discussionI think this should be post here: https://dockyard.com/blog/2015/11/18/phoenix-is-not-rails It's very interesting to see such different philosophies.
Comment linking /blog/2015/11/18/phoenix-is-not-rails
on “The Rails Doctrine”Submitted Phoenix Channels vs. Rails Action Cable as a story · 7 points
HN discussion> it tries too much [to be] like Rails Only on the surface. Please see: https://dockyard.com/blog/2015/11/18/phoenix-is-not-rails
Comment linking /blog/2015/11/18/phoenix-is-not-rails
on “The Rails Doctrine”Submitted Five benefits we saw after going all in (including machine learning) on Elixir as a story · 6 points
HN discussion
