ciconia

No, the real question is how to keep the earth from being cooked by greenhouse gases, not in 500 million years, but actually in a few decades. This article borders on climate change denial.

It would be interesting to measure the environmental cost, which is substantial, against the benefits: 40 minutes instead of 50 from Tokyo to Nagoya, 67 minutes instead of 90 from Tokyo to Osaka. Is this reduction in travel time worth consuming 3 to 4 times the energy?

Oh there's nothing to worry about, AI is gonna make everything just great! /s

I think it's called HTML+CSS...

> Around 10% of Gaza's journalists have been killed versus 2.5% of healthcare workers.

One possible explanation is that journalists have a much higher probability of being close to where the fighting is, than healthcare workers.

> This platform for tech news should not become a place for political posts, nor even for posting regular news headlines.

What's a political post? What's "regular news"? And where do you draw the line? If not interested, you can just move on and ignore. There's plenty of AI articles all over the front page.

> Uch. TRAINS. They’re a necessary evil in many of our lives. Horrible big tin cans full of smelly people that never turn up on time and make you late for everything. The less time spent on them the better. At least for most of us in the UK, anyway.

Not my first though when I think of trains, but I'm not in the UK.

Personally, I welcome our new anonymous block overlords. As a developer who writes more library code than app code, I think this is a good addition. Doing a cursory check on my code, in about 80% (gross estimation) of cases where a method captures a block, it just passes it on to another method call. The new style of anonymous block helps signify that the block is not directly manipulated or stored, but is just forwarded to another method. LGTM.

> I just wish Web wasn't such a frustrating development experience.

I have to say, having recently gone back to doing some web dev work (doing some dashboards with lots of D3 visualisations), I was pleasantly surprised to see how better things have gotten. working with CSS is better (with stuff like grid, flex, nested selectors), and JS is also much much better (import maps, fetch API).

I'd say for developing cross-platform apps it's a pretty good deal.

I find those new car screens a total turn-off. When driving I don't want a giant screen just in the periphery of my view to take my attention off the road. The passengers anyway don't need it - they each have their screens, so what's the point? Just give me a good electric car with good range and the usual accessories and features, minus the screen.

The Oxfam report can be found here: https://policy-practice.oxfam.org/resources/inequality-inc-h...

Note this is for a Ruby on Rails application. The slowness is I believe more due to the framework than the language runtime. In any case, it's still early to determine the impact on performance from upgrading to Ruby 3.3. I guess we'll be able to tell more in the coming months.

I believe with version 3.3 Ruby is back in a big way! The language focused on developer happiness and derided for its slowness is slow no more.

YJIT is an amazing technology, and together with other innovations like object shapes and various GC optimizations, Ruby is becoming seriously fast! Big Ruby shops such as Shopify [1] have been running 3.3 pre-release with YJIT and reporting double digit percentage performance improvements.

Personally I'm really excited about Ruby and its future. I can't wait to start working with Ruby 3.3 and using it on my client's production sites...

[1] https://railsatscale.com/2023-09-18-ruby-3-3-s-yjit-runs-sho...

Edit: add percentage to performance improvements.

Canning is a very useful method to deal with a surplus of production from your garden. We regularly conserve vegetables from our garden in glass jars. We also do this with meat, legumes, really anything we can get our hands on that's on sale. We also make soups and mixtures such as sloppy joe and conserve them.

It's really simple: you take glass jars (the kind that can be closed hermetically, there are multiple kinds), put the food in them, seal the jars, put them in a big casserole full of water, and boil them (an hour for vegetables, and hour and a half for meats). That's all. They can last for years if properly sealed.

Fun fact: when my wife and me got married, we went to the flea market and got ourselves two simple silver rings that cost us about $5 each and that was it (we were both kinda broke at the time). 15 years later, we're still wearing the same rings.

Doing everything possible to prolong life has consequences beyond the life of the individual: it's a significant cost to the economy and to family members. There's the cost of the medical treatment itself, but people living longer now also have to finance their life with their savings or even keep working instead of retiring, so their kids get a smaller inheritance, and have to compete with their parents in the labour market.

When using green threads/fibers/coroutines, an interesting technique to make signal handling safer is to run the signal handler asynchronously on a separate fiber/green thread. That way most of the problems of dealing with signals go away, and there's basically no limitation on what you can do inside the signal handler.

I've successfully used this technique in Polyphony [1], a fiber-based Ruby gem for writing concurrent programs. When a signal occurs, Polyphony creates a special-purpose fiber that runs the signal handling code. The fiber is put at the head of the run queue, and is resumed once the currently executed fiber yields control.

[1] https://github.com/digital-fabric/polyphony