skysight-inc/HackerNews huggingface dataset:
> I live in a city apartment and simply don't have the space for the required antennas

I used to load the gutters around my apartment as an antenna, I once even loaded up the box spring in the bedroom, then I got a MFJ isoloop also back in my apartment days. There are ways to get on HF. They might not be ideal, but when you do make that contact it sure is sweet.
cities do because they exist in a system that generate carbon, but they are vastly more resource & carbon efficient than suburbs per person

https://usa.streetsblog.org/2015/03/05/sprawl-costs-the-publ...

https://news.berkeley.edu/2014/01/06/suburban-sprawl-cancels...
Naively I would expect studies like this to be particularly sensitive to cognitive changes in young adulthood, but the authors did not adequately discuss the limitations of using undergraduates - I understand there are supply-side reasons for this, but it should have been addressed in the discussion. These students have not experienced much life outside of school, and their prefrontal cortices aren't even mature yet, so there are environmental and biological reasons to suppose undergraduates aren't representative of the general population. (This is true for any study but I think it's especially salient for metacognition and psychological confidence. Youths are notoriously overconfident.)

It would be interesting to see this experiment repeated with different age groups, and fascinating to see a long-term study that keeps track of individuals. This study is a bit old, I wonder if there were any follow-ups.
He should just have called it microservices instead of objects.
Some devices report as keyboards in macOS but are not. My Logitech mouse for whatever reason shows as both. I’m assuming it’s the way Logi handles the extra buttons.
Why aren't web components there/more popular yet? They seem like a fantastic solution
Clear as mud. No matter how good Alan Kay is, he failed to properly describe messaging, as used in an Actor environment. He missed the Actor Programming model. Also the late Carl Hewitt failed to properly explain and implement a working Actor model. A shame, since there are many working Actor implementations in many languages.
Many of us aren't even doing things above (or below) ground on Earth.
Considering both recent US vehicle losses have been on re-entry, I feel NASA is vindicated on being ultra-conservative around that stage.

So anomalies that might be acceptable during ascent would be unacceptable during decent.

Personally? I'm glad Boeing launched.

I wish they were perfect technically, but I also realize that an infinite amount of time and money doesn't protect against unknown-unknowns.

IMHO, they should be operating more like SpaceX (and the earlier days of the US space program) -- using calculated risk and engineering to decide when it's reasonable to do an inherently risky thing, when doing so is needed to move the entire program forward.
How is increased FCP, LCP, ttvc better ux and DX? We've had hard data that decreasing page load time make for better user experience[0].

Please don't make this an Us vs. Them thing.

[0]: http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20....
But logs are stored on IRC as well. It’s not a part of standard protocol, but a lot of ir c-servers can do that automatically and there are boys which do that not to mention personal archives.
The difference is that end-users don’t have easy access to this logs. And on discord they do (because it is a part of protocol)
> ‘So what’, you say. ‘I’ve put the public domain notice on my work. I’m
promising I’m not going to threaten or sue anyone for using my work.
Shouldn’t that be enough?’

> Unfortunately, you are not the only person who will exercise control
over your intellectual property. At some point, you will die, and the
control will pass into the hands of your heirs and successors. (One of
the absurdities of the 70 years p.m.a. copyright term is that every
copyrightable work created by an adult will almost invariably be
controlled by others after their death for longer than it was
controlled by them personally while they were alive.)

My response to this is still Why should I care, I'll be dead.

I feel I should point out to the author, that you can put any license you like on it - after you're dead you have no control what the law does and doesn't care about and you won't be able to update the license accordingly.

Some people in copyright law seem to fail to grasp that you can't protect anything for definite once you're dead.
I think their point is that they already effectively lost the trademark—they only had it on paper. That paper was enough to scare a lot of people into paying, but now even those who were cowed into paying a license fee in the past are free to stop.

Letting one more usage slide would not make "Super Heroes" more generic.
> [...] since Discord is also very not E2EE.

I have stated that at the end of my original comment. I'm not advocating for Discord (merely enumerating IRC's and XMPP's shortcomings), but I would like to point out once again, that post-2013 any solution that does not enable strong E2EE by default should not be advocated for - at all.

> That said, XMPP my preferred protocol that checks all of the boxes.

Read up soatok's breakdown on the design & status of OMEMO. I'm not a cryptographer, but I do trust a cryptographer when they say some protocol's design/crypto is broken.
To be fair, here is the RFC meaning:

SHOULD This word, or the adjective "RECOMMENDED", mean that there
may exist valid reasons in particular circumstances to ignore a
particular item, but the full implications must be understood and
carefully weighed before choosing a different course.

It means you can’t simply ignore it, and instead have to have compelling reasons to justify any deviation.
SpaceX being the most competent at their game doesn’t change the fact that Musk’s plans are pure fantasy. My bet is that won’t see any people going to Mars during his lifetime.
https://archive.is/KwQzM
> I can't win this battle

You are fighting the wrong battle. You harp on the technology used rather than the specific functionality you desire.

The bad way to do it: "You made a single page app with PHP and {other tech} and {database}! I hate those! Don't you read (reddit, twitter, hacker news)? Best practices say..."

The good way to do it: "Our users often share links within the application with each other to navigate and the new single page app you demoed doesn't allow that."

Or: "While the page load times look great on the metrics in your power point, as everything is lazy loaded it takes 10 seconds for the page to actual become usable, the old site loaded in under a second why are we regressing the user experience here?"

Or the evergreen: "What does that buy us?"
His main thesis is that very high performance (which he defines as efficacy towards a known goal plus efficiency) and very high robustness (the ability to withstand large fluctuations in the system) are physically incompatible.

…what about humans? We’re far more efficacious than any other animal, and far more capable of behavioral adaptation.

Plus, isn’t “physically impossible” a computer science argument, not a biological one? Unless we’re using the OG “physis”==“nature”, I guess
New electric field around earth discovered
From the same author that did flutter_rust_bridge :)
https://github.com/fzyzcjy/flutter_rust_bridge

