skysight-inc/HackerNews huggingface dataset:
Officially: 2202 deaths (attributed to the nuclear disaster) from evacuation, and 1 death from radiation.

Technically: determining the health impact of radiation is difficult and the methods are disputed. Moreover every specialist agrees that waiting at least 15 years is necessary because most induced ailments have a non-neglectable latency. Solid cancers, for example, develop in up to 15 years.
Beyond Compare is a lovely Delphi application.
Any thoughts about this? I'm opening waitlist page https://get.fomosh.com
I highly doubt this will happen. There are a ton of apps that use things like Cordova or Capacitor (usually for cross-platform purposes).

What I could see them doing is making apps declare URLs that they need access to. Basically, you get full functionality on declared URLs, but if you are just using WebView for a "generic" in-app browser you lose the ability to inspect random pages.
Yes, thank you, in distributed setting they really use only two filters.

But my main point is that the video addresses the issue from the article.

The video lays out intuition for the Bell's theorem using the 3 filter experiment.
And then, at 8:50 they say: "what if the act of passing through one filter changes how the photon will later interact with other filters? Then you can easily explain the results of the experiment" and continue explaining that the real spookiness can be proven in a distributed experiment.
Don't be discouraged. You're more likely to succeed by targeting a niche.
That's fair, I must be lucky in that I don't have a monthly or annual card fee for my Visa debit.
> the rotary encoder. I don't see what the aim of this is - what's the intended usecase?

I actually have a separate USB rotary encoder next to my keyboard. Glad to see it integrated into the design. It's like a more comfortable mouse wheel. If you need to scroll a lot (editing audio, for example), the constant "scroll a little, lift finger, scroll a little, lift finger" routine gets old real fast. But if you've got a wide enough knob, you can just spin it around indefinitely in one circular motion.
If he, and others in his profession before him, had written on typewriters, the typewriter company employees could still be working at typewriter companies.
I'd like to be, but it's still not legal in my country, and our state leader just flipped and said he won't consider legalizing it.
My partner worked in a Research School of Chemistry.

On the top floor of the building a tip-over failure replacing an argon bottle broke the valve off the end and emptied the compressed lot of Argon in short order.

Argon being colourless, ordourless, heavier than air = whole building "anti-suffocation" evacuation. But no fire problem!
It doesn’t actually matter unless your API is expected to be consumed without any particular entry point. If you can expect users to enter at specific points, you can represent state as hypertext and give them links (URLs) rather than ids. They don’t need to know or care about your URL patterns, they just need to follow the hyperlinks you provide.

You can do the same even if some entry points are known, and then I'd follow the approach of /top-level/:id, because it’s at least a predictable way to start. If further API access requires discovery, go wild and format your URLs how it works best for your service. Just keep them unique and stable, because stable URLs are cool!
There's one at the Pole, capable of handling C-130s. https://en.wikipedia.org/wiki/Jack_F._Paulus_Skiway
In Australia, our New Payments Platform (which has been rolled out to almost all banks at this point) allows you to set up an email address or mobile phone number as your "PayID", which negates the major advantage you mention for P2P transfers. (People are still getting used to using PayIDs at the moment, so I still get many friends sending me their bank account numbers like they always have, but usage is definitely picking up.)
Hasn't stopped them in the past, usually completely ineffectively.
I think its a non problem
Yes, agreed, this is nothing more than a cute toy, and not anywhere close to a full-blown productivity application. But it does show some fundamental API (and language) stability, and especially with X11 in the mix I really had anticipated more problems.

It's not even a particularly cherry-picked example. One day a few years ago, I suddenly remembered that cat, and went out to see if I can still find it. I tried to build it more just for kicks and remember being surprised when it not only "just built", but even "just ran", on my Mac, for which it wasn't even for.

Yeah, something bigger will most likely push back more, especially as soon as more dependencies than just the C library itself and X11 come into play. Though overall my track record in building ancient C stuff with an acceptable amount of changes is pretty good!
How about a slightly different approach?

I just use a tablet --- supplemented by a compact foldable bluetooth keyboard with touchpad as needed ($30 on Amazon).
Yeah, status quo is almost all apartments get a score of 0! OTOH, I did have some friends that lived in a giant apartment complex in Santa Monica that was one big debuached party 24/7. People who moved there knew that that's what they were in for. Not sure what conditions set that up. It seemed like the reputation of the building was self-sustaining.

My concerns about the gamification are that it would be quite easy to accidentally make things really creepy. E.g. lets say you have a game intended to get you to share stories with your neighbors, and the win condition is that you prove to the app you know stuff about each other, and then you accidentally end up with neighbors aggresively researching each other, and it's 1984.
This falls under the category of problems where verifying, hell describing, the result is harder than the code to produce it.

