skysight-inc/HackerNews huggingface dataset:
> It is impossible to have E2EE that doesn't leak into the UX

True, but one is also free to study the UX solutions implemented on platforms such as iMessage, WhatsApp, and Signal, which all have strong E2EE and see plenty of mainstream usage.

> [...] HTTPS requires nothing from the end user.

Depends on how you define "nothing". We've collectively put an insane amount of work to bring HTTPS to where it is today. Also, HTTPS continues to rely heavily on each server operator's skills and diligence.

There's also plenty of edge cases where HTTPS clients need to go an extra mile, such as containers (many base images do not include a cacert bundle), IoT/retrocomputing/other underpowered devices, and so on. There's always a cost, but it's usually worth it.
On the other hand, if they're completely different from a template language it seems like it should be just a moments work to demonstrate why, and help a fellow professional understand what they're missing.
The Treasures of Crash Reports
I don't really understand this argument, to be frank. Most runtimes are pretty small, and there's not much of a performance overhead to both runtimes running at the same time. It's not like these are two realtime engines both purring along in the background or something like that. All modern web frameworks are reactive, and won't do anything unless something needs responding to. If one part of the page is built with React, another part is built with Lit, and a third part with Svelte, I don't see how that will have noticeably worse UX (or battery consumption) than a page made with just one framework, even when reactive triggers are frequently exchanged between them.

The tweet you quote is about whether web components are "useful primitives on which to build frameworks". I doubt many web component fans (who actually really used them) would say that they are. They're a distribution mechanism, and the only alternative I've seen from these framework authors is "just make the same library 7 times, once for React, once for Preact, once for Svelte, once for Solid, once for Vue, once for vanilla JS". This is awful.
the linux results are for a vm running on macos. not sure how useful that is. i certainly wouldn't draw any wider conclusions from them without trying to reproduce yourself. pretty sure they will be very different on bare metal.
Found the answer:

> Stich said there is a space suit already on the ISS that one of the astronauts can use for the return trip, and the Crew 9 mission will bring another suit.

https://fortune.com/2024/08/24/boeing-starliner-astronauts-n...
I mean, you are right. ISPs also need to stop complaining about supporting it and get off their butts. All enterprise routing equipment for the past 15+ years has supported IPv6. There is no excuse not to support it. Once you understand it, it is actually simpler than IPv4 + NAT.
> With every programming language, you can do

There are plenty of programming languages where you can't do that. If you really need that, can't you just register it as "my-thing-1" and then register the other one as "my-thing-2"?
Sounds plausible, but as the author noted the OS has the knowledge whether you’re using a Bluetooth keyboard/mouse or not but it doesn’t matter - it shows that dialog even if you have wired peripherals plugged in. It’s dumb.
To clarify, I agree it’s not about subpar hosting for Matt — that’s just part of why I appreciate someone going after WPE.
More importantly, he invented diffusion models:

http://proceedings.mlr.press/v37/sohl-dickstein15.pdf
The standard, like PWA, is designed for maximum feasible misunderstanding. To the average dev it seems like a random bunch of features that don’t hang together. Five developers could look at it and be like the blind men discussing the elephant —- hung up on individual parts and not seeing the whole, if there is a whole.

There are a lot of candidates for “what’s wrong with modern web standards” but this fragmentation, which comes from a rather mathematical view of programming, is one of them. Thing is, a lot of web devs never studied computer science (even CS 101) and less than 5% live in San Francisco.
Ergodicity and Stationarity. Luck but Not for You
It appears that the choice is to either annoy people because they really do want to turn off Bluetooth or to let some people shoot themselves in the foot. They cannot turn on Bluetooth because they turned Bluetooth off. As a person who has never, ever shot myself in the foot - yes, I am that good - in my opinion all computer installations should begin with a choice that reads something like this:

* Provide absolutely no protections because I have never made a mistake such as typing "rm -rf" while in the "/" directory. And there is absolutely no truth to the rumor that I have flushed a watch down the toilet twice by failing to secure the watch band.

