Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nickjj
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
49 ms
·
541.
▲
by
nickjj
3y ago
It's not about reading comprehension or the lack of it. It's saying the list price is $100 but then you have to invest time and provide information during the checkout process only to find out on a much later step that the list pr
542.
▲
by
nickjj
3y ago
I haven't booked a flight in a while but any situation where I don't know the "final" cost of my ticket before I start the checkout process is a dark pattern in my book. I don't want to see a $100 ticket before I st
543.
▲
by
nickjj
3y ago
> Most of them, including mailcatcher, seem to be unmaintained. MailCatcher is great. It "just works" and has Docker images for both AMD64 and ARM64 CPUs.
544.
▲
by
nickjj
3y ago
Back in the mid-2000s some places had crazy incentives like PokerStars. They had a form of rakeback where you could sit and grind out hands while playing break even'ish poker but still net $100,000 a year back then. The idea there was
545.
▲
by
nickjj
3y ago
What's really nonsense is that prices for known covered procedures through insurance aren't available until you've already enrolled into that insurance. For example, insurance companies will never tell you the "allowed c
546.
▲
by
nickjj
3y ago
> I don't know how they measure it, but other measurements have shown different results The big difference is the blog post you linked performs a very basic GET request to an endpoint. It mentions it doesn't hit the database or
547.
▲
by
nickjj
3y ago
One of the biggest time wasters is when the request doesn't come with the context. It's like they try to save time by keeping everything on a need to know basis but the "why" or the context is a really important aspect o
548.
▲
by
nickjj
3y ago
Oh yeah, please don't get me wrong. My original reply isn't to take away what YJIT accomplished. It was mainly to reference that in the past YJIT used more memory but maybe starting with Ruby 3.3 you won't have to think about
549.
▲
by
nickjj
3y ago
Enabling YJIT comes at the cost of using a noticeable amount more memory so it might be tricky to get going on a single server deploy that runs let's say Puma, Sidekiq and Action Cable (3 processes) on a $10 or $20 a month VPS. But the
550.
▲
by
nickjj
3y ago
I've been maintaining my Build a SAAS App with Flask video course[0] for 8 years. It has gone from Flask pre-1.0 to 2.3 and has been recorded twice with tons of incremental updates added over the years to keep things current. In my opi
551.
▲
by
nickjj
3y ago
People are weird when it comes to ensuring they get absolute maximum value out of the things they buy. I had a 3 year old $20 electric shaver that got dropped into water a few months ago. It wasn't water proof. It stopped turning on bu
552.
▲
by
nickjj
3y ago
This is what I do too, I've written about it in detail at: https://nickjanetakis.com/blog/using-a-custom-ssh-key-to-acc... You can also set that in your `.git/config` file on a per repo basis. Additionally yo
553.
▲
by
nickjj
3y ago
Nothing is ever perfect but I don't recall having feelings between OS upgrades back then where I was like "why is the OS trying to shove ads down my throat?" or having things change under my feet without warning or "what
554.
▲
by
nickjj
3y ago
> In 1999, a CRT with a 20" viewable area cost $999 [1] with reviewers saying "The price point on this monitor is fantastic" Not all monitors were that expensive back then. I got a 21" 1600x1200 NEC for $150 around th
555.
▲
by
nickjj
3y ago
> $1 from 1999 would be worth much less for technology This is expected given technology is advancing but pricing hasn't changed much if you factor in relative costs to relative performance / outcomes. For example in 1999-2000
556.
▲
by
nickjj
3y ago
Yep. I remember back in the day installing 95, 98, 2000, XP and then 7. In the earlier days the sentiment was wow this is great and exciting. I looked forward to upgrading and enjoyed the discovery of new features and generally things were
557.
▲
by
nickjj
3y ago
There's ZenDesk. Here's a comment from last year: https://news.ycombinator.com/item?id=32178105 It references a RailsConf 2022 talk where they chatted about handling a billion requests a day with mostly a Rails mo
558.
▲
by
nickjj
3y ago
I wonder how much of this was premeditated vs deciding what to work on based on preference or mood for the day. I've always enjoyed working on things without a dedicated predefined list of tasks that I'll accomplish in X time (1 d
559.
▲
by
nickjj
3y ago
> I think your parent comment point is that they could have skipped half the changes and still kept up to date with frontend tech. How tho? Things naturally progressed from a lot of asset related things with few choices being baked into
560.
▲
by
nickjj
3y ago
> But my point stands: the prescribed way of handling assets with Rails is ridiculous What would the alternative be for a 20 year old project? I think what we're seeing is a natural progression based on how the web changed over the
561.
▲
by
nickjj
3y ago
I took a 13,000 line Rails 7.0 app and updated it to 7.1. I had to change 1 line of test configuration code to make everything work beyond the diff between 7.0 and 7.1[0]. I would say that's a success for having an easy upgrade path. N
562.
▲
by
nickjj
3y ago
Even though Rails 7.1 comes with a Dockerfile, there's still a lot of opinions you can add such as using Docker Compose to have a fully working out of the box experience that works in development and production -- complete with Postgre
563.
▲
by
nickjj
3y ago
The article mentions: > What if that compose.yaml file is checked in as part of the project? Does the whole team have to agree on a set of port numbers to use for each project? That's only if you choose to use hard coded values. Y
564.
▲
by
nickjj
3y ago
Recent versions of Docker Desktop have a "Resource saver"[0] mode. It will de-allocate memory and CPU when containers aren't being used. If there's a leaf icon next to your Docker icon then it's in resource saver mo
565.
▲
by
nickjj
3y ago
Does below cost only apply for selling certain types of 1-off physical goods? A lot of online apps tend to operate at a loss to gain a large audience and then once they've gained market share they often increase fees or more generally
566.
▲
by
nickjj
3y ago
The article mentions "Strangers on a Train" which I've never seen or read but I've had a number of really interesting encounters from train talk. It's a natural place to end up in a scenario where you could chat wit
567.
▲
by
nickjj
3y ago
> A lot of this was done by the credit card processors in order to increase their rake. I can't speak for every terminal supplier but store owners often do have the option to turn it off. But it becomes problematic when it ships wit
568.
▲
by
nickjj
3y ago
Indeed. That use case hasn't been something I encountered yet since we generally operate at a scale where our apps at the Argo CD level rarely change once they've been created. But thanks for pointing out the mismatch on the sourc
569.
▲
by
nickjj
3y ago
> With _just_ Kustomize and Argo CD, those changes roll out to all environments all at once. With Kargo, you can progress the change and (re-)validate it environment-by-environment. In prod it wouldn't get rolled out until someone m
570.
▲
by
nickjj
3y ago
What about having a git repo that has a Kustomize base which has overlays for different environments? This way each environment is in its own directory which can have its own patches such as using a private load balancer instead of public f
More ›