less than 5% of Americans support using economic strong-arming, and less than 1% support military force for Greenland or Canada (source below). Annexing is overwhelming unpopular for both conservatives and liberals. The people, including people in the military, will revolt if Trump uses force to annex any country. And the people of Canada and Greenland have made it very very clear: force will be necessary.

No comment from me about the rest. Expectations can be bad but keep them in check.

https://angusreid.org/canada-51st-state-trump/

Once you’re >25 this is just a flex

I think it could be a great solution. I’ve never considered it before. That said there’s one sticking point for me:

Apportion payment to developers based on software use by paid users and the size of their contribution to that software.

That^ . That needs a lot more detail. If they provide solid details – details that most can agree on – then I will actually be on board with the solution.

0

Don’t forget the fully fledged remote desktop thats built in, WebVR (which is being replaced with Web XR), Web Bluetooth, Web USB (aka Web Serial), the API’s for notifications, ambient light sensors, an entire transactional database (indexed DB), the language translation API, the Gamepad API (videogame controllers), hardware passkeys (yubikey), speech to text, text-to-speech, webGL, webGPU, webworkers, service workers, an entire suite of cryptography tools, GPS location, battery, vibration, FileSystem API, picture-in-picture API, WebRTC, WebSensors, etc.

And then, on top of all that, building a miniture OS-kernel so that tasks can be sandboxed scheduled/executed and prevent 1 tab from crashing everything or hogging resources.

(I know I’m two months late)

To back up what you’re saying, I work with ML, and the guy next to me does ML for traffic signal controllers. He basically established the benchmark for traffic signal simulators for reinforcement learning.

Nothing works. All of the cutting edge reinforment algorithms, all the existing publications, some of which train for months, all perform worse than “fixed policy” controllers. The issue isn’t the brains of the system, its the fact that stoplights are fricken blind to what is happing.

Kinda surprised nobody has said this: start your own instance. Seriously, thats the power of the fediverse.

The sorting algorithm(s)

Ever since the accidental event that was interpreted as war, no not the one in 1957, not the one in 1958, or the other one in 1958, not the one in the 60’s or 70’s. The one in the 80’s. No not that one, the other one in the 80’s. Yeah that one. Anyways, ever since that one happened and triggered nuclear armageddon there hasn’t been much activity at all. Give it another couple millennia and maybe more complex organisms will roam the earth again.

“Select where you heard about typst”
-> Fediverse

Finally somewhere that actually has Fediverse as an option, this must be a good app.

Heroin

This is pretty cool. I’ve got a couple repos that Microsoft uses for VS Code. I switched one of them to GPLv3, but maybe I’ll switch the other to this license.

This is a bit like asking “how do you cook meat for a lot of people?” Not only does number-of-people and kind-of-meat matter a great deal, but even with that info, there’s a million different valid answers and an entire sub-field-ish of science on how to do it.

Based on what little info there is, I’m going to guess that A B testing with groups of experimental features enabled would be best for your case.

Not only in order but also

1. very human-obvious (international 1-1-2020 is not obvious if day-mo-year or mo-day-year)
2. Allows for arbitrary additional levels of precision to be appended. (E.g. year-mo-day-hour-min-sec-etc)

Fair, I did miss that requirement

It is a sad story. Keeping it in legendary meme status is the best way to remember it IMO.

Temple OS

For standard notes, its got an auto-export plaintext file option on desktop. Were you wanting two-way editing of plaintext? (e.g. Auto export and import)

When you’re editing yaml, why not just always write JSON?

Almost all nix attr keys are unquoted strings. Maybe I’m missing the point list, but I kinda wouldn’t expect it to be on the list.

Despite my love of yaml. I actually think he has a small point with unquoted strings. I teach students and see their struggles. Bash also does unquoted strings and basically all students go years and years without realizing

cat --help
cat "--help"
# ^ same thing

cat *
cat "*"
# ^ not same thing

cat $thing
cat "$thing"
# ^ similar but not the same 

To know the difference between special and normal-but-no-quotes you have to know literally every special symbol. And, for example, its rare to realize the -- in --help, isn’t special at a language level, its only special at a convention level.

Same thing can happen in yaml files, but actually a little worse I’d say. In bash all the “special” things are at least symbols. But in yaml there are more special cases. Imagine editing this kind of a list:

js_keywords:
- if
- else
- while
- break
- continue
- import
- from
- default
- class
- const
- var
- let
- new
- async
- function
- undefined
- null
- true
- false
- Nan
- Infinity

Three of those are not strings. Syntax highlighting can help (which is why I don’t think its a real issue). But still “why are three not strings? Well … just because”. AKA there isn’t a syntax pattern, there’s just a hardcoded list of names that need to be memorized. What is actually challeging is, unless students start with a proper yaml tutorial, or see examples of quotes in the config, its not obvious that quotes will solve the problem (students think "true" behaves like "\"true\""). So even when they see true is highlighted funny, they don’t really know what to do about it. I’ve seem some try stuff like \true.

Still doesn’t mean yaml is bad, every language has edge cases.