Really nice work!
Everything doesn't have to be for everyone, and that doesn't make it bad.
When you have extremely limited supplies, are as isolated from humanity as possible, and there are only 2 vehicles capable of transporting you, and one of them is reigniting a cold war with you, you are considered imperiled. I'm sorry. If dragon did not exist, the rescue mission would still be embroiled in diplomacy and not in orbit already.

You only get the luxury of your non-rescue position due to hindsight.
Hey, you are thinking about wordllama. We explicitly compare to wordllama in the results. Feel free to check it out.

Your point about BM25 is very interesting. We can run some comparisons! Thanks
I'm bullish on web components as a distribution mechanism. In fact, we're currently hard at work betting our entire company (https://talkjs.com - a component library + API for chat) on it.

I agree with Nolan here that the performance is fine. People keep comparing web components to React or Solid components, but the latter inherently have a tiny granularity whereas web components is primarily a way to distribute reuseable elements, not an application framework on its own. Don't make every tiny piece of your app its own little web component (or, at least, don't do it without a framework such as Lit to skip the pain). But web components are the way to build a component once and have it usable in all web frameworks (including none at all) out of the box. That's fantastic! And also unprecedented (on the web, that is).

It bothers me that so much of the discussion is still about whether web components are good primitives to build frameworks on top of. No, not really, they're pretty awful for that! But for distribution, nothing else comes close.

I'd love it for some alternative standard to emerge, without all the awful design choices of web components. And I agree with Rich (Svelte) and Ryan (Solid) that WCs being built into browsers are getting in the way of some other collective component interop design emerging. But until the framework authors stick their heads together and invent a fast, modular, non-shitty, property-only, functional-smelling standard for distributing components, I'm sticking with web components. For component authors, the only alternative is making a React version, a Preact version, a Lit version, a Svelte version, a Vue version, an Angular version, a Solid version and a vanilla JS version of the same UI component. That's awful! Web components are clunky but they're here, now!
> a low-yield device over the Black Sea or the North Sea

How is it different? What "panic reactions"? What "panic reaction" can connect a low-yield explosion over Black Sea and a suicidal strategic strike on the continental US?

> I'm just advocating that we observe the cautionary principle here

"The cautionary principle" is only applicable if you disregard hundreds of thousands of killed and maimed Ukrainians, millions of refugees, unknown number of abducted children, and entire cities raised to the ground. Letting a genocide continue for years is not a default safe option.

Again, I invite you to reflect on this exchange: you'd "rather not delve into scenarios", but when weighing what's basically just vibes against very material, prolonged, ongoing suffering of the second largest country in Europe you decide to advocate for vibes. Putin's bullshit has already won and his deterrence succeeded, because you give it enough credibility (whilst refusing to outline a credible scenario) to talk about "WW3" as a real risk worth more than dead and maimed Ukrainians.
Our frontend is a bunch of barely working wonky react-soup, and we really need to rewrite it. It's mostly a "tables and forms"-type frontend with a lot of complexity in the backend: it's a great use case for htmx (or even vanilla/jQuery).

