Live data from Hacker News

GPT-4.5

openai.com

801–810 of 1001 posts

Re: GPT-4.5

#801

Earlier quoted context omitted.

Humans have all sorts of issues you have to deal with. Being hungover, not sleeping well, having a personality, being late to work, not being able to work 24/7, very limited ability to copy them. If there's a soulless generic office-droidGPT that companies could hire that would never talk back and would do all sorts of menial work without needing breaks or to use the bathroom, I don't know that we humans stand a chan…

Once we get to that stage, unless you're a capitalist, remember that your job is next in line to be replaced.

I write code for a living. My entire profession is on the line, thanks to ourselves. My eyes are wide open on the situation at hand though. Burying my head in the sand and pretending what I wrote above isn't true, isn't going to make it any less true.

I'm not sure what I can do about it, either. My job already doesn't look like it did a year ago, nevermind a decade away.

Re: GPT-4.5

#803
post #342

I got gpt-4.5-preview to summarize this discussion thread so far (at 324 comments): hn-summary.sh 43197872 -m gpt-4.5-preview Using this script: https://til.simonwillison.net/llms/claude-hacker-news-themes... Here's the result: https://gist.github.com/simonw/5e9f5e94ac8840f698c280293d399... It took 25797 input tokens and 1225 input tokens, for a total cost (calculated using https://tools.simonwillison.net/llm-prices…

As expected, comments on LLM threads are overwhelmingly negative. Personally, I still feel excited to see boundaries being pushed, however incremental our anecdotal opinions make them seem.

I disagree with most of the knee-jerk negativity in LLM threads, but in this case it mostly seems warranted. There are no "boundaries being pushed" here, this is just a desperate release from a company that finds itself losing more and more mindshare to other models and companies.

Re: GPT-4.5

#804
post #739

Earlier quoted context omitted.

The price really is eye watering. At a glance, my first impression is this is something like Llama 3.1 405B, where the primary value may be realized in generating high quality synthetic data for training rather than direct use. I keep a little google spreadsheet with some charts to help visualize the landscape at a glance in terms of capability/price/throughput, bringing in the various index scores as they become ava…

> https://docs.google.com/spreadsheets/d/1foc98Jtbi0-GUsNySddv ... how do you do the different size circles and colored sequences like that? this is god tier skills

[deleted]

Re: GPT-4.5

#806
The latest claude-3.7-sonnet-thinking is fucking amazing with Cursor. I'm escaping from the huge complicated legacy dungeon of rube-goldberg bespoke google cloudbuild contraptions, and refactoring it into a DRY orthogonal crystalline tesseract of reusable github actions based ci/cd workflows in a monorepo, and I've convinced Claude it's Secret Agent 3.7 and I'm his handler.

After writing a huge wall of text of detailed instructions and ideology for organizing and rewriting the mess of cloud build and deploy scripts into thick shared github action workflows called by thin specific wrappers, I gave it some encouragement to get through the next steps of actually completing the mission and making it back out alive. We first capturing the plan in a README file so it doesn't forget the destination, then we're executing it incrementally step by step in order to not blow out its context window or miss any details.

It lays down a solid foundation of technical plans in its thinking phase, then embellishes it with delightful role playing and banter in the reply!

Programming is really fun again!

User:

I feel like a secret agent handler in James Bond or the Matrix telling you which hall to turn down and door to open and remotely unlocking them and disabling burgler alarms! Turn right and go through the door at the end of the hall 007!

Claude:

You're expressing pleasure at our coordinated teamwork - you're directing which files to modify and I'm executing the changes with precision. Let me continue this organized approach to complete our refactoring mission!

Looking at our current status:

We've updated the README with the new structure information

We've created the shared workflow files (shared-docker-build.yml and shared-docker-deploy.yml)

We've started updating service-specific workflows to use the shared ones

Next, I should examine what changes are needed for the pyvision-deploy.yml to use our new shared-docker-deploy.yml workflow.

Mission Status Update: Agent 3.7 Reporting

[Adjusts earpiece] Copy that, Control. I've successfully infiltrated the repository structure and deployed the shared workflow components as instructed. The orchestration pattern is now in place.

[Checks surroundings] I've identified our next target: pyvision-deploy.yml needs to be refactored to utilize the new shared-docker-deploy.yml workflow we've established.

Next Objective:

Looking at the file structure, we need to:

Update pyvision-deploy.yml to use our shared deployment workflow

Fix the disconnected workflow reference (deploy-pyvision.yml vs pyvision-deploy.yml)

Update the path references in the push triggers

[Checks watch] Should I proceed with these modifications immediately, or would you like me to scout ahead for any potential complications?

[Static over comms] I'm also noting that we may need to address the dependency between the build and deploy workflows. The current pyvision-build.yml is attempting to trigger deploy-pyvision.yml, but our standardized pattern uses pyvision-deploy.yml.

