kokanee

Interesting stuff, particularly the estimation that 140 TW of solar radiation are captured by photosynthesis. In arguments about the efficacy of tree-planting as a climate control effort, I've heard about the effect on albedo radiation and of course on the sinking of CO2, but I've never heard it pointed out that photosynthesis itself captures solar radiation that would otherwise be reflected heat.

The refusal by these companies to accept the realities of the modern printer market reminds me of the tagline that Michael Scott wrote for Dunder Mifflin:

Limitless paper in a paperless world

Wouldn't work for me without the ability to add other exercises. I'm also not familiar with a lot of these exercises, so descriptions and images would be very helpful.

I'm aware that they reversed those decisions, which I see as proof that broad customer dissatisfaction with those choices forced them to walk back those cash grabs. I recognize that these events could be interpreted differently, but that's my read of the situation, and it's certainly my experience as a long time customer.

I could write a manifesto on my hatred of the move from headphone jacks to bluetooth across all device categories. I admit that I'm an outlier here, but regardless I just might have to make time to write up my thoughts on this travesty.

I agree with this. The main aspect in which they've lost their way in my mind is that their product design choices are intended to appeal to customers only as means to profit, rather than choices that earn profit as a side effect of delighting customers. For example, they've developed this incessant habit of trying to remove basic and often loved features in order to save a buck (ports, headphone jacks, mag-safe cables, glare-free screens, escape keys and other buttons, etc).

I despise Google and many of their practices - but I'm mulling over whether "spying" is a fair characterization here. Was this profile not built from searches that were manually submitted directly to Google? If you have turned off all location features and then attempt to use localized features like weather and local search, should Google just place you at coordinates 0,0? Is the association between your IP and your request history what makes it spying, or is it the existence of persistently-stored request history at all?

As a software engineer I have associated user IDs with their request logs at almost every job I've ever had; a lot of debugging would have been impossible otherwise. Is that unethical? Are user IDs and IP addresses inherently different?

I was thinking this too. My favorite fishing lake was recently found to have unsafe levels of PFAs. I suspect that if we pumped the lake through an electron beam purifier, it wouldn't be my favorite fishing lake anymore.

Well, that was not at all an expected reply, but it's well-received. Thank you for the thoughtful linguistic advice; I'll keep it in mind.

As a W2 software developer, I've held options at three companies and RSUs at two. I've netted around $30K from RSUs, and netted a loss of $20K from options. Only once did my options "liquify," when a startup I had worked at was acquired. The proceeds were distributed entirely to preferred shareholders and employees were left with nothing, several of us having spent thousands to exercise.

I made my bed and slept in it, so I have no axe to grind, but going forward I will never accept options over any other form of compensation, given a choice.

Don't worry everyone, it's only the design collaboration services

Interesting, I could have sworn it was at some point, but maybe I'm thinking of the AirBnB settings.

If you do this, you need to think through all the possible types for the comparators and how type coercion will affect the expression. For example, `0 == ''`, `[] == ''`, and `[] != []` are all `true`. If you're using typescript to get guarantees about the input types, maybe that's a good use case for using type coercion intentionally.

I wonder if it looks different on different platforms. My first reaction looking at the site was that it looked super grainy - a lot of the embedded screenshots and interactive snippets are almost too noisy to read. I played with the setting and found that while I do like the aesthetic, it needs to be about half as strong to my eye.

I'm not going to dive in and play with it, but often it can help to add the CSS rule "transform: translateZ(0)" in order to force rendering to the GPU instead of CPU.

One of the biggest warts is the difference between the == and === operators. Eich attempted to alter the behavior of == in order to fix it, but was not allowed to ship the change for fear of backwards incompatibility, forcing him to add a new operator instead. To this day, recommended linter settings disallow use of the == operator entirely.

The rings are extremely dark, reflecting only 2% of incoming light. The James Webb image is an infrared photo, and doesn't show what the planet looks like.

Your emphasis on true color is worth underscoring. I think it's a bit unfair to publish a photo like this one from James Webb without providing a few less-stylized edits for comparison, and an explanation of what the colorization process entailed. Obviously as an infrared photo there isn't going to be any edit that gives us a great idea of what it would look like to the eye, but it seems like they chose the most wondrous-looking settings in photoshop on this one, as opposed to the truest.

