Time is local Timestamp is a counter

A unix timestamp does not have different timezones. It is a counter. No matter where u are in the world a timestamp call should give you the same numeric value at the same instant. It is not time zone adjusted. Store that number, unadjusted as the source of truth. You can get to any local time after that.

I think the thinking is that if you had kids you created future cows for the tax plantation so you contributed more to the country.

Yep, gotta keep breeding more little tax slaves to keep the plantation operational.

But I'm paying taxes for my pension, and my kids will pay taxes for theirs.

I know that the economics don't actually work like this, but this is the social contract.

You need to pay taxes and have kids for the numbers to work out.

If your pension benefits are calculated based on a 4 workers/retiree ratio, but then your whole generation has like 1 kid per family then the system will obviously break down...

But why? That would imply a worker 30 years ago produces only as much as a worker today. Which is obviously untrue.

No, it would only imply that the worker/retiree income ratio (and tax/pension burden) are somewhat constant which is arguably the case; german pensions specifically rise with wages and get adjusted for inflation.

Productivity gains on the other hand get easily eaten up by increased consumption/expectations, or are overstated to begin with: producing 5 times more TVs/ipads does not make the plumber cheaper (nor a house), and unaffected professions actually suffer (=> baumol effect).

> german pensions specifically rise with wages

Is that because higher earners make higher contributions to the pension plan?

No, it is because pensions are scaled (yearly) proportionally to wages (simplified, the actual process is more complicated)

People automatically get a higher pension because they make more money? Without actually paying more into the system? That's an obviously flawed and unfair system, bound to fall over no matter what.

Working people collect points each year based on their income relative to the average (this is proportional to how much they pay).

Retirees then get paid based on how many points they have.

Both the worth and the "cost" of those points scales with average income every year.

This basically autocompensates for inflation and rising wage levels, but decreases in population size are problematic.

As I said, this is how the economics of pensions work.

But the social contract does not care about that.

Its like growing a crop.

Except the farmer demands you grow while stomping all over you, and then reserves the fertilizer for the dying crops.

Internet related would be, back in the early 2000s when I was building out infrastructure of pinkbike/trailforks I was optimizing things and discovered that this initcwnd parameter was hardcoded to something like 2 or 3 packets in the linux kernels. This was causing the initial page to require multiple RTTs to load so I figured I would change that and recompile the kernel to make sure all out pages would be transmitted in one go. This made out site perform a lot better compared to most sites at the time. Funny at the time I was a bit worried that the IETF would discover this and shut us down or something. These days that parameter is default to something like 10 and you can increase it with a config parameter.

Hats off. Great interface and i enjoyed making a few simple beats which is probably a very small part what the system is capable of. Thank you

Thank you. The UI is pretty basic but I tried to design it in such a way that the functionality would feel intuitive to newcomers, with as few hidden features as possible. I picked this project to share because I figured that it was very easy for people to play with by editing the pattern, without needing to understand how the sound synthesis works.

I think this article is cherry picking here trying to make Canada look good compared to say the USA and other countries. ( im canadain btw ) I think it's easy to take in 28K refuges when the illegal load is very small in Canada, of something like 20K per year [1] Compare that to the USA that needs to deal with an illegal load of 20X that. [2] And for 2019 the USA load seems to be twice that of 2018. [3]

1. https://irb-cisr.gc.ca/en/statistics/Pages/Irregular-border-...

( and this is just the sw border, not accounting for flights ) 2. https://www.cbp.gov/newsroom/stats/sw-border-migration/fy-20...

3. https://www.cbp.gov/newsroom/stats/sw-border-migration

I suppose it depends if the use/need is in serial or in parallel.

If you agree that using a CDN for static content is a good idea, then it would seem HTTP/2 Push is useless. The website is served from your servers while the static content is served from a CDN so you can't "push" it in the same stream as you webpage content. Am I missing something here?

Yes, you can't push cross-origin.[1] However, there's still a lot of use-cases where this is useful, such as if your entire site is static content, or if your app servers are behind the CDN as well.

[1]: Yet. I believe the web packaging standard (intended, among other things, to replace AMP) allows pushing bundles signed by other origins.

So there are 3 basic cases that websites use:

1. Site and static content are served directly by your webserver. ( HTTP2/push helpful )

2. Site served by your web servers but static content is served by a CDN ( HTTP2/push NOT helpful )

3. Site and static content proxied by some service. ( HTTP2/push helpful )

I'm not sure if I never understood this right, but it seemed server push was not an ideal overall solution. It seemed it was targeted to push needed css/js/image in the stream of the page result. But most assets that one would want loaded are coming via an external CDN so doing a push of that does not make sense. Yeah, I guess if you are proxying your whole site via the CDN. Am I missing something here?

My view on this is that it doesn't just work for "http page preloads assets to get", and more like "http request preloads other http requests" ... the difference is, in the case of a CDN, they could basically download a JS file for, say, a JS framework, but also send you jQuery, etc because they know it's dependent.

All this is to get away from a lot of our current hacky workflows (like file concatenation).

I don't see a lot of external CDN script (like cdnjs) use in the real-world anymore. That's sort of dated compared to bundling and using something like S3. Ideally, these days you'd still minify, but your *.html files could plainly include scripts, and the server would read the resources to be sent, and send them all over the same stream, rather than forcing a client to open multiple connections.

I saw a talk on this from someone at Fastly where they talked about protocol changes that would allow CDNs like theirs to do push from the edge

I hear ya...of the two bolded feature headings in the story we get: 1. Supersonic speed ( always welcome ) 2. League of extraordinary emojis ( the last thing I would care about in a new os release )

You can get centimeter accuracy with gps. http://swift-nav.com/piksi.html Even with cheaper modules and phones that dont carrier phase rtk, you can get meter which would be plenty for this application.