Hacker Newsnew | past | comments | ask | show | jobs | submit | krschultz's commentslogin

In my experience as a VT homeowner we have relatively frequent short outages. It's pretty rural and the weather is brutal. I think the grid doesn't have as much redundancy as denser areas. We had one 3 day outage 2 years ago in the middle of winter which got quite dangerous, but otherwise I haven't had anything more than a few hours.

Also we have propane heat - but I need electricity for the blower and control board. So the electric consumption is pretty minimal, but it is critical.


I tried to signup for this program but the building code gets in the way. You need 3' from both edges of the battery to a window or door. I don't have a wall with 8-9' between windows. The alternative is to build a fire proof room in your house which takes up a lot of space. Ultimately it was not worth it even with all the financial incentives. The rules might seem innocuous but they're a dealbreaker. It's far easier to get a propane or diesel generator installed.


Which is kind of wild, because generators powered by combusting fuels are also giant fire hazards (and produce noxious CO and other gases), of course.


Generators are generally used outside. There are some rated for use inside, but they also have strict regulations on how that is done. (there are also some used inside but they will kill someone soon)


Batteries can also be located outside, of course. There's still fire risk (from both) due to proximity.


Maybe where you live, but where I live the temperature outside is bad for batteries.

Though what is "inside" is debatable. My car can sit outside because it has the batteries in a case that is climate controlled when needed, and so the batteries count as inside even though they are in a car that is outside.


Right, very fair.


I would be much more nervous about a 13+ kWh battery than a natural gas generator.

The generator is generally only risky when in operation. For natural gas units, a normally-closed solenoid keeps the gas off unless the controller actively commands it. A battery is constantly in a state of non zero fire risk when charged.


Taking out a window and putting the battery in front of where it used to be was no option, I suppose?


Why downvoted?


The Highlanders are testing vehicles: https://zoox.com/journal/autonomous-zoox-testing-vehicle


You don't make breaking changes. You provide the new API and the old API at the same time, and absorb the additional complexity as the library owner. Best case scenario everyone migrates to the new API and eventually remove the old one. This sounds onerous, but keep in mind at a certain scale there is no one commit in production at any given time. You could never roll out an atomic breaking change anyway, so going through this process is a reflection of the actual complexity involved.


Thank you for the response!

Genuine question: if you can't have one commit in production at any given time, what advantages for the monorepo remain?


> if you can't have one commit in production at any given time

That might be possible in a simple library + 1 consumer scenario if you follow the other commentors' recommendation to always update library + consumer at once. But in many cases you can't, anyway, because you're deploying several artifacts or services from your monorepo, not just one. So while "1 commit in production at any given time" is certainly neat, it wouldn't strike me as the primary goal of a monorepo. See also this discussion about atomicity of changes further up: https://news.ycombinator.com/item?id=44119585

> what advantages for the monorepo remain?

Many, in my opinion. Discoverability, being able to track & version all inter-project dependencies in git, homogeneity of tooling, …

See also my other comment further up on common pains associated with polyrepos, pains that you typically don't experience in monorepos: https://news.ycombinator.com/item?id=44121696

Of course, nothing's free. Monorepos have their costs, too. But as I mention in the above comment and also in https://news.ycombinator.com/item?id=44121851, a polyrepo just distributes those costs and makes them less visible.


Thank you very much for the info!


Because they make more money using their servers for their own products than they would renting them to other people. Meta has an operating margin of 41% AFTER they burn a ton on Reality Labs, while AWS has a 21% margin with more disciplined spending. Social media is a more profitable business than infrastructure.


Does Meta make money from anything other than ads? It's not a dismissive question. I'm curious if social media implies anything other than ads.


> Advertising (over 97.8% of revenues): the company generated over $131 billion in advertising, primarily consisting of displaying ad products on Facebook, Instagram, Messenger, and third-party.

https://fourweekmba.com/how-does-facebook-make-money/


That's not universally true. The sewer system in my town was overbuilt in anticipation of a development that fell through. That's why sewer / water bonds are typically up for vote separately from property taxes because there's such an interplay with development.


That's still cheap when you're looking at the whole picture. Sewer is much cheaper than police, EMS, road construction/maintenance, schools, etc.


Huh? You have to pay property taxes now and those could end up being too high for subsequent generations to afford. That happens all the time and is a common reason why property gets subdivided. This is simply a question of whether the value of structures on that land should be included.

If anything a pure land value tax should be more predictable than a property tax, I got hit with a major property tax increase and looked into it, the town had calculated the new property tax based on an incorrect square footage and number of bedrooms for my house. After filing an appeal and going to court I got it fixed, but that was a more capricious process than if it was simply based on the value of the land under the house.


Threads is already GDPR compliant, that's not the only regulation the EU has made that covers these kinds of apps.


I would heavily consider this type of system once build times become a major pain point. That often happens somewhere around 20-50 people working in one codebase. So I think this is a problem space for medium sized companies. Truly small companies probably don't need this and should use the standard ecosystem tools, BUT if your team knows how to use it there's little downside in started from a Buck / Bazel. Especially since you get most of the benefit if you have a nice clean DAG of your modules, and that's easy to build at the beginning and hard to refactor into later.


IMO one of the nice things about Buck or Bazel is that once you learn it, switching languages doesn't require you to learn a completely new tool. Obviously the cost of learning it the first time is high and if you are used to one ecosystem may not be worth it. But I'm now on my 3rd different ecosystem that uses Buck/Bazel (Android, iOS, C++) and it's nice to not worry at all about the underlying tools.


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

Search: