bajsejohannes

Mirror, since the link is down for me: https://web.archive.org/web/20211031161220/http://harmful.ca...

> My ideal programming screen is a 1:1 square

I have never tried it, but to me that seems ideal too. There seems to be close to zero demand for these, though, so I could only find this very expensive and not very high DPI monitor: https://www.bhphotovideo.com/c/product/1138908-REG/eizo_ev27...

$1,429.00 for a 1920 x 1920 monitor? Meh. I'd rather stick with a single large landscape monitor.

The video doesn't start until 7m39s, but HN wouldn't let me post the following link to that time: https://www.twitch.tv/videos/1220717732?t=0h7m39s

For those who prefer text (albeit a lot less detailed), the announcement was recently discussed here: https://news.ycombinator.com/item?id=29390751

The Opera browser did for a short while. If I recall correctly, it was taken out since sysadmins at schools, workplaces, etc would ban the browser. Of course that behavior unfortunately ensured that bittorrent would remain a protocol mostly for piracy.

It's not entirely unlikely that I am remembering just the good stuff :) But I was surprised how many books would define even the most common notation, like ⊂, ∀, and ∃.

I guess if you call your book "Introduction to..." you ought to do that. And it seems that all books were called that, regardless of how narrow and advanced the rest of the title was :)

> I think a real problem in this area is the belief that there is "one true notation" and that everything is unambiguous and clearly defined.

Just to back up this point: In probably every university-level math book I've read, they introduce and explain all the notation used. In the preface and/or as concepts are introduced.

There are lists at wikipedia [1] and other places, but I'm not sure how valuable it is out of context.

[1] https://en.wikipedia.org/wiki/Glossary_of_mathematical_symbo...

I had this same objection. And in a reductio ad absurdum, it certainly is key that all the steps leading to the contradiction are indisputable.

> There are many people who are extremely skilled who produce things people hate

There's a dedicated subreddit for this, even using the word "taste": Awful Taste But Great Execution https://www.reddit.com/r/ATBGE/

Another great hidden feature is the LISTEN/NOTIFY system. You can use it to watch for changes on a table, and then use that to e.g. update a view in the UI.

For example create a table with a trigger on insert "NOTIFY new_data". Then on query do

    LISTEN new_data;
    SELECT ...;

Now you'll get the results and any future updates.

Unlike all the preview builds this actually crashed on `dotnet run` after upgrading. Luckily a `dotnet clean` fixes it.

Good to finally have an official version!

Pony, amusingly, has both structural and nominal typing. https://tutorial.ponylang.io/types/traits-and-interfaces.htm...

Thanks! I will try hydrogen!

This seems to built for people with a lot of rooms/people. I think it's a classic mistake to enable it for all users, and I see it in all kinds of products. Everyone starts out by building something simple, but eventually it's bloated with features that I don't need (I'm sure someone does).

Personally, I use matrix every day. However, it's only for a single room. With this new feature, I lost 70 "pixels" (or 140 actual pixels) of horizontal space.

The paper outside a paywall: https://www.microsoft.com/en-us/research/wp-content/uploads/...

The "optimized shadow" version has a lot of subtle banding artifacts, presumably because of the layers. If I squint, the optimized looks better, though.

It's also incredibly slow. On my M1 Macbook, touted as one of the fastest laptops ever, it takes 3 seconds from opening it until there's anything on the screen, and than about 5 seconds more until it's interactive.

> You tell your applications to drain connections and gracefully exit on SIGTERM.

The problem is that k8s will send requests to your application after SIGTERM. So you have to wait some amount of time before shutting down to allow for that.

This was at least the case last time I used k8s, and it seemed like it was due to the distributed architecture, so something that was more than a mere bugfix away.

> solving a specific problem

The problem to me is that Kubernetes is not solving a specific problem, but a whole slew of problems. And some of them it's solving really poorly. For example, you can't really have downtime-free deploys in kubernetes (set a longish timer from SIGTERM to increase the chance that there's no downtime).

Instead I'd rather solve each problem in a good way. It's not that hard. I'm not implementing it from scratch, but with good tools that exists outside of kubernetes and actually solve a specific problem.

There's a huge difference between solving an instance of a problem and understanding the problem. Enough commits of "this seems to fix the problem" and the codebase becomes really hard to work with.

That could also be solved by licensing. Stack overflow, for example, uses CC BY-SA 4.0 for all posts, and provides data dumps for anyone who might want them.

My next project will use Nomad over Kubernetes, and the reason is that I want to keep complexity down. I haven't used rancher, but another layer won't remove complexity, just hide it (until the abstraction leaks).

Somewhat related, I'm confused every time iOS says "Processing Payment" when I download a free app.

The fact that it has proper function-keys instead of a touch bar also makes it an easy choice. At least for people like myself :)

Unpopular opinion, maybe, but:

I don't really get why "reversing a binary tree" seem to be used as an example of what's wrong with hiring. I will say, though, that if someone said "how do you reverse a binary tree?" I would have asked the follow up question: "what do you mean by that?". If asking that would be used against me, sure, that's bad hiring.

But if the answer is: "swap all the left and right nodes in a binary tree", then... isn't that pretty basic programming?

> The soft start feature ramps the unit to full brightness over a couple seconds when pressed and does the same when turned off. This action can save the life of your bulb and isn't as jarring as lights that instantly pop on and off when pressed.

It actually not jarring when lights turn on instantly. It seems like a lot of these "smart home" solutions provide a much slower experience. Hold-to-dim is the worst of these.

I wonder when we'll see https://danluu.com/input-lag/ for light switches.

From the source:

; Inspired by "Auguries of Innocence", a poem by William Blake

;

; To see a World in a Grain of Sand

; And a Heaven in a Wild Flower

; Hold Infinity in the palm of your hand

; And Eternity in an hour

And 32 is of course the size in bytes of the executable.

I used to use the keyboard a lot in Opera back in the day. Favorites included searching for links on the page by text and pressing enter to get there, and navigating back/forward using "link rel" tags in the documen (for example, you could go to the "next page" regardless of the browser history)

I seem to recall that web pages were steadily making it harder for it to work. E.g no "a href" or "link rel"s.

Here's hoping that Nyxt will have success in bringing this era back!

I'm curious if even Apple follow the guidelines. It has been way too long since I read them, but I remember the minimum button size being quite large. A while ago, the pull up menu (with camera/light/volume/airplane mode/etc) was redesigned. As part of that the play/pause/skip buttons became so small that my iPhone SE frequently does something other than my intention.

I can't find any reasons why it was rewritten.

Was it C before? (I can't tell, because https://github.com/matryer/bitbar redirects to xbar)

It's not like you can drop off anyone for euthanasia, though. From the article, they must

- suffer a "serious or incurable illness" or a "chronic or incapacitating" condition that causes "intolerable suffering"

- be an adult Spanish national or a legal resident

- be "fully aware and conscious" when they make the request, which has to be submitted twice in writing, 15 days apart

They will drop python 2 support completely in SQLAlchemy 2.0. That's at least how I read it.