522 karma · joined September 24, 2008
My last use case for it was selling a car and giving away some free stuff. Sadly, those have been replaced by fb marketplace.
Weighing the tradeoffs of doing this calculation server or client side. That'll be an architecture shift away from my current set of background jobs fetching state and towards something more functional and on-demand.
- dark mode
- 3-column responsive layout, interesting it hides the watchlist
- like the view transitions for expanding content
- improved charting
- removed portfolio and holdings. Likely unpopular, but I thought it was a good way to track investments across banks without a 3rd party aggregator
I also like making up stories when we go on hikes. Long, rambling stories about unicorns befriending spiders and flying to faraway lands.
Redesigning investment holdings for wider screens and leaning on hotwired turbo frames. Thankful for once-campfire as a reference for how to structure the backend. The lazy loading attribute works great with css media queries to display more on larger viewports.
Enjoying learning modern css in general. App uses tailwind, but did experiment with just css on the homepage. Letting the design emerge organically from using it daily, prototype with tailwind, then slim it back down with plain css.
In a good headspace now, right after the first year was feeling lost on where to go next.
I wrote another post about building a search form about progressively enhancing a search form (https://jch.github.io/posts/2025-01-30-building-modern-searc...). Starting with semantic <search> and <input> elements gives sane browser and screenreader behavior.
Perhaps my title came on too strong, but I'm not advocating against javascript. It's more about understanding capabilities HTML and CSS can handle, and what is better suited for JS.
When I was reading the header/footer section, it reminded me of this issue to push for first-class includes in web platform https://github.com/whatwg/html/issues/2791
I see this as different layers of stability. On the bottom is a solid foundation of web standards that's widely adopted and resilient to breaking changes. Layered on that is the web framework and language. Before ruby, I really enjoyed perl, so I've experienced the collapse of a language and community. Matz had some good insights drawn from the history of other languages https://www.youtube.com/watch?v=4MM5b2F9zrM
Javascript is fascinating because of its evolution. Its initial popularity and wide install base guaranteed a lot of resources for it to grow. I'm excited to see whether wasm can bring more languages to the web.
Reminds me of Cucumber testing framework
Beautiful site, well done! I love the idea. I'm based in the US.
What stood out in the article was the attention paid to designing intuitive haptics. What our bodies expect in feedback when we turn a weighted dial. Doing it in software allows controlling multiple things, but I would still prefer a dumb dial per function, placed in close proximity to where the function acts. Seat controls near seats, climate controls near vents. Personalization stuffed into the screen and menus and profiles.
I did not think I would like auto climate controls until I lived with one. Even then, I would fiddle with it because I didn’t like the sudden high initial fan speed until I got used to it.
Simple Clock Daylight percentage Sunrise/Sunset Timer Face (Advanced Countdown) Alarms (16 alarms) Stock Stopwatch Moon Phase Pulsometer Alarm Thermometer Toss Up (rolling dice/flip a coin) Time Left (Days passed since my birth/Days left to 90years old) Secondary faces
World Clock (Dual Time) Tally Counter Save/load Databank (Emergency phone numbers +important passwords) Preferences Set time