Hacker Newsnew | past | comments | ask | show | jobs | submit | chooma's commentslogin

I am building a luxury villa park from scratch in Kuta Lombok Indonesia:)

I wanted to try my hand at something else than software.


Curious, We need more info :)

Upvoted because I giggled :)


All year maybe?


From the samsung S10 forward, this is a feature while recording video in zoom mode. I was always really curious how they did it.


Working gathering the most accurate lead data, which then is used as input for AI sales development representatives: https://billie.ai


Super cool. I have something similar in my browser tab for years now when I open a new one


Nice. Is that an extension?


Yes, it's called: Mortality - Death Clock - New Tab

It's a countdown timer of sorts ;)


Somehow I hadn't thought of this, now I have this as well, thanks :)

~ $


I am really struggling to get hotwire running to be honest. I now just postponed implementing it till after the launch. Any good ways of getting up to speed on hotwire and debugging it?


It’s really a different mindset shift. In react, you think about components — updating components and replacing one component with a new component. But in hotwire, you think about pages. First implement everything as full page transitions. Only after you get all your functionality working with full page transitions, then you do a pass back through it and ask: how can I minimize the amount that changed between the transition from this page to that page? “Oh, just wrap this part in a turbo frame or have this one controller action reply with a turbo stream in this one case.”

I don’t know if that’s helpful, but realizing that I needed to shift from thinking about components to pages was the a-ha when Hotwire all started making sense.


A lot of people seem to overcomplicate it by bringing their thoughts on how other modern js apps are written. It would be helpful to have a specific example of some of the things you need to work through. Reading through the [handbook](https://hotwired.dev/) should get you most of the way there.

One of my colleagues recently switched from mostly react to default full stack Rails. He was really struggling with how to filter things in a table. When I showed him how I would do it, his comment was along the lines of: “I can’t believe how simple this is. Modern JS just doesn’t work this simple any more. This is like how jquery used to work but way more organized”.

I can’t say I know enough about modern js development to validate that comment. He noted something about expectations of how the dom managing things…

So, if you’re coming with a certain mindset of how to do things, try to leave that behind a moment and read through the handbook. Especially if it involves making fetch requests to do things. That’s like, the number one “you probably shouldn’t do it like that” in Hotwire.


this is a nice tutorial too - https://www.hotrails.dev/turbo-rails.

then this series on youtube - https://www.youtube.com/watch?v=b7dx1Yt3FzU&list=PLm8ctt9NhM...

some things have changed a bit - so you just have to work through the kinks.

one other thing though - since railsword conf - there was an announcement that certain things have simplified but I haven't found the docs or the new simplified api's.



I wouldn't word it that strongly, however I would've like to see the first line of the documention on the homepage :)

I'll give it a spin later, looks interesting.


After test drive countless of frameworks...I've settled for a very boring stack

Ruby on rails is the only framework I use for SaaS applications.

Plain ES6 for a lot of things that are not as big as a SaaS. React when I need frontend stuff.

Python lives mostly in notebooks for all my thinkering.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: