skysight-inc/HackerNews huggingface dataset:
Commenters seem to be analyzing this as though it were a steady-state phenomenon. But it isn't. The article clearly states that this is a result of increased costs along the supply chain that appeared due to disruption during the COVID pandemic.
Will try it and might add it too, I find those annoying. Thanks!
Knockout is fine to use if your JS doesn't exceed 1000 lines or so. After that, in more complex apps, 2 way data binding becomes an absolute mess of side effects.
> I predict llm based agents will be used as a 3rd party layer on top of the modern web to work in users favor against enshitification.

I'm predicting the opposite -- LLMs will be used to turn Dark Patterns into Vantablack Patterns.
What evidence makes you believe this is happening?
>Another almost worst thing is having production environments with significantly different stacks to what you are using locally,

Everyone has a test environment, some people also have a seperate production environment :D

Database/datasize issues typically are the worst here. Dev/UAT environments are typically considered a cost center and you'll commonly see them with some small amount of ram and compute resources. Which is fine when you're testing 'small data'. But if you have enterprise style clients that have hundreds of gigs/terabytes of data, your dev environment behavior is generally going to be very different.

Ran into a case where an enterprise client ran massive db performance problems. We found an unindexed table scan that was killing performance. When doing a post mortem on it, it turns out that 95% of our customers only had around 5 entries in the table. No reason to add an index to that. But this customer had found a neat and interesting workflow that had added thousands of entries to that table.
Please share them to see if I can improve mine :)
Congrats on the launch!

Looking forward to seeing more people trying out this architecture.

Still hoping we can find some time to collaborate on reactivity, tree-sql, typed-sql or some such other effort in the near future.
Student invents electric motor to convert petrol and diesel cars into hybrids
So You Want to Start a Bank?
If you ever want to start a bank, you have two options:

1. Build one from scratch
2. Buy an existing charter

For both options, you will need a robust business plan, an all-star team, a ton of capital, and most importantly - a ton of patience. I write more about how to do it here:

https://easilyamused.beehiiv.com/p/want-start-bank
> It is only scale at this point.

I see, this is basically the "AI of the gaps" argument. :P

It is NOT "only scale" at this point. But at the current rate, you will see this soon enough (I just happen to see it already). We'll have some very intelligent-seeming, very useful, but relatively uncreative zombies missing a "spark" (or any willpower, or any real source of what is valuable to them, or any sense of what is aesthetically pleasing or preferable or enjoyable or beautiful, or any consciousness for that matter). It will allow us to redefine what it means to be human. But our distinct human-ness will stand out even more at that point.
Yes, Vue and Solid — like Knockout — use a dependency tracking mechanism. Back in the day it was called `ko.observable`, nowadays we call them signals.

That's the part Knockout was right about. It's absolutely true that you can mishandle them and create a spaghetti mess, _if your design allows it_. Svelte 5 doesn't — it uses signals as an implementation detail, but in a way that prevents the sorts of headaches you're describing.

Signals and observables (e.g. RxJS) are related but separate concepts. The framework world is converging on signals as the appropriate mechanism for conveying reactivity — even Angular (which has historically been most closely tied to RxJS) is moving in this direction. I promise you it's not just a mass delusion.
I think this somewhat inevitable given the flexibility of javascript. The lack of convergence on one single paradigm as a long-lasting set of best practices speaks to all of things that a web framework needs to have in order to accommodate all developers.

In Svelte's case, it feels like they went as far as they could without directly addressing observables until they reached a point where it became one of the largest features that had yet to be addressed.

Open source frameworks, not unlike companies, need to continue attracting new users to grow the ecosystem, which means pleasing an ever-growing user base.
General Availability of GitHub Advanced Security for Azure DevOps
You need to break apart the basil and distribute it evenly in a larger pot. Supermarket basil has fertilizer that makes them grow super fast and look good on the shelves, but what you're buying is actually a bunch of little plants that will exhaust the nutrients unless they're broken up.
> It does give more space in the sense that the model generates more tokens of steps/etc that it can then base its actual answer on,