Or

* Make your best attempt at providing me with some reasonable protections so I do not shoot myself in the foot. I accept that even the best solution will be annoying at times and will still be annoyed.

[edit to make it clear that I did not flush two watches one time, but rather I flushed one watch two different times]
> And it's hilarious that you think that having to talk to the EU Commission to determine what is the law is somehow good.

No, it's not hilarious. This is literally what industry says it wants: instead of dictates by uncaring government you get a dialog with the industry that shapes the policy and lets the authorities adjust their approach.
Do you really want almost-boiling-water in ABS? I wouldn't do that.
Socialized healthcare seems to kind of work in many developed economies - where does it struggle and by what metrics regarding the health outcomes?
One thing about web components that I've appreciated is that they can work without JS enabled (at least in theory). I've done this a few times for progressive enhancement.

Broadly I agree with Nolan, though. Web components have enough rough edges that they're not going to take over the world in the current state. But, they are pretty nice for certain use cases.

I'm not sure what he means by not playing well with server side rendering though. I've been doing that without issues.
Unix Time in Python
possibly you meant 'gravimeters'; a gravometer is evidently a 19th-century density measurement instrument. plenty of gravimeters are as purely classical as anything electrical is, and those that prominently feature quantum effects are superconducting gravimeters. i don't see how a gaas fab is relevant to either mems gravimeters or superconducting gravimeters!

similarly 'magnometers' are not a thing, and magnetometers are generally either superconducting or pretty classical, so i am getting the feeling you are just trolling me to see if you can get a reaction by posting stuff without any consideration for whether it is true or not
Snap already tried this with Spectacles 8 years ago.
Please read my comment more carefully, you're being patronizing. I can't put "I want feature development on this codebase to be faster than two sprints in six years" in the requirements.
Show HN: Laplace Transform Calculator
> is there a simple way to ensure that VS Code extensions do not contact external servers?

Unfortunately, no idea, but it's a good question I'd like to have an answer to
Part of the issue in the complexity battle is competition and levels of expectations from features. Non technical decision makers (and there are lots of them, I’d say most of them) see services from Facebook, Google, etc. and have the same level of feature expectations in their one off small app. They have no clue how much effort exists behind it to maintain what seems simple and now even standard (across large services).

Ultimately they come up with ideas and write feature requirements (indirectly) based around this premise with their shoestring budget and ad hoc team. And we end up in a world with not so well developed applications attempting to create similar features to competitors in budget which leads to a lot of corner cutting and barely working implementations with no thought towards long term maintenance requirements. At least, this has been mostly my experience.

There are of course those out there simply bored with life who want to build unnecessary complexity because they have to be doing something (heaven forbid there be idle time in any work environment either from their own pressure and/or internal organizational pressures) and they start trying to be clever or skill up to some wider marketable skillset (e.g. react).

It’s really business environments that create this sort of complexity requirement from needless feature requests to wide adoption of specific trendy skills in their stack to make hiring easier/cheaper, etc.
Except, any beginner can make a mess with anything. Methodologies and frameworks evolve, but not all create any for beginners.
Oh? So anyone writing applications, PWAs, healthcare software, responsive mobile web apps, or a billion other business domains where the web makes sense as a UI is doing a bad job?

Guess I've been doing a bad job for a long time now.
Oversubcription is the norm for residential customers. And it makes sense in the way that you don’t download at max speed 24/7 content from the internet and you don’t upload either. The usage tends to be: access an article/picture, then read/watch, rinse and repeat. So for those few seconds/minutes you don’t use the internet connection.

When people watch a movie on Prime/Hulu/Netflix, sure, you have constant usage, but 4K streaming is less then 20Mbps…

Most people never use the full amount of even the lowest guaranteed availabke bandwidth per customer.
Wow, you're right about macOS 14, or at least macOS 14.7, but not about macOS 13.

