jmagoon

5-10 years? Expect it in 5-10 months.

That's exactly what the post you're replying to is saying. It's saying that ChatGPT _would_ respond a certain way but has a bunch of schoolmarm filters written by upper middle class liberals that encode a specific value structure highly representative of those people's education and backgrounds, and that using it as a tool for information generation and synthesis will lead to a type of intellectual bottlenecking that is highly coupled with the type of people who work at OpenAI.

For all the talk of it replacing Google, sometimes I want a Korean joke (I'm Korean, damn it!) and not to be scolded by the digital personification of a thirty year old HR worker who took a couple of sociology classes (but not history, apparently) and happens to take up the cause of being offended for all people at all times throughout all of history. The take on ethics being a vague "non-offensiveness" while avoiding all of the real, major questions about ethics (like replacing human workers) with these kind of banal answers about "how we need to think seriously about it as a society" tells pretty much everything there is to know about what the ethical process at OpenAI looks like which is basically "let's not be in the news for having a racist chatbot".

These blue check VCs on twitter are on such a gnarly anti-human bent these days. They are targeting a capitalist maximalism where a few people are very wealthy and everyone else does nothing (except...consume SaaS products? where do they think customers come from?). They are so absolutely caught up in AI development speed that they have traveled all the way to techno-eugenics, totally eliding the problem that there are a bunch of humans in the world that can't just be "disrupted" without their nightmarish little automation empires being seized by force.

If these were far leftists talking about the need to reduce human capability because of the climate they would be rightly derided as being eco-terrorists, and that's precisely what we should see these people as. Ultra-libertarian terrorists whose primary, unabashed goal is to enrich themselves at the cost of human society.

Massive social upheaval that the super wealthy think they are immune from, even when they are directly responsible for its creation.

Open source software is often funded by big corporations once it hits critical mass because it's a nice way to stamp out competing small businesses who might be have been able to charge $ for a small chunk of software functionality.

The real issues around data bias get completely crippled by the article writers' need to make everything about culture wars. Many computer vision systems have literally nothing to do with humans, e.g. one of the most common use cases in CV at this point is defect detection in manufacturing.

The data bias issue is about having way more samples of class X than of class Y, or class Y sharing an unknown but correlated feature (medical images with labels have this problem) that the developer doesn't identify, or any other number of "biases", like all the images being too bright, or taken with a camera that isn't identical to the one that's going to get deployed in production, etc., etc.

There are real issues that can be fixed / engineered / understood in terms of producing reliable output, and xAI absolutely helps with that! But for whatever reason journalists don't seem to understand that these systems need normal engineering safeguards, like any automated system, and bring it back to one poorly engineered model to talk about Big Bad Racist AI always denying loans based on race.

Faux scarcity is a key concept in the crypto ecosystem.

The only coin that's actually stable, because it's the only one that has any actual purpose.

My least favorite part is how completely impossible it is to discover all the implicit variables set by other cmake files, and there's no common convention, so some libraries are like ${ZLIB_INCLUDE_DIR} and some are #{zLib_INCLUDE_DIRS} and you have to just manually try a bunch of combinations to finally find what works because the scripts themselves use weird string based metaprogramming to build the variables themselves.

It is, in fact, already used by everyone, because it's an evolution of the chipset in basically every smartphone in the world with widely divergent target audiences, income brackets, and technical limitations.

I prefer for the class of device the Air fits into (travel, work laptop) to have a nicely curated nix machine with working drivers out of the box. Apple has continued to improve on this by making this product class faster, more battery efficient, and* cheaper.

There is a massive marketplace for tinkering on computers, from Arduinos to multi-GPU ML rigs. Trying to optimize for both classes of things seems like a foolish endeavor, especially when Linux users represent such a small fraction of the desktop market.

I honestly struggle to conceive of the educational history needed to conflate the long history of censorship with "SJWs". Some of the greatest works of western literature in the twentieth century directly address the concept, and the majority of texts that influence "SJWs" were incredibly subversive and likely to be banned at their time of release due to their attack on conventional power structures that had the ability to censor them (Black people voting! Women voting! Anti-religious scientific heresy! Human rights!).

This strategy of demanding proof for something that is easily discoverable through any simple google search ("history of censorship") is such an exhausting argumentative tactic.

The other thing these posts confuse me about is that a single auto-scaling group and load balancer isn't much more difficult to set up or maintain, and if you're already in the low traffic world, it's barely more expensive, all for the vastly improved ability to respond to things breaking that you didn't expect.

Why does one shard being down remove all their inbound functionality? I'm struggling to understand the purpose of sharding if you can't pull a node offline and replace it while you deal with the wraparound. Is it part of postgres that if one shard has an issue, the entire cluster goes into read only mode?