It doesn't give more space in the sense of increasing the upper bound on space used; it may bias the space used higher than a single naive prompt aiming to respond to the same question, but it doesn't alter the constraints.
How to send emails using Bun
One day my MooTools skills will be cutting edge again, i'm positive.
We Are Not Sustainable
Scientists Working in Antarctica Unwittingly Started to Develop a New Accent
If we want to reduce produce waste, then we should be buying more of our produce frozen rather than fresh.
Sure—but you aren't comparing to other ways of indexing sites.
I am an inspector at a globally significant bank, what should I ask
Imagine you had the ability to ask a bank any question youd like, request any member of staff to walk you through any process, what kind of questions would you raise?

I am an inspector at a globally significant bank. We are investigating their IT landscape and their ability to accurately aggregate their data.

What parts of the IT landscape, systems, infrastructure would you be most interested in?
Angular right?
Now if only we had an analogous borrow checker in Vue and Svelte so that we don't hang ourselves with 2-way binding. That might a good research project, actually.
What about long arrays? Is there a mechanism where Svelte knows which element is mutated, and do fine-grained recomputation/update only the corresponding view elements?

This is the primary place where we have to go outside the framework in React. Only a large linear list has this problem -- if it was a decently balanced component tree, then we could skip updating huge swathes of it by skipping at a top level node. But it is not possible in an array. You have it iterate through each element and do a shallow comparison to see if the references have changed.

That said, it is fairly easy to escape to DOM from inside a React component with useRef and the portal pattern. Then we can write vanilla JS which makes updates to only the values it changes.

If Svelte solves this in an elegant manner, then it would be a very compelling feature over React. I'm asking here because last I checked, most of the examples in Svelte's documentation pointed to simple counters and regular objects, and I couldn't find an example of a large linear list.
My pet theory as to why pinball has gotten so popular in the Northwest is because it's a way to pay a few quarters to temporarily avoid interacting with other people. A win-win for introverts and bar owners!
The concept of a fixed-wing VTOL UAS is well-tested, though. They’re not as simple as a quad or a “native” fixed-wing, but well within reach of a motivated hobbyist.
Guardian article:

> https://amp.theguardian.com/environment/2023/sep/19/do-carbo...

First line is a bit of a fudge:

> The vast majority of the environmental projects most frequently used to offset greenhouse gas emissions appear to have fundamental failings suggesting they cannot be relied upon to cut planet-heating emissions, according to a new analysis.

Starts strong with "vast majority" but gets woolier from there. Does "cannot be relied upon" mean they'll only work 1 time in 100 or 10 or 2? And we are only "suggesting" that conclusion?

And do I have dejavue or did they run this same story about 6 months ago? I definitely remember debate about the definition of "junk" status.
Indeed, why doesn't Vanguard or State Street Corporation control the world? I think there's a lot of little things that hurts the credibility of his overall story. The usage of "scamdemic" is another one - which if you dig into what he means by it, his reasoning is no better than that junk RFK is pumping out. There's even a dig at Bill Gates over the pandemic!

It's a great read, but best viewed through the lens of "All models are wrong; some are useful".
Yeah but SQLite doesn't protect against unlimited CPU use and has historically had issues where "malicious queries" cause crashes -- not OK for a browser to surface to scripts.

https://www.sqlite.org/cves.html

> Almost all CVEs written against SQLite require the ability to inject and run arbitrary SQL.

> The advertised consequence of most CVEs is "denial of service", typically by causing a crash through a NULL pointer dereference or a division by zero, or similar.

> But if an attacker can already run arbitrary SQL, they do not need a bug to cause a denial of service. There are plenty of perfectly legal and valid SQL statements that will consume unlimited CPU, memory, and disk I/O in order to create a denial-of-service without requiring help from bugs.

