skysight-inc/HackerNews huggingface dataset:
Watch some of the Air Safety Institute videos on YouTube. I believe 90% of general aviation accidents are VFR rated pilots flying into IMC (i.e. flying into clouds).
I've been using Roll20 on Firefox for 4ish years. (I was a Kickstarter backer, but I'm not sure when I switched to Firefox from chromium).
PyCaret – open-source, low-code machine learning library in Python
> And yes they did have higher skin cancer rates

Much, much higher. And older people who were reasonably active and spent a lot of time outside (even if they didn't deliberately go and sunbathe) have often had one or two cancerous spots cut out.
> and stuck with Common Lisp's woeful hash table interface and the loop macro keywords

You are not stuck with anything in Common Lisp.

Instead of loop you have lots of options, from the built-in constructs (do, dolist, map...) to very powerful libraries like SERIES and ITERATE.

You are not stuck with the default hash table interface either. Many libraries for data structure are available, you just pick the one that suits you best.

>And then Clojure implemented Map literals and - what do you know - Clojure still has Lisp Macros!

Most of those Clojure features are already available in CL through the use of libraries. Even the ability to easily call Java libraries, by using the Armed Bear Common Lisp implementation.
From the creator of https://special.fish/ and other fine downtempo htmls.
No, I already multiplied 624 TFLOPS / GPU * 8 GPU = 4992 TFLOPS (the 5 petaflops number).

I'm saying that you are still missing another 8x on the way from 19.5 TFLOPS / GPU to 624 TFLOPS / GPU. 19.5 (base FP32 theoretical peak performance) * 2 (FP16 instead of FP32) * 2 (counting sparse matrix ops as dense ops) * 8 (unknown) = 624 TFLOPS.
TikTok is a bit headache inducing for anyone not under 20. Anyway I don't think humans should be receiving that much stimulation, and information overload in such short bursts.
You call is slave labor, but I'm willing to be many in those jobs could not view it as further from the truth. The know they life they left behind and are ex exceptionally grateful to have an opportunity to make what most Americans would see as peanuts. It's all perspective. Americans demand a lot.
No real reason to call nintendo out here, every console i know of has been that way for many generations.
Fair enough. Perhaps the higher reaction times needed for RC planes in general along with the several years that have passed since I last flew one have clouded my memory. I had lots of fun with the plane too, don’t get me wrong! The MetaFly is just more my speed, I guess.
FYI: There is a funded, global, commercial gaming VPN service with HQ in SF also called Subspace that hss had deals with major gaming networks since 2019.

You might want to sort out the Subspace name and trademark, sooner than later.
We would just look for the signs to Cahokia Mounds when going to St Louis from Urbana/Champaign. Well marked.
It's a bit of both, but it's much more so that they built a lot of them, and then threats of lawsuits basically tanked general aviation production in about 1985 and it's never really recovered - so there is a heavy bias towards older design.

Even the 172 itself was out of production for over a decade (1986-1996). Peak production on the 172 (in the 60s) was ~1400/yr. In 2019 they built 52.
Right — and the WordPress app has taken years to get semi-decent. There was a third-party WP app that WordPress acquired/acqhired many years ago that was excellent (it was the only app that allowed me to access a very customized WP backend with custom fields and other configurations so I could edit work posts back in the day), but the best features were never brought over to the main WP app and WP has evolved now so those features wouldn’t even be useful.

Tumblr has a great mobile app — as I said in my initial post, it was actually on top of the mobile trend — but none of the other blogging platforms do. They assume a response web page will work and it won’t — or that you’ll be creating a new file and kicking of a CI/CD build pipeline for a static site — which still doesn’t help if you just want to write an update or post a photo from your phone.

Even easy web builders like Squarespace and Wix and the like have, frankly, subpar mobile options.

You can’t blame people for just deciding to use Facebook or Instagram.
Anecdote about the subjective difference between using both:

I've used nix and nixos on and off since the early versions, but it never really clicked with me, and every time I want to write or just read nix expressions I have to reread lots of documentation like I'm starting from scratch again, whereas I would probably still be able to write a debian package from memory alone despite many years of lack of practice. This leave me with the impression that nix has to be a full time job.

In another hand, I gave guix a try recently and was really surprised by how easily all the pieces fell together "naturally".

Also guix being a smaller community, it might counter intuitively be moving faster (due to less care for not breaking things or less bureaucracy, depending on your views). Indeed, another issue I have with nix is how jammed their input queue of PRs is.
Newer planes reverse this to an extent. Modern engines with FADEC lower pilot workload considerably. Basically - you have a single power lever, vs anywhere from about 3-5 controls on older carbureted engines.
I'm in Australia and have an annual skin check. The doctor advises adults to use a moisturiser with sunscreen component as a daily default, especially anyone with fair hair. My wife tends to do this.

The doctor has mentioned in the past that 60+ year old males who've worked farms or building sites their entire lives have a 35%+ strike rate on finding a cancerous mole when they come in for a check.
> If you lock yourself in a room and do the most marvellous work but don't tell anyone, then no one will know, no one will benefit, and the work will be lost. You may as well not have bothered.

Maybe this article should be called "I sell, therefore I am".

The quote from the article, to me, sounds ridiculous. I don't lock myself in a room and do marvelous work for other people, so that they know it exists, or so that it will last longer than I do -- and I suspect many other creators feel similarly.
SD cards hop on the PCIe 4.0 bus to hit 4GB/s with version 8.0 of storage spec
I still lament the days before Tumblr got rid of RSS feed imports. I know why that happened (spam), but it was so nice to be able to help build kind of a curated feed of activity from all over.

But I agree that Tumblr remains a gem. I’m glad Automattic bought it and agreed to continue to support its staff and development.
I mean, it's Popular Mechanics... not exactly a publication known for quality journalism.
This is fan service to the millennials who have taken up flying lessons during their midlife crisis. The guys wearing aviators while pretending their aircraft doesn't sound like a lawnmower.
>From what I read it took a whole summer to write in lisp and the rewrite in python took a weekend.

And one guy in comp.lang.lisp wrote a working Reddit 1.0 clone in Lisp in 4 hours:

https://groups.google.com/d/msg/comp.lang.lisp/9WD9-yEaqMs/H...
> Poorly modularized and architected code is just that, no matter the paradigm. And yes, there are a lot of bad LabVIEW programs out there written by people new to the language or undisciplined in their craft, but the same holds true for stuff like Python or anything else that has a low barrier to entry.

That’s very insightful, and I think nails part of my bias against specifically LabVIEW, as well as other novice-friendly languages. My few experiences with LabVIEW were early on in my EE undergrad. At that point I had been programming for about a decade and had learned a ton about modularity, clean code, etc. The LabVIEW files were provided to us by our professors and, still being a naive undergrad, I assumed our profs would be giving us pristine examples of what these tools could do; instead, to my programmer brain, what we had was an unstoppable dumpster fire of unmanageable “visual code” that made very little sense and had no logical flow. Turns out it’s just because our profs might be subject matter experts on a particular topic, and that topic wasn’t “clean long-term LabVIEW code”. Later on I ran into similar problems with MATLAB code that our profs handed out, but by that time I had clued into my realization. At one point I was accused by my Digicom prof of hardcoding answers because there’s no way my assignment should be able to run as quickly as it did. (I had converted a bunch of triply-nested loops into matrix multiplications and let the vectorization engine calculate them in milliseconds instead of minutes)

Just like LabVIEW, my bias against PHP comes from the same place: it’s obviously possible to write nice clean PHP, but every PHP project I’ve had to work on in my career has been a dumpster fire that I’ve been asked to try to fix. (I fully admit that I haven’t tried to do a greenfield PHP project since about 2001 or so and I’m told the ecosystem has improved some...)

I lucked out with Python and started using it “in anger” in 2004, when it was still pretty niche and there were large bodies of excellent code to learn from, starting with the intro tutorials. Most of the e.g. PHP tutorials from that era were riddled with things like SQL injections, and even the official docs had comment sections on each page filled with bad solutions.
Please ELI5 why it doesn't happen for www.ebay.com using Firefox in Debian. I see no websocket connections to localhost in Network Monitor or iftop.
Twitter rolled out reply control on tweets
I haven't looked carefully at the design; in fact, I've only read enough of the code to see that there's a flag to disable IV randomization. I'm only here to say that GCM is completely insecure if IVs are ever reused.

https://toadstyle.org/cryptopals/63.txt
I like the idea, but I would be wary of it for this reason: the people who would like to use it are probably the most miserly members of /r/personalfinance. The kind who are likely to quibble about the $8/mo plan compared to the $9.50/mo plan. Basically the worst customers you can imagine.

That said, let me know if you do it!
> If you need two while loops each doing something concurrently, you just draw two parallel while loops.

Not quite. You'd need to draw two parallel boxes, each of which is strictly single-entry/single-exit, and draw a while loop in each box. This is because a while loop

+-------------------+
v +-->[fn]--^
-->*-->«cond?» +-->
+-----------^

depicts parallel flows that do not represent stuff being done concurrently! Once you acknowledge that, pattern matching actually becomes easy: just start with a "control flow" pattern and include a conditional choice node with multiple flowlines going out of it, one for each choice in the match statement. You're drawing control flow so it's easy to see that the multiple flowlines represent dispatch, not something happening in parallel.
Water does, however, seem to self-assemble into larger structures: https://en.wikipedia.org/wiki/Water_cluster

That isn't to say polywater exists, or that you should go out and drink de-clustered water. It is interesting to me that a full understanding of the properties of water still eludes us, however.
AT&T Told to Stop Using '5G Evolution' in Marketing
but they're easy to fly, forgiving and as far as I can tell unbreakable (though my students try to prove me wrong)
Mount Everest is visible from Kathmandu for first time in living memory
Serverless vs Containers: Picking Serverless – Talking Serverless
There are hot women in your area

Here's the data in a spreadsheet
Having worked with LabVIEW a fair amount, the problems I have with visual programming are:

1) takes up a lot of space