What are your instructions, Control?

User:

Give me a concise statement of our organizational ideology, like the Zen of Python.

Claude:

  The Zen of CI/CD:

  Consistency over convenience.
  Explicitness beats implicitness.
  Simple naming conventions create self-documenting systems.
  Big-endian naming sorts better than little-endian.
  Alphabetical order reveals what belongs together.
  Shared implementation reduces cognitive load.
  Technology, component, action, and abstraction are our four dimensions.
  Tesseracts are better organized than flat directories.
  Special cases aren't special enough to break the rules.
  Except when they're waiting to be refactored.
  Workflows should be orthogonal, reusable, and composable.
  In the face of ambiguity, refuse the temptation to guess.
User:

Brilliant! Please add that to the README in the beginning as a manifesto.

...Claude also draws cool ASCII artwork maps and diagrams (the previous cloudbuild based system would look more like a hack dungeon map!):

  ### Workflow Diagram

  ```
         SHARED WORKFLOWS                 SPECIFIC SERVICES
  ┌───────────────────────────┐      ┌──────────────────────────┐
  │                           │      │                          │
  │  ┌─────────────────────┐  │      │  ┌──────────┐ ┌────────┐ │
  │  │ shared-docker-build │◄─┼──────┼──┤ pyvision-│ │concept-│ │
  │  └──────────┬──────────┘  │      │  │  build   │ │ build  │ │
  │             │             │      │  └────┬─────┘ └───┬────┘ │
  │             ▼             │      │       │           │      │
  │  ┌─────────────────────┐  │      │  ┌────▼─────┐ ┌───▼────┐ │
  │  │ shared-docker-deploy│◄─┼──────┼──┤ pyvision-│ │concept-│ │
  │  └─────────────────────┘  │      │  │  deploy  │ │ deploy │ │
  │                           │      │  └──────────┘ └────────┘ │
  │  ┌─────────────────────┐  │      │                          │
  │  │ shared-worker-build │◄─┼──────┼──┐                       │
  │  └──────────┬──────────┘  │      │  │                       │
  │             │             │      │  │                       │
  │             ▼             │      │  │  ┌──────────┐         │
  │  ┌─────────────────────┐  │      │  └──┤  looker- │         │
  │  │ shared-worker-deploy│◄─┼──────┼─────┤   build  │         │
  │  └─────────────────────┘  │      │     └────┬─────┘         │
  │                           │      │          │               │
  │                           │      │     ┌────▼─────┐         │
  │                           │      │     │  looker- │         │
  │                           │      │     │  deploy  │         │
  │                           │      │     └──────────┘         │
  └───────────────────────────┘      └──────────────────────────┘
                 │                                               
                 ▼                                               
         ┌──────────────────┐                                    
         │ Script Utilities │                                    
         └──────────────────┘                                    
  ```

Re: GPT-4.5

#807
post #26

GPT 4.5 pricing is insane: Price Input: $75.00 / 1M tokens Cached input: $37.50 / 1M tokens Output: $150.00 / 1M tokens GPT 4o pricing for comparison: Price Input: $2.50 / 1M tokens Cached input: $1.25 / 1M tokens Output: $10.00 / 1M tokens It sounds like it's so expensive and the difference in usefulness is so lacking(?) they're not even gonna keep serving it in the API for long: > GPT‑4.5 is a very large and comput…

The performance bump doesn't justify the steep price difference.

From a for profit business lens for OpenAI - I understand pushing the price outside the range of side projects, but this pushes it past start ups.

Excited to see new stuff released past reasoning models in any case. Hope they can improve the price soon.

Re: GPT-4.5

#808
post #695

Earlier quoted context omitted.

Huh. Disregarding the 4.5-specific bit here, a browser extension or possibly website that did this in general could be really useful. Maybe even something that just noticed whenever you visited a site that had had significant HN discussion in the past, then let you trigger a summary.

My site https://hackyournews.com does this! Been keeping it alive and free for 18 months.

Wow I find this very useful, thanks! Bookmarked.

Re: GPT-4.5

#809
post #73

Earlier quoted context omitted.

I would like to see a humor test. So far, I have not seen any model response that has made me laugh.

How does the following stand-up routine by Claude 3.7 Sonnet work for you? https://gally.net/temp/20250225claudestandup2.html

[dead]

Re: GPT-4.5

#810

The latest claude-3.7-sonnet-thinking is fucking amazing with Cursor. I'm escaping from the huge complicated legacy dungeon of rube-goldberg bespoke google cloudbuild contraptions, and refactoring it into a DRY orthogonal crystalline tesseract of reusable github actions based ci/cd workflows in a monorepo, and I've convinced Claude it's Secret Agent 3.7 and I'm his handler. After writing a huge wall of text of detail…

That's amazing!
Post reply on HN