indysigners

Since the usual arguments pro RE are being made: One of the main downsides of RE is

a) its need of fossil backup and b) profits of solar / wind goes into the pockets of its owners while c) the costs of fossil backup and increased network capacities are to be borne by the general public so that d) wealth is distributed from the bottom to the top whose e) RE systems a being subsidized by the public too.

In conclusio, the bottom half pays for the profit of top earners who can afford to invest in RE. That’s the green „revolution“ for ya.

Addendum: https://twitter.com/m_ott/status/1584648614282133504

US have fought in two theaters at the same time before, remember?

Photopea is super easy to use and I’m using it almost every day, despite having a fully licensed PS 2021 version installed on my iMac.

Photoshop is just way to slow compared to Photopea. So it’s both easier to use and much faster than the original.

Kudos to Ivan for this!

If you prefer reader mode, like I do, any Medium-based platform is a PITA cause all images are blurred. Anyone who is on a crappy connection will have them same. What a fuxxing shame! Can we stop using this crappy platform please?

What’s about the claim that if you drop GA, your site will degraded by Google and you’ll lose traffic?

Both the :has and the :contains selector (as in ul:has(> li:contains("Built")) ) were new to me. So thanks to the author for sharing that little trick!

I was using Ecosia for a number of weeks and did achieve some 80 planted trees over the course of that period.

However, I eventually was so frustrated over the poor search results that I did move back to DDG.

Ecosia‘s intentions might be noble and worth supporting, but I cannot really follow how one can stay with them when the overall experience is so poor.

I don’t even mind some possible privacy issues as noted above but it all comes down to being at least comparably good to Google and DDG. Which is sadly not the case with Ecosia.

Haha, they are up for a good joke it seems!

Haven’t heard about generative.fm either so thanks for sharing it!

From inside of Shopify I’ve heard about a lot of shit stories. For their employees, it may be less ideal to have a CEO messing around with code.

From the outside though, the company does extremely well.

Nonetheless, CEOs are generally not supposed to „make“ but to manage. There has to be a tradeoff somehow.

Disclaimer: It’s one of the Smashing Books I’ve been working on as their (ex-) product manager.

TypeScript in 50 Lessons was written by Stefan Baumgartner (https://twitter.com/ddprrt) and technically reviewed by Shawn Wang (https://twitter.com/swyx).

There’s a sample PDF chapter available at http://provide.smashingmagazine.com/eBooks/typescript-sample...

I hope it may be worth a read or perhaps even buying the book. Enjoy!

I’d rather have no telly at all than buying some crap Samsung tv for €2.000 only to see their programmatic advertising. Whoever at Samsung decided this must be drunk! But hey, I guess there still are enough people around who don’t care.

What most HN-“experts“ and the author of the article forget is: Fessenheim 2 has had so many interruptions and incidents because the whole technology being 50 years old, you lost count on how many incidents there have been. Think of you running a 50 y/o computer at home.

I live nearby the plant (within its 30km radius) and we had reports on Fessenheim incidents every other week or so.

The answer to why Fessenheim is closing is sadly one of politics.

This is some outright BS from the author here. Fessenheim is built next to the Rhein-river but below its own water-level. If the dam would breach because of an earthquake or flood, the whole nuclear plant would be under water. Does Fukushima ring a bell, what happened there? Exactly that!

Several examinations also found the inbounds of Fessenheim to be poorly protected from flood. They even have their own security measures and fallback circuits not properly secured against flooding. Only a water leakage would cause some serious issues not to mention a dam breach.

So with the combo of old tech, often interrupted uptime and shitty protection against floo, there are simply too many good reasons to close down the whole thing.

I know the folks at Baymard for quite a bit and love what they are doing. They aggregate years of research into their resources and for nearly every possible variation in the e-commerce world, they already have found an answer.

It's absolutely fantastic and very timely for an new IA project of mine. Thanks so much, Gerald (Gera2ld)!

Yup, exactly that. WordPress editors (WYSIWYG and Gutenberg) are still far more user-friendly and mature than a Netlify CMS that still is buggy like hell and where many little details and YAML formattings need to be fixed in code editor. You really cannot expect such a thing to be done by a non-coding person.

In iOS you can make use of Reader mode, just click on the Hamburger-like icon to the left side of the URL.

I switched only a few weeks ago and am not looking back!

Despite its simple appearance, login forms bring in a bunch of usability failures that so many sites suffer from, actually most of them. Social media login hasn’t necessarily helped matters either.

There’s a whole book dedicated to good, simple, mobile input-friendly and accessible forms at https://www.smashingmagazine.com/printed-books/form-design-p... and it has a whole chapter dedicated to good login forms... sorry for the plug, but I think it’s a really good book — I learned a whole lot while reading it!

I also found it pretty shocking to learn (https://www.smashingmagazine.com/2018/12/gutenberg-accessibi...) that @photomat did hold a potential professional engagement hostage over Marcy Sutton’s personal blog decision... although he seemingly did reverse that, but still, the whole attitude is fairly disturbing in doesn’t help where there already are lots of emotions involved.

This is such a big shame, especially since the native Slack app is consuming such a lot of processor and battery power and it runs much more efficiently in the browser!