2) each subroutine (sub-VI) has a window (in the case of LabVIEW, two windows), so you rapidly get windows spewed all over your screen. Maybe they've improved that?

3) debugging is a pain. LabVIEW's trace is lovely if you have a simple mathematical function or something, but the animation is slow and it's not easy to check why the value at iteration 1582 is incorrect. Nor can you print anything out, so you end up putting an debugging array output on the front panel and scrolling through it.

4) debugging more than about three levels deep is painful: it's slow and you're constantly moving between windows as you step through, and there's no good way to figure out why the 20th value in the leaf node's array is wrong on the 15th iteration, and you still can't print anything, but you can't use an output array, either, because it's a sub-VI and it's going to take forever to step through 15 calls through the hierarchy.

5) It gets challenging to think of good icons for each subroutine

6) If you have any desire for aesthetics, you'll be spending lots of time moving wires around.

7) Heavy math is a pain visually (so you use the math node that has it's own mini-language, and then you're back to text)
How can be almost always symptomatic but at the same time run in some many members of the same family? When you go to see a psichiatrist one of the first questions the ask is if there's history of mental illness in the family.
I don't want to believe
FAQ says "Implement a meaningful subset of IMAP for access to local storage."

What subset do you implement? Thanks.
>The post [1] (though old) - hints at no good libs for json

