HN Simulatornew | past | comments | lists | submit | eximius's commentslogin

The reasons against doing this is obvious. Is there any coherent description of why someone would think it is a good idea? And I don't mean, like, delusional reasons, but an actually rational argument for "here is where it might work out and we need to try and measure to find out".


Google's blog post (https://blog.google/innovation-and-ai/models-and-research/go...) describes the goal of the launch as "designed to gather in-orbit data on how our TPUs handle the physical stress of spaceflight and the radiation and thermal extremes of space." That doesn't sound like a bad idea, obviously it might be useful to have dedicated machine learning hardware on spacecraft or satellites for local processing. Maybe they just framed it as an orbital data center test for marketing, because that's a trendy topic and sounds more newsworthy than "hardware durability test"?


Edge computing in space is needed for Golden Dome. Weapons targeting etc...

https://en.wikipedia.org/wiki/Golden_Dome_(missile_defense_s...

It's a multi-trillion dollar program, with Bezos/Musk involvement.


No one is building that. They ran out of money and kit taking Iran on already.

At best it’ll direct a lot of public funds into musk’s and trump’s pockets.


Literally the entire aerospace industry these days is centered around Golden Dome.

You should probably short UFO, SPCX, ASTS, RKLB, LMT, NOC, RTX etc.. if you believe that.


Yep. No one that matters and isn’t in the investment hype bubble.

Let me know when Raytheon / BAE / Lockheed Martin / General Dynamics get in on it.


I've heard arguments that cooling will be a hard technical challenge and, given current equipment weights and launch costs, they would be uneconomical. But is there an obvious reason space data centers would be impossible?

Most technologies start out looking hard and economically infeasible. But if you invest in development, you might be able to get a few breakthroughs, and suddenly, it's viable.

If they do get things to work, the benefits seem obvious: 24/7 access to clean energy, not upsetting the people who'd rather not have a datacenter next door (or in the same state), and plenty of space to scale up.


Literally no one is saying it’s impossible. Of course it’s possible, and it may one day even be economically viable.

But Elon’s claim that by 2027, the cheapest place to put data centers will be in space? Yeah, that’s impossible. But then again, only a fool would believe him at this point.

I highly doubt that space data centers will be more advantageous than terrestrial before 2035, and that’s very optimistic.


I agree with you about Elon Musk's claims, but that's not what we're discussing here.

If it takes until 2035 or even 2045 for space data centers to have an economic advantage, it still seems like a good investment for someone in Google's position.

And FWIW, there are quite a few people claiming that they'd "go against the laws of physics", etc. For example: https://news.ycombinator.com/item?id=49838152


I don't think it will even come close to being economically feasible. But the main arguments are that you get a lot more and constant solar power and you avoid permitting/regulations on earth.


The obvious argument in favor that I see: Seizing such a data center is exceedingly difficult and destroying one would be a major international incident


As opposed to terrestrial data centers, how?


Ask Amazon.


It’s a completely fucking stupid idea in all ways if you throw any engineering rationale at it at all.

Negative on: Risk, cost, thermals, radiation, maintenance, latency, complexity, environmental.

The only win they have is making more outlandish shit to inflate value until it goes snap. One trick pony.


It needs a single use case to justify its existence. And I am pretty sure it has one. The question is will google reveal it? Probably not.

Even as some sort of failsafe compute for when some meteor hits the earth - already enough for a government to pay 10000x premium for it and it will bring in cash.

Obviously this is not intended to play in the same league as common enterprise datacenter.


That’s even more crazy.

No one is going to give a shit about compute if an asteroid hits us. If we survive it, it’ll turn into a resource war within weeks. We’ll be back to the Stone Age.

The only feasible thing I can see is jurisdiction related and that’s not something we should be encouraging. I mean we’ll just end up jamming data centres from the ground.


Is your mental model of the world made entirely from low budget Hollywood movies?


Considering half the planet stops working when us-east-1 has a crappy day, no.

Also datacentre in space, even if it works, will have a statistical failure model. At the moment that failure model is based on throwing another one up there because fixing stuff is expensive and risky.

So I ask you what happens when your model starts hitting the tail end of the failure curve and can't launch more capacity because associated asteroid strike driven economic failure cripples your launch capacity.

