MurphyA/hacker-news huggingface dataset:
by fch42 | 2025-05-03 18:41:33+00:00
Symbian was not quite as great as you describe it there. Asynchronous/message-passing-based alright but with a non-scaling message queue model (servers couldn't horizontally scale because there was only one request queue - you always had multiple clients hammering one singlethreaded server). The ability to scale I/O on Symbian (via shared mem/paging) came too late to benefit Nokia (who was extremely tardy at adopting newer Symbian releases ...), and no multi-core ARM-based phone ever ran Symbian. It only got multicore support in v9 (the last) anyway. Did I mention it didn't have an ARM64 port either (press releases notwithstanding)?

"Symbian C++" used to be a great search term ... for clubkiness horror stories. Or at least warnings that "don't expect this to be your pal's C++". Nevermind the kernel actually used a more crude form (a C++ "standard library" for kernel code is ... challenging). Definitely not "easy to read".

Symbian (and Nokia) recognised this to a degree; hence the "posix environment" or the Qt purchase. Symbian 9 was a great step towards scaling it. It only got into a phone ... with the last Symbian phone ever made. Bit of a pity - it could never really show what might have been.

They were steamrollered. Things just happened too fast for non-unix-kernel based systems to take the then-imminent multicore and 64bit ARM. Nevermind other misses like keyboard vs. touchscreen (Symbian UIQ was rather nice to use but nokia's S60 was not). Or in Nokia's case, not going all-in on Maemo/Meego.

(yes, been there. Only at its tail end, and only stayed as long as I did because in 2009, the job market wasn't great. Nonetheless, I remember a few things - great, sad and stupid. Symbian had all of that and then some. And definitely, Nokia also had a few "Varros").
by typedef_struct | 2025-05-03 18:41:34+00:00
You could start with something like this:

customElements.define('html-import', class extends HTMLElement { connectedCallback() { const href = this.getAttribute('href') const fetch = new XMLHttpRequest() fetch.responseType = 'document' fetch.addEventListener('readystatechange', (function onfetch(e) { if (fetch.readyState !== XMLHttpRequest.DONE) return const document = fetch.response.querySelector('body') ?? fetch.response this.replaceWith(document) }).bind(this)) fetch.open('GET', href) fetch.send() } })
by taurath | 2025-05-03 18:41:40+00:00
What gets me the most about this is how certain you are that because you have some data about people’s browser history you can make these conclusions. I hope age and experience avails you of these notions - there is no master database that will tell you the nature of people. All you have is the data you have - I’m sure there are many interesting insights and confounding results, but it’s foolish to think you can know anyone from a database, or social media.

Genetic comorbidities with IQ? You at least have a lot to learn about mental health as well if you’re using these as examples.
by kamranjon | 2025-05-03 18:41:43+00:00
Actually that's a really good question, I hadn't considered that the comparison here is just CPU vs using Metal (CPU+GPU).

To answer the question though - I think this would be used for cases where you are building an app that wants to utilize a small AI model while at the same time having the GPU free to do graphics related things, which I'm guessing is why Apple stuck these into their hardware in the first place.

Here is an interesting comparison between the two from a whisper.cpp thread - ignoring startup times - the CPU+ANE seems about on par with CPU+GPU: https://github.com/ggml-org/whisper.cpp/pull/566#issuecommen...
by Loughla | 2025-05-03 18:42:02+00:00
My biggest complaint with NOLA is absolutely the school system. There were too many people taking advantage of the destruction of Katrina post hurricane, and the government was shamelessly complicit in the cash grab. Middle and upper middle class kids benefitted immensely, while the poor were further tracked into shitty schools for the most part.

When we were evaluating places to settle as adults, the schools are what kept us from stopping when we were there.
by croes | 2025-05-03 18:42:14+00:00
> Harmful material” means material whose dominant theme taken as a whole:

(A) appeals to the prurient interest of a minor, in sex, nudity, or excretion;

(B) is patently offensive to prevailing standards in the adult community as a whole with respect to what is suitable for minors; and

(C) is utterly without redeeming social value for minors.

B and C are pretty broad.
by zozbot234 | 2025-05-03 18:42:43+00:00
Note that I was only commenting on modern quantized LLM's that basically avoid formats like FP16 or INT8, preferring lower precision wherever feasible. When in-memory model values must be padded to FP16/INT8 this slashes your effective use of memory bandwidth, which is what determines token generation speed. So the only feasible benefits are really in the prompt pre-processing phase, and even then only in lower power use compared to GPU, not really in higher speed.
by sabslikesobs | 2025-05-03 18:44:33+00:00
I observe that the letter of the law intends to severely restrict pornographic materials from being made available to minors: see "harmful content" [1] and obscenity [2] definitions for the state of Texas.

Realistically however, fringe content and the risk of misinterpretations of the law place a huge burden on the distributors of any kind of media, where they could be at risk for a suit at any time.

This seems to point towards the need for age-checks at the book store, just to quash all possiblities---which is absurd since community-sourced content like tiktok is already so much worse for them, and that's not half as restricted!

[1]: https://codes.findlaw.com/tx/penal-code/penal-sect-43-24/

[2]: https://statutes.capitol.texas.gov/docs/pe/htm/pe.43.htm
by nbadg | 2025-05-03 18:46:17+00:00
I agree with your implicit point that the key question is probably cost effectiveness compared with insurance. However, in the context of the OP, insurance premiums in hail-prone regions was listed as a prime reason why single-axis-tracking panel installations are, in some regions, probably still a better bet at grid scale.

The point I'm trying to make is just that there are a lot of off-the-shelf (or nearly so) hail protection strategies that seem like they might have better economics than single-axis-tracking installations, which might improve the cost effectiveness of a fixed panel installation to the point where, even in hail-prone regions, it might be doable.

To be clear: anti-hail nets are already a COTS product, just not for this application (as far as I'm aware). Nets are just really, really good at absorbing kinetic energy. I mean, that's effectively what kevlar ("bulletproof") vests are made of -- netting with a very small cell size. But it seems to me like some kind of roll-out kevlar or dyneema netting could be really effective at protecting panels, though I think you'd need some kind of better strategy for safely dispersing the hailstones after they were caught, so you don't end up with a huge collection of hailstones on the net.

I agree that there's probably too much light blocking to leave them up continuously, and I'd also be worried about UV damage. But remember that the comparison here is to single-axis-tracking installations; I think automatic deployment of anti-hail netting could easily be made at least as reliable as the tracking system, if not significantly more so. Maintenance and testing would also be very cheap in comparison, since you could do it at night (ie without affecting power production), and damage to the protection system could be repaired without taking panels offline.

The more I think about it, the more I'd be interested in seeing it deployed.
by WhatIsDukkha | 2025-05-03 18:46:35+00:00
As an EATER of food what is the benefit of CRISPR/GMO?

There answer after a good 40 minutes of searching is... nothing.

It's a technology 100% in service of being lazier/sloppier for industrial scale food production and in service of IP restricting the food supply in favor of shareholder X or Y.

"but we can make tasteless US tomatoes on even more inappropriate cropland!"

...

Great for my stock portfolio to screw over developing countries but useless for me as a first world eater of food.

No proof of existence of a benefit.
by johnfn | 2025-05-03 18:46:38+00:00
You are using "script-kiddy" as an ad hominem rather than making an argument with proper justification. "script-kiddy" refers to website vandalism and cracking. That has nothing to do with using AI to learn what rev-parse does.

Learning about `git rev-parse` through documentation and learning about `git rev-parse` through AI fundamentally have the same outcome at the end of the day: you have learned how to use `git rev-parse`.
by Spunkie | 2025-05-03 18:46:52+00:00
> Also, if all these were so much concern, I doubt so much of the web would run on Wordpress.

I used to run a company that all we did was wordpress, joomla, and drupal maintenance, performance optimization, and hack recovery. It very much was and mostly continues to be that bad.

> Risk of breakage on update is a thing everywhere, not just Wordpress.

Ya the issue with server side rendering is that your live environment is made of up dozens to hundreds of difference software stacked on top of each other and they all pretty much need to work perfectly to actually work and or not be vulnerable. And if you use something standard like cpanel to manage your environment, add another 1000 layers of complexity to the stack.

And lets not even go into all the work it takes to have that environment have decent performance and run on reasonably priced hardware.

Where as my concerns for my SSG live environments basically amounts to, is the host publicly accessible? To be vulnerable you would need to do something very stupid like set file permissions to 777 or something.
by photon_garden | 2025-05-03 18:46:54+00:00
We’ve been using n8n in production for the last few months at my startup and are planning on migrating to regular backend code.

Pros:

- Good observability. It’s handy that they track all executions and let you see when workflows run.

- Usable for non-technical people.

- They’ve had all the integrations we needed.

Cons:

- Implementing parallel execution for async parts of the workflow is complicated and flaky.

- Pricing is expensive for the hosted version.

- Version control is bad.

- If you have engineering capacity, it’s faster and simpler to write some more backend code if you already have a backend.
by mchannon | 2025-05-03 18:47:15+00:00
I've been in solar energy as my primary vocation since the 1990's.

I've built solar cars, I've built solar panels, I've installed solar panels, I've designed solar trackers. I know this industry inside and out.

I'd never heard of an east-west array before (though I did experiment with one-cell-wide "crinolations" at 60 degree angles, did not find any value to using them but it was a different application where low-angle light wasn't a factor). I'd never thought of such an array on this scale, at this low angle, before.

I don't think most of the people reading this article quite understand that this is a completely different kind of array topology to flat-plate fixed-tilt, or tracking-based systems. Do yourself a favor, if you consider yourself intellectually curious, and if you came away from skimming this article thinking there's nothing new under the sun, read it again with a keener eye toward the novelty of it.
by scarface_74 | 2025-05-03 18:48:08+00:00
It’s called “skip lagging”. The airline can possibly try to collect money and if you do it often, ban you from flying with them.

https://www.npr.org/2023/08/23/1194998452/skiplagging-airfar...

The reason is happens is that take for instance ATL (former home). ATL is a Delta hub and has direct flights to a lot of places that other airlines don’t. Between people preferring direct flights and the lack of competition, they can charge more.

But flying out of MCO with a layover in ATl, they lose the non stop flight advantage and they have to compete with other airlines.

Also ATL sees a lot more price insensitive business travelers than MCO. Businesses aren’t going to force their salespeople and consultants on one of the low cost carriers.
by geor9e | 2025-05-03 18:48:16+00:00
I did the same. Sync'd my Obsidian .md vault between my macbook and my server. Asked AI for an index.php that would render a nice html/css webpage at domain.com/whatever for every whatever.md on the fly. Works fantastic. Supports everything Obsidian markdown does - pics, videos, resizing via drag, wikilinking, codeblocks, etc… No publish step - from my site you can literally see me typing live in Obsidian. No more friction to share things.
by crazygringo | 2025-05-03 18:49:30+00:00
I think this is the most likely answer.

I'm not defending it, because when I started web development this was one of the first problems I ran into as well -- how the heck do you include a common header.

But the original concept of HTML was standalone documents, not websites with reusable components like headers and footers and navbars.

That being said, I still don't understand why then the frames monstrosity was invented, rather than a basic include. To save on bandwidth or something?
by MrJohz | 2025-05-03 18:49:33+00:00
As others have pointed out, gitignore exists and you should try and build your configuration so that most of the time you're changing gitignored files rather than checked in ones. That said, you can do some pretty cool stuff with Jujutsu in this regard. Because changes are always automatically rebased, you can often create the change that will ultimately become your final commit, then create a new change where you edit any config you need to, then a change on top of that that's basically your staging area.

For example, I recently had a set up that looked something like this:

@ w - the checked out change where I'm editing files | * x - local config change | * y (bookmark 1) - CI config change that sets up a temp test env | * z (bookmark 2) - Start of the changes that will eventually get reviewed and merged

With this set up, I could make changes in an environment that included all of the config changes I needed. Then when I was happy with something and wanted to "save my work", I could run `jj squash --to z`, which would squash everything in change w into change z, rebasing everything else automatically on top of that. Then I could run `jj git push`, and this force-pushed the changes at y and z to their separate branches on GitHub. I had a pull request for the branch at z which other people could then review and where all the tests could run. Meanwhile the branch at y had updated the CI config to remove the usual tests and deploy everything to a temporary environment. So each push automatically updated my test env, and updated the pull request with the "clean" changes (i.e. without my config file fiddling).

If I wanted this sort of setup more long term, I'd find some other way to achieve it without relying on Jujutsu, but for ad-hoc cases like this it's absolutely great.
by wenc | 2025-05-03 18:49:35+00:00
This brought back memories. I remember dialling into BBSes using Qmodem, downloading QWKs (compressed email packets) from “conferences” (similar to newsgroups).

I would read/reply offline using OLX (Offline Express, a QWK reader also part of the Qmodem suite), and then batch upload my replies (.REPs, also compressed) to the BBS.

This was back in the day when you weren't connected 24/7, and when dial-up wasn’t unlimited (in my country — even if it was, BBSes were node limited so you couldn’t stay connected forever). So participating in BBS conferences meant quick dial-ins and uploads, where most of the messaging/replies was done offline.

Although bandwidth is abundant these days, I still think the QWK/REP idea is an attractive one. There is an art and a beauty to crafting replies offline from the cozy Turbo Vision UI that was OLX.
by exe34 | 2025-05-03 18:50:07+00:00
> But because of the quick response, the customer will write back to say they'd rather talk to a human

Is this implying it's because they want to wag their chins?

My experience recently with moving house was that most services I had to call had some problem that the robots didn't address. Fibre was listed as available on the website but then it crashed when I tried "I'm moving home" - turns out it's available in the general area but not available for the specific row of houses (had to talk to a human to figure it out). Water company, I had an account at house N-2, but at N-1 it was included, so the system could not move me from my N-1 address (no water bills) to house N (water bill). Pretty sure there was something about power and council tax too. With the last one I just stopped bothering, figuring that it's the one thing that they would always find me when they're ready (they got in touch eventually).
by pixl97 | 2025-05-03 18:50:09+00:00
Yea, the problem most often in computer security checklists is misapplication of the checklist.

I do cyber security related stuff for the finance and they have some of the dumbest checklists ever.

A more recent one I got was

"We only allow the HTTP verbs 'GET' and 'POST', your application can only use that and the verbs PUT, PATCH, and DELETE cannot be used.

After not replying 'are you fucking stupid' I said

"You do realize that you are using a RestAPI application and that these verbs can go to the same interface to modify the call in different way? Not only would we have to rewrite our application which would probably take months to years, you would have to rewrite tons of applications on your side to make this actually work."

You get these dipshit auditors from other firms that pick up some 'best practice' from 2003 and put it in a list then get a god complex about it needing to be implemented when they have absolutely zero clue why the original thing was called out in the first place.

For those who wonder, typically these verbs are disabled to prevent the accidental enablement of WebDAV on some platforms, especially Windows/IIS that had some issues with security around it. It makes zero sense for such a rule in a modern API application.
Show HN: Live Air Quality Monitor
by benbojangles | 2025-05-03 18:51:24+00:00
A comprehensive indoor air quality monitoring system built with ESP32-C3 Super Mini and multiple environmental sensors. This project helps you monitor CO2, temperature, humidity, volatile organic compounds (VOCs), nitrogen oxides (NOx), and particulate matter (PM1.0, PM2.5, PM10) to maintain healthy air quality in your home or office.
by blincoln | 2025-05-03 18:54:05+00:00
I'm American, and I fully support moving to the metric system. But it's a tough sell for most people.

If someone is an adult, it's a bunch of new information to learn, and unless they work in a field that involves measurements and math, it probably won't be an obvious net positive for them.

The biggest benefit IMO is for future generations, who wouldn't grow up having to memorize conversion factors for a bunch of ancient legacy units (feet per mile, teaspoons per cup, etc.) as well as having to do the conversions when working with people from outside the US.

I'd greatly appreciate it as someone who does a lot of hobby work in various fields, because metric measurements are something I can use across all of them. But the impression I've gotten is that professionals in a single field are so used to working with whichever specific imperial units are relevant to them that it would be a wash. And since they'd have to redevelop all of that intuitive knowledge for the metric equivalent, they see it as a net negative.
by pythonguython | 2025-05-03 18:54:37+00:00
To the extent it’s measurable, LLMs are becoming more creative as the models improve. I think it’s a bold statement to say they’ll NEVER be creative. Once again, we’ll have to see. Creativity very well could be emergent from training on large datasets. But also it might not be. I recommend not speaking in such absolutes about a technology that is improving every day.
by aiforecastthway | 2025-05-03 18:54:47+00:00
> Are you saying that while a company would be responsible (current laws), an employee should not because of free speech?? (proposed law)

Absolutely. Circumscribing liability in civil actions is one of the fundamental purposes of commercial legal structures; to wit, the two L's in "LLC" stand for "Limited Liability".

The basic principle of limited liability has been deeply embedded in the USA's system of free commerce since its founding. Historically, there has always been a high bar for exceptions to this general principle. I think that should still be the case.

I have two reasons for this.

The first is selfish. The legal exposure risked by an hourly employee working at a bookstore would be far too great to justify the wages earned. The lines of "obscenity" are blurry enough that the risk to any employee would be substantial.

If the business chose to indemnify their employees and owners -- which they likely would need to do in order to employ anyone -- then that indemnification would be part of a larger legal insurance policy.

I do not own a book store, but I do own a large stake in a business. I carry a legal insurance policy (actually, two). These bookstores are probably part of the same risk pool that I'm buying into. Which means that if some random Karen is angry that a character in a book had two moms, my insurance premiums get to pay for that bullshit.

The second reason is more principled. The intent of the proposed exception is to establish a statutory framework that would allow conservative religious groups to use civil courts to harass their ideological enemies. I do not find common cause with that purpose, because I do not believe in bullying people into silence via the State's courts, because I am a proud American.

BTW: if the employee's actions are criminal, then the state can already prosecute that individual employee. Allowing private civil actions is extraneous, unless the ultimate goal is coercive or political. Weaponizing our system of commerce to wage culture wars was a bad idea when the intolerant left was doing it a decade ago, it was a bad idea when the intolerant evangelical right was doing in two decades ago, and it is a bad idea now that the new right is doing it.
by mike_hearn | 2025-05-03 18:55:07+00:00
There is such a thing as objective truth. Note that NPR's former head doesn't believe that [1]. Anyway, most people in Britain disagree that the BBC does its best to report it. Here's a simple reality check: how does the BBC describe right wing politicians? Dame Andrea Jenkyns DBE is a former Tory MP, government minister and campaigner for Brexit. She has a degree in economics, spent 20 years in Parliament and she just won mayorship of Greater Lincolnshire. This is the headline the BBC went with:

"Reform UK's Andrea Jenkyns is the new mayor of Greater Lincolnshire, marking a return to politics for the former Gregg's worker and Miss UK finalist"

She's 50 but the BBC's audience hears about what she did as a teenage girl. It's not an isolated incident. Nobody serious tries to argue the BBC is neutral, fair or objective anymore. Reform is the highest polling party in Britain, it's awful to make all those voters pay money to an organization that openly hates them.

> Did you know that Fox didn't even report the stock market drop after liberation day? They just pretended it wasn't happening!

Yes they did:

https://www.foxnews.com/video/6370983289112 "Stock markets crashing in response to tariff announcement"

[1] https://www.realclearpolitics.com/video/2024/04/17/npr_ceo_k...
by andsoitis | 2025-05-03 18:55:15+00:00
” Now, after being eradicated from the US since the early 1980s and largely forgotten, top veterinarians expect the screwworm could be back as soon as the summer. More than 950 cases have been reported in Mexico so far this year, including one within miles of a livestock checkpoint in Chiapas. A resurgence in the US would have devastating consequences for farm animals and wildlife”