WesolyKubeczek

Yeah, but our food eats it too.

They say no one is buying.

Also if they make cheese there, the fermentation stench is very potent.

I used to play with this on TextSynth when it has very few models and plain design (so GPT-6J or whatchamacallit). “Meandering texts that go nowhere” was the precise defining characteristic of all of the completions, every single one of them.

But if you are from outside the EU, it’s tad different.

> A hail-mary is when you throw the ball to the end zone and just pray someone catches it. This is almost always at the end of the game.

So that's why that Andy Weir's book was named that!

Sorry, I was mistaken!

I was using vim-enhanced as red hat-based distro installed it. No customization. No customization of nvim either.

I often use vim or nvim on disposable machines, so persistent undo is something very low on my list of things I want.

I used neovim because it felt way faster by default. I think treesitter runs circles around what classic vim is using to highlight syntax. That said, I never used both beyond basics, thus no horror stories either.

You discover it’s a bear trap not before you try to pull out from the parking lot.

Funny that Honda's hybrids seem to be licensing Toyota's eCVT magic, so it's quite a bit like Apple and Samsung, where they would be filling each other's pockets while also being at each other's throat.

Back when I had cable it was all like 15 minutes of content blocks separated by 30-minute blocks of ad. Because fuck me, I guess.

As if mice didn’t have enough of their own brain diseases!

I like neither of the three and prefer for loops and if statements instead. Yay for shallower stacks!

> as the other guy said, it's incomprehensible (to everybody but you apparently)

also a skill issue

This cannot be a true passenger simulation unless it also contains full airport experience, complete with TSA cavity search and CBP detaining you or denying entry for the pettiest reasons imaginable (in case of the US).

Or, maybe, people have skill issues?

Jesus fuck, would you get off your high horse already? This is every investigative article heading since before Dario or Sam even finished high school.

Seeing LLMs everywhere is another kind of AI psychosis.

Imagine here the goose and a jacket guy meme, where the goose says "Why then you have so many microphones in it? Why so many microphones!?"

Since https://github.com/micro-editor/MICRO exists for some years now, a comparison would be welcome.

Or "if you're going to submit a comment, credit Tim Berners-Lee".

It's easily the quote of the month. And we are only halfway into the month.

They will add $27,008 in time.

Test your cables once in a while.

There is a lot of USB cables that look the same but have different capabilities, there is a lot of HDMI or DisplayPort cables that look the same but have different capabilities, there are cables that stop working once you bend them in a particular way.

There are cables that can get sticky and filthy practically on their own (Apple!).

Mind cables whose plugs are bent.

I think the same should apply to perfectly fine screws you take off broken stuff, pieces of metal profiles, nuts etc. But I could never be arsed to sort them proactively. My late father used to keep a Big Jar of Screws and spend time rummage through them when he needed a particular one. I don't know which approach is superior, to be honest.

Now that I'm thinking about it, it could be a darn nice docking station.

In the later presentations, presenters definitely looked like Autons of the Doctor Who, from the first episode of the Ninth Doctor, where they were CGI.

A proper PowerBook Duo of modern day would be a 32" iMac-like monstrosity with a big ass slot (opening on the right) into which you slide the whole MacBook Pro, and a whole lot of ports in the back. The MBP attaches by its thunderbolt ports and magsafe in the back of the slot.

Obviously, if you have macbooks of different sizes, you would need to buy separate duos for each size. MacBook Air might have a 27" dock, incompatible with the rest.

What stood out for me was that a complete rewrite of the backend application took 72 hours. Even pulling all-nighters. Especially pulling all-nighters. If I did it even 20 years ago, back when I was young, I'd expect the quality of my code to nosedive.

If it indeed took this little time, I strongly suspect the backend wasn't doing too much in the first place. Usually you can rewrite those quickly and demonstrate speedups. Some real big software that had a misfortune to have been written in something interpreted and inferior, might be more problematic, especially if you can't afford downtime or are unsure about all important corner cases, and when the program itself is your only documentation.

Another thing that was very jarring was that the article as a whole sounded very LLMese. Or PowerPointy? Take your pick. This little example screams that an LLM might likely have writen it:

    > I'm not going to give you a lecture. Here are the concrete numbers:
    > RAM — the real deal
    > 
    > Node.js, on my latest version, was using 1.4 GB of RAM just to boot the app on one instance.
    > 
    > Go? 48 MB. I'm not kidding.

When talking to LLMs, I cannot now unsee how often they feel a need to assert something is real and they are not making things up. When I see this much LLM-like writing, I'm asking myself, maybe this all is made up? A plausible story, but maybe it never happened? Why would I spend my time reading it?

Didn’t Steve Jobs use that formula as well? The most powerful thing we released compared to last year’s thing we released?

It was, I have one.