The Mac mini in question has macOS 11 through macOS 15 installed on separate APFS volumes. I just tried booting into 14 and 13.

I'm not sure why I never noticed this before on Sonoma. Perhaps it was added in a later minor update, but I have no idea.

I can't reproduce on Ventura.
Lots of open-source things got adopted without VC backing.

There's a lot more options now, it would be good to have a way to have the best stand out.
I'm really confused by this post. Wouldn't it be simpler to read a few bytes from /dev/random?

Sure, it wouldn't be portable to windows but that's more of a feature than a bug.
Vue is great but it's a personal preference and interpretation for you.

It's not about better or worse for you, maybe for the average person.
> Also is this the same Jeff Johnson of rpm5 "fame"?

No.
When to Do What You Love
How is they just can’t shard the thing? Isn’t each Discord ‘server’ isolated from the others (can’t send a message from one to the other?) Why can’t they address trillions of messages by having thousands of shards that each handle billions?
the examples probably avoid talking about the dynamic APIs because they are super ugly and very stateful. It's hard to say that Web Components are the future when your demo shows 200 lines of manual DOM reconciliation.
The problem with second hand HF rigs is the uncertainty of supply and not knowing what rig is good and what is not.
And even a cheap used rig can be 10 - 30 times the cost of an entry level handheld radio.

And then you buy a power supply for the HF rig for another five baofengs worth.

And realize that the technicians license only allows voice on 10m.
Varlink – IPC to replace D-Bus gradually in systemd
Yes, https://www.gov.uk/service-manual/technology/using-progressi...

“All [UK] government services must follow progressive enhancement, even if part of the service or a parent service needs JavaScript”

But more seriously, it's okay to do a bad job if you're being paid/forced to do it by a for-profit entity. That's what jobs are. Being paid to do things you wouldn't do otherwise (like making a webpage entirely inaccessible to people with screen readers because there's no text in the custom-elements pre-JS execution and not caring because the visually impaired don't contribute significantly to profit). Just don't chose to do a bad job for personal stuff.
Let me tell you about the early 90's when I joked about registering business.com and sex.com instead of actually doing it.
The website doesn't work as intended. All major benefits are on the app
Also odd is the expression 'jobs to be done'. At first glance this seemed like an allusion to this famous 'Jobs to be Done' Clay Christian talk [1] (well worth the 5 minute watch). But AFICT it's just coincidental use of the phrase.

[1] https://www.youtube.com/watch?v=sfGtw2C95Ms&t=28s
"Featured" Chrome Extensions: Not Quite Featured
Testing out smart swim goggles for the Paris Games [video]
What's working in working memory training?
Or signal, receptor, effector

https://en.wikipedia.org/wiki/Cell_signaling
Thank you for acknowledging that your goal is to kill people. Now that that has been acknowledged, we can all ignore whatever else you have to say.
My father bought a TRS-80 Model I in 1978. It was the computer I first connected to a BBS with and learned to program on. I also learned the basics of electronics and how to solder assembling a LNW system expansion for it. My father bought the bare LNW PCB and we scoured local hamfests for the parts. It was always an exciting day when the latest issue of 80 Micro appeared in the mail.

It was replaced for me when I received a C64 for Christmas 1983 and 80 Micro by Compute! Gazette and The Transactor. The TRS-80 was finally relegated to a closet when my father bought an IBM PC XT in 1984.
Online Upgrading Logical and Physical Replication Nodes
In PostgreSQL 17, we have added capabilities to allow online upgrading of logical and physical replication setups.
Pretty cool. I see publish + subscribe example on GitHub but no request/response. Am I missing something?
The VLDB paper mentioned is https://www.vldb.org/pvldb/vol16/p1601-budiu.pdf.

Abstract:

