191–200 of 333 posts
Earlier quoted context omitted.
This speaks to my soul! How cheap of a VPS?
Currently 4.29 EUR/month VPS on Hetzner. (Although I have some fun features planned and might need some more processing power so I might upgrade in the future.) They have great AMD-based VMs, 2x perf/$ over Intel. (I've benchmarked.)
I want to launch some toy projects and confuses whether go for AWS or vps.
I plan to write the server in Racket (likely leaning heavily on [0]) and have it interface with a sqlite database. Since the load will be quite low, I'll put it on a small VPS.
I've enjoyed using Racket for some small projects and am interested in scaling up my abilities to use it in a larger project. Based on my reading the first half of [0], it seems like something that's achievable give my other constraints (real job, etc.).
- Gatsby.js static site generator framework
- Posts written as md or mdx (markdown with jsx support)
- Github Actions to build the site
- Published to and served by Cloudflare workers
- Uses [sci](https://github.com/borkdude/sci) and ClojureScript to add a live Clojure REPL component that can be used in blog posts
- Tailwindcss is used for styling via emotion css-in-js and a tailwind plugin.
The setup mostly works ok, but as always with the JavaScript community the amount of breaking changes can be a bit taxing. Because Gatsby handles static site generation the blog works without JavaScript enabled for those that only want to access the static content.
Earlier quoted context omitted.
As someone fairly new to elm: How do you mix Elm with something like react-admin? Do you set up an elm SPA and embed the react part as a custom element? Or do you go the other way around, having the main App be JS controlled and only some components be an embedded elm App?
No mixing. react-admin serves as a quick standalone admin interface.
For all of my new side projects I am all in on Phoenix live view. I couldn’t be happier, you can write web apps quickly and it is super reliable. It’s probably not the best choice for every project, but for now it lets me do a lot as a solo dev who has maybe 30 minutes to an hour free a day to code side/personal projects. My personal project that has the most use is https://readastorytome.com/ . Almost all of the pro…
Why are you debating killing it? Is it not making any money, or is it too much to maintain?
It’s been a great project to work on though. I have had to think about how I to handle a lot of issues that come with web chat widgets, like how and when you alert your customer they have a new message or how to create an embeddable widget.
Another possibility is I will just make it open source.
This partially might be more of a what's old is new again, but here's what I use: - 100% server side rendered - Progressively enhanced (fully works without JS, but having JS enabled makes it nicer) - In select places where I need SPA-like snappiness I use a ~100 line long DOM diffing algorithm (I request full HTML through AJAX and diff it into the current page; if the user has no JS enabled then the page just refresh…
People who haven't tried it will be excited to discover how much faster it is. The only trick is to store your data in a format where you can write the changes easily. E.g., logging changes and then playing back the log on startup.
This partially might be more of a what's old is new again, but here's what I use: - 100% server side rendered - Progressively enhanced (fully works without JS, but having JS enabled makes it nicer) - In select places where I need SPA-like snappiness I use a ~100 line long DOM diffing algorithm (I request full HTML through AJAX and diff it into the current page; if the user has no JS enabled then the page just refresh…
- Chakra-UI (for ui + ux)
- Hasura (graphql + postgresql)
- Express.js (for custom actions, event hooks etc)
- Kafka for message brokers
Previously, I was fullstack javascript developer using raw html with only express js and its renderer. Later I discovered ui and ux, react with dsl also graphql as data layer overwhelmed me. So I found simple stack for faster shipping. Learning curve is not that difficult I think.
SVELTE[2], routify[3] and Orbit.js[4] for SPA Frontend with API requirements API Platform[5] or JsonApiDotNetCore[6] for Backend
SignalR[7] when realtime is required