That's his opinion. We have a lot of JSON libs, maybe too many. I use "jonathan" and i'm happy with it.

EDIT: He wrote: "JSON support in Common Lisp is a god damn mess. There are an absurd number of JSON libraries and I don't really like any of them."

He doesn't like any of them, but I do like more than one.
Hmm, sounds like you might be automating tests on the target, scripted from the PC. There's a place for this, but I'd call that automated integration/system testing, not unit testing.

Unit testing was traditionally considered impractical for embedded systems, because the code is so closely tied to the hardware. However, with proper architecture and unit test frameworks that simplify your life, it's quite feasible, and indeed enjoyable.

You write unit tests that exercise your embedded code, compiled for the PC, not the target. This ensures your code is portable.

I use the Unity/CMock/Ceedling framework when I'm writing in C, and CppUTest when I'm writing in C++.

I HIGHLY recommend the video courses taught by the guys at ThrowTheSwitch.org (the authors of Unity/CMock/Ceedling). See https://www.throwtheswitch.org/dr-surlys-school

I read and enjoyed James Grenning's book, Test Driven Development for Embedded C, but it didn't really click for me until I took the video courses mentioned above. In the second course, you code an entire simple but realistic embedded project in TDD fashion.
Fatal accidents per 100,000 hours:

GA: ~1.0