> Hence, the mere fact that an attacker has a way to inject and run arbitrary SQL is in and of itself a denial-of-service attack. That the arbitrary SQL might also tickle a bug in SQLite and cause a crash is not a new vulnerability.
Ford has been known to send corp engineers to dealerships to help diagnose and resolve recurring issues in specific vehicles (has happened to a coworker of mine, and the engineer did end up fixing the issue!) -- I wouldn't entirely doubt.
Many types of memory leaks are simply because you're holding on to data you don't need to hold onto anymore. Languages cannot prevent this, at least not that I've seen.
If the company didn't want their email to come across as 'Ominous' they should have replied 'no comment ;p' /s
What explains the huge difference in perf with the approach from 2019 mentioned at the end?

For image classification, couldn't one use the residual from applying a jpeg codebook learned on a training example as metric?
Yep! https://svelte-5-preview.vercel.app/docs/fine-grained-reacti...
Even if that's their motivation, doing that is still a terrible practice at least in the way they're doing it. It's certainly one of the big reasons why I won't buy these devices.
Reminds me of https://this-museum-is-not-obsolete.com/ - which is more about using old technology (art rather than preservation, but also more of an emphasis on being able to see the step-by-step relays operate while you're dialing.)
I’d agree with you about HTTPS providing most of the benefit that VPN advertising focuses on if I hadn’t seen repeated direct evidence that even most technical users will blithely click through HTTPS errors’ “accept the risk” bypass. It’s as if knowledgeable users think “sure, this could be a man in the middle attack, but it’s most likely just a benign cert problem, because certs are hard.” Sigh.
A silly corner of the spec, considering that this is a spec that specifies exactly how to handle e.g. misnested elements and admits plenty of other things that read intuitively as standardized sloppiness.
If that's your idea of fun you need to get out (more).
I applaud these researchers, but I have to admit this quote made my blood boil:

>> "I can only do this because I'm a cancer researcher and clinician and so inherently understand the risks," he said.

As a cancer survivor, and someone who lost a loved one to glioblastoma, I despise this mindset. The idea that us "common folk" aren't intelligent or educated enough to make the decision to join risky trials is maddening.

I fully understand and support this mindset when it's regarding minor diseases. But if someone has 6-9 months to live, and zero chance of survival, I think they have every right to choose to be used as guinea pigs.

I know my relative would have LEAPED at this sort of opportunity. She was given 6-10 months, and was dead by 4.

At the time, there was an on-going trial she was rejected for, because she had a minor preexisting condition, and thus is it was "too risky." I remember her saying that she would rather die in 2 weeks and help push science forward, then helplessly linger for a couple more months.

I am hopeful that the rapid development of the COVID vaccine may have flipped a switch in biotech, and may lead to more risky and experimental trials for truly deadly diseases, such as glioblastoma.

If not, I will continue to look to China for hopeful developments. They seem to have more relaxed barriers for trials, and I firmly believe this is one of the reasons their biotech industry is exploding at such a rapid pace.
There are refuseniks like me who will never buy into Apple's (or Meta's or Microsoft's) ecosystems for reasons of privacy and control. I'm F/OSS only. In some areas, that leads me to do without. Having options like SimulaVR is very exciting even if the value proposition is arguably less strong.

Whether their potential customer base is large enough for success is a question I have, too.

My fear is that they'll want to make the system as like commercial offerings as possible, which will actually make it less appealing for nerds like me.
As a recent adopter of Svelte, these changes are intriguing but I don't really have a grasp of how I feel about it quite yet.

One thing that I am definitely happy to see is the removal of $: as it should help Typescript users. Personally, I was quite sick of writing:

let input = 'Hello';
// ...
let loudInput: string;
$: loudInput = `${input)!`;

Instead of:

let input = 'Hello';
// ...
$: loudInput: string = `${input)!`;

It's an incredibly minor thing, but when you do it 1000 times it becomes very frustrating. Having reactivity be rune-based should help TS avoid the syntactic confusion, bringing us to:

let input = $state('hello');
// ...
let loudInput: string = `${input)!`;
Here are the rules I’ve been using for Stack Exchange; you can see that I have been doing this for a while. Some of these may no longer even be necessary…

