rdhatt

I had some books that referred to it as .NET Server printed before the name change. In the long history of terrible Microsoft names, this was a rare case where they were able to right the ship.

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.

Really impressive since Internet Explorer 5 for Mac was the best browser anywhere at the time. First to support HTML4 & CSS1.

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.

Has any CEO known a failure of this magnitude?

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.

Practical Engineering did a video on the complexity of bringing a power grid back online, called "black start" (not cold start).

https://practical.engineering/blog/2022/12/5/what-is-a-black...

Second stage reusability was certainly proposed by SpaceX:

https://spaceflightnow.com/2017/04/11/musk-wants-to-make-fal...

https://arstechnica.com/science/2017/04/this-six-year-old-vi...

https://youtu.be/4rC2Z5El-8E [Everyday Astronaut - Can SpaceX Reuse a second stage?]

I think they mean to say that the animated gif[0] your site is misleading as it shows an animated transition that doesn't actually occur in the product.

[0] https://www.screenstab.com/editor/resources/demo.gif

Wendover Productions has a great video on this topic:

Big Plane vs Little Plane (The Economics of Long-Haul Flights) https://www.youtube.com/watch?v=NlIdzF1_b5M

... imagine how far ahead their newer stuff is.

Trump gave the whole world a good idea how far ahead the newer stuff is when he tweeted an image from an NRO satellite. Estimated at ~10cm/pixel resolution.

Scott Manley published a great break down: https://youtu.be/JRLVFn9z0Gc

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.

YouTube channel "LegalEagle" did a discussion contrasting two Florida women being charged with felonies for throwing a glitter bomb vs Mark Rober's glitter bomb pranks:

https://www.youtube.com/watch?v=QRSHeKgMFlo

Strongly agree. There is a huge amount of value in what RDS provides (over DIY EC2).

Fellow HN user quinnypig described it succinctly:

  RDS is a huge win not because of anything intrinsic to what the platform actually is, but because we collectively suck at setting up and managing replication, backups, etc.

https://twitter.com/QuinnyPig/status/1173377290815721473

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.

Remember:

"The x86 architecture is the weirdo" --Raymond Chen

https://devblogs.microsoft.com/oldnewthing/20040914-00/?p=37...

https://devblogs.microsoft.com/oldnewthing/20130320-00/?p=48...

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.

That is a different entity than Getty Images.

https://www.getty.edu/research/library/faq.html#gettyimages

> No, Getty Images has no relationship to the J. Paul Getty Trust.

The "Getty" name derived from the same person, but the museum and Getty Images have nothing do with each other.

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.

This is the workaround my place is using for now:

https://github.com/NuGet/Home/issues/10491#issuecomment-7684...

I have to agree - the LinkedIn requirement was a deal breaker for myself. I have one, but I already gave my real name and email. What if I didn't have a one?

My inner conspiracy voice is telling me this is a fake and just a front for headhunters. Absurd, but true haha.

At my workplace we're using a modified version of ShadowReader - https://github.com/edmunds/shadowreader; note it is AWS-specific. It works by re-running the load balancer logs, either in near-real time or a replay window. We use it test changes to our Solr search engine. It complements our Locust testing which is more about red-lining our servers and isn't as user-specific.

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.

Funny enough given the linked post - Powershell owes it philosophy to VMS as well, e.g. the verb-noun command structure.

https://devblogs.microsoft.com/powershell/verb-noun-vs-noun-...

https://ilovepowershell.com/2013/08/05/microsoft-virtual-aca...

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.