HN user

nirse

189 karma
Posts6
Comments71
View on HN

Secondary school physics teacher here: The article is conflating power (watt or joule per second) and energy (joule or kilowatt-hour), so any claim they make is nonsense and the article shouldn't be taken seriously. My students make the same mistake all the time but they don't get to publish it :-)

Power is energy per time unit (thus: energy = power x time), so while the power of a lightning strike is very high (~10GW), the overall energy isn't because it only lasts for a very short duration (apparently the duration of a lightning event is hard to define, [1] says about 0,5 seconds, other places mention much shorter durations, ~10us). So if that 10GW lasts for 0,5 seconds, the total energy is 1,4MWh, which is 1/6 to 1/10 of the electrical energy an average American household consumes in a year[2].

[1] https://amt.copernicus.org/articles/16/547/2023/ [2] https://www.eia.gov/energyexplained/use-of-energy/electricit...

Bored of It 1 year ago

I believe it would be a far greater problem if those people didn't die. Aging populations are a huge problem around the globe and unless we'd improve the quality of life to such a margin that octo- and nonagenarians are able to care for each other, I think we're all better off with people dying of old age.

I work for a small company, around 10 devs. We've picked up quite a few projects over the years where a freelance team came in, built something and when the going got tough, walked away. That said, I've seen the same happen at renowned companies, so perhaps it's just an issue of generally people taking advantage of the shortage in experienced devs. I would aim to get some longer term stability, either by working with a company you trust through your network, or engage a tech Lead/CTO for a longer term who can oversee the contractors.

I've read somewhere that the iodine can negatively affect the fermentation process, so that it's better to use iodine free sea salt. Cant remember the source, though.

Is it just me, or has DDG been having trouble often lately? Or is it just a combination with some outage + degradation of search results lately that makes me g! regularly these days? Didn't use to need that.

My mom grew up in South Africa, '40s and '50s, she always made us wash our lips after eating mango to avoid a rash. Only later did I discover I didn't need to, I always assumed the rash-causing compound has been bred out of modern mangos.

Funny, I started typing a comment here, about the author not getting the Ruby side of things right, that actually the difference would rather be that Ruby uses a special language construct and Python just normal methods and conventions. But just skimming through the previous comments it seems that Python also has these a `yield` keyword that would be more idiomatic to use.

I think we're dealing with someone who had limited experience with both Python and Ruby. This article is somehow getting more attention then it merits.

It's hard to compare as the business model has changed, I believe that nowadays it's basically impossible for a library to get an individual subscription to a individual journal: subscriptions are bundled and (online) subscriptions are sold institution wide with contracts running in the millions. That's very different from what Kunth is describing, where individual libraries choosing what subscriptions they need (eg we need the JoA in our (physical) collection so we buy a subscription to that).

I agree, if you think of just a few big OSS project, like Linux, Postgres, Sqlite, nginx or apache web server, run as proprietary companies each of those would easily be worth way more then $177M (for reference, nginx was sold for $670M in 2019).

This is a webserver that can run various web applications for you. In a typical setup you'd run a web/http server (nginx or Apache etc) to handle the 'slow' connections to the client and a separate app server (say, an express application, or Django or Rails etc) that is completely separate from the webserver. The web server acts as a reverse proxy, sending the request on to the app server. The response from the app server is then passed to the webserver, which sends it back tot he client. So a request would this path: client -> web server -> app server -> web server -> client.

This is done because web servers are optimised to handle (many) requests from clients (including things like TLS termination, optimised handling of static files, orchestrate to which backend service to send a request and much more), while application servers are optimised to run the application code.

In this model, the web and app servers run separately, for example in separate containers and they have to talk to each other so you have to somehow connect them (often this is done through a network socket).

So what Nginx Unit does is combining the two: it can do the standard web server stuff (not everything a normal nginx can do, but often that's not needed anyway), but also run your application for you, which could, depending on your setup, make your life a bit easier, as now you don't have to tie the two together.

Why would that be misleading? This seems to be just an attempt to better understand (some of the / potential) causes that unknown condition. Perhaps it doesn't help to diagnose it, as there might not be any direct evidence left in the body to point at the original cause, but in the longer term it certainly helps if you know where to look.

But also the sun is burning fuel and eventually that will run out and we don't really have any means of renewing that fuel (I don't know where to order intergalactic hydrogen).