frou_dh

He's so charming:

https://www.youtube.com/watch?v=B8-ZmuJixIg

AFAIK that setting is opt-in, at least in Bash.

We have to settle for the smiley face changing slightly.

It's got to be somewhat depressing working on a household name product in its trashy downturn. Surely you can't have the pride in your work that an equivalent employee once would have.

I wonder about the timing in relation to the OpenAI acquisition of Astral this week. Was it a two-horse race to be acquired and then Deno got word that they were not the chosen one, and so said oh well, mass layoff it is?

BTW the Deno architects would contend that "mastering Deno" could never be a waste of time, because what you're mastering is to a large extent standards-based JS (in comparison to the APIs that came before).

Yeah, that's pretty much tailor-made to be the official resource for an experienced programmer to get an overview of C++ as it stands. Fairly slim book so it's approachable.

https://www.stroustrup.com/tour3.html

It's abject hackery because such "comment" directives don't even necessarily have to be a comment to be active:

    const x = `This whole thing is
    a
    //go:generate worse-is-better
    multiline
    string literal`

A lot of people in this discussion are beating up Go for using syntactical comments for directives, but in reality the implementation is even less principled than that!

You really gotta wonder how much value the "Digg" brand actually has, because the number of people that remember/care about the site from its original glory days is ever dwindling.

See also all the programmer blogs that feel the need to use a monospaced font for prose, to signal that they're a programmer.

Safari's devtools has a visual <canvas> debugger. I remember using it, seeing all the CanvasRenderingContext2D calls that affected the canvas listed, and scrubbing left and right through time to see how a frame was built up.

Obj-C++ was used for some hall-of-fame OS X apps, e.g. TextMate

> sometimes, I allow myself to lean back in my chair and just scroll

WHAT??! This cannot be allowed!! /s

It's clear from reading programmer geek thoughts on peripherals over the years that autistic types love the "Use keyboard 100% of the time!" dogma because it is black-and-white thinking. The idea of someone knowing how to do things in a multitude of ways and changing it up based on mood is displeasing.

On the off-chance I ever do reply to some of the months/years old things that I've never replied to, then I will surely include an apology, because it's definitely rude what I've done.

I don't think many people in the real world worship the sanctity of the "Asynchronous Communication" principle above all else. Maybe the author is the 1/1000 that does.

One of Reddit's cutesy error pages (presumably for Internal Server Error is similar) is an illustration that says "You broke reddit". I know it's a joke, but have wondered what effect that might have on a particularly anxiety-prone person who takes it literally and thinks they've done something that's taken the site down and inconvenienced millions of other people. Seems a bit dodgy for a mainstream site to assume all of its users have the dev knowledge to identify a joking accusation.

In 3D games, something that's key for roads to look/feel realistic is to have small amounts of banking here and there all over the place - as opposed to just having a crude categorisation where there are flat roads on one hand and ramps on the other.

If you don't do that then large parts of the game world end up seeming like ice rinks with roads painted on them.

Is that so? Sounds like this commandment has a lot of authority, I'd better start following it.

Used in space but NOT cleared for attaching the Space Shuttle to the fuel tank.

The whole GitHub paradigm has muddied the meaning of the term "forking". It used to imply a serious intention to diverge. Now to a lot of people it just means doing any development on a copy of a repo. The "Fork" button on GitHub is really "Clone (to my account)".

That's the holy Unix justification for self-flagellation via deficient tooling and you're sticking to it.

When drawing outlines, tables, etc, I hope the new approach (vui) uses real Unicode box-drawing characters and not - | + etc. It's high time TUI people raise their standards a bit and consider unbroken line drawing (no gaps between repeated characters) a requirement rather than a luxury!

The strange thing is that they never did manage to get it done for Ruby.

AFAIK macOS does not ship any version of Python in the normal installation, and it's Xcode / Xcode-CommandLineTools that bundles a Python.

I feel this topic is approaching circlejerk status. Basically any mention of StackOverflow on HN/Reddit is just teeing up everyone to go on about how the SO moderators are the worst people ever.

OCaml is a scripting language in this sense. No need to compile an executable ahead of time, just have a `#!/usr/bin/env ocaml` shebang (or more realistically: `#!/usr/bin/env -S ocaml -I +unix unix.cma`) at the top of a source file.

Though, I don't think it has the capability for single-file scripts to declare 3rd-party dependencies to be automatically installed.

What I got from this is that the author doesn't like the term Extensible being used for situations that don't follow good software engineering practices. Maybe the term Hackable is less offensive and implies dirtiness being okay.

What's obvious to me is that the PRIMARY motivation for Liquid-Glass-ifying MacOS was not to improve MacOS, but simply to make it look consistent with the new version of iOS/iPadOS.

So for Apple to start with a level of disrespect for the existing product where the question of whether each change is actually an improvement is effectively off-topic, it's no wonder they made a dog's dinner of Tahoe.

e.g. https://pkg.go.dev/github.com/zyedidia/generic/mapset

Hopefully it gets added to this comparison:

https://htmlpreview.github.io/?https://github.com/python/typ...

If that table is anything to go by, Pyright is not to be underestimated.

I have briefly tried ty (LSP) in Emacs and it seems to work well so far. The only questionable thing I've encountered is that when the signature of a method is shown, the type annotations of some parameters seem to be presented in a particularly verbose form compared to what I'm used to - maybe they're technically correct but it can be bit much to look at.

Anyway, odds are pretty good that ty is what I will end up using long-term, so thanks and congrats on releasing the first beta!

Sounds like you haven't learned your lesson and are still in mania.

The contrived example used in the first half of the post is offputting. Why would you have a function of 1 argument that only accepts a string with a specific value? There's no point taking an argument then - it might as well be a constant inside the function.