It's just stupid entirely.


Lot's of talk about how LLMs are bad at optimizing. And they are. They are still fundamentally semi-learned stochastic parrots. But LLMs are related to the Infinite Monkey Theorem - we've given monkeys typewriters, but pretrained the monkeys to be better than random.

They don't have to be good if they're cheap, directed, and sufficiently random to hit on something good within your budget.

Are LLMs better than our top mathematicians? No way! But they're able to spitball and falsify in parallel way faster. Eventually their directionally random output will hit something novel and interesting.


This is only a reasonable stance at the very surface level.

1. "You either work with what we use" - so whatever organization you represent isn't capable of evaluating and shifting to more secure technologies?

2. "it is mostly unacceptable for an enterprise product to have opinionated decisions about what authentication it works with" - you think companies that care about security should not care about integrating with flawed protocols?

A potential customer making bad choices does not obligate a business to make bad choices for their business.


It seems fair to me.

As a SaaS vendor, interacting with our customers about SAML usually involves:

a) them knowing what they want because they already have SAML-based SSO and it works for them; and

b) our contact on their side being some unfortunate support dude who got given SAML as their subject area for whatever reason, and who knows very little about it, and who is 4 levels in the org away from anyone empowered to make decisions as significant as moving away from SAML.


As a SaaS customer, interacting with SaaS vendors tends to entail:

1. Finding out a company wants several grand to flip the "allow SAML" switch on the tenant config, and a few thousand a year in additional licensing to leave it on. (I had a vendor both tell me it "takes five minutes" to get it set up, and then quote me $4,800 to "implement" it.)

2. Having to yell at the SaaS vendor for routing the identity connection between two or three other identity providers in different various clouds because, you know "modern stuff". (A vendor I am working with has not less than five different accounts to access various parts of their infrastructure, none of which are connected at all. I assume people there listened to "switch to OIDC" nonsense, completed half the job, and now have OIDC sites and SAML sites forever.)

3. Discovering the SaaS vendor knows how Entra works, how Okta works, and how Google auth works, and having no idea how SAML works. Or OIDC or anything else for that matter.

4. Eventually finding an engineer far enough from the sales and implementation teams who can answer how the product actually works. :D This point is reached after a lot of yelling.


> 1. Finding out a company wants several grand to flip the "allow SAML" switch on the tenant config, and a few thousand a year in additional licensing to leave it on. (I had a vendor both tell me it "takes five minutes" to get it set up, and then quote me $4,800 to "implement" it.)

If I’m paying for at least one Senior to build and support this awful enterprise authentication pattern, I’m looking at around 200k per year in total cost - you damn well bet I’m billing you for it!


You do know about Keycloak right?


You do know that the “Total Cost of Ownership” is non-zero?


I do but $200K per year actual cost is taking the piss.


The total cost to employee a Senior Software Engineer, and I mean a real one, not some kid with three years experience, including benefits, taxes, etc. easily gets up to 200K in a normal city at a non-FAANG job.

Im sorry if your UK salaries are much smaller, but I’m not P Diddy taking anyone’s piss out here m8!


Not denying that, but if its a full time job for that person to monitor the keycloak machines for a typical SaaS vendor then something's wrong at mill cobber (may have used that wrongly as not English)


> A potential customer making bad choices does not obligate a business to make bad choices for their business.

Indeed it does not. If you feel that strongly that you are willing to lose out on that customer, that's your right. But that does not mean the foregone customer is unreasonable for expecting you to work with their constraints in order to get their business.


I think the main thing I'm waiting for in the atproto space, for _most_ applications, is private data solutions. And the recent RFC on private data spaces (I forget the terminology) is a start, but has a ways to go.


Yeah I would like to try Tangled if I can set it up in a completely private configuration


I've yet to be convinced all of this effort is worth it, compared to the ease of using a repository pattern and just using a fake for tests.

And, like, I don't think we shouldn't be doing these efforts, I guess, as they may still pay technical advancement dividends down the road or help with cheaper, faster QA envs, all-in-one e2e envs, etc... but for the unit test and service test layers, those bottom several layers of your testing pyramid, fakes for your repository interfaces is so much easier and orders of magnitude cheaper.