Here’s how I would do it. The challenge is that the result can’t be precisely defined because it’s essentially art. But with TDD the assertions don’t actually have to actually live in code. All we have to do is make incremental verifiable progress that lets us fearlessly make changes.

So I would set up my viewport as a grid where in each square there will eventually live a rendered image or animation. The first one blank, the second one a dot, the third a square, the fourth with color, the fifth a rhombus, the sixth with two disjoint rhombuses …

When you’re satisfied with each box you copy/paste the code into the next one and work on the next test always rendering the previous frames. So you can always reference all the previous working states and just start over if needed.

So the TDD flow becomes

1. Write down what you want the result of the next box to look like.

2. Start with the previous iteration and make changes until it looks like what you wanted.

3. Write down what you want…
If you follow Nims on Instagram he often links to other accounts.
It is more like a random audit than whack-a-mole. It will scare off a huge amount of small time players with lives they don't want ruined that had thought they could use it to tax dodge. Maybe they still can, but now they have a chance of random audit hanging over their head.
I think they did, but then found it too much effort to maintain (I think there was also some hacking scandal? I forget)

For what it's worth HK internet presently uncensored, though ironically TikTok pulled out of the HK market as they felt it was too expensive to comply with Hong Kong laws given the size of the available market here.

DouYin is still available in HK though -- not sure if DouYin is available in US/Euro market or not??
The proof is in the pudding as they say, but the idea appears to be exciting on the face of it!
You don't have an absolute right to arbitrary speech. I can't, for instance, do a public reading of a copyrighted work.

I don't see why this case requires constitutional review any more than, say, the concept of copyright.
The creator of the keyboard literally posted this to ask for feedback from HN users. I'm pretty sure in this instance HN users _are_ the target audience--or at least part of it. In any case, feedback is helpful at this stage (and is sought by OP).
I like Gruber, he has a CS degree and had a brief career as a web developer (which certainly helps him write about technology as well as keep his site operational), but he has been a full-time columnist for his own tech blog for 16 years. As far as I know, he does not have experience writing client side code, either using AppKit/UIKit or using a tool like React Native.

He has plenty of people in his network who are professional developers with SwiftUI experience. However, he was talking about his gut feel from a core system service having so many UI nits from Apple, likely associating that with issues he has heard of from developers who have tried to adopt SwiftUI in their existing and/or new projects.

So thats the basis of my opinion - a quote or two from those full-time developers would added greatly to the article, significantly more his personal reaction.

As a developer with some client-side experience, I'd say the nits speak far more to Apple's MacOS development process these days than to the quality of SwiftUI. A decision was made to add it to the 13 beta and commit to shipping it, rather than hold it back for macOS 14.
Method to determining whether a login page is real or a phishing scam.
I'm sorry you're interpreting my comments as hostility, but basically you're being a the sort of commenter that it isn't really worth engaging with. You're not interested in my answers, and you've accused me of using arguments from authority. From my perspective you seem intent on finding some loophole where i'm either lying to you or i'm incorrect. In a message board format, particularly with the number of outright bad actors when it comes to anything COVID related, how is it actually in my interest to provide you with a freshman course on molecular biology?

The problem is you haven't grasped that they're actually the same answer. It can be true that a field driven by stochastic behaviour consists mostly of degrees and probabilities, and still, due to the realities of how evolution and natural selection work, mean that it is impossible for an extremely highly conserved component of spike protein to jump to a new configuration, that at the same time escapes antibody response for the conserved region and maintains any degree of fitness in the wild.

Please park your antagonism and if you are actually interested, walk through the door and explore the field yourself. It's fascinating
3) One cannot put substantial content into the cloud without knowing that it will be used in ways one cannot anticipate.
A foldable, bluetooth keyboard with touchpad is only $30 on Amazon.

Pair it with a cheap tablet of your choice and you have similar functionality and (from what I hear) superior reliability --- at lower overall cost.
> All electronic cash transfer systems should be assumed to be incompatible unless there's a clear AML chain established that can reasonably defend against a blanket sanction.

Nonsense absolutism.

Is that why Stripe, Moneygram, Circle, etc invested in Stellar, and they are still using ISO 20020 compliant cryptocurrencies like those ones after waiting for regulatory clarity in March 2022?
That was about the last time I had even heard it mentioned. I still remember trying to play with it circa the early 2000s and thinking it had potential, but never coming up (at the time) with anything I wanted to solve with it.
Hmm I'd imagine Sydney fits the bill for "big rich city"
What I learned working with a senior engineer as a new grad
In some cases there might be a next stage of complexity where you have users with access to multiple tenants who are browsing them in different tabs. Then putting the organization as the top level in _every_ URL helps signal intent; otherwise you have to take other precautions that someone isn't on a tab with Organization A, clicks "Post new article" button (-> POST /articles) and happens to have their session logged into Organization B and so creates the new article ere.
> - /organizations/:id

