Earlier quoted context omitted.
The developer experience is bad, even compared to other PHP-based frameworks like laravel. It may not be bad 15 years ago, but when the rest of the word has moved forward. When other frameworks compete with each other to give the best developer experience, wordpress developer experience hasn't improved (or even regressed depending on who you ask). I've been creating and maintaining several plugins and themes in the p…
Edit; sorry I misread your comment somehow! I will leave my response anyway. But it is not actually relevant to your comment; sorry about that. I agree with you, I guess the ‘even compared’ threw me off; laravel is pretty painless imho so maybe it does actually apply? What is bad about laravel for development experience? I don’t like php or js or, dare I say it, ts (I don’t mind the language and like the type system…
Ask HN: Companies of one, what is your tech stack?
151–160 of 206 posts
Re: Ask HN: Companies of one, what is your tech stack?
#152C# on Azure Functions for backend. Azure managed SQL Server for storage. Azure managed Redis for caching. Azure Application Insights for monitoring. Forest Admin front end. Quite a pleasant experience overall for what I need.
You tried the Azure durable entities?
Re: Ask HN: Companies of one, what is your tech stack?
#153Earlier quoted context omitted.
It's actually not that bad when you get the hang of it
The developer experience is bad, even compared to other PHP-based frameworks like laravel. It may not be bad 15 years ago, but when the rest of the word has moved forward. When other frameworks compete with each other to give the best developer experience, wordpress developer experience hasn't improved (or even regressed depending on who you ask). I've been creating and maintaining several plugins and themes in the p…
Re: Ask HN: Companies of one, what is your tech stack?
#154Django, Celery, Postgres, RabbitMQ, Minio, Lots of different Python environments for different scientific “stacks” (some pip based, some conda)
Machine learning done in pytorch, models wrapped and deployed by simple FastAPI wrappers
Deployment moving to be totally dockerized (maybe 90% done) because I was having a lot of trouble with deploying esoteric, fragile, scientific libs.
System core is a monolith, with a bunch of micro services in different repos - especially worker machines (structure optimisers, various energy calculators, etc) this way worker code can be deployed to relatively untrusted machines without having to put the entire codebase on there.
I applied for ycombinator this batch, I am hoping to get in, and find a cofounder at the same time
Re: Ask HN: Companies of one, what is your tech stack?
#155Building an agtech platform (with quite a few other people, including a designer and data scientist, but I'm currently the sole developer, and for the most part it was built by a single developer). Backend: Rust, rocket, sqlx, postgres + a little bit of R. Ansible for deployment. Frontend: Rescript + React. Also a significant portion of Rust/WASM, but that was a mistake I'm trying to undo. In short, statically typed…
Nice. Are you able to share what you are working on and why WASM was a mistake?
- Very slow compilation times. A medium-sized app can take 30s to build incrementally on a fast desktop computer. And that's just way too slow for front-end development where fast iteration is key. In comparison, Rescript takes maybe a few hundred milliseconds on an app that's about the same size.
- Poor abstraction mechanisms, for making reusable and configurable components with more than a few properties, some being required and some being optional. The common Rust solution for this is the "builder" pattern, which is very verbose to implement, and still quite awkward if you have more than a few required properties.
- Poor debugging ability. WASM is opaque and there's no debugger for it as far as I know. The stack traces you get from Rust is also very noisy and imprecise. You basically only get the function name, and have to search for it in a big noisy stack trace. And because of inlining the problem might not actually even be in that function. Also, when a panic happens the app just freezes. There's probably some way of intercepting and overriding this behaviour, but by default it's quite bad UX.
- The cognitive overhead of manual memory management. Fighting the borrow checker and having to always think about who owns what and what strategy to use to manage data ownership is just completely unnecessary for most front-end development. Most of the time the app is just waiting for an event to happen, and when something does happen the processing needed tends to be dwarfed by the time spent by the browser to update and render the DOM.
- Large bundle size. Because you tend to use native Rust libraries instead of binding to non-idiomatic and often poorly designed browser APIs.
- Somewhat poor browser support? We've had some issues with the app simply failing to load after a new version is deployed, and having to clear the browser cache in order to fix it. We've yet to reproduce this reliably and therefore still haven't been able to track down why it happens.
Re: Ask HN: Companies of one, what is your tech stack?
#156Earlier quoted context omitted.
Nice. Are you able to share what you are working on and why WASM was a mistake?
I'm literally about to do my weekend coding on a WASM UI using sycamore-rs (a rust library), so I would love to find out too lol
I find Rescript to be much more enjoyable for both hobby and production use. If you're looking for a front-end language that is quite similar to Rust, just without the manual memory management :)
Re: Ask HN: Companies of one, what is your tech stack?
#157Monster server (128GB RAM, 18 core) on Hetzner ($60/mo). CloudFlare to front everything to add a little extra security mostly - I only allow my home IP and CF to connect directly to the app/db/web server.
* MySQL, because one key source has a library that ingests easily to MySQL
* Postgres for the main warehouse and app data (fdw to pull in MySQL data)
* Django for the webapp, with celery and redis for async jobs
* SES for email
* Prefect (vs Airflow) for running data ingestion/transform jobs
* DBT (triggered by prefect) for transform jobs
* Netlify for the static site frontend, jekyll for static site gen
* Google Analytics
Re: Ask HN: Companies of one, what is your tech stack?
#158I run a data warehouse for sports data, with a web frontend. Lots of integrations with 3rd party APIs to pull in data. Monster server (128GB RAM, 18 core) on Hetzner ($60/mo). CloudFlare to front everything to add a little extra security mostly - I only allow my home IP and CF to connect directly to the app/db/web server. * MySQL, because one key source has a library that ingests easily to MySQL * Postgres for the ma…
Re: Ask HN: Companies of one, what is your tech stack?
#159You're going to love to hate this: Best choice I made was using WordPress! I run https://rpgplayground.com , a web tool to make RPG games without coding (6000+ user published games) The app itself is written in Haxe. My website is WordPress. Haxe because it will be easy to port to any device. Why was WordPress the best choice? Basically everything you need has a plugin. I needed a forum: bbPress I needed a community…
As a developer, WordPress makes you feel miserable if you ever worked in any other framework/ecosystem. That's my experience at least.
Re: Ask HN: Companies of one, what is your tech stack?
#160Earlier quoted context omitted.
It's actually not that bad when you get the hang of it
The developer experience is bad, even compared to other PHP-based frameworks like laravel. It may not be bad 15 years ago, but when the rest of the word has moved forward. When other frameworks compete with each other to give the best developer experience, wordpress developer experience hasn't improved (or even regressed depending on who you ask). I've been creating and maintaining several plugins and themes in the p…