Yeah that is the sad thing. Fewer desktop options these days. And CLI client is OK. Actually for an astronaut probably OK as they are used to learning systems. They'd appreciate reliability.
Enshittification has reached space. Woohoo! We did it. Just use the web version! Love to know how how the web version loads with a couple of seconds network latency.
Multiply by 1000. Then multiply by 10. And that is expenditure on another country but instead of for promoting equity (how can anyone be against DEI as it is properly defined???) it is spent on slaughter.
If you pay tax on generated energy they would have to let you deprecate the cost of the panel as a cost. Would be interesting as to where that lands and if it makes much tax revenue at all.
No your normal socket can be used the other way around without issues and that reverse load doesn't create a problem.
Its even reducing your load on your main line beause the energy directly flows into the next consumer.
German socket has earth, thats fine. It has protection mechanism and shuts down if it can't sync to the powergrid. The panels only produce (in peak!) 400-800 watts. Thats not an issue.
That is very interesting. I guess it makes sense. A properly fitted solar does roughly the same thing. But electics are weird and there are lots of rules that defy intuition. E.g. you can get a shock without a full circuit on AC.
The same people that pursue economic incentives are who I hear speaking about number of lines produced by developers as a useful metric. I sense a worrying trend toward more is better with respect to output, when the north star IMHO should be to make something only as complex as necessary, but as simple as possible. The best code is no code at all.
Yes great so we sell shit. No one buys a ticket because ofnhow safe the 737 Max plane is or buys a post office franchise based on how good the software Fujitsu sold the post office is, but fuck lets take some pride in outselves and try to ship quality work.
I don't think that's a fair comparison. Google Maps, Google Calendar, Google Drive, Google Search, Google Chrome, Google Ads, etc. are all clearly completely different products which have very little to do each other, they're just made by the same company called Google.
GitHub is a different situation. There's one "thing" users interact with, github.com, and it does a bunch of related things. Git operations, web hooks, the GitHub API (and thus their CLI tool), issues, pull requests, Actions; it's all part of the one product users think of as "GitHub", even if they happen to be implemented as different services which can fail separately.
EDIT: To illustrate the analogy: Google Code, Google Search and Google Drive are to Google what Microsoft GitHub, Microsoft Bing and Microsoft SharePoint are to Microsoft.
Completely agree, it makes it worse actually as Github's secondary functions so to speak are things we implicitely rely on.
When I merge to master I expect a deploy to follow. This goes through git, webhooks and actions. Especially the latter two can fail silently if you haven't invested time in observation tools.
If maps is down I notice it and immediately can pivot. No such option with Github.
It depends, for example - I would consider Google Drive uptime as part of say Google Docs’ overall uptime because if I can’t access my stored documents or save a document I’ve been working on for the past 3 hours because Drive is down I would be very pissed and wouldn’t care if it’s Drive or Docs that is the problem underneath I still can’t use Google Docs as a service at that point.
reply