HN user

open592

178 karma

https://www.github.com/Open592

Posts1
Comments42
View on HN

how much of this is just trying to optimize the nutrition facts to come across as less unhealthy? the "full of air" version is half the fat and has less sugar. consumers are generally trending in the direction of avoiding these two line items so guess it's a win win for breyers if it's also cheaper to make.

edit: also if i'm looking at the website correctly, it looks like both the "ice cream" version and the "frozen dairy desert" version are the same price ($6.99):

- https://www.fairwaymarket.com/sm/planning/rsid/4000/product/...

- https://www.fairwaymarket.com/sm/planning/rsid/4000/product/...

This story has been played out numerous times already. Anthropic (or any frontier lab) has a new model with SOTA results. It pretends like it's Christ incarnate and represents the end of the world as we know it. Gates its release to drum up excitement and mystique.

Then the next lab catches up and releases it more broadly

Then later the open weights model is released.

The only way this type of technology is going to be gated "to only corporations" is if we continue on this exponential scaling trend as the "SOTA" model is always out of reach.

I checked with their "AI chat" about whether I could lock in current prices by renewing early but they said they would not allow this. I'm kind of surprised that there is no option to do this (I see Jetbrains as an example of a company which makes this very easy)

I've been a 1password customer for many years, so I'm a bit bummed out about this.

Sorry for the late reply, this was for when you're adding a renovation for instance and there is a section for "notes" - you can hit `ctrl+e` and it will open in an editor.

Looks like it doesn't register `$VISUAL` but does use `$EDITOR` not sure if that is a `xdg-open` behavior though.

This is awesome, love the sense of humor and just downloaded it and started adding data.

Only small piece of feedback is that I would use `$VISUAL` when opening the editor. When I tried to use `Ctrl+e` it opened nano which I haven't used in ages.

Edit: Oh looks like you use `$EDITOR` - I just didn't have that set. Awesome!

These are the projects which make me love Show HN!

Gemini flash thinking:

Unless you’ve discovered a way to wash a car via remote control or telekinesis, you’re going to have to drive.

Walking 50 meters is great for your step count, but it leaves your car exactly where it is: dirty and in the driveway. At that distance, the drive will take you about 10 seconds, which is probably less time than it took to read this.

For some context on demographics of this survey: I signed up for SO in about ~2011 and haven’t participated in SO since about 2015. But I have generally positive sentiment towards the survey so I do it every year.

A lot of comments in this thread make the assumption that the only respondents are people who actively use SO but that isn’t true. I just get notified about the survey through email every year and respond.

The speed is less correlated with the language it’s implemented in, and more with the amount of man hours spent building and optimizing it.

Vapor is a very small project, and thus is slower then other larger more mature projects.

The question then becomes whether or not it's possible (or will be possible) to effectively use these LLMs for coding without already being an expert. Right now, building anything remotely complicated with an LLM, without scouring over every line of code generated, is not possible.

I'll always remember finding that Pocket had exposed their Redux dev tools to production and they had a "dev panel" you could open that allowed you to bypass all the payment walls (for example switching fonts, layouts, etc). Never used Pocket though, so it didn't do much for me besides being fun to find.

i.e. if you wag your tail chasing a bad end for 15 mins, this is a fail in an interview

In all pair programming interviews I have run (which I will admit have been only a few) I would fail myself as an interviewer if I was not able to guide the interviewee away from a dead end within 15 minutes.

If the candidate wasn't able to understand the hints I was giving them, or just kept driving forward, then they would fail.

Not quite sure I would blindly trust this account from Madoff, as it was made within a letter to his daughter-in-law who disliked him due to how hard this situation was on her husband (who later committed suicide). She wrote him purely to boast about the life he was missing out on, and to chastise him about what he had done to his family.

There are also accounts of him being injured (some accounts saying severely) during his early years within prison.

Obviously as he spent more years in the system he became more comfortable and may have had a more or less "easy" life. But I would guess that his life wasn't like something out of Goodfellas.

I’ve never seen a car get the same amount of attention at this price point. There is certainly a slice of the population who is excited by the idea of people stopping and taking a picture of their car. The slice is not big, but it’s enough to satisfy Tesla.

This is no different than any other optimization performed in any other software ecosystem. There is no reason to do this unless you have to. And the reason you would have to is because of performance and user experience.

When your web application requires the following:

- Large amount of user interaction (requires client side JavaScript)

- Large amount of experimentation (bundle is not static, changes per request)

You are going to want to split up the logic on the server and client to reduce the amount of JavaScript you're sending to the client. Otherwise you have a <N>MB JavaScript bundle of all the permutations you're application could encounter. This may be fine for something like a web version of Photoshop where the user understands that an initial load time is required. But for something like Stripe, Gmail, etc. where the user expects the application to load instantly you want to reduce the initial latency of the page.

You can move everything to the server, but like GitHub experienced you then encounter a problem where user interaction on the page suffers because user actions which are expected to be instant, instead require a round trip to the server (speed of light and server distribution then becomes an issue).

You can lazy load bundles with something like async import, but then you run into the waterfall problem, where the lazy loaded JavaScript then needs to make a request to fetch it's own data, and you're left making two requests for everything.

If you encounter all these problems then you end up reaching for solution which make it easier to manage the complex problem of sharing logic/state between the client and the server.

"Based on the research I have available wearing sunscreen with a SPF at or greater than 95 is the most likely to prevent the harmful effects of sunburn".

Go to google -> Search "sunscreen" -> (Sponsored) Banana Boat new Ultra 95 SPF sunscreen

Oh wow! 95 SPF! Perfect

It's no different than professional sports. When you win the super bowl for instance, the value of many of your players (employees) suddenly jump. At that point it's infeasible to pay everyone what they can realistically get on the market. Thus you identify and pay your most essential assets, and the others leave and receive huge pay bumps.

I think it's very valuable for the industry, and as long as the teams who are picking up these employees are able to utilize them effectively, will result in broader innovation.