> - /blogs/:id

The pragmatic, large-company-only counterpoint is the narrow edge case where:

- :id must be human-readable for "SEO reasons"

- there are many competing organizations and blogs to the point where there may be a name collision.

Although in that case, I'd still suggest:

/:organization-name/:blog-name
I wouldn't go that far... I've used Linux since the mid-90s, and Windows for a few years longer than that, and Linux is still orders of magnitude easier to follow and especially to dissect than Windows. Windows is pretty much entirely opaque, you're at the mercy of whatever happens behind the curtain. UNIX-y OSes like Linux and OpenBSD blow that curtain wide open, but OpenBSD is just much more consistent because it's all built "in-house". (And then some super popular stuff like OpenSSH gets exported from it.)
This is probably akin to the Latinos in Texas who lap up Ted Cruz calling Beto’s nickname pandering and ignore the face that Cruz’s Spanish is worse.
>at least for anything actively being used and updated

This implies that the strength of the tests appears when it's modified?

Like the article says, TDD doesn't own the concept of testing. You can write good tests without submitting yourself to a dogma of red/green, minimum-passing (local-maximum-seeking) code. Debating TDD is tough because it gets bogged down with having to explain how you're not a troglodyte who writes buggy untested code.

And - on a snarkier note - this is a better argument against dynamic typing than for TDD.
Not to be too much of a cynic, but this article definitely has me losing a bit of respect for this writer.

It reads like the social acceptance of his writing/illustration is of the utmost importance to him, and that social acceptance should trump other considerations. This type of yearning is a trust buster for me. I don't want writers/publications towing whatever the politically correct line is for that given moment, I want them to be intellectually honest and open for whatever topic they are writing about.

Perhaps I would interpret it differently if he was honestly wrestling with the impact and considerations of technology, instead of just reacting to a Twitter rainstorm that came and went like they all do. I don't feel like he's really grappling with it, just giving into the simplistic "AI art can take our jobs away, so therefore it's bad" take, but then ignoring how he uses other technologies that people aren't complaining to him about on Twitter. (this of course is not to say anything about the ethics of said technology, my comment is about intellectual honesty and not groveling)

If this writer was really sincere about not wanting to leverage technology that could have the downstream consequence of job displacement, why on earth is he writing on the internet and interacting with so many people on the internet? There are so many jobs that could be involved in physically distributing the information that he wants to distribute, but he knowingly plays a part in using a distribution system that is essentially zero-cost and doesn't need labor to distribute information. Why is he using Getty instead of working with independent photographers/illustrators and paying them MORE? (I know he said he will pay the complaining illustrator on a future one, but that was done because he was called out)

It's going to be the same story with AI art and AI other things. I would predict that at some point in the next 5 years this writer will be using AI art again, because it'll be more socially acceptable then.

I obviously say this all from the position of not being in the eye of a Twitter outrage cycle, but man, I would love to see more people not kowtow to the mob and just let it pass...
Yep this is it. If you nest IDs you just end up burdening all consumers with having to mimic your hierarchical structure when they don't need to.
Practical examples: Scrolling a soundwave in Audacity. Scrolling the sequencer in a DAW like FL Studio. Binding it to a MIDI control to play live music. Rotating a 3D model.
Apple security flaw ‘actively exploited’ by hackers to fully control devices
> No other English poet wrote successfully in so many structural forms, or summoned so many of the language’s ancestral voices […] claiming as personal playground the entirety of English versification.

An interesting example, not mentioned in the article, is Auden's "verse commentary" in Night Mail, a documentary by the General Post Office: https://www.youtube.com/watch?v=zmciuKsBOi0 (full film: https://www.dailymotion.com/video/x7utm3o)

Auden wrote his lines "timing the spoken verse with a stopwatch in order to fit it exactly to the shot". Wikipedia says the director Watt had only grudgingly agreed to the idea in the first place, but came around:

> Watt cared little for Auden's fame and well known work, calling him "a half-witted Swedish deckhand" and complained of his frequent lateness during filming. Watt later wrote: "[Auden] was to prove how wrong my estimation of him was, and leave me with a lifetime's awe of his talent".
The method that works best for me is from code complete. McConnell argues (correctly, IMO) that tests are a technique, and writing tests means more code to maintain and debug. Tests can be wrong, and if the test is wrong, the code will also be wrong. Thus, a bug is introduced. He advocates first making sure you have good software design, i.e. components are laid out, how they're going to interact with each other is well defined. So before writing any code at all, make sure you have a documented design that works conceptually.

