As others have mentioned you have to watch the battery if you do this for real.

The battery will swell and explode if you run 24x7 on a phone.

This is a great game and a lovely use of the minimalism found in pico-8.

It would be cool to have a speed indication when a plane is selected or height but that makes everything more complex.

Again amazing game for the pico

I feel like this is nothing more than a side effect of what happened with Covid.

Which would mean if we were willing to shut things down like we did we should be willing to take the secondary effects and solve those problems too.

I agree it can be seen this way. The pandemic years were the perfect time for everyone to lose their minds.

On the other hand, negative performance trends started in the early 2010s, and this may be more associated with the phone-based childhood.

The health establishment did not appear to think about children’s futures, only about making sure 86 year olds made it to 87.

This is personally offending to me, I lost two friends in their 40s in Brazil when Bolsonaro acted like Trump, and didn't implement any federal policy to lower risks during the first year of the pandemic.

Your take is stupid, that's how discourse goes now though, stupid hot takes from people who don't want to think, ponied up as some grand opinion while padded with derision and cynicism.

It's just stupid... And quite tiresome, be better.

I lost a relative because they wouldn’t let us in the hospital, waited too long to put in a stent while giving us the runaround over the phone, and caused lasting heart damage that took their life not long afterwards. We couldn’t advocate for them.

My take is not stupid. I saw the damage shutdowns caused personally. It’s offensive to me that you call my lived experience a “stupid hot take”.

Not to diminish your loss, but this whole debate is mired in the difficulty in moving from individual outcomes to aggregates that matter for public health policy. Things got ugly (and will do so again in the future) facing something novel, where many basic assumptions we have about individual results are based on other baseline assumptions that are no longer true. The very expectation of a good surgical outcome for a common stent surgery is based on statistics from "normal" times.

But, would the procedure have helped if the surgery was expected to cause COVID exposure, and the patient could have that severe respiratory illness during their surgical recovery? Would it be a good outcome if the surgical staff were dropping like flies with COVID they would get from the regular flow of patients? Alternatively, could the procedure be expected to work as reliably if the staff were wearing all that extra personal protection gear? That is not the conditions under which the procedure was developed and its benefits determined to be worth the risk...

I hope that our global experience produced enough data for someone to come up with better answers before the next novel pandemic. But, I don't know how you plow through all the inconsistencies in the data to come to any statistically valid conclusions. I.e. we have different regions/subpopulations who, in effect, ran different arms of an experiment. But, how can we compare their outcomes with sufficient rigor to find clear answers?

I wish I saw what these guys do in scheme. I only barely know what is happening and it seems interesting.

The parens are so hard for me to follow and always have. I have yet to find an editor that fixes that. Perhaps I did not try enough or am not smart enough to acutally use the editors correctly.

Anyway interesting read I think

The "such parens, much overwhelm, so confuse" attitude of non-Lispers always baffled me. Especially since when working in C-syntax languages, I'm cautious enough to enforce an explicit order of operations (to avoid confusion that can lead to errors) that I put nearly as many parens in my C or Java code as I do in my Lisp code. What's a few more pairs of round brackets among friends, eh?

Emacs was purpose-built for working in Lisp. Out-of-the-box it really helps with paren-matching by highlighting the matched bracket (of any type) when you cursor over a bracket (also works by highlighting the open when you type the close) and providing commands for traversing and selecting whole sexps. Those alone, combined with its smart indentation, will get you pretty far. Add something like Paredit or Parinfer if you want even more assistance with sexp manipulation.

I had a talk with someone very much allergic to lisp (a college trauma for him iirc). For people like him, extra distinction through syntax is a mental benefit while I assume lisp fans need the opposite, removing 90% of syntax makes things easier (sexps and fp composability being key too)

This is a good starter. Technically, it's Lisp and not Scheme, but once you understand one, you get the other. The benefit of Emacs Lisp is you can immediately play with it by modifying Emacs to meet your needs.

https://www.gnu.org/software/emacs/manual/eintr.html

C-like syntax:

    foo(1, 2, 3);

    if (x) {
        aaa();
    } else {
        bbb();
    }

Lisp-like syntax:

    (foo 1 2 3)

    (if x
        (aaa)
        (bbb))

Syntax is easy. Practical semantics is a little bit harder, but it's not hard.

Editor-wise, you want an editor that does automatic indenting and some kind of matching parentheses highlighting. Emacs is one. (Once you've learned the language, you can use a fancy structural editor, but maybe don't confuse yourself with too many new things at once.)

For vim/neovim users out there, here's my setup https://gist.github.com/mhitza/a00d7900571e9f13bac2bbf4a203d...

Not quite structural editing, minor annoyances, but pretty decent.

I've never understood why people who have no problem with

print(foo)

get stuck at

(print foo)

I've always found the parenthesis comforting, we know where it starts and where it ends.

I don't think they're fine with print(foo) and stuck at (print foo).

They're fine with:

    if a < b + c then d * e - f

And stuck at:

    (if (< a (+ b c)) (- (* d e)))

I personally don't mind s-expr syntax, but not having any infix expressions or precedence levels means a lot more parentheses in idiomatic code.

What I found weird in Lisp (and didn't even realize at first) is that

foo

and

(foo)

mean something different.

I now understand it similarly to the way in set theory x and {x} are different, but one is not used to the ordinary parenthesis symbol behaving in this way.

paredit on vim is great.

Working through all the exercises in "The Little Schemer" was a huge help for me when getting started. You start with a few primitives and build up all common tools from those with recursion, like how to build an addition function using just `add1` as an early example from the book.

Interesting point about the difficulty of parsing all those parentheses! I remember getting pretty frustrated with it when I first picked up Scheme. It felt like trying to read a book written in a strange code. But then I stumbled onto paredit in Emacs—it totally transformed the way I interacted with the code. The structured editing made it feel more like composing music than wrestling with syntax.

And you're right—working through "The Little Schemer" was a game-changer for me too. There's something about gradually building up to complex concepts that really clicks, right? I wonder if there could be a way to create more beginner-friendly editors that visually guide you through the syntax while you code. Or even some sort of interactive tutorial embedded in the editor that helps by showing expected patterns in real-time.

The tension between users wanting features and implementers wanting simplicity is so prevalent in so many languages, isn't it? Makes me think about how important community feedback is in shaping a language's evolution. What do you all think would be a good compromise for Scheme—more features or a leaner report?

Anything with crypto has a scam smell

virus stuff... should not be here

As expected. While Trump and Musk have or will have killed a lot of people with their cost cutting with USAID.

I expect the larger number of deaths to come from RFKjr. He is a deeply stupid man who cannot read and does not understand science or health related issues at all.

Linear.app is a product management tool like Jira. The article describes how they sync their data to their backend

I used to do this and it worked pretty well I thought.

I eventually broke it into years (YYYY-MM-DD-notes.txt and just grep'd the directory.

Finally I made it to markdown files also stored in the same directory.

It was great for searching.