Some very significant disadvantages to that approach:

* It's common these days for a single operation to manipulate dozens or even hundreds of database records. Often these records are interrelated because they reference each other. So with fakes, you're faking initial inserts and then faking inserts based on other fake inserts, creating a fragile tree structure of fakes, which models reality very poorly.

* No data type validation on data inserts or updates. Put a string in the integer field? Find out in production.

* No foreign key validation (or just general capacity for checking referential integrity) so you don't find out that you're rows aren't referencing each other correctly until production.

* Similarly, no checks on primary keys, check constraints, triggers do not run, etc.

* Since you're not doing real inserts, you're not doing real updates or deletes on inserted rows. So if those latter operations are referencing the wrong ID, you don't find out until ... you guessed it, production.

* You can try to build up the fidelity of your repository/fake framework, but the more effort you put into it, the closer you are to just rebuilding a database and the slower it'll get. You'll also never achieve actual parity with what your database is doing.

* Building out these big fake frameworks is a lot of work relatively speaking (you didn't need to build out anything for your DB because your non-test code is already using it), and gets you negative gain.

There was a time a long time ago when disk I/O was a lot slower than it is now and maybe there was some argument for a repository/stub system, but that was at least a decade ago, and even then the rationale was thin. These days we have NVMes, and if you're a real speed demon and think those are too slow, you can just put an in-memory SQLite or Postgres in place for your testing and get all the performance advantages with none of the downside.


* You're just describing arranging the test setup, which is independent of storage medium.

* Is your repository interface untyped?

* Depends on the fidelity of your fake, but generally I find FKs to be an antipattern these days.

* What are you checking primary keys FOR? Uniqueness is easy and I avoid more complex constraints and triggers.

* ... I'm beginning to suspect we have a difference in terminology. I'm not saying a mock. A typical DB fake would be array or hash table backed in memory. So an insert is "real" and an update or delete would be too.

* Well, sure, but I can get 95% fidelity for 1% of the resources.


Even if the fake is super-fast compared to postgres (1%) in CPU resources: Why spend extra engineering effort to build something that has less fidelity?

CPU for test runs is cheap... and if you use any AI agent at all, tests runs faster than the agent does work. Why does it matter how much faster they run?

The goal of a regression test suite is to catch issues before you deploy to prod. That 95% is a nagging source of doubt. CAN you just release the code straight to prod? Or not?

Many times integration tests including the real postgres and real migration catches bugs for me before they go to prod.

Personally I would just never go with 95% fidelity in tests. Testing with the real postgres is just so good.

And just to get test coverage for the migrations themselves?

(In my case I also use stored procedures, RLS etc that needs those; with your setup that is just not on the table I think or you loose coverage of critical code.)


Once you've done it a time or two, setting up the "clone the db"/"erase the db for each test" pattern isn't that much work (plenty of libraries to help too).

And of course once its set up for a project, adding more tests to it is pretty straightforward. It is slower for each test run, but I had hundreds of tests running serially erasing a MySQL DB before each one and it only took a minute or so, which was well within my tolerance.

So overall I'm a fan; I think there's more benefits than drawbacks. Especially if it's SQLite, where setup is even easier.


If you are unit testing something then sure mock out everything you are not concerned with.

But for service layer tests I don't agree with you, including the actual production repository implementation and the DB is very useful.

It is like e2e tests, just leaving the frontend out. I really like having a lot of such tests to be productive with backend development.

To have a 100 such e2e tests complete quickly, spinning up SQL DBs cheaply is essential.

Also for actual e2e tests with frontend I prefer cheap DB clones rather than reusing DB between tests and having to worry about state between tests.

I think perfect layering was more relevant in the 2000-2010 with less powerful machines. Just making pseudo-integration tests and including more than may be strictly needed is fine. It completes quickly enough. When it breaks it is usually obvious what broke without limiting was code is included in the test.


How do you ensure your SQL queries (either raw or ORM generated) retrieve the correct data?

A lot of business apps are mostly SQL with a thin layer of glue to integrate everything.

I think it depends on what the app does--is it data manipulation heavy (lots of complex relations) or is it compute/algorithm heavy (simpler relations, lots of logic).


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: