HN user

rdhatt

203 karma
Posts0
Comments34
View on HN
No posts found.

I find it interesting for your example you chose Moment.js -- a time library instead of something utilitarian like Lodash. For years I've following Jon Skeet's blog about implementing his time library NodaTime (a port of JodaTime). There are a crazy number of edge cases and many unintuitive things about modeling time within a computer.

If I just wanted the equivalent of Lodash's _.intersection() method, I get it. The requirements are pretty straightforward and I can verify the LLM code & tests myself. One less dependency is great. But with time, I know I don't know enough to verify the LLM's output.

Similar to encryption libraries, it's a common recommendation to leave time-based code to developers who live and breathe those black boxes. I trust the community verify the correctness of those concepts, something I can't do myself with LLM output.

One unexpected upside moving from a DC to AWS is when a region is down, customers are far more understanding. Instead of being upset, they often shrug it off since nothing else they needed/wanted was up either.

It was originally an internal tool, so I would guess either A) he doesn't have permission from all the contributors or B) he used reused code from elsewhere within Microsoft that wasn't open source compatible.

A lot of people here put Unix on a pedestal, so finding a published book that so explicitly hates Unix is quite novel. Furthermore, the criticism doesn't come from the typical demographic, Microsoft Windows users.

Solr and Elasticsearch are both Java servers built on top of the Java search library Lucene. There are plenty of articles on the internet describing how they differ. However since they share the same core, so they are very similar as well. For the context of this discussion, you can consider Solr & Elasticsearch as interchangeable - a potayto, potahto situation.

This question comes up commonly on reddit —- yes iMessage is very popular here. In my experience - Facebook Messenger, Snapchat, Discord are the top messaging services.

Whatsapp is not uncommon to be sure, but I would wager a significant portion of users in the United States have it installed because they chat with people overseas.

Signal & Telegram are pretty small userbases.

I think it's poor word choice from the author, not a transcription error. The article refers to 'stability' a second time at the end of article as well:

As a result, it makes sense that even though Tesla and Lincoln are the lowest-ranked in terms of reliability, they continue to fare well among its buyers and rank high on its customer satisfaction index — proof that buyers may value brand loyalty and innovation over stability.

I believe 'stability' here refers to "an overall pattern of reliability", and not describing road handling. If the author wanted to use another word, perhaps 'dependability' would better than 'stability'.

Microsoft spokesman Tom Pilla on Tuesday confirmed with iPod Observer that his company initiated the creation of the iPod packaging parody video that was first reported last month. "It was an internal-only video clip commissioned by our packaging [team] to humorously highlight the challenges we have faced RE: packaging and to educate marketers here about the pitfalls of packaging/branding," he said via e-mail.

https://www.theguardian.com/technology/blog/2006/mar/14/ifmi...

"Opinionated" means the software has made very deliberate design tradeoffs and is very inflexible/resistant to changing that. This is done to optimize certain objectives like software scope or increasing productivity by enforcing certain methods.

So in this case they cited "no client-side routing wiz-bang" -- that's one of their opinions and won't be introducing any support for that sort of thing.

The classic example is Python's motto "There's Only One Way To Do It", which was in a response to Perl's "There's more than one way to do it."

Another example is Ruby On Rails...it has a strong opinion on how the application should be structured -- must be MVC, most of your code should be in a model, convention over configuration, etc.

I work for a company that sells images online. I could see a technique like this being used for NSFW images that come up in our search results. It would allow you to have an idea of the image before clicking into the image detail page to see the normal watermarked image.

These are my mnemonics, pretty sure I'm not too far off though:

  r = RAM.    Instances are biased toward having more memory.
  i = I/O.    ... have fast SSDs.
  d = DISK.   ... lots of disk space.
  x = XL.     ... lots of RAM
  g = GPU.    ... have GPU hardware
...and of course now I realize this is already answered on SO. I'm keeping mine though.

https://stackoverflow.com/a/56880093

it's just a slightly more usable list of EC2 properties and costs

For anyone who has to constantly (re)evalaute EC2 instances, this is a huge understatement. Now, I just looked at AWS EC2 pricing page and it looks way better than what I remember using in 2018.

Back then, for a given instance family, the specs and prices were on separate tables, making it maddening to compare. And forget comparing across instance families. instances.vantage.sh nee ec2instances.info made that so simple. Even the AWS ProServe employees that I worked with preferred it.

So AWS may have closed the gap but ec2instances.info is still superior since it offers advanced features such as "sorting" and "searching". The "Compare Selected" is super handy as well.

The biggest plus for Vantage is that ec2instances.info wired in to my fingers, I suspect that's true for a lot of AWS devs. By buying this site, they get a lot of eyeballs for their product. And frankly, it does make sense - Vantage is trying to selling you a better AWS console, this is a better pricing page, so it fits. The original dev gets some cash for a side project that was probably a huge headache to deal with. Win win for both parties.

Typically, you're right - GC internals aren't usually relevant. That is, until you're fire-fighting a GC-related issue in production. GC internals aren't something you want do a crash-course on while your app burns.

I believe kayodelycaon is saying change tracking IS critical - specifically Word's implementation of it (aka "Track Changes"). Many authoring workflows I've witnessed heavily rely on all parties being able to see the changes made in a Word document.