and the reason why duplication jams me up is that all 3 have comments on them, that each of the 3 audiences who stumbled upon their individual submissions won't see
although that last one was kind of addressed by the once link because in its FAQ is "we don't care about your other platforms" so the answer is "because NIH is awesome"
Aurornis · 1h ago
> although that last one was kind of addressed by the once link because in its FAQ is "we don't care about your other platforms" so the answer is "because NIH is awesome"
The 37Signals (now Basecamp) company found a lot of success in the past by creating simple web tools and then marketing them hard into new (at the time) marketing spaces like podcasts and social media. Using small company 37Signals products instead of corporate Jira was viewed as forward thinking, rebellious, and the superior choice in some contexts. DHH (founder) was constantly stirring up controversy and clickbait and leveraging it as marketing. I actually saw it more from people in non-tech companies, some of whom would boast about using 37Signals tools as a sign that they were keeping up with technology trends.
I tried using their tools multiple times over their early years but never felt impressed, so I always migrated away. They were the kind of company that was highly opinionated, didn’t care how other companies did things, and didn’t care how you wanted to use the tools. They built what they built and they were going to gaslight you into believing you didn’t actually want the features they didn’t have (until they implemented them later, of course). For people who hung on DHH’s every word this all seemed eminently correct, but all of the DHH and 37Signals fanatics I knew eventually had some break where they realized there was more to the world and that other tools were actually very good and often better.
As for this tool: I think they just have enough success and cash that they can build whatever they want and have fun. If the past trends hold, they’re probably trying some reality distortion field marketing to convince users that other platforms are bad for some reason and you don’t actually want any of the features that they haven’t shipped in this product (until they ship them, at which point they become great).
willsmith72 · 2h ago
A demo/playground in the readme would be very helpful
nomilk · 2h ago
Reading through some controllers and models, haven't encountered a single code comment yet, just chiselled-out ruby.
It's Ruby. No amount of comments will make somebody who doesn't grok Ruby understand the code.
wereHamster · 1h ago
Could it be that they removed /all/ comments from the codebase when they made it public, to not release some sensitive information that was in them?
jbl0ndie · 6m ago
We're a Ruby shop and we have pretty much zero commented code. Ruby's intended to be readable enough not to need them and when we do need them, it's a sure sign we need some refactoring.
micromacrofoot · 48m ago
possible, but I've worked in similar sized codebases that didn't use them intentionally (linted them out)
the idea being that the code should be readable enough to not require then
I dont know for sure why but could it be that they are using importmaps and so it needs some browser versions to support it out of the box.
One the other hand there is an advantage to use importmaps removing the dependency on nodejs for FE assets thus making both DX and deployment a breeze.
(b) ok, fine, then include any english anywhere (in the source code, in the incompatible_browser.html.erb, in CLAUDE.md, whatever) so future generations would have any sane reason to mutate those magic numbers
napsterbr · 2h ago
Reminds me of Ash (Elixir framework).
Seems great on paper, but quickly turns into a nightmare. Magic is great to get you up to speed, but as soon as you find yourself having to bend the magic, good luck.
ch4s3 · 1h ago
There's not much magic in any of these. Scopes for example are just a convenience on top of a self method that can be chained to spit out SQL.
sebau · 1h ago
Thx a thousand times.
Once is definitely a cool thing, for people learning how to code, for small companies that could pay one time with no monthly fees
I was interested in this chat and installed it locally, to test. That was super easy with docker. It works, it looks like it works well. It doesn’t have any notifications on my iPhone, it says I should enable them in the settings, but I couldn’t find where exactly, there was no Campfire as they say. It is so simple, the chat, that I expected it to work on an old iPad 3 with iOS 9.3.5. It doesn’t. I’m not surprised, and I don’t expect it to work. All I mean, it looks so simple, I thought I won’t be too surprised if it would work with the obsolete Safari.
Surprised to see four same links over the week, but all of them have just one comment. Aren’t people not even remotely interested in the app? Not even investigate the code, huh?
One can try to migrate it to vitejs for example or any other JS/CSS build tool and it might have good chances maybe to work on older browsers.
nomilk · 1h ago
> Aren’t people not even remotely interested in the app?
Could be extremely useful to many communities given (free) Slack no longer stores messages beyond 90 days.
mdaniel · 23m ago
Please, no. Zulip offers free hosting for open source communities and they also have publicly browseable archives, so information doesn't go into chat black holes to die
Also, no one needed Yet Anther Self Hostable Rails Chat Gizmo, so if those communities were previously on Slack then their lack of remediation was inertia, and not lack of options
- https://news.ycombinator.com/item?id=45126432
- https://news.ycombinator.com/item?id=45132968
---
and the reason why duplication jams me up is that all 3 have comments on them, that each of the 3 audiences who stumbled upon their individual submissions won't see
> More info about Campfire: https://once.com/campfire <https://news.ycombinator.com/item?id=45128162>
> Too bad they didn't say "here's why not (Mattermost|Zulip|probably 15 other ones)" <https://news.ycombinator.com/item?id=45134447>
although that last one was kind of addressed by the once link because in its FAQ is "we don't care about your other platforms" so the answer is "because NIH is awesome"
The 37Signals (now Basecamp) company found a lot of success in the past by creating simple web tools and then marketing them hard into new (at the time) marketing spaces like podcasts and social media. Using small company 37Signals products instead of corporate Jira was viewed as forward thinking, rebellious, and the superior choice in some contexts. DHH (founder) was constantly stirring up controversy and clickbait and leveraging it as marketing. I actually saw it more from people in non-tech companies, some of whom would boast about using 37Signals tools as a sign that they were keeping up with technology trends.
I tried using their tools multiple times over their early years but never felt impressed, so I always migrated away. They were the kind of company that was highly opinionated, didn’t care how other companies did things, and didn’t care how you wanted to use the tools. They built what they built and they were going to gaslight you into believing you didn’t actually want the features they didn’t have (until they implemented them later, of course). For people who hung on DHH’s every word this all seemed eminently correct, but all of the DHH and 37Signals fanatics I knew eventually had some break where they realized there was more to the world and that other tools were actually very good and often better.
As for this tool: I think they just have enough success and cash that they can build whatever they want and have fun. If the past trends hold, they’re probably trying some reality distortion field marketing to convince users that other platforms are bad for some reason and you don’t actually want any of the features that they haven’t shipped in this product (until they ship them, at which point they become great).
Arbitrary examples:
https://github.com/basecamp/once-campfire/blob/main/app/cont...
https://github.com/basecamp/once-campfire/blob/main/app/cont...
https://github.com/basecamp/once-campfire/blob/main/app/mode...
the idea being that the code should be readable enough to not require then
One the other hand there is an advantage to use importmaps removing the dependency on nodejs for FE assets thus making both DX and deployment a breeze.
(b) ok, fine, then include any english anywhere (in the source code, in the incompatible_browser.html.erb, in CLAUDE.md, whatever) so future generations would have any sane reason to mutate those magic numbers
Seems great on paper, but quickly turns into a nightmare. Magic is great to get you up to speed, but as soon as you find yourself having to bend the magic, good luck.
https://x.com/dhh/status/1963675999012552970
Surprised to see four same links over the week, but all of them have just one comment. Aren’t people not even remotely interested in the app? Not even investigate the code, huh?
One can try to migrate it to vitejs for example or any other JS/CSS build tool and it might have good chances maybe to work on older browsers.
Could be extremely useful to many communities given (free) Slack no longer stores messages beyond 90 days.
Also, no one needed Yet Anther Self Hostable Rails Chat Gizmo, so if those communities were previously on Slack then their lack of remediation was inertia, and not lack of options