Right, but which columns? The goal absolutely IS to select columns from a table. ie. my goal is not to select created_at, my goal is to select Foo's created_at.

> The goal absolutely IS to select columns from a table.

No. The goal is to have an output column $FOO, where $FOO is meaningful and might not even be in the database in the first place.

> my goal is not to select created_at, my goal is to select Foo's created_at.

Then your goal is to get a value out of a specific table, namely `Foo`, presumably because the end-user wants to see some value in the results.

The end-user getting the value has neither an interest in nor knowledge of your schema. `Foo.created_at` is no more meaningful in the result sets than an unadorned `created_at`.

For this specific example, the end-user might want a column in the output called `age` (if it came from an inventory table`, or `duration` (if it came from a metrics tables), or perhaps `expiry` (if it is a table containing perishable stock). These are all a column in a Foo table, but the request that caused you to write the query in the first place does not mention table at all.

You get their requirement as either `age`, `duration`, `expiry` or similar. That is what you are starting from: "a need for a specific piece of data". You are not starting from "a need from a specific table", because the information needed is coming from someone who neither knows nor cares what your schema looks like.

I dunno, I can barely see my OLED phone's screen when I'm using it on full brightness in the sun.

I am grateful they left it at "inspired by python", as I find python with its libraries and all its warts strangely complex and indigestible. Then, from a tooling and ecosystem perspective, wildly frustrating and unfriendly to work with. So I'm glad they took the chance and made something that's tailored to their use case and gives them the space to diverge and optimise where and when it makes sense.

Also C# is available as a scripting language for Godot, which makes a lot more sense than python from a performance perspective.

Amdahl's law states that "the overall performance improvement gained by optimizing a single part of a system is limited by the fraction of time that the improved part is actually used".

For anyone else who didn't know.

Thanks

I think they're essentially using "hashtags", so they could have many for one note.

I've taken to "installing" the webapp version on my phone. It's only a little bit different, but doesn't come with the frustrating issues the android app does.

I've tried, but the analysis UI is different enough to be a bit more frustrating :(

And what would that advice be?

Before the second cup

Woah, mind blown. Def gonna try this tomorrow morning.

Thanks, teknolog!

It was to not have a cup until your natural endorphins from waking up have worn off - say around 10:30am. Whenever I have an earlier cup I seem to do less well.

The road you're talking about was 1400km long

1400km / (70km/h) = 20 hours of driving. This was no "a thousand volunteers on foot spent days searching for even a scrap of evidence" effort.

Pretty sure it's also the only road connecting a lot of these places; this is far remote WA.

Perhaps consciousness is just an observer of those physical systems that exist in the brain, and under anaesthetic the interface between consciousness and those systems is interfered with. I don't know what I'm getting at.

They're talking about JavaScript's fetch API. It's not an external library.

It ships browsers but not because it's a JS standard (ECMA) rather a web standard (WHATWG). Almost everything in JS is an external library as it doesn't have a true stdlib to go with the language just a core language and implementation specific APIs like browser Fetch or Node sockets.

Hopefully WebSockets (W3C/IETF) will get embedded in Node's core one day as well.