manoDev

This Pandora box is already open. Any argument about guardrails now are only attempts to create an artificial monopoly or keep this power in the hand of a single nation state, and _that_ is the absolute worst, most authoritarian future possible.

Don't you Dare use logic to analyze their statement, it's based on moral panic.

There's money now to _build_ these massive data centers. If there is long-term money to operate, we'll see.

It might mean we'll get cheaper cloud compute in the future, but I'm also positive on the market's ability to absorb the excess capacity quickly. It's Jervon's paradox.

It's inevitable. The value proposition of the software isn't large enough to justify (by itself) the valuation. Not to mention it's trained on lots of public or scraped data.

It's a gold rush, and the only guy getting rich will be the one selling the shovel (nvidia + cloud in this case).

CSAM is the perfect trojan horse to undermine privacy everywhere. No politician and no company can oppose it on the grounds of protecting privacy before having the reputation ruined.

Meanwhile the real pedos are rich people vacationing in well known places.

Mid-August there’s a shareholder unlock of 20%, we haven’t seen the dip yet.

The organism dumps Mg on the blood as much as necessary because it needs to remain in stable concentrations.

When a serum Mg test comes out low, the patient already has severe deficiency and visible symptoms, so isn’t very useful unless you’re investigating a systemic issue.

As explained by my endocrinologist.

Not great, not terrible.

> Some people don’t care enough > > The more people you hire, the more likely you are to hire people who don’t care enough about good interface design. Good interface design needs to be valued by everyone who can affect the work. That includes developers, designers, product managers, and often the CEO.

I know where you're going with this, but here's a twist:

A CEO who cares about interface _design_ is path to micromanaging and pain. A CEO should care about interface _designers_, who are (hopefully) the people trained on how do it well.

Even better: CEOs should care about developers with UI/UX skills, because too often CEOs adopt designers like a pet and keep them busy 24/7 asking for mockups.

The grime around the pot convinced me they’re telling the truth about 52 years :)

In the old times, I bought a Nokia smartphone (5230) because it shipped with offline maps – Nokia had the license for satellite data before Google Maps existed. I also drive a VW with built-in GPS and map loaded from SD card.

Offline maps are an obligatory "survival" tool. Most people trust too much they'll have connectivity, but it'll be the first thing to go down when it's most needed (extreme weather, blackouts, conflicts, etc).

Thank you for the tip on the app!

I understand that, but I would expect distant LEO satellites to appear close to the horizon, such that a relatively small aperture in the orbits would allow for a large cone of clear sky near the ground.

Should it be possible to coordinate orbits to create permanent clear spots on the sky where observatories are? A LEO no flight zone of sorts.

That's the difference between "inventing things" and "discovering things".

If you believe you're inventing a solution, doing just enough to solve the immediate problem and stopping is the consequence.

If you believe you're discovering a solution, diving deeper into the problem to try and uncover some truth about it, stopping at the first solution is not enough if you can't explain why it works or why it will keep working in the foreseeable future – because that involves solving a category of problems, not just this single instance.

People like to think in terms of under vs. over engineering, but I don't think this is the right angle to discuss. You can certainly over engineer the first solution because you focused on a single instance of a problem and "missed the forest for the trees" – identifying a general pattern is useful to find what category of problem you're dealing with, research prior-art on it and uncover elegant/economical solutions.

They make sense for so called audiophiles who don’t understand Nyqist frequency theory.

It’s like photographers who are confused about the difference between raw and bitmap (jpeg), videographers confused about the difference between linear raw vs log vs gamma encoded, etc.

Just because a data format with higher bit depth/sampling frequency/whatever exists for editing purposes, doesn’t mean it’s “better” or makes sense as a consumption format for a finished work.

Selling tele-operated robots in the hopes you get AI valuation is borderline scam IMO.

This is hiring a human worker with extra steps, worse cost benefit and in a dehumanising manner.

Roasted barley is also appreciated in Italy prepared like an espresso (Caffe d'Orzo), and in Peru as a kind of cappuccino with brown sugar (Pinol).

It’s always useful to look at prior art and review capabilities we might have missed. Innovation can happen by mixing the “good parts” of different old ideas.

Only in theory. The US still forces emergent countries to trade in USD under the menace of tariffs, staging coups, and military intervention.

The military budget is how the US enforces Bretton Woods. The jobs part is just a nice side-effect of any govt. spending.

If you ever worked with mainframe, you'll see a lot of similarities:

- Unified interface for object stores

- Source code stored with data files

- Job runner

I also see some similarities with Lisp machine, the fact Python also has a REPL, and able to dump/restore image state (but in this case discrete objects are serialized, not the entire memory).

This might sound crazy for people used to having 90% glue code / 10% business codebases, but to me seems like a very efficient way to have users directly drive what is effectively a large computer, and more like how things used to be.

The drawback is that it seems to be a monolith, and maybe hard to reimplement on top of more modern foundations. But as a general API, it seems to make sense.

It’s the same narrative as “the communists are developing nukes so we need to develop first”.

Have you taken a look at kids nowadays? They look like fking zombies glued to their smartphones and wireless headphones. I go walk my dog, and not a single kid tries to play with it - only people of my age (40s) do.

We’re raising a generation of completely emotionally detached robots. There’s something deeply wrong and unsettling, and it’s happening in plain daylight.

Isn't it reassuring the entire CC business hinges on a single proprietary appliance inside a cage at some DC? :)

Definitely. The secret will be identifying use cases where AI usage is a potential upside with limited downside, not the current blanket statements about replacing all jobs without considering lifetime ROI. There’s a lot of boring work AI can automate with minimal risk. There’s also the potential to decrease risk with AI too, including ensembles of different AIs modals and AI + human.

Git LFS is a major PITA, and if you use GitHub is even worse since there are quotas and rate limits that are charged separately.

I’m bullish on Apple because of that. Tech waves always oscillate between mainframe/thin-client models at first, then commodity hardware catches up. Apple is well positioned to deliver that with the M series, all it takes is for the current AI bubble to pop a bit and memory costs go down.

I’m working on a photo editor. As a first step, I’m collecting all my learnings about color science in a comprehensive article:

https://www.riq.net.br/pub/colorscience/

To make parent’s point more exact: from Chen’s definition, these ER diagrams derived from SQL are the “physical” (most low-level) diagrams, you cannot recreate the “logic” or “conceptual” diagrams from it.

I guess nowadays few people care about this difference.

Don't worry, open source AI will win. There's a reason everybody is desperate to IPO fast and get an exit, their competitive advantage is not lasting long.