I'm starting a new project using Ruby on Rails, mostly because it has been a while since I looked at it and my initial experiments with it have worked nicely.
Some chisels and Japanese saws. /s Honestly, what do you expect to get back from such a question? The answers are completely useless to anybody, unless they provide some context about the project. Is it a piece of software? Should it run locally on your laptop, on your smartphone, on your tv, on your refrigerator? Should it be a web application? Is it mostly static text? Does it store user data? Do users exchange information? Is it a piece of custom electronic hardware?
On the other hand, given some context and some reasoning why a technology was chosen, one could really something from the answers.
Just learned the other day to be careful when using what appears to be a saw for flush cuts (Suizan I think) that the little blades stick up/out a bit so its not good to use for flush cutting a dowel since it marks up the surface. I think putting some painters tape down helps when in doubt.
I have a strong distain for web dev due to the JS ecosystem and a new framework every 2 weeks but Elixir + Phoenix + LiveView seems like the perfect web dev stack for me...no need to switch languages/stacks from frontend to backend and no need to deal with the JS ecosystem (to an extent).
For work, I've been diving deep into Rust for backend development. Its promise of safety and performance is hard to pass up, especially when working on systems where reliability is critical. The ownership model does have a steep learning curve, but it pays dividends in the prevention of common bugs that plague other languages.
On the frontend, I've been leveraging the power of TypeScript with React. TypeScript's static typing brings a level of rigidity that's much appreciated for maintainability and scalability. Pairing that with the robust ecosystem of React has significantly accelerated development without sacrificing quality.
For hobby projects, I'm experimenting with WebAssembly. It opens up the web to a multitude of languages and performance-critical applications that were previously confined to native environments. It's exciting to think about the potential for high-performance web apps without being tied to JavaScript.
Additionally, I'm keeping an eye on edge computing with technologies like Cloudflare Workers and AWS Lambda@Edge. With the shift towards a more distributed architecture, I believe these platforms are going to be crucial for low-latency, scalable web applications in the near future.
I have a read-it-later tool (https://hamsterbase.com/) that I've been maintaining as a hobby for 2 years, supporting Mac, Linux, Windows, iOS, Android, and self-hosted Docker.
All these versions share the same codebase.
VSCF: I extracted part of the source code from VS Code and developed a framework called VSCF. It includes commands, themes, dependency injection, key bindings, IPC.
Local server: On top of VSCF, I developed the underlying business logic, and file IO, SQLite, and the logic related to synchronization will be placed here.
Frontend: On top of VSCF, I used TypeScript and React for front-end development.
nodejs-mobile: This is an open-source project that allows me to use Node.js on mobile devices.
Self-hosted version = local server + frontend, using WebSocket for communication.
Desktop version = Electron + local server + frontend, using Electron's IPC for communication.
Mobile version = nodejs-mobile + self-hosted version. Users use webview to access the UI. It looks just like a native application. They can even use their phones as servers to access data on their phones from a computer.
23 comments
[ 4.3 ms ] story [ 48.1 ms ] threadOn the other hand, given some context and some reasoning why a technology was chosen, one could really something from the answers.
Still the same. Still working perfectly. No need to change and waste time learning something new.
I have a strong distain for web dev due to the JS ecosystem and a new framework every 2 weeks but Elixir + Phoenix + LiveView seems like the perfect web dev stack for me...no need to switch languages/stacks from frontend to backend and no need to deal with the JS ecosystem (to an extent).
I'm giving Cloudflare a look, managing domains there now since Google domains got sold off
On the frontend, I've been leveraging the power of TypeScript with React. TypeScript's static typing brings a level of rigidity that's much appreciated for maintainability and scalability. Pairing that with the robust ecosystem of React has significantly accelerated development without sacrificing quality.
For hobby projects, I'm experimenting with WebAssembly. It opens up the web to a multitude of languages and performance-critical applications that were previously confined to native environments. It's exciting to think about the potential for high-performance web apps without being tied to JavaScript.
Additionally, I'm keeping an eye on edge computing with technologies like Cloudflare Workers and AWS Lambda@Edge. With the shift towards a more distributed architecture, I believe these platforms are going to be crucial for low-latency, scalable web applications in the near future.
All these versions share the same codebase.
VSCF: I extracted part of the source code from VS Code and developed a framework called VSCF. It includes commands, themes, dependency injection, key bindings, IPC.
https://github.com/hamsterbase/vscf
Local server: On top of VSCF, I developed the underlying business logic, and file IO, SQLite, and the logic related to synchronization will be placed here.
Frontend: On top of VSCF, I used TypeScript and React for front-end development.
nodejs-mobile: This is an open-source project that allows me to use Node.js on mobile devices.
https://github.com/nodejs-mobile
Self-hosted version = local server + frontend, using WebSocket for communication.
Desktop version = Electron + local server + frontend, using Electron's IPC for communication.
Mobile version = nodejs-mobile + self-hosted version. Users use webview to access the UI. It looks just like a native application. They can even use their phones as servers to access data on their phones from a computer.
Python FastAPI if I want LLM backends.
Using Netlify for deploys. Prefab for config / logging.
commander-rb for CLI.
replit for projects I want to collaborate on with kids.