Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
chillfox
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
24 ms
·
451.
▲
by
chillfox
4y ago
I still buy books and have a nice little library of tech books. I try to only buy books for things that don’t change much.
452.
▲
by
chillfox
4y ago
Correct, but in the context of deploys I would hope they are not random failures, but rather planned events that you do when you have updates to... deploy.
453.
▲
by
chillfox
4y ago
That's fair.
454.
▲
by
chillfox
4y ago
Most business have daily downtime where the entire business is closed as in not business hours. Being sensitive to downtime is more common for companies that has some kind of online service as their primary product, but most companies are n
455.
▲
by
chillfox
4y ago
I did not say that there does not exist good reasons to do it that way. I said it is usually not a considered choice.
456.
▲
by
chillfox
4y ago
And so it is, but I have never gotten that as an answer when asking. edit: I feel like I should be more specific here. I would only call it a considered technical reason if it was actually considered. The fact that it is possible to come up
457.
▲
by
chillfox
4y ago
And yet it has been done just about everywhere I have worked in the past, The justification is usually that VMWare will move the machines to another host if it goes down.
458.
▲
by
chillfox
4y ago
Most organisations run a lot of server applications and most of them don't use much resources considering the size of servers these days.
459.
▲
by
chillfox
4y ago
Most things don't need zero downtime deployment. Now it's nice to have and might be an interesting technical challenge to solve, but it's usually not strictly needed. edit: when I worked as a sysadmin we would have to schedul
460.
▲
by
chillfox
4y ago
I haven't looked into how everyone else does migrations in SQLite. The way I do it is to check the DB version `PRAGMA user_version;` on application start and run migrations if required, before the app starts taking connections. Yes, th
461.
▲
by
chillfox
4y ago
Depends upon what you are optimizing. If you are optimizing for learning as few tools as possible then yes, learning PostgreSQL as your one database is a good idea. Personally I use both PostgreSQL and SQLite. I like SQLite because it'
462.
▲
by
chillfox
4y ago
I guess it depends upon how SQLite is configured and what storage it's deployed on. If it's setup with WAL mode and on SSD storage then it should handle thousands of writes a second fairly easily.
463.
▲
by
chillfox
4y ago
Having learnt SQLite before PostgreSQL I get that experience every so often with PostgreSQL... Both have got nice features that the other does not and what you got used to is going to determine what you miss when picking up the other.
464.
▲
by
chillfox
4y ago
Most of the time people separate the app and database into two different VMs that the infrastructure team then runs on the same box. edit: This is done not because of any considered technical reasons, but because that's how one learned
465.
▲
by
chillfox
4y ago
you.com it allows you to customize it to some extend.
466.
▲
by
chillfox
4y ago
I have been using a different search engine for about a year now and almost never go back to Google anymore, and when I do go back to Google it's almost always to use it as a dictionary (search: define something).
467.
▲
by
chillfox
4y ago
Communities never went away, they are all over the place. I guess you got too lazy to seek them out?
468.
▲
by
chillfox
4y ago
You don't escape configuration with the cloud unless you are talking about the most simple of use cases on a platform like Heroku.
469.
▲
by
chillfox
4y ago
Sure, but if you are considering a physical box then you have presumably already decided that you are OK with it taking longer to replace.
470.
▲
by
chillfox
4y ago
yes, or Puppet, Aviary, Shell, CFEngine, Salt, Capistrano, etc... Doesn't really matter which one, the point is that you have one that can build you a new box or bring a misbehaving box back to a know good state by simply running a com
471.
▲
by
chillfox
4y ago
The key is to use some kind of config management, even for a single box. The problem you need to solve is basically to separate your configurations from the system default and make it easy to bring the system into a known good state.
472.
▲
by
chillfox
4y ago
Thanks, I find the quality of answers you receive out of GPT drastically changes with the way you phrase questions. I don't think I would ever have come up with asking the question in the way you did. As someone who has english as a se
473.
▲
by
chillfox
4y ago
They are all arbitrary (including nginx) in the sense that there are many stacks out there that don't use any of them. But I don't think it's a controversial selection as they are all extremely popular.
474.
▲
by
chillfox
4y ago
What prompt did you use? and how big chunks of text would you say it can handle reliably.
475.
▲
by
chillfox
4y ago
Sometimes I honestly think that the problem is that the SQLite ecosystem makes it easy to understand how things work, so people get scared. Whereas other things comes off as magic and magic is comforting, you don't need to know how it
476.
▲
by
chillfox
4y ago
"you’d have to build some bespoke solution" Or you could use one of the many off the shelf solutions that has sprung up over the last few years.
477.
▲
by
chillfox
4y ago
For most of the world (outside silicon valley) stateless is not the typical. The typical is stateful app + stateful DB run on stateful VMs. For most enterprises, running a stateful app with SQLite is not only possible, it's easier than
478.
▲
by
chillfox
4y ago
If you are planning on supporting niche languages, then please support Crystal ( https://crystal-lang.org/ ), I am currently using Copilot with it and it’s doing ok for writing tests, but is quite bad otherwise.
479.
▲
by
chillfox
4y ago
I only end up doing that when using an ORM to work around the limitations. I have never needed to do it when just using SQL.
480.
▲
by
chillfox
4y ago
I find that ORMs makes it significantly harder to construct queries for anything but the most basic of queries. I routinely end up having to fight the ORM.
More ›