Define the systems that make up your software, the classes that make up the systems, and then the functions they'll use to talk to each other. Once it works on paper, start coding. If the design is good, the code should be so brain dead simple to write that a monkey could write it.

I find doing this I do end up with long call stacks, because each module will do something, then pass the data on like an assembly line. In each step my functions are super short and I don't find it worth writing a test for 3 lines of code that I can tell is correct at a glance. For those few meaty functions that do more heavy logic, I will write tests for, though.
The $5 bargain bin webcam comes with software.

I’d expect my PinePhone to come with software too. I mean, I guess it did, I think I just expected more from the open source community than from the nameless fly-by-night vendor.
I don't feel let down by Pine64.

Pine64 produces affordable hardware that's easily hackable, and with more open schematics than most.

Pine64 fund a great community manager to collate and collaborate with the community.

Without Pine64, I don't think we'd have made as much progress as we have.

At this rate, we risk driving companies away from communities.
I'd do it this way as well for most cases.

Complicated URLs are hard to remember and annoying to share. The one benefit of the nested URL is that you get is of being able to "inspect" what organization or section or comment a piece of content belongs to. This is probably a rare edge case and something you should only implement if it makes your system much more usable, for some reason.

e.g. I'd probably rather have podcastsite.com/:podcastname/:podcastepisode/:comment_id
Android is in basically the same situation.

Obviously both Android & iOS let you open things in the default browser.

iOS has SFSafariViewController, which more-or-less corresponds to Chrome Custom Tabs on Android. These basically make a browser UI that is in the of the app for the purposes of multitasking/app-switching, but which is controlled by the browser. Devs can't inject code into these.

And both have WebViews, which let the dev do more-or-less whatever they want inside their own app.
[Ibn Khaldun] widely acknowledged to be one of the greatest social scientists of the Middle Ages,[13] who made major contributions in the areas of historiography, sociology, economics, and demography.

https://en.m.wikipedia.org/wiki/Ibn_Khaldun

… are unclear translations revealing biases?
We have some great models but what actually happens doesn't quite fit into any one model. For example all photons are constantly redshifted as they travel through space because space is expanding. That’s not really relevant on human timescales but it is an effect that takes place between your monitor and your eyes.

When you really dig into this stuff your realise stuff like the density of air is really an abstraction that doesn't quite fit what is actually going on.
I bought one exactly like that, used AutoHotKey to configure it for various productivity applications. By default it mimics my mouse wheel, for more comfortable scrolling.
It's not investing. It's gambling.
Right, this sort of malicious app issue imitating system UI to capture passwords is only really solvable this point by non technical means - App Store rejections, criminal penalties, etc.

Capturing a password is not going to be solved by a frame-busting header because the malicious app can just present its own content instead of rendering the requested enterprise/bank/etc login page.

Well, and new authentication tech like Passkeys/WebAuthn - the platform won't let a web view authenticate for domains other than ones associated with the native app.
This sounds like it might be playing a role. A while back someone posted an article about jet stream changes forcing commercial flights to land.

https://www.theweathernetwork.com/gh/news/article/stronger-j...
Book suggestion: "Digital Minimalism" - Cal Newport
May the next time you quit be successful :)
> If you _want_ to have some sort of hierarchy in the URL, you can redirect:

> - /organizations/123/blogs/1234 -> /blogs/1234

And:

/organizations/123/blogs -> /blogs?organization_id=123

Because what you're doing is just applying a filter to an index of blog resources.

I.e. the "/organizations/123/blogs" route is simply an alias to "/blogs?organization_id=123" which you can just redirect to in your gateway.
What would the difference be between this hypothetical “credit account” with payment card attached to it and a credit card?
> like "space-optimized 6502 processors

I don't think this is fair though. Some processes may support finfet, or gaffet, or some neat trick, where, if you switched to the process, but didn't optimize for size, you may be able to double the performance at half the power.

Like you suggest, it's some crazy multidimensional problem space. There's no hope in representing it with one number. And, nobody that's actually designing would care about any of these numbers. In the end, they would only be used by marketing, which is all they're used for now.
"for such an expensive proposition"

We need something cheaper than what we have now. People gravitate to walled gardens like Facebook because setting up their own systems is too expensive.

"No doubt there's some unnecessary complexity in there"

At no point did I mention the unnecessary complexity of IP/TCP/UDP, I'm not sure where you got that. I'm only talking about the necessary complexity. It's a great protocol that enables the modern Web. But it is complex enough that there is some expense to setting everything up, and that is why humanity ends up in walled gardens like Facebook. If you want to destroy the walled gardens, then you will need a simpler, cheaper protocol.