I don't like anything Apple, I had an awful experience with MacOS (the laptop was great), iPhones and their 12 finger gestures (again, terrible software) aren't for me.
WiFi and worsening slowness woes with the Google TV/Chromecast pushed me into buying an Apple TV, and it is the single Apple product that I would glowingly recommend; that's saying something coming from an Apple hater. It is truly a fantastic product.
My biggest problem with Nextcloud is that it intentionally broke (at least twice by memory) on some updates, wanting me to run some oci command on the box. Remember that "for my family" also means "for my family when I'm gone." I never got round to having to find an alternative thanks to the divorce, but I'd consider Nextcloud a complete non-starter for this reason.
Dynamo is a fundamentally different DB to Postgres. If your problem fits into the dynamo approach (I'd argue that more problems do), then you should be using it. No all problems fit, though.
Agreed, my critique was about how the article frames scalability. I've yet to see an OLTP problem that can't live in something like Dynamo. KV can model anything if you put in the work, the question is how much modeling discipline you trade for the scale, and in my experience the up front work is always worth it. Most of the time operational issues are swept under the rug and not consider tech debt.
Take for example AuroraDB: the sheer engineering it took to make SQL do scalable OLTP at all tells you how much that flexibility actually costs to keep.
Upfront modeling work is always worth it, but that only holds if you actually know your access patterns upfront. Most teams don’t, especially early on.
$1000 in a month? What on earth are you doing in CI? We're on Warp build (50% cheaper instead of 33%) with 6 people hitting it pretty hard across a few repos and only reach $150/mo. That's with building rust - a worse case than anything you're using for build time.
1. I'm not sure if blacksmith offers larger runners, but you if you're using them you have checked that bigger runners are worth the squeeze? A 2x runner does not mean a 2x faster build - I had a goal and sized CI according to that.
2. Caching. Nx can do this for your TS, provided your code is decomposed into packages.
3. At a previous job I had a post-run timings job. GH markdown supports Mermaid; I used a gannt chart to express it. I don't remember if the GH api supports getting timing for the current wf - so it may have been a second workflow.
The first is just a little legwork, the rest your agent should be able to do in 5 minutes.
> API is definitely being sold at a decent profit.
Where do you get this from?
Enterprise plans are being cancelled or limited all over the place (Uber, Microsoft). I doubt Anthropic would be leveraging a loss leader with their consumer plans, while catastrophically hemorrhaging customers on the enterprise.
They are either operating at a loss (possibly a minor one), or a minor profit (which is chasing customers away).
If they were comfortably profitable they wouldn't need to participate in the circular deal circus.
It would be insane, if they can't serve the models at a profit sure at current GPU prices the profit might be 10% or lower.
But at realistic gpu prices it would have been close to 30-60% based on how big the models actually are and how much they have optimized the stack to serve them.
1T parameter models like Kimi K2.6 can be served for 1/10 to 1/5 of the price of opus 4.8 for perspective.
Sure opus is 2x the size and hosting might be non linearly scaling so still it should be around 50% margin at regular gpu prices.
If it isn't I would be very surprised.
Also for enterprises we joke but Google is not paying same rates as us there are big massive enterprise discounts. I have heard upto 20-30%...
OpenAI is supposedly even more generous.
I don't think API is being sold at a loss at the end of the day even if the API profits are marginal 10-20% because of insane GPU prices now.
Zig and probably Pascal have the same advantage, can't speak for Ada as I've never built it.
C and C++? You've got to be joking. If the project provides static binaries, sure, but I don't want to have to worry about finding a necronomicon and summoning the correct kind of imp required to properly use whatever insane build system the project is using.
And thus, we all agree that Linux, Windows, and OS X are all bad software, because they're written in C and C++ and have insanely complicated build systems.
You are missing the point here. Single binary files are not what makes a programming language good or bad.
Its like saying "I want a red car because it goes fast" when people are actually disucssing how the engine works or how easy/difficult is it to drive etc.
You cannot base your like/dislike on that single criteria and expect that to actually make sense.
For some people, Linux package management is not solved. Static binaries at least work for deployment.
More useful for client software, but you can’t just dismiss someone for having this preference given the poor viability of running arbitrary binaries on Linux due to GNU’s userland style.
No, it does not depend. Your parent is correct with his analogy.
Linux package management is solved, if it depends on something, it depends on the specific Linux distribution, but "Linux" package management is definitely solved.
Off: I thought I am becoming dumb, but this really puts me in a new perspective. The odd thing is that even people who work in IT hold similar beliefs. I am not entirely sure what is going on. Favoring a language so blindly seems like a thing, apparently? For example they seem to have convinced themselves that Rust is "safe" if you use it for anything (without implementing the security features) because it is (memory) safe? I did not imagine beginners would make such a mistake either, but alas.
I noticed your comment is getting downvoted. I wish I knew why though. Is it because of your analogy? Is it because they think that somehow "single binary" has anything to do with the programming language? Would like to know. I am not going to assume that it is a confirmation of what I wrote earlier.
If the figures look softer than expected, keep in mind that it's local lay-men buying in - while foreign career investors are selling out[1]. Broadcom's earnings call may have kicked it off: the CEO started off mistaking last year's figures, and had to start over with below projected numbers[2].
WiFi and worsening slowness woes with the Google TV/Chromecast pushed me into buying an Apple TV, and it is the single Apple product that I would glowingly recommend; that's saying something coming from an Apple hater. It is truly a fantastic product.
reply