orangepanda

Plain ol’ sql

He wasnt even the only Julius Caesar elected as Consul in that decade

https://en.wikipedia.org/wiki/Lucius_Julius_Caesar_(consul_6...

I, for one, thought the entire weekend drama was hilarious

Doesnt std::shared_ptr use garbage collection?

> And you can get rid of them by paying for the service.

Get rid of _some_ of them

Tell me more about your lawn

Not particularly. I value predictivity over "smarts" when it comes to productivity tools. For me, using the already existing autocomplete, that I know the outcome of, is faster than understanding (and subsequently fixing) copilot’s suggestions.

A colleague types no more than 30 words per minute, and is fawning over copilot. There’s probably a correlation.

On the otherhand, open source anti-kamikaze drones?

My nit pick over Jira's UX - they recently changed how board is implemented, breaking ctrl+f

Keyword being "similar", as in, not the same. Its neither the behaviour of html onclick attribute, nor dom onclick attribute.

Its a typo then?

    onclick="addFruit" 

is not the same as

    onclick="addFruit()"

My brain is too smooth to grok this.

This calls a referenced function:

    @click="addFruit"

This executes an expression:

    @click="images.pop()"

What if I have a expression that returns a function that should be called?

I googled that exact phrase (and put on the kettle for the visit I'll soon get). The first page was all government related resources on how to deal with terrorist attacks.

If not outright blocked, instructions do seem to be weighted down.

As I understand, with SKIP LOCKED rows would no longer be processed in-order?

I cant verify the earth is round, but I trust the information sources that claim so

jQuery from 2009 also still works today. What I meant was, developers want to use the latest and greatest. Hooks added in 2018 havent changed, there’s no replacement api for them - it’s still modern code.

They got the DX right from the start, that other libraries are still trying to emulate.

React Hooks has its problems, but it got so many things right from the start - code written in 2018, when hooks first came out, still works today. No need to rewrite everything when a new major release comes out.

That said, svelte5 does solve a lot of problems that stop me from trying it.

Going through Stripe's forbidden business list, sounds like you fall under:

> Sales of online traffic or engagement

And, imo, also this one:

> No value added services including sale or resale of a service without added benefit to the buyer

My problem with these :ifs and v-ifs and {#ifs} is I cant place a breakpoint and step through _my_ code with a debugger.

You dont have to specify the dependency array, it’s an optional optimisation.

As I understood, the problem was not that the queries were slow, but the sheer amount of them. Boost would not have helped much with that.

I most commonly use CTEs for splitting ranges into individual values (1-5 into 1,2,3,4,5). It’s an order of magnitude faster than joining some utility table, which some still recommended.

I vaguely remember one of typescripts developers stating that if they had to start it all over again, enums would not be added; as enums are the only thing emitting runtime code.

Typescript does not change runtime behaviour, there is no special typescript {#if}

Preact takes the King Bumi approach to API compatibility - by sometimes doing nothing.

The syntax may be compatible, but the semantics are not. For example, it doesn’t support react's concurrency features; transitions are just empty wrappers.

I automated my accident

As eastern european, this was rather anticlimactic.

Of course it could have been done without Svelte. Thats the only stack their team know and/or wanted to work with. Nothing wrong with that, but would be nice if they were more upfront about that instead of "impossible for a different solution to exist".

There was a psychological term for it, making a decision first and only then finding supportive arguments in favour of the decision?

What privileges a superwhite QR code has versus a regular white?

The logo and "home" do not lead to the product page - they lead to developer docs home page.

Did not think to try the first link though.

Offtopic — is it some cardinal sin to include a link to the home page from a documentation? I dont know what canva does, if I stumble on a documentation page first, should I not be allowed to see the product's landing page at some point? This is so prevalent, it has to be a conscious choice.