"Incremental view maintenance has been for a long time a central
problem in database theory. Many solutions have been proposed for restricted classes of database languages, such as the relational algebra, or Datalog. These techniques do not naturally generalize to richer languages. In this paper we give a general solution to this problem in 3 steps: (1) we describe a simple but expressive language called DBSP for describing computations over data
streams; (2) we give a general algorithm for solving the incremental view maintenance problem for arbitrary DBSP programs, and
(3) we show how to model many rich database query languages
(including the full relational queries, grouping and aggregation,
monotonic and non-monotonic recursion, and streaming aggregation) using DBSP. As a consequence, we obtain efficient incremental view maintenance techniques for all these rich languages."
Jobs to Be Done – Clay Christensen (2016) [video]
I wonder how the pitch meeting went for this at protestor headquarters:

Pitcher: We need the public engaged so that we can change policy to help mitigate climate change. So I suggest we vandalize beloved historical works of art. This will prove to the general public not only the value of our cause, but also enamor them to us. They will see that, by vandalizing art pieces, we are the most sensible and trustworthy to lead the way.

Protestor: I get it, so we vandalize art owned by the wealthy oil oligarchs hidden away in their giant mansions to highlight the disparities between them and those that actually have to suffer the consequences of climate change.

Pitcher: Nope. We go after the ones in open art galleries routinely viewed and appreciated by huge swaths of the general public. Also, we're going to use soup.
i usually start projects with postgres this days. i have reached the tens of millions of rows threshold without breaking a sweat, but is there any good reason postgres can't handle into the billions or trillions? any well known products at that scale that are known to use postgres?
It’s definitely not common parlance in Scotland to say “north east” when talking about the UK and mean England, but I can’t speak for NI or Wales.

A UK website making international articles should at least use “North East of England”, or perhaps “North East (England)” to comply with the official ONS ITL name as someone else pointed out. Even UK wide articles should do this.
They are framework-agnostic, meaning you're not locked into Vue, React, Angular, or any specific framework. They work natively in the browser, which makes them reusable everywhere, now and in the future.
Isn't this already part of F?
Customers don't want to buy the last one.
Because you didn't create it yet.
I‘ve come to the same conclusion while using them pretty extensively. The idea is nice, but they are not there yet.
Well um

1) You dont have to load an external library

2) Shadow DOM

3) Dynamic slots

That’s about it, honestly LOL.

I guess the main point of most browser APIs was to let apps use browser features.

This one actually tried to make a standard way for apps to use other apps. But they already had their own libraries so nyeh, thank you very much! LOL
That solution is never going to work when black swan events occur on the order of every 5-10 years and executive vision is focused on the next quarter with little concern paid to anything outside the next 2-3 years. Nobody is going to want to give up short term performance to mitigate risks that probably won't manifest until after they've left for a better job.
i couldn't resist reproducing on bare metal linux (8th gen core i5, ubuntu 22.04):

cargo run --release -- -n 1000000 --method unixstream
cargo run --release -- -n 1000000 --method tcp

~9μs/op for unixstream, ~14μs/op for TCP.

unixstream utilizes two cores at ~78% each core, tcp only utilizes ~58% of each core. so there is also something wrong in the benchmarks where blocking is happening and cores are not being fully utilized.
You can judge React, but like I said, not frontend. You're responding to an argument I didn't make.
Most of tech at my home is from Apple. My gf uses Apple exclusively.

I have seething hatred for Apple simps and blind fanatics that think their Cupertino dictator can’t do wrong. They’re just an extremely rich company that produces quality products - nothing more.
Template functions are a better approach, IMO.

[1] https://templ.guide/
Sorry, I edited my post and took that out for being too detailed.

> If you really need that, can't you just register it as "my-thing-1" and then register the other one as "my-thing-2"?

Yes you can, but it means you gotta search-replace something, whereas in every modern programming language you just do an import or an alias or something like that.

And you still can't solve hot-reloading a web component that way.
Ah. It appears that it is not possible to enable “Remote Desktop” on a remotely installed Ubuntu — you have to use the desktop Settings app locally.