! 5/8/2018, 9:16:29 AM https://emacs.stackexchange.com/questions/13080/reloading-directory-local-variables
emacs.stackexchange.com###overlay-header
! 3/31/2020 https://emacs.stackexchange.com
emacs.stackexchange.com###divQuestionFollowFeaturePopover
! 2021-04-14 https://emacs.stackexchange.com
emacs.stackexchange.com##.js-teams-promo
! 2021-08-14 https://emacs.stackexchange.com
emacs.stackexchange.com###hot-network-questions
! emacs.stackexchange.com###sidebar
! 2021-10-01 https://emacs.stackexchange.com
emacs.stackexchange.com##.js-create-team-cta
! 2022-09-18 https://emacs.stackexchange.com
emacs.stackexchange.com##.s-sidebarwidget:not(.js-review-actions)
emacs.stackexchange.com##.js-feed-link
! 2022-12-18 https://emacs.stackexchange.com
emacs.stackexchange.com##.icon-winterbash
! 2023-07-28 https://emacs.stackexchange.com
emacs.stackexchange.com##.js-announcement-banner
Because sometimes someone (a partner, a friend, etc.) is driving for you.

Yes, you could take a taxi, but that can easily cost more than parking, even when parking is as expensive as in London.
Ah. I misunderstood the function of PREP/assumed it was the treatment given to people who are already infected. I don't know why, because I feel like I've heard about PREP before.

That does kind of muddy the waters a bit. I think it's better for everyone to have more treatment options, in this case, and a vaccine is certainly better, but ... deciding who has to take the hit in the risk department to develop one is odd.

It still feels like it should be ethically possible. Logically, we don't want to pigeonhole ourselves into something of a "local minimum" when it comes to a viable solution to a problem, IE a situation where we have something that kind looks better than the surrounding avenues of research and the energy investment needed to find a lower-risk, higher-reward outcome is too high to be worth bothering.
I guess the obvious next step is to cull the dead neurons from the model data? I imagine the brain does the same thing after the childhood years
If you like this, I recommend you also look into SolidJS, which is basically this idea with less compiler magic and fewer dollar signs (and more JSX).

It also comes with a built-in model layer called Stores which is genius in its simplicity. In React land I’ve used Flux, Redux, MobX, mobx-state-tree, zustand and pullstate, and IMO Solid Stores beats them all (because Solid makes this possible, not because those libs are dumb)

https://www.solidjs.com/
I was devastated when I learned about Richard's tumor, the molecular profile is also very aggressive. Already showing that immunotherapy does anything is a huge step, I hope it works well enough to keep him here a bit longer.

You can follow his treatment on twitter

https://twitter.com/ProfRScolyerMIA
> go straight to the APIs for definitions

Do you really think no-one has tried that?

The API definitions (even the good ones, like Azure) do not contain sufficient information to be able to build a declarative tool. Google seem to view their internal annotations about what is mutable or not as some kind of competitive advantage (bizarre). The AWS API is wildly poorly specified for building anything except 1-1 API wrappers. (Cloud Control improves it, but covers few important resources).
I was taught by a couple of friends from Italy about how to harvest the seeds and re-grow them, very easy to do. Probably my favorite plant to cultivate now considering how simple it is to grow it, it's always nicer to have fresh herbs than store-bought (often going bad) or dry (no flavour). There is a key time to harvest but I think it depends on the climate you're in so I can't really advise on that unless you live in köppen zone AF.

Mint is about the same and I think even more easy.

One of the things about herbs is that alot of them are great chelating agents for soil. It's something to be aware of because if for example your soil is rich in arsenic, cadmium or lead, you can remediate some of it out with oregano or thyme but since these things absorb enough of that to become a potential hazard to health it's actually fairly prudent to grow your own as consumer reports has pointed out that all brands they have tested in stores have this crap in them [1], especially if you're gardening in an urban setting [2]

[1] https://www.consumerreports.org/health/food-safety/your-herb...

[2] https://clf.jhsph.edu/sites/default/files/2019-03/suh-soil-t...
Frankly once you go down that rabbit hole you have to make sure that you aren't prone to anxiety. I wrote a tool (not sure if open-sourced) that just crosses the output of 23andme with dbSNP and the number of possible diseases that came up was impressive.