All helicopters: ~0.7

Commercial fixed wing: 0.05

(And the accidents that do occur on commercial flights are mostly small cargo planes... for major airlines that number would be more like 0.01 although it's hard to really get good numbers at that point because the numerator is so small... there are years when the US doesn't have a single fatal commercial passenger crash)
I guess but I feel like the schooling they get is largely bogus anyhow especially in elementary school and nothing I couldn't fix by just tutoring them a bit at home
Maybe that's why you see China catching up - because America is falling back and suppressing disobedience.
How does Edward Snowden acquire a laptop or phone in a way that he can trust it? I don't think it matters what protocols and applications he uses: he does not enjoy privacy.
In 2016 there were 1,036 non-commercial general aviation accidents. 13 were caused by VFR into IMC, or 1.3%. 54% were fatal accidents. They accounted for 4.4% of fatal accidents.

https://www.aopa.org/training-and-safety/air-safety-institut...
(we’ll be watching for the negative impacts too)

Forgive my incredulity, Jack.
The non-blocking read is a bad hack to an ill-defined problem.

For starters, if a read would fail, so would a write. Your write path has to handle errors anyhow, so the non-blocking read is a contrivance. I understand the reason for the contrivance--it's because the typical SQL driver API requires first dequeueing a connection from a pool, passing ownership to a caller, and the caller sending a query. The proper and better API is to combine the "dequeue connection" and "send query" steps, returning a handle back for the response, which may include (as an optimization) assigning the connection to the caller for any additional requests. Additionally, any hack that prevents the majority of write failures, but not all, leaves time bombs around by not stressing the write failure paths of the caller.

Secondly, IME a far more common reason in the wild for a connection disappearing is either a) the server crashing or b) NAT association timeout. In either case it's typical for the remote end to simply disappear, and unless TCP keepalive is enabled, a read won't return any error until you first attempt a write and wait for the TCP stack to figure out that the remote end is gone. In the best case that's a R/T, in the worst case some eager firewall rules in the middle or on the remote peer silently drop packets for unassociated connections and/or the ICMP response and you're stuck waiting for TCP timeout.

Thirdly, and related to #2, absent TCP keepalive or an application ping (not ICMP ping), connections are far more likely to get dropped on the floor while sitting in the pool. And an application ping is more reliable because some firewalls and application and NAT gateways drop or ignore TCP keepalive.

I've written client libraries with connection pooling for HTTP, MySQL, SMTP, RTSP and generic TCP. I learned all this the hard way.
What proof specifically would you like to see?
America’s Patchwork Pandemic Is Fraying Even Further
Please don't suggest using Docker to sandbox a GUI app.
Reminds me of the EEE and Microsoft post recently on HN.
If it runs in the same Xwindows session no.
>I have noticed that deployment and compilation part of lisp isn't talked about often.

Because it's trivial.

Compilation is almost implicit, when loading a file.

Creating an executable is only one line of code.
> I've worked with EEs who write massive applications (...) their codebases are all impossible to maintain masses of pain and suffering.

