251–260 of 310 posts
pi's article on this seems relevant here:
Just use Rails.
This one hits really hard and I'd love to see more of that content.
Earlier quoted context omitted.
We've been using SQLite for 100% of our data persistence needs for the last ~5-6 years now. Our largest single environment is probably getting close to 500gb total size. Hundreds of concurrent users are no problem for us, even without these enhancements (we use WAL currently). The biggest single trick I learned was to use 1 sqlite connection instance for the entire lifetime of the application. You can add orders of m…
How do you backup a 500 GiB sqlite database ?
Longer term, we are looking at synchronous log replication so that no business data would ever be lost on a primary outage. Having an availability problem is acceptable as long as we can bring everything back up in a reasonable amount of time.
Earlier quoted context omitted.
It was true then and it's true today. Certainly not in HN or at 8-person startups nobody's ever heard of, but the vast majority of developers work on boring business software in Windows.
Why is it at every tech conference you see a vast preponderance of Mac's? Are conf goers not representative?
The prevalence of MacBooks at tech conferences is in my experience a very US-centric thing. I rather associate ThinkPads with tech conferences.
Earlier quoted context omitted.
Why is it at every tech conference you see a vast preponderance of Mac's? Are conf goers not representative?
1. They're probably not representative 2. You probably notice macs more because of their uniform branding, compared to a mish-mash of different looking other laptops. 3. Is it not enough to watch and listen to a keynote without pulling out a laptop?
4a. Dual booted, is it running macOS, Linux, Windows, *BSD?
4b. Is it running a VM (or more than one)?
4c. Is it used as a very expensive terminal with SSH to a different *nix OS or a remote desktop system?
At various times, all those have been true of mine.
In the 90s-00s, when I was a younger, (even) more arrogant nerd, I looked down on Microsoft and their stupid technologies: Visual Basic, Access, Word, and more. Simple, limited tools that I only saw ugly, half-broken systems built with. Until I saw a something by Steve Ballmer (I think), explaining that their strategy was to provide tools for those "99% developers". The ones who don't read HN, the ones who don't code…
I think there is really not much to add to this, I just wanted to say thank you for this, a lot of people need to read this and wake-up call, that markets hammer on your. The true feedback loop has no feelings, no compliments - just pure and direct feedback by either using the product, or not, irregardless whether its Kubernetes, Solana or
Earlier quoted context omitted.
>why the vast majority of developers prefer to develop on Windows Was that ever true?
It was true then and it's true today. Certainly not in HN or at 8-person startups nobody's ever heard of, but the vast majority of developers work on boring business software in Windows.
On the one hand, your MVP version 1.0 should probably be built in anything that is fast and works. On the other hand, you're gonna want to rebuild that ASAP in something that has legs for longevity's and paying down tech debt's sake. You won't potentially have an edge over any competitors by using their same tech stack.
I suspect that for most companies, the tech stack they run, the custom software on top of it, isn’t meant to be a competitive advantage. It’s just the cost of doing business.
Earlier quoted context omitted.
It's also that, in the past, the capacity of our monoliths to scale was far lower. There's many apps that need say, a 100GB database in 2022. Those apps also needed 100GB database in 2007, when horizontal scaling was the hottest thing around. Nowadays however, Moore's law has steadily overtaken an order of magnitude of use cases from 2007. Maybe 1/10th of the 2007 use cases still need that kind of enormous, big tech…
Scale vertically and you're still a single point of failure away from a big, potentially fatal outage. The coding and architecture can often be trivial though. Definitely good for internal systems and more green programmers. Scale horizontally and you're often constraining and or complicating your design/architecture, but you can handle outages far better, if not seamlessly. It's much harder to get right, so it's usu…