Our first year on Vercel, the bill was $40,000. When our management went back to negotiate the second year, Vercel wanted $120,000! Vercel wasn't offering 3x the features, mind you, they just knew we were locked in. Our management got it down to $60,000 (still a 50% cost increase, year over year).
Our app is small beans, too. We don't even have that many users. To borrow a favorite term from DHH, Vercel are "merchants of complexity."
But they're only half the problem. Our management is the other half. They can't be bothered to grow a spine and move away from Vercel. So we'll just keep paying, and eventually some people will "be affected" by a "reduction in force."
I once had an external monitor with a maximum refresh rate of 30 Hz, and mouse movements were noticeably sluggish. It was part of a multi-monitor setup, so it was very obvious as I moved the mouse between monitors.
I'm not sure if this LG display will have the same issue, but I won't be an early adopter.
My wife and I canceled Netflix a while ago and went back to DVDs. An FYE store in our area recently had a store closing sale, so we bought three DVD players and snapped up all our favorite DVDs for a few bucks each.
No subscription, no mid-movie ads, and no worrying about this or that service losing the streaming rights to whatever.
I never actually type semicolons in my JavaScript / TypeScript. In work projects, my IDE adds them for me thanks to the linter. In personal projects, I just leave them out (I don't use a linter, so my IDE does not add them), and I've never had a problem. Not even once.
I occasionally run into problems with JS weird parsing rules. My favorite is:
return
x
Which does not return. It returns undefined.
Typescript helps a lot with that. A linter will probably flag it as well. Still, JS went way out of its way to accept just about anything, whether it makes sense or not.
Cormack McCarthy proved to me that when structured correctly conversive language does not need any quotation marks (while remaining entirely comprehensible).
But " " still exist (for us/mere mortals) because few can write so clearly.
I know nothing about coding (beyond changing others' variables to fit my installation), but would imagine this parallels many coding environments (e.g. yours).
I'm seeing a 404 page. I assume this is unintentional, but it's making a funny point: How could AGI possibly be imminent and we still have 404 pages?
Regardless, I agree with this article whose body eludes me: AGI is not imminent, it's hype in the extreme. It's the next fusion. It's perpetually on the horizon (pun intended), and we've wasted trillions on machines that will never reach it.
We went from having new JavaScript frameworks every week to having new AI frameworks every week. I'm thinking I should build a HN clone that filters out all posts about AI topics...
Looking at the most popular agent skills, heavily geared towards react and JS, I think a lot of the most breathless reports of LLM success are weighted towards the same group of fashion-dependant JavaScript developers.
The same very online group endlessly hyping messy techs and frontend JS frameworks, oblivious to the Facebook and Google sized mechanics driving said frameworks, are now 100x-ing themselves with things like “specs” and “tests” and dreaming big about type systems and compilers we’ve had for decades.
I don’t wanna say this cycle is us watching Node jockies discover systems programming in slow motion through LLMs, but it feels like that sometimes.
Ironically, using LLM’s for React is an exercise in pain, because they’re all trained on the lowest common denominator. So even Opus is constantly fighting stupid reactivity bugs.
Just give me your bank account, claude API, Mother's maiden name, your zip code, your 3 digit security code, and anything else you think I might need to live as malfist the magnificant. Can I call you that?
I've long wished for a 'filter' feature for the hn feed -- namely the old trend of web3 slop -- but with little else than keywords to filter, it would likely be tedious and inaccurate. Ironically, I think with AI/LLMs it could be a little easier to analyze.
This is how software is being written now. What you propose is like joining a forum called "Small-Scale Manufacturing News" and filtering out all 3D-printing articles.
Our app is small beans, too. We don't even have that many users. To borrow a favorite term from DHH, Vercel are "merchants of complexity."
But they're only half the problem. Our management is the other half. They can't be bothered to grow a spine and move away from Vercel. So we'll just keep paying, and eventually some people will "be affected" by a "reduction in force."
reply