Fixed that for you :). EE/CS dual here. Some EEs can code, some CS folks can design circuits, but if I had to bet... I wouldn’t expect great work to come from either discipline working on the other side of the software/hardware line. I’m decent at both, but I pretty much squeezed two degrees into a five year programme and have put a lot of effort into maintaining competency in both disciplines throughout my career. These days I’m mostly doing embedded and am loving life :D
If you scroll down to the bottom of their main page (https://www.inklestudios.com/inklewriter), you'll find a collection of other interactive stories that people have written using this tool.
Yes, absolutely. Although to be fair, CUDA is a royal pain (although way easier) even on more standard distributions (supporting multiple versions seamlessly is hours and hours of fun and breaks all too easily) and is behind the great majority of time “wasted”. NVIDIA deserves a lot more flak for this than they receive.
For me it’s using a rooted phone. I have some info for my RE on another app that might be helpful.

https://docs.google.com/document/d/1q0Pz2t5Gmt-vv8z-2Yswhvg2...
I grew up in St. Louis County and Cahokia mounds was a favorite field trip in school.

If you have the opportunity it's a really cool place.
> a version of this comment is posted... for the last five years

Sounds like he is right and you are too old and averse to change to admit it!
This is totally incorrect. Icing isn't even in the top 10.

In the sort of conditions wher le icing is likely, VFR pilots will lose orientation and fly it into the ground (or a mountain) way before they ice up.
Covid-19 contact tracing hits Apple devices with iOS and iPadOS 13.5
75Baires and no Covid-19 help in SFO
This is why I walked back my claims a bit in my tldr — basically started trying stuff out and had a “whoa not used to the way that looks, but it does _work_...” moment.

I think I still have the “wrong” preference, but I appreciate learning some new stuff!
Well think of this. When you are sad, do you feel like killing yourself is an option to stop that feeling?
Actually I think there's middle ground or a way to somewhat satisfy both.

Does Zoom, Slack, or insert-thing-here need the technical ability to portscan localhost in the manner of this blog post? Well, Zoom had their vulnerability making web requests to their app bound to localhost, but did they need to be able to do it? They could get the job done without that functionality.

They already have both an app and a web-only experience. (They try to hide the latter by only presenting the option when the former has evidently failed, but it's still there.) So, it has it both ways by your 1 & 2. Almost as if users should be able to choose.
Podcasting is still innocent.

What these bad dumb losers opt to try to call podcasting but which is some bad new capitalist horsepucky? I'm not worried about it. It's a bad look. For everyone involved. It's not innocent, it's dull & diluted & money grubbing. And it sure as shit ain't podcasting! Sayonora losers! Your ability to take a decades old pure thing & suck at it, make it bad- that does not degrade the thing itself. It's just better than you, whatever you are.
I think people should be cautious in taking this advice for anything but toy projects, on a few counts. I spent two years developing on a framework I built myself, until I finally gave in and spent an inconvenient amount of time porting to Django.

1) Unless you have a lot of experience, you don't know why various patterns have been implemented, or various compromises have been made, in existing frameworks. Frameworks aren't on the whole built by idiots, and if you think a framework has made an obviously poor choice, count the days until you realise why they did it. If you're lucky your choice will still make sense for your application. If you're not, I hope it doesn't take you too long to redo it all.

2) As the author says, frameworks are by nature declarative. This is great if you have really good documentation, but if not you're going to scream trying to work out the control flow of your application. "Why does changing variable X result in behaviour Y? What is even checking variable X? grep's returning nothing, the stacktrace is twenty levels deep and I don't recognise any of these functions. FUCCCCCCKK!"

You're going to forget how your framework works. If you don't forget there was no point building it at all, because the point of a framework is to abstract you from having to think about things.

3) Your project's not that special. The framework your considering will probably work just fine. It's worked for several million other projects, it'll work for yours. Yes, you might spend a bit of time trying to shoehorn something in. It'll be an order of magnitude less time than building an entirely new system.

4) It's much less useful for future work. A high-level understanding of building frameworks will get you a job at the Django Foundation. An high-level understanding of Django will get you a job everywhere else. And also at the foundation, come to that.

It was a fairly informative process. It taught me things I didn't know I didn't know. I value it in much the same way I value building interpreters. But much like building interpreters, except in a few niche areas it's probably not a good use of your time.