But I'm not really sure how we're going to handle that or who we'll hire for it, because I fear we'll end up with another react-soup. My current strategy is to make a MVP in my spare time to show it can be done and that it'll be quite nice.
And also screw up the browsers back functionality in the process
Gift link: https://wapo.st/47NMdUD
Amadeus, released 40 years ago this month, 'an unmistakable stab at the USSR'
In the frontend dev land, there is a constant tension between user experience(UX) and developer experience(DX).

Providing good UX with HTML/CSS/Progressive enhancement usually means less-than-ideal DX. And good DX with JS frameworks tends to end up with less-than-ideal UX.

Poor DX usually results in slower development, thus devs are usually incentivized to prefer DX over UX.

The holy grail of good UX/DX requires exceptional developers whatever path you choose.
Serialization Is the Secret
Rust could probably generate the HTML.
User hostile? It’s a warning so people don’t get locked out if they don’t have a wired keyboard. Disabling WiFi doesn’t keep someone from using a computer.
While it’s true that messages are read more, reading can be cached so not every read necessarily results in a DB call.
you're using applianceOS, power users are not the target market, people with too much money are
It's slightly more nuanced than that, in that starliner didn't actually break down. It had some issues which presented increased risk for the astronauts, but it was still operational. If there was a true emergency on ISS, they would've gone on starliner. But because there was no danger of them staying longer till the next ride, they opted out of using starliner given the increased risk.
If anything, there should be more space for this topic in our collective consciousness.
The problem is that you can only subsidize a for-profit entity (including non-profits that act as such) by simultaneously controlling prices (or scaling supply supra-demand).

Anything else, including any personal contribution, and the prices just raise to include the subsidy.

Which is exactly what you'd expect a market rate to do!

* The sole exception seems to be if the subsidies are targeted and few enough in number so as to not influence the broader market rate, but then you're not helping as many people.
If Malta choses to give a ship a flag, they should bear some level of consequence for that action.
I think this minimizes the fact that interop - the main selling point to me as a user - comes at a performance cost where every component you use could have its own unnecessary runtime attached.[1] Using a framework like Lit with web components is the recommended way to use them.

This cost will compound over time where new frameworks emerge, and components get stuck on older versions of their frameworks.

I can't see this as anything but significant, and not to be minimized. Having multiple redundant libraries on a page is not the direction I would advise anyone to take, particularly not when baked into the accepted best practices. This bodes poorly in the long term.

I've listened to the arguments from web component advocates in blog posts, social media, and videos for years now, and I should be in the target market. But on top of the interop tax, they're full of negatives that aren't present in the mainstream frameworks.

Interop works great within each framework's ecosystem. The same dynamics that cause developers to seek interop cause them to huddle around a small number of mainstream frameworks. So we get a few vibrant ecosystems that push the state of the art together. Web components cannot keep up on the tech side of things, and introduce a ton of complexity to the web platform - ignorable to me as a dev, but not for browser implementers - in service of their early 2010s designs.

[1] https://x.com/Rich_Harris/status/1840116730716119356
I'm aghast at the comments in that thread. They are truly asleep at the wheel.

No wonder the front end is such a disaster with those mindsets running the show.
Personally I'd always want "today", never "tomorrow".

So now we have two extra buttons on the form.

And perhaps the extensive user testing that gov.uk do would discover that for most people this added UI complexity makes the form less usable than keeping it as simple as possible.
There doesn't seem to be any single food that is alone nutritionally complete, but potatoes are certainly one of the closest... many people seem to do well with just potatoes for a month or two. A few supplements (B12, etc.) would likely allow potatoes to work long term.
Very mid compared to Visual Studio in my experience. You don't even get a modules window, and there's a whole litany of core C++ debugging features missing.
In reality, no one will believe anything Microsoft says about Recall. All I know is this is yet another reason to avoid Windows no matter what.

The only way to make people believe Recall is not a privacy nightmare is to fully release the full source of Windows for examination by the Free Software Community. Anything short of that will be branded as "marketing speak" or even lies.

>Weston argues that this design protects against malware and unauthorized access through rate-limiting

What about "authorized access", who defines that. If Microsoft, there in lies the problem.
Why should it be on that list? When does a webpage work on macOS and Windows but not Linux?
US' largest solar panel maker First Solar debuts its $1B 3.5GW Alabama factory
> First Solar (Nasdaq: FSLR) inaugurated its new $1.1 billion fully vertically integrated thin-film solar factory in Lawrence County, Alabama. The factory adds 3.5 gigawatts (GW) of fully vertically integrated nameplate solar manufacturing capacity to the US, and it’s expected to create over 800 jobs.

