chris_pie

The potential customer rarely cares whether a service provider is running their business well. What matters is the product's value added and risks added, as compared to just using the underlying tech directly.

That's a big name for a slop fork. So many possibilities (with LLMs and without) but Google just can't bring themselves to do anything creative, let alone transformative.

note that the front page also says: "61 chapters • Project-based • Zero AI"

I don't think so, I think it's just a pompous style of writing.

I wish the author explained the difference between pipelines and multi-statement queries

You're right, for example age is useful when picking targets for scams. It would also be great for groomers.

Hot take in regards to the good old statement taken literally: the boring<->exciting dimension is irrelevant in terms of something being good or bad.

Yes I know, stable things are stable

The meaning has changed very quickly for some reason, but I think the original meaning was that you evaluate the result in a superficial manner by checking if the program seems to work fine. So "vibe" here is as opposed to any methodical or formal approach. No code review etc.

The second one seems very similar to the "using static" feature, but less verbose.

For this specific case there's a "Nitter Redirect" extension

Hasn't the blue light affecting circadian rhythms been debunked at this point?

To your point, ValueTask is less safe than Task. For example, it's important not to await it more than once.

I can't find the actual decision, but there was some discussion here: https://github.com/WebAssembly/gc/issues/77 Microsoft later in 2023 said that that discussion "is the current state we are in. We will keep eye on wasm GC in the future."

edit: found a more concrete statement https://github.com/dotnet/runtime/issues/94420

Here's a benchmark of int keys in .NET https://github.com/MessagePack-CSharp/MessagePack-CSharp#des...

.NET doesn't use WasmGC because Microsoft found it too different from how .NET's GC works. Which is quite unfortunate

I've been using Pixel 8 for nearly a year now and I agree that it's surprisingly buggy. Also, the chip is excessively power-hungry, especially for the performance it offers. In addition: the modem is bad and very power-hungry as well. And the cherry on top for me was the subpar fingerprint scanner. Can't recommend.

Best he could do was DEUS I

attribute names depend on the implementation, Solid uses JSX and `class`

what's funny is that there are 2 libraries called hyperscript

Some features of Kiwi were merged to Edge, which means it now supports extensions (any extension if using developer options in Canary)

Same on a not-old Pixel 8

Great job! Does anyone know which one was first: Slime Volleyball or Blobby Volley? I fondly remember playing Blobby Volley at school

There's also Paddle (who's a Merchant of Record)

Also the Units of Measure are a great feature. I think they're a zero-cost abstraction that Rust users love to mention.

To be fair, my knowledge of F# is a bit superficial, but I meant stuff like classes (including abstract ones), interfaces, and the ingrained interop with C#.

I have to say, I laughed when I noticed the framerate, in what's (in a way) a hardware ad

I'd say F# is closer to filling that gap than OCaml. It's a bit less insistent on being functional and has a more familiar syntax. I find it more practical in general.

I'm on Chrome on Android and AdGuard blocks all your visualizations, just FYI

There's also a long standing issue of random peaks to 100% CPU, that they don't seem to be able to fix.

This is very similar to the idea of Zooming User Interfaces (ZUI) https://en.m.wikipedia.org/wiki/Zooming_user_interface