zerker2000

pulling the concrete friction-report referenced in the reply https://news.ycombinator.com/item?id=35316159

(these are not necessarily the same issues, but at least similar-sounding ones I found by googling)

• widgets opening in wrong place: https://bugs.kde.org/show_bug.cgi?id=459188

• ignoring icon size configurations: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/i..., closed as wontfix

• on touchscreen menus open wherever you left the cursor: https://bugs.kde.org/show_bug.cgi?id=406025, more info in https://github.com/PeterCxy/evdev-right-click-emulation/issu...

• cursor framerate issues: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1827 maybe, it's in the gnome issue tracker but described as wayland-specific, so might also be happening on KDE

• firefox using wrong screen's DPI: https://bugzilla.mozilla.org/show_bug.cgi?id=1632829, resolved by original reporter but last comment is a repro from someone else. also reported in https://github.com/flatpak/flatpak/issues/5300 but closed as "wrong bug tracker"

• fullscreening a video rotates it from portrait to landscape: https://bugzilla.mozilla.org/show_bug.cgi?id=1600962 possibly, https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/190522... possibly

In general wayland seems too buggy for major software like firefox to use it by default, per https://askubuntu.com/questions/1409389/why-doesnt-firefox-r...

Impressive list to hit in only 5 minutes!

I wish any of these projects(obsidian, logseq, Roam) supported WikiWord autolinks alongside [[Mediawiki]] ones. See also: https://apenwarr.ca/log/20100901

I believe GP is referring to government legal action against Parler for "helping" organize lynch mobs. Extralegal retribution from oligopolistic service providers is of course also allowed by law, that just doesn't make it fine.

Ah, I see ILang deals with the issue by… not having a name binding primitive, making you SKI-calculus your arguments into place. (Compare the piles of roll-swap-dup you get in varless forth dialects, though not as bad due to there being two directions args are passed in from.)

I suspect there is room here for an unprincipled "preceding word/pattern is defined by the following line/s" loose-binding operator, to restore skimability, and a separate inline destructuring let form that cannot leak out of lexical scope. Which I suppose would warrant lambdas - perhaps with ⍺ ⍺⍺ ⍺⍺⍺ to denote enclosing function input, rather than argument/operand/hyperand, though nonconcrete functions would stress the type system as is

Parentheses may be used to specify the order, but there's a (usually) better way as well: whitespace! Fewer spaces means the function will be executed earlier.

Oh man, that is a fascinating idea I've played around with some, glad someone's put it more seriously into practice.

Re: assignments, Aaron sure seems to sprinkle them liberally inside lines - though not generally ones referenced in subsequent ones, to be fair. (I suppose another notable attribute of the co-dfns codebase is extensive use of ⊣ as a leftwards statement separator)

Mathematical functions are prefix, which imo is much harder to follow than either infix (OO/APL) or suffix (RPN/Forth), though this may be more of an english-speaking intuition than some manner of universal truth. I do at least observe a trend towards "imperative but functionally pure / side-effect isolated" in recent language design.

I've always been curious one decision pervading various APL: what are the relative merits of right to left evaluation order, vs more conventional left-to-right method chains? The core principles are incredibly elegant, but I must admit hitting "expressions are executed right to left, except if you hit a {} lambda, wherein separate statements are ordered left to right, but are themselves expressions going right to left again" is always kind of jarring.

That's a question for PR review, not what intermediate states they can push to their own branches

there will doubtless need to be some alternative channel for events that need to preventDefault, most notably clicking on links that should route instead, and form submit; I’m not sure how that will work.

Naively I would expect that to be part of the rendered DOM("<a prevent-default='click'>"), or otherwise in a declarative datastructure available to the UI thread. Are there many events that need conditional preventDefault, such that the JS handling code would grow nontrivial?

I think the one shown on hover is `title` text?

https://technomancy.itch.io/bussard is a game about UI-building over low-level spaceship controls/sensors

None of this is to say that it’s impossible to design a macro system for languages with non-Lispy syntax

For me this was most poignantly demonstrated by https://chrisdone.com/z/

These examples do not appear to have been run.

  const jwt = require('jonwebtoken')

For "you ran some sort of permission check" I'm a great fan of the React.js `dangerouslySetInnerHTML` interface, which accepts a corresponding `{__html: ...}` object that has at least nominally been properly vetted.

"Almost" doesn't count for security. Android is a known insecure platform, don't allow things running on the platform to open people's cars.

  Instead of thousands of debugger options, let's have a magic tool where you click on the thing that's going wrong.

If you're listening via AirPods, you can't charge the AirPods

Non-atomic writes to a single memory location, from what may well be separate cores etc, happen essentially at random due to out-of-order execution. What are the downsides to using the value from the last thread ~spawned~, and calling it a day?

Love the quine "difficult mathematical type exercise". I wonder if there's a better solution than the naive:

  ((lambda (src)
    (cons (cons (quote lambda)
          (cons (quote (src))
           src)
    (cons (quote quote)
     src)
  (quote
    (cons (cons (quote lambda)
          (cons (quote (src))
           src)
    (cons (quote quote)
     src)
  )

Or for that matter http://urbit.org/home/pub/docs/user, which is a simple-html rendering of the OP link. Some of the pages require JS to list children components, however.

I'm still holding out for Homomorphic Encryption.

http://rbutr.com is a contradiction-focused social plugin for linking pages together, I'm not sure how widely used.

I think the article is too eager to dismiss hotspot-style links, valid as its point about multiple connections may be. The solution I'd prefer would be something like Medium-style inline comments, where the immediate "hotspot" is a number representing a collection of responses, and the links occur inside of those.

  it solves a lot of the problems that CoffeeScript is trying to solve without drastic syntax changes.

The requirement is that they are sortable, nothing about the numbers reflecting the actual order of proposals (inasmuch as uncommitted actions in a distributed system can be considered to be ordered). Concatenating system time and node number upholds this property: 4:01-A and 4:01-B produced by nodes A and B respectively are distinct and numerically sortable, and both in turn "predate" 4:13-C attempted later.

I'm not sure much strictly non-lapidary hoon exists, but for samples marginally less lapidary than the kernel, I would like to point you to a simple algorithm translation at https://gist.github.com/MichaelBlume/17a227cc839f52f68c97, and the twitter library /main/lib/twitter/core.hook in the standard distribution.

Not as such, http://urbit.org stands. If people still want to explore unofficially, github is their oyster.

Let's hope this gets somewhere before all UAV hackers move to Canada.

Is anyone reminded of http://www.bibliotecapleyades.net/tesla/occultether/occultet...? Which is complete pseudoscience but...

"For any type of a tag, a new node with a name matching the id parameter of the tag is inserted into the default object scope. In other words, <div id=test> will create a global variable test (of type HTMLDivElement), pointing to the DOM object associated with the tag." Did not know this.