Earlier quoted context omitted.
Elsewhere in the thread it says they have a goal to be free from "Big Tech" within 5 years, but that there are no reliable non-Big-Tech cloud platforms at the moment. Apparently "cloud" was a mandatory part of the platform. ️
My guess was Azure, because of the Github link to Ruby. But it's possible that AWS has some email functionality they need.
DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
91–100 of 259 posts
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#92For more detail see the Gemfile for Hey [0], posted in a follow-up tweet. [1] [0] https://gist.github.com/dhh/782fb925b57450da28c1e15656779556 [1] https://twitter.com/dhh/status/1275917612556226562
Is the "magic" this line here? > gem 'turbo', github: 'basecamp/turbo' I get a 404 when trying to access it, so maybe still private till the big reveal?
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#93 * Search engine indexing works as expected.
* Informational web pages don't need a lot of interactivity anyway.
* You don't need crazy amount of build tools.
* You don't need extra browser extensions just to debug the JS.
* If for some reason there's one JS error, most of the pages are still functional.
* I am unconvinced that SPA is faster than server side rendering.
* Separation of concern is natural, business logic is handled by BFF, UI interaction is handled by JS.
* If you super love Javascript, you can write the BFF in Node.js.
I am glad that Hey is another high profile app exemplifying this.I can't wait for the pendulum to swing back.
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#94Idk,I actually don't understand the obsession of many with Tech Stack or predicting the doom of a language. Because Facebook uses PHP for their service, Would you still use PHP? A lot of people despise PHP. But there's PH maker Mubs, most of his indie products LAMP stack. The main lesson I get from any of these is that pick the one that you're comfortable with and deliver the project than looking for what's the best…
Yeah, tech stacks are important, but which one is right is so dependent on the specifics of a given project, which is what most of these tech-stack-hype conversations ignore. My small company pays out the ears in so many different ways to run our Python service, but we picked it because certain big companies can use Python at much larger scale than ours. Of course, those companies are mostly just doing CRUD operation…
When I first learned Java I though like this. I liked Python, Perl and even PHP.
Then after reluctantly joining a Java team I learned to like it.
Next I realized how much I actually missed from Java every time I went back to work on a hobby project. Having a
Still for a couple of years other languages still seemed to have an advantage when it came to bootstrapping something, but today? With Quarkus reloads are as fast as in PHP. Things just work and are maintained by grown-ups. If you cannot pair program, the compiler will still have your back.
I'd recommend everyone to look outside the box once in a while: if you use Java, try Rails. If you use Python, try Asp.Net or Java (Quarkus or JavaEE or something). Etc.
At least I feel I have learned a lot from being forced through this process.
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#95It uses ElasticSearch? Does this mean that HEY only supports searching when the device is online? I would expect search to work on a mobile app with no internet access when I'm paying $100 for an email service...
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#96It uses ElasticSearch? Does this mean that HEY only supports searching when the device is online? I would expect search to work on a mobile app with no internet access when I'm paying $100 for an email service...
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#97I tried hey and was put off by its bulbous, fisher-price UI. Signing up and having to press "next" after every single bit of information they collected should have been my first clue at the brain-dead thinking that went into this product. About the UI -- Why is there a trend in designers to add padding to an interface as a disguise for limited features? It's like, does a button really need to to take up half the scre…
Bit of an exaggeration. Extra padding on buttons is more to do with enabling an increased hitbox for mobile and touch users, what with fingers being less precise than mice.
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#98Idk,I actually don't understand the obsession of many with Tech Stack or predicting the doom of a language. Because Facebook uses PHP for their service, Would you still use PHP? A lot of people despise PHP. But there's PH maker Mubs, most of his indie products LAMP stack. The main lesson I get from any of these is that pick the one that you're comfortable with and deliver the project than looking for what's the best…
Using just your bare hands to build a startup is cool.
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#99Earlier quoted context omitted.
Yeah, tech stacks are important, but which one is right is so dependent on the specifics of a given project, which is what most of these tech-stack-hype conversations ignore. My small company pays out the ears in so many different ways to run our Python service, but we picked it because certain big companies can use Python at much larger scale than ours. Of course, those companies are mostly just doing CRUD operation…
> tech stacks are important I'd argue that tech stacks are unimportant 99% of the time. It really doesn't matter if you use Java or PHP or Python or Node. Failures that I have seen due to the choice of tech stack include: - Technologies that your team doesn't know well - Technologies where hiring is difficult (I've seen attempts to turn C# devs into F# devs and Java devs into Clojure devs and productivity suffered) -…
I think this is true if your product is so wildly profitable that differences in tech stack are relatively unimportant--use whatever lets you move the fastest and just solve performance problems by scaling vertically or horizontally. If your business is cost-sensitive and your cloud-bill is a significant portion of your expense, then tech stack starts to matter a lot. Further, your tech stack doesn't matter very much when you're just writing a CRUD webapp--you can use whichever stack and you won't run into issues unless you're massively successful; however, if your app involves a lot of data crunching per request, the stack and architecture matter a lot more (you might have to do more than naive vertical scaling to meet performance requirements). Note that I'm a big proponent of "boring", but "boring stacks work" is orthogonal to "tech stacks don't matter [much]".
Maybe these cases are really only 1% of cases, I'm not sure--there are a lot of CRUD webapps out there, so maybe this is true. But it's not much of a consolation when your use case is one of those 1%.
Re: DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
#100Good retro old-fashion ruby stack from d̶i̶n̶o̶s̶a̶u̶r̶s veterans. Nice :) No fancy magic. Went to check some of their stack on github and some component describe IE5 hacks. Kind of awkward to see how they trying to create a PR driven fight with Apple for obvious reason. "From creators of basecamp" sounds like anti-motivation to use product. They were first infomarketing company. Eventually they lost all the competit…
" Eventually they lost all the competition to every other company..." -> Are your referring to Slacks? "Why on earth someone would trust their business communications to outdated pre-hipster infomarketing company?" -> Probably because they are not under pressures from VC. In HN, we like to bash companies who have done unpleasant things because of pressures from VC. We like to said it like this, "Why did this company…