The special property of a DAG is that there are no cyclic paths between nodes. In the DOM, every node has a path to every other node, so you can create infinite loops (e.g. element.parentNode.nextElementSibling.previousElementSibling.firstChild).

That's the document tree - when it comes to application state, which is just data in memory, anything is possible. These state libraries tend to treat in-memory application state as the "real" state, and try to treat the document tree as a side effect. This is one reason that front end unit tests tend to miss bugs - application state being what you expected doesn't mean the user sees what they expected.

How is React state not a DAG out of the box? What problems does this solve? The pitch appears to be:

> any outside change (user action, api result) unleashes a graph traversal. Our UI components become much simpler, because they just need to dumbly reflect values in the graph.

But that sounds the same as the reasoning behind React's one-way data flow.

I chose Mithril with JSX for a real startup's main product. It felt like what I expected React to feel like, and it scaled with no issues. The only downside is that everyone on your team is anxious that they're missing out on marketable React experience.

Bloomberg link not working; here's TechCrunch: https://techcrunch.com/2023/12/07/googles-best-gemini-demo-w...

I imagine the commenter was calling out what they perceived to be an inauthentic yet carefully planned facade of diversity. This marketing trend rubs me the wrong way as well, because it reminds me of how I was raised and educated as a 90s kid to believe that racism was a thing of the past. That turned out to be a damaging lie.

I don't mean to imply that companies should avoid displays of diversity, I just mean that it's obvious when it's inauthentic. Virtue signaling in exchange for business is not progress.

Anyone else finding it ironic how difficult it is to interact with this article because it is so utterly plastered with ads? I attempted to follow the link to an article about Edge blocking Chrome, and was met with a full-screen interstitial ad instead of the article I clicked on. Sad times on the Internet.

> Don't shun others on subjects you are unfamiliar with. Speak gently and listen.

For someone pointing an awful lot of fingers and making a lot of extremely condescending accusations throughout this thread, I'm surprised you're offering this advice.

I work in the renewable power industry, and my father was a biologist who spent his career trying to mitigate the ecological disasters caused by my state's hydroelectric dams.

The link you've provided suggests that miners and hydroelectric providers could establish mutually beneficial economic partnerships. That hardly needs to be written; it's obvious. But I think if you polled the public on whether creating additional revenue streams for hydroelectric is a higher priority than reducing our overall energy demand -- well, do I even need to suggest what the results would be?

> "Why do we need currency when we can just store commodities?"

Did I imply that we don't need or shouldn't have currency? And are you implying that crypto and stored renewable energy should be equivalent priorities?

> You are deeply out of touch with reality if you believe they aren't curtailing capability

"At all times" was the key qualifier to my statement. I'm well aware that excess capacity from intermittent sources is a huge problem and curtailment is the workaround employed these days, which is precisely why I'm saying that storage should be a higher priority than crypto.

I can't speak for others but I'm definitely not blindly following group-think on this. There are countless uses for energy, and the idea that mining crypto is the best possible use for excess renewable power is a bold statement that requires a lot of explanation.

Your point of view here seems to neglect energy storage. There is no use for excess renewables that is more productive than storing it for later, when intermittent renewables go offline. Stored renewable energy is the only thing that can replace fossil energy at those times.

This is why billions of dollars are going into storage and transport for renewable energy (batteries, hydrogen, and some outliers like methane and ammonia). Creating any new energy demand, be it flexible or constant, only increases the total amount of renewables we need.

> our entire grid could be renewables in excess of peak demand

Are you hypothesizing about a world where we have more renewables than we can consume at all times? Sure, I guess mine away in that world. In this world, though, it's doing measurable damage.

Thanks for sharing. When you read articles like the above, which suggest that those perceptions are hallucinations from oxygen starvation, how do you react?

iPhone 8 and later support inductive charging. But it's not perfect - my wife's phone was melted by a third-party inductive charging pad that was intended for use with iPhones.

I wonder if part of the solution is for us to start designing the Internet for bots. We're entering a phase where websites are coded by bots, content of all stripes (text/video/audio/images) is generated by bots, and increasingly that fact doesn't necessarily mean that we want to block it.

The main tenets of apps that are resilient to bot spam are 1) scalability, so that they can handle huge quantities of traffic and bot-generated content, and 2) the ability to differentiate high quality from low quality content (regardless of whether it was created by a human). Ironically, AI is probably the solution to the second problem.