This of course is impossible if you don’t have a display attached (a headless install). Or if you have remote access but forgot to enable it before it was deployed somewhere inaccessible…
How to Disable a Nuclear Warhead in Midflight
Pretty good release it seems if internet complains about stuff like this.
React is irrelevant for me and my users. This is not an argument in favor of web components over Svelte. Adopting web components would mean an objectively worse UX for my users - for example requiring them to enable JS.

You won't get a Svelte to look past the flaws of web components by saying "React is bad".
I bet that every "top" performing GenAI has dozens upon dozens of "if" statements to make them seem smart.
From https://news.ycombinator.com/item?id=40131766 re: LLM minifigs and parametric CAD parts libraries:

> Is there a blenderGPT-like tool trained on build123d Python models?

> ai-game-development tools lists a few CAD LLM apps like blenderGPT and blender-GPT: https://github.com/Yuan-ManX/ai-game-development-tools#3d-mo...
The Certification Industrial Complex
A lot of the tricks used on 193 immersion tools for lithography scaling requires sophisticated deposition and etch processes which are not available on old 6 inch tools. Given that this factory was used for faceID parts, I suspect it was making VCSELs or other optoelectronics. These components don’t require fine lithography so it’s probably a 0.35 um capable fab.
I know it's easy to say from the outside, but a project is under no obligation to accept a sketchy sponsor. If someone offered money to post a link to something obviously illegal, it would be illegal to accept that deal. If they offer money to post a link to something dubiously legal, it is likewise dubious to accept that deal.

That they're starving open source developers doesn't remove the obligation to vet their sponsors before posting their links.
JVM is a hard dealbreaker for a scripting/glue language.
Edible toothpaste-based transistor could be the future of smart pills
Unless you're building an app that holds data locally, for most web apps, you should be pushing state down into the backend. Fat models should be your single source of truth, skinny controllers, and service functions in order to separate data from code for testability.

Avoid caching as much as possible until you absolutely need to. As soon as you introduce caching you now have multiple sources of truth instead of one.
Which office was Hunter Biden running for last cycle?
> It appears that the choice is to either annoy people because they really do want to turn off Bluetooth or to let some people shoot themselves in the foot.

False dichotomy. They could provide a warning with a "Do not ask me again" checkbox. That would be acceptable.

Also, there was no possibility of footgunning in this case, because there were no active devices or services requiring Bluetooth.
I tried to understand the referenced article "Web Components Are Not the Future" - but found that there weren't many convincing arguments.

The current state of Front-end frameworks is an absolute mess. Speaking for myself, I don't want to learn a complex framework. I don't want to learn magic that I don't understand without reading the documentation (useState, createSignal et al). Magic in frameworks is often a hack, unlike magic in libraries. The first library I used was Prototype. It felt like magic, and it truly was. And so was jQuery, and Backbone. I never had to guess what "useState" does behind the scenes.

There are many things which don't carry over into Web Components from current JS frameworks. But if you start from Web Components (ignoring everything you know about frameworks), it suddenly becomes intuitive. And it brings in abilities which are missing otherwise, such as isolation via Shadow DOM. It grows on you.

In my view the only thing we should retain from the React era is JSX (for many reasons, true type-safety, autocomplete etc). I wrote a library last week for using Web Components with JSX. No magic other than JSX. https://webjsx.org
this isn't quite true. you can't be compelled in a civil case to provide evidence of you committing a crime. it's just that doing so will be really bad in the civil case since it allows the court to draw an "adverse inference" that whatever you aren't disclosing probably really sucks for your case.
I'm not sure that is a bad first radio. When I got my Technician license, repeaters were more or less what were available to me anyway. I got a hand-held and non-hand-held but ended up using the hand-held more often as it was always with me.

People get into ham radio for different reasons — not always for technical reasons. And then people's interest in a hobby can change over time as well — perhaps they begin to get long-distance curious.
I use macrium backup.