I did have the SIRT1 mutation associated with a long life so there's that.
It's not at all obvious to me investors who bought their stock after they IPO wanted any of this.

The board and upper management together with their VC backers (they also gave Unity a significant loan to fund the IronSource acquisition which will be exchanged to stock in a few years) seem to be the main driving force behind this.

The only way most public shareholders can express their approval is by buying or selling stock and looking at the share price over the last 1.5 years they don't seem to approve that much.
It must be a very awk-ward service to deploy.
> This misses that the browser sandbox doesn't include sandboxing internet access. I can't be sure that the application will never send what I enter into it out to the server

Aside from the factual inaccuracy (Firefox has a "Work Offline" menu item), this is an irrational demerit. Other apps can do exactly the same things (and more); you're applying a double standard.
thank you so much for sharing this site! I've been having a hard time wrapping my head around some Vue2->Vue3 changes and this is very helpful
Our distinct humanness will be found in the narcissism of small differences.
Great way to concede the point by failing to address my response.

:)
I mean, no matter how hard anyone tries, there will be a few bacteria that get on a spacecraft. The major contamination shouldn't happen in space. It is however happening in the generic drug market, that's the reason a lot of cancer drugs are hard or impossible to find now.
For sure. Look at this Svelte 5 example:

<script>
let time = $state(new Date().toLocaleTimeString());

$effect(() => {
const timer = setInterval(() => {
time = new Date().toLocaleTimeString();
}, 1000);

return () => clearInterval(timer);
});

</script>

<p>Current time: {time}</p>
I make a lot of pesto also and freeze it to use it throughout the winter. Garlic is one of my favourite crops. It's not as cost beneficial to grow as basil, but being able to pick the cultivar is amazing.

It's unfortunate that pine nuts are so expensive. We base most of our pesto on other nuts to save money, but you just can't beat the taste of a pine nut pesto IMO.
>For example, you can make a shaft that fits in a hole like a spring because it can slide freely but air can't get out and you can shave a few microns off and it will sink into the hole at a controlled rate. This is all easily achievable in a home machine shop on a manual lathe.

I can tell from this statement that you do not have a home machine shop with a manual lathe. Home machine shops most certainly do ~not~ typically (or easily) achieve micron accuracy.
"I could park with impunity in a place where parking was impossible" -- I.e., parking where he should've have been in the first place regardless of expense.

"Also various speeding tickets." -- The opposite of parking.

"I ran up probably $20,000 dollars worth of tickets pretty quickly" -- I read this as "within a year or so I got fines totaling around $20k," which is fucking nuts.
I use it professionally and can't disagree more with this statement.
Sending mail to the President doesn't mean it was handled by the President. They've got a staff to handle customer service requests.
Because you aren't adherering to the above comment: you are reading stories about him, in fact you're also posting in the comment sections in said stories.
>"How do we handle all unsupported use-cases?"

Until you find out that your operating system handles 95% of unsupported cases in one way, then uses a hidden API to deal with the weirdness of other languages and the unsupported case isn't detected in that last 5% of languages. Of course that never came up in testing because who uses a hebrew/japanese combination and now the error message being returned by your application has nothing to do with the actual problem.

Your worst case scenario is just the common edge case bug handling that support/QA/dev's handle every day.
> create a spaghetti mess, _if your design allows it_. Svelte 5 doesn't — it uses signals as an implementation detail, but in a way that prevents the sorts of headaches you're describing.

Care to elaborate or do you have a link to a blog post explaining further?
Hard to say without seeing what it looks like in real life. In principle it seems like it could replace delivery vehicles on the road and those delivery robots on the sidewalk, which could be a net benefit. In practice I imagine we'll just get the worst of all three.

Trying to get your wheelchair across the street when there's an Amazon van with its blinkers on blocking the curb cut on one side and two delivery robots in a stalemate in the other curb cut, above you a delivery drone gets confused by GPS signals bouncing off the skyscrapers and crashes into a freshly cleaned window, falling to the street beside you. Two thirds of this story is already happening, we'll have to see what new excitements drones can add to the mix.
Not everything has to be built in if the APIs are available:

https://www.hiya.com/products/app