> First Solar’s unique selling point is that it’s a fully vertically integrated manufacturer of thin-film PV solar panels. This means they can turn a sheet of glass into a functional solar panel in about four hours, relying heavily on US-sourced materials like glass and steel, the latter of which is being sourced within a 25-mile radius of the new factory.

> The Lawrence County factory, along with First Solar’s three operating factories in Ohio, brings the company’s domestic nameplate manufacturing capacity to almost 11 GW and its global capacity to over 21 GW, once fully online.

> First Solar is also constructing a $1.1 billion, 3.5 GW factory in Louisiana, which is expected to be commissioned in the second half of 2025. The company expects to have over 14 GW of annual nameplate capacity in the US and 25 GW globally by the end of 2026.
Safari is the only browser without the full support

*Supports "Autonomous custom elements" but not "Customized built-in elements"
Seems weak, ineffective, theatrical and unnecessary.
Separate from everything else, I'm glad the first crewed launch from SLC-40 went smoothly. Being able to use that pad for Crew Dragon launches provides some helpful flexibility for important Falcon Heavy launches at LC-39A.
> My problem with Just Stop Oil is all their activism is just targeting people that have nothing to do with oil

They regularly blockade oil facilities and corporate office of oil companies.. except that does not make the news.
It all depends on the state the phone was in when the shooter was killed. I had a look at the Cellebrite documentation at https://cellebrite.com/fr/services-avances/ - this in French and the interesting part for Samsung reads Extraction complète du système de fichiers Android (Samsung Galaxy S10, Note 10 et toutes les Séries A (2019) (Full Android File System Extraction (Samsung Galaxy S10, Note 10 and all A Series (2019))

Such software relies on vulnerabilities that are fixed once they are found, and therefore they offer bounties of ~1M€ for a RCE without user interaction instead of going to the vendor (who will offer, best case, 10x less)
I do think there is a balance to be struck, because directed communication means the recipients of old messages are also stakeholders, such that maintaining a consistent record by default is a fundamental part of the "service" they offer. The message contents are different from e.g. secretly hoovering up click patterns. Matrix had some thoughts when they faced the same questions:

The key question boils down to whether Matrix should be considered more like email (where people would be horrified if senders could erase their messages from your mail spool), or should it be considered more like Facebook (where people would be horrified if their posts were visible anywhere after they avail themselves of their right to erasure).

Solving this requires making a judgement call, which we've approached from two directions: firstly, considering what the spirit of the GDPR is actually trying to achieve…

https://matrix.org/blog/2018/05/08/gdpr-compliance-in-matrix...
This is fairly basic advice, and it feels a bit insulting to assume I'm just hating on some tech. Obviously, if things were as easy as "here's the immediate and unambiguous problem with this approach", I would have gone that way.

Things would be great if the risks were as simple as this. The actual problem is "six years later, the frontend is a ball of spaghetti code and it takes you two sprints to change a component".

How many developers do you think heed those warnings?
That's one dream. There are advantages to thick clients as well... less network traffic if the device can do processing on site, A much easier to maintain and update distribution model over the traditional desktop experience for what is essentially application software, etc.
Awesome, yeah those are pretty nice technologies. Definitely let me know if you do / encounter any issues!
While this is true I think the multiple libraries problem is a rounding error when you look at the majority of web apps created today. React and react-dom combined are over 100KB. Svelte and Lit are in the single digits. So you could embed a lot of frameworks before you get close to the bloat people use every single day without even thinking about it.
I agree with what you're saying.

I hired a single Atlassian consultant, and after taking the time to understand things, he delivered something that shut my opinion up about JIRA.

Like you are implying, every company can be different, and tools like JIRA have many ways to get the same thing done.

Still, since JIRA self-hosted version has gone away, there is opportunity for something new to cover it's feature-set in a new way.
I’m on the other side of the international date line, you insensitive clod.
incoherant babbling
But dragon does exist. This is like saying you’re stranded when you’re car camping in the woods.
The main part is to avoid holding state in two places (frontend and backend) if you can do with holding state in only one (either frontend or backend).
Low level in the sense that it doesn't have things you would traditionally need to build an application, such as re-usable components, conditional rendering, etc. To do that you have to wire it up with something else such as your backends templating system, alpine, etc.
Because we also have hard data that users absolutely hate a blank or frozen screen and "CONFIRM FORM RESUBMISSION." Users are allowed to hate multiple things at the same time and it's up to the web developers to stack rank those.