I think as programmers we naturally want a single, universal standard for everything, but there are genuine advantages to having the current system as well, even with all of its flaws.
169 karma · joined March 6, 2024
I think as programmers we naturally want a single, universal standard for everything, but there are genuine advantages to having the current system as well, even with all of its flaws.
Source: https://www.canr.msu.edu/news/tulip_mania_the_history_of_the...
What's old is new.
Colour me surprised then when I see, since circa 2024, an absolute deluge of AI products coming from these companies, each with their own naming scheme, marketing page, and accompanying hype post, and despite giving them MORE than the 30 second elevator pitch interval, I am left not understanding what it is they want to sell me. I have claude, I have codex, I get my work done just fine with each. I don't need another product for this. Any software these companies try pushing always ends up being something I could've made with their own AI models in a day and then never end up using. What's the end game here? What's the goal? What's the moat? I'm not sold on a single product outside of codex and claude code.
The bar for something like this should not be 100% accuracy. It should be 100% accountability and transparency, followed by being at least as accurate as google search.
Similar to autonomous driving: it doesn't need to be perfect, just less likely than humans are at causing an accident.
You should be writing everything in a sans-IO pattern: define your core, the interfaces, and your own types, (even if it seems redundant) and never, ever import a single dependency from a cloud provider in that core. Make two implementations of the interfaces: one in-memory that can be spun up quickly for testing and one that uses the actual cloud provider APIs. Now instead of hoping fakecloud or localstack update their mocks to be inline with AWS, all you have to do is update your dependencies and the implementation code and the core can be left alone for a long time.
This is also why I avoid lambda and other "serverless" compute like the plague because it's designed from the ground up to lock you in.
The interaction here is eerily similar to the pilot interactions preceding the 1997 Korean Air Flight 801 (B747) disaster in Guam [1]. It's not clear based on the NTSB update if the Captain was ignoring the First Officer or the other way around.
[1]: https://en.wikisource.org/wiki/Korean_Air_Flight_801_-_Aircr...
Also this was Amazon, not Southwest.
I'm hearing two completely conflicting stories. Buckmaster is claiming the approach used by OpenAI is so strikingly similar to the one he used, that mere coincidence is astronomically small. Yet OpenAI is claiming that the methods used are entirely different.
Anyone care to provide primary evidence proving one way or the other?
I don't know, maybe a mass shooting?
https://www.npr.org/2026/09/02/nx-s1-5953021/openai-tumbler-...
Oh, and let's just forget the uncountable early deaths from the environmental disaster of the Datacenter buildout. It's not as sexy and doesn't make headlines, so those deaths don't really count or matter do they?
Me and quite a few others are getting real tired of the constant name-dropping of mega-corporations that do not care about your safety, health, or well-being. This does not resonate with anyone except a small circle of wealthy tech elitists.
If they can make a profit from those things, great, but they will also not hesitate to make a profit from your suffering as well. Ask the lung doctors of the people living next to xAI's data centers if their patients are better off than before.
It's only going to grow every year as apple stops releasing OS updates for perfectly functioning hardware.
We're seeing a mass exodus of companies and people from the Windows ecosystem. If this gets more people using/familiar with Linux I can only see this as an absolute win.
Stick to the original definition of AGI of an AI model being able to self-improve independently with 0 human intervention and become an "everything" solver. Ever since money got involved in this, the goal posts have shifted considerably. If OpenAI truly had an AGI on their hands they would then be able to crack encryption, destroy world markets, and funnel all resources back into their new for-profit organization. Since their mission is now share price, until I see any evidence of an infinitely growing stock I will reserve my congratulations.
It's very clear what the motivations are, and just because they don't seem harmful in isolation doesn't mean it's going to have no consequences for everyone else.
Cities are by definition economical logistical hubs. It's where the jobs and opportunities are. Most people aren't saying "gee I better pack up and move to suburbia before having a child" it's more like "having a child could cost me my high-paying job so I better not". And that issue is exacerbated in the U.S. with the worst parental-leave policy among developed nations. Regardless though, the trend will still exist in countries with generous parental-leave policies because having a child is an opportunity cost in an urban environment. That doesn't mean the environment itself isn't conductive to raising the child. Completely different stories.
Most of my American friends I know turn to the suburbs as a default for "family" style living once they have kids. Imagine their bemusement when they go to a place like Amsterdam or Tokyo and see plenty of families with small children walking around. Heck, you don't even have to go far to see how a city can be a great place for a family, just look at Boston.
Cities, when done correctly, are a better place to raise a family than the suburbs. And yet, when done incorrectly, are terrible.
> This is a pretty simple type, which is a vector that you can push into, but cannot modify the elements of. The data structure never moves an element once allocated, so you can push to the vec even while holding references to elements that have already been pushed.
This is the left-pad of rust. Reconsider your life decisions if you need to pull in an external dependency replicable with 30 lines of code:
use std::vec::Vec;
#[derive(Debug)]
pub struct AppendOnlyVec<T> {
inner: Vec<T>,
}
impl<T> AppendOnlyVec<T> {
pub fn new() -> Self {
Self {
inner: vec![],
}
}
pub fn push(&mut self, element: T) {
self.inner.push(element);
}
pub fn clear(&mut self) {
self.inner.clear();
}
}Rust is one of the better languages when it comes to batteries included in it's stdlib. Even then, it's impossible to have a 100% coverage batteries included language because nearly everyone on planet earth has some different/unique use case for their code that doesn't fit a stdlib.
Engineering to these folks is a one-and-done endeavour. You just prompt and fire it off and ride off into the sunset, leaving the mess for someone else to clean up. They never see the work that goes on after the launch party. The midnight debugging sessions, the database migrations, the DNS failures, debates over which auth provider to use, the list goes on. Until the "citizen developer" is willing to engage in the less "sexy" part of software engineering, the world will move on without them as well.
It's the actions. The compute to run them isn't cheap at scale nor is the amount of auditing you need to do for security and compliance if you want enterprise/government customers.