skysight-inc/HackerNews huggingface dataset:
It's good for quick things and prototyping cause you can always swap out those calls with native later. It's API is generally easier to remember/less typing that most native equivalents. You can also use its API serverside via Cheerio to do parsing & manipulation of html without a dom.

edit: also its way more lightweight than React/Vue/Svelte i don't necessarily disagree you shouldn't reach for jQuery if you have a dynamic page (something like uhtml+preact signals would be good if you have fair bit of rendering logic going on) but I would say you should totally try seeing how far you can get with jQuery instead of Svelte/React/Vue on simple pages.
I have to say I love Arc. Simply because it takes existing OS UI/UX paradigms like Tab/Window switching, Spaces, etc. to browser. This is imo long overdue since the time we started using more webapps than websites.
At least for x86, there's an incredible wealth of architectural details out there, both from the vendors themselves and from people who have worked tirelessly to characterize them.

Along the lines of another comment on this post, part of the problem is the GPU compute model is a lot more abstract that what is presented for the CPU.

That abstraction is really helpful for being able to simply write parallel code. But it also hides the tremendous differences in performance possible...
I ask dumb questions to tease out useful responses all the time, I don't think you're wrong in the general case, and an exhortation not to rush to judgement can only be good. But these guys have been at it at least twenty years. Every time they pop up with "what about the Mediaeval Warm Period/Little Ice Age/Roman Climatic Optimum?" someone explains that they're comparing local phenomena with a global phenomenon and they go quiet until the next time. There has to come a point where you are forced to assume bad faith.
> many not tech-savvy people prefer it because of its ease of use.

You realize how much you're hurting your argument when saying this?

iPhones are in no way “easier to use” than Android phones, if anything the lack of a back button and more limited Windows support makes it marginally harder for beginner to use but that's not hard to overcome either so it's not a deal breaker in any way. But it's not easier, except in Apple's marketing pitch and Apple fan's head.

The only thing saying things like this shows it that's you're an Apple fan whose PoV is too biased to be worth reading.
Thanks, I did not think of that but iCloud Private Relay requires an iCloud+ subscription[1] which I do not have.

I'm referring to the "Limit IP Address Tracking" option[2] in Safari/iOS and "Hide IP address from trackers" option[3] in MacOS/Safari

[1] https://support.apple.com/guide/icloud/set-up-icloud-private...

[2] https://support.apple.com/library/content/dam/edam/applecare...

[3] https://appletoolbox.com/wp-content/uploads/2014/02/Hide-IP-...
There's no guarantee that the calendar event will exist 50 years in the future as well.

Gmail might not exist or be replaced, text files might suffer corruption, cloud hosting could go off line or the database could die or a physical letter can be lost or destroyed.

Really need to use a multitude of options to ensure delivery in the future.
This is great! I would love to see a passmark/$ metric on here as well.
Another day another JavaScript framework! I'm so tired of all this churn in frontend. /s
I’ve a bi-annually repeating task on my calendar -- HN: Pi-Hole / AdGuard? ;-)
Carbon Emissions from the Concete-Making Process
Different use cases. A lot of the web only has only one or two interactive elements in a scope. The DOM being changed by any random piece of code is not a problem when all of the JavaScript fits on two screens. In fact, it’s a benefit here.
People here railing against cryptocurrency are generally unable to see past its proclivity for scams. This is an entirely reasonable situation. Further, cryptocurrency proponents are historically completely unwilling to admit there are any flaws to the point that it’s obvious they have a stake in cryptocurrency and it’s severely biasing their judgement.

You don’t seem like that per
se but if you haven’t seen it before you haven’t been watching.
Correct, but the key part I mentioned was "Given Ruby's lack of static typing". It's nearly impossible to hunt down source code in large Ruby projects due to mix-ins, dynamically adding methods to types, etc. At least in Ktor I've reasonably able to track down the implementations of most DSLs I've come across since it's statically typed. I tried the same in Rails long ago and gave up.
Twitter didn't become big by being almost exactly like something that came before it. Learning something new was not a burden for all the users that jumped on to the Twitter train.

Elon has weakened Twitter substantially and now it's leaving the door open to newcomers with ideas in a different direction.

It's the churn. Platforms rise and fall. But this time the power vacuum is so big a non commercial platform might have a fighting chance.
That the plane landed safely is not an indication that every part of the post-incident process went well.

There could be steps that weren't followed, there could have been training gaps. There could have been secondary impacts of sudden depressurization that could have spiraled out of control, but the pilots thought on their feet to save the plane. We'd want to know exactly what they did so we could add it to the recovery process.
and scriptaculous!

http://script.aculo.us/
Eh, do'h, of course. There's a few selectors anyway, but I'd have to check which ones exactly. :eq(n) and :visible from a quick check (:nth-child(n) can replace :eq(n) in some cases, but not all).
People have been waiting for decades for the Canadian housing market to tumble.

There are so many Canadians waiting on the sidelines with their down payment ready to be deployed and are out competed year after year.

The pent up demand for housing is enormous. Even with the high interest rates.

Hell, with the rumors of interest rates going down, there is a frenzy to BUY now, suck up the high interest and get a relief in a few years, because people are afraid that if the rates go down, more people will qualify for a mortgage and it will bring more pressure, so better to buy now if you can.

I am convinced it will not go down in my life time ever. Too much demand, not enough supply.
>> "“In a hybrid work world where demand for WeWork’s product should be greater than ever, my clients believe that the synergies and management expertise offered by an acquisition could significantly exceed the value of the debtors on a stand-alone basis,” the lawyers wrote. “WeWork should at least educate itself about that potential and not preclude itself from maximizing value.”

> hybrid work

> demand

> greater than ever

WAT
Self-Discover: Large Language Models Self-Compose Reasoning Structures
Yes! And I’ve noticed it tends to be the older cars with ‘low’ temperature lights.

I have two theories:

1- They are trying to compensate for their hazed, plastic headlight enclosures. Unfortunately not only are the high beams brighter, they point up.

2- It’s a stick it to the people with newer cars and their obnoxiously bright lights mentality.
No, interstellar atoms (or other particles) aren't static, they aren't just hanging in one place. Everything is moving. Some particles are moving very fast.
Nobody mentioned trombones. This discussion is about automobiles.
Different Urbit.
Dexie.js – Minimalistic IndexedDB Wrapper
> I find $.ajax() much more simple than promise, await, async of native JS.

$.ajax() returns a promise. If you're calling .done() / .error() on it to handle the results -- well, that's exactly how you work with promises.
That's one of the reasons I like them, yes. I've done a lot of manual DOM manipulation, and a lot of jQuery. When you're building anything complex, it starts to become quite difficult to figure out why a particular piece of the DOM is behaving the way it is. It could be an overly aggressive selector that accidentally targeted it, or any number of things.

Prior to React (and similar libraries), DOM manipulation was generally done in a mutating, effectful way. With React (and similar), if a thing is behaving strangely, I just need to go to the component that rendered said thing, and I can almost always find the problem.
jQuery is still excellent if you are creating websites (not web apps) with minimal JavaScript.
There seems to be an assumption baked in here that somehow GPT will be "adequate legal representation" and I'm not sure how to get there. An "adequate" source of revenue for OpenAI, I guess.
A lot of what jQuery was created to do is now baked into the browser. CSS selectors, proper ajax, animation, etc.

I built a small convenience library around fetch to make it super easy to use ajax like in jQuery. Also built a small utility library around ES6 methods that recreate jQuery methods. It doesn't take much to get back the convenience of jQuery but still use all the new tools.

I love jQuery and used it for years. But there are better tools now.
And Dojo! https://dojotoolkit.org/
I started with Jquery, I learned React. I prefer React.

React complexity is often conflated with things like Next JS or other SPA solutions. React was originally meant to be a library for building small components that you drop into an otherwise static websites. But people usually don't talk about React unless they're talking about whole sites being in React. For that reason, I think its complexity is exaggerated.

More importantly, what the commenter is referring to is the fact that you are encouraged to write Jquery code that can break if you decide to move a div or change a class name. The workflow of CSS selectors is fine for small apps, but can lead to hard to track bugs down the road. It can be avoided if you make a lot of unique IDs. But otherwise you're screwed. There's no scoping. You technically have to read every piece of Jquery code before changing any other code, html, or css, because you could break half the site depending on what people were depending on. There's no IDE support telling you what is selecting what. Events are not colocated on the things they attach to, they could be anywhere.

I can update a React component and be sure that the only places it affects are the places its rendered. And I can get type checking on every input going into a component. That's just way better to me.

I still use JQuery at work, but I usually dread it. And people say JQuery is "smaller" but I would still prefer something like Svelte to Jquery if that's a concern.

I can take or leave Vue, I don't really notice a huge difference between it and other component frameworks.
Just because Marissa took the credit doesn't mean it was her idea.
Ask HN: What are some non-LLM techs to look out for in 2024?
Everyone keeps talking about LLMs, but I was wondering if there other interesting tech on the horizon that have got neglected under all the AI hype in the past two-three years.
Yes, I also happened to run a browser which shares the same philosophy on RAM.
You're only addressing half the issue here. By delegating control of your domain to bsky.app, you're still beholden to a centralized ban list and retain no control over your own instance.
Did you study anything about Hashgraph, or Hedera?
Interestingly you've left it somewhat ambiguous as to whether you view these immigrants as morally upright while being somewhat naughty. You could certainly say that they've found an exploit/hack in the system by claiming asylum and could view that as clever and/or immoral depending on the eye of the beholder.

I will say that I don't think the situation is being handled all that well (and I suppose hasn't for decades, but perhaps that just goes to show that there's not much we can do at all), but as a resident of South Texas, I haven't felt any actual problems with my day-to-day life that I can directly attribute to illegal immigration.
I’m baffled that they decided this was a worthwhile thing to do after the bad press/lack of results Elon got for the same thing.
(Your comment reads to me as having a tone of disagreement, yet you seem to just be providing further evidence of the point: we are confident that this is the case as Microsoft is actively trying -- if failing due to some of the other things you didn't bother to quote about existing expectations -- to gain this kind of control.)
It's good for resale, it's good for inventory management of bundled accessories/hardware (e.g., that bracket you didn't need originally, you now need to still own and be able to find), and sometimes it's good for protecting the product while moving apartment/house.
Mainframes deliver reliable uptime. They so far are the only ones that can do it reliably, for decades.

Essentially the bunch of boxes model(k8s being the new kid on the block) has been trying (and mostly failing) to provide what mainframes have been providing for 60+ years.

Which is being able to treat your workloads as just a random virtual job you can push wherever and let it run while also giving you ridiculous uptime.

Mainframes are basically the hardware infused uptime deliver machines. They can and will offer 5 9's without any trouble. AWS, Azure, Google's cloud, none of them can deliver that amount of uptime, they ALL have failed repeatedly, so much so, that they purposely try to obfuscate their downtime records. Many don't make any historical data available.

k8s and the like have been trying and failing at reliable uptimes. Sure we've arguably been making some progress, but your average self-hosted k8s team has full-time dedicated teams of people that do nothing but babysit k8s. How many staff do your average mainframe org dedicate to keeping the mainframe alive? Usually 1 person, maybe two. Of course the price you pay IBM or whoever you choose as a mainframe provider will help offset the staff savings from your k8s team :)

It's not about raw compute power. It's about keeping a workload alive for as long as you can deliver power to the mainframe. i.e. the Mainframe promises to deliver uptime for as long as you can keep power to the machine. As parts fail, seriously any part: memory, CPU's, disks, backplanes, it doesn't matter. Mainframes can route around the failed part and you can replace it without turning anything off or affecting your workload. This means your mainframe is sized larger than your workload of course. It's not like the fundamentals of compute change in that regard.

The question then becomes, is the juice worth the squeeze? If your entire business model requires uptime, then you best really, really care about uptime. There is a reason the Visa and Mastercard networks have basically never, ever been down. It's because they know their business only exists as long as their network works. When you want uptime at all costs, you don't run k8s(or whatever the latest craze is tomorrow), you run a mainframe.

Most of us get more uptime than we need with insert favourite cloud provider here. Uptime isn't something they actually sell when you read the contracts you sign. Uptime is just marketing spam.
> It seems to me that only Scorpion meets all three of these rules

Do you have any links to Scorpion? I'll keep looking but I haven't been able to turn up anything. I'm aware of the others you mentioned. Thanks!
Right, but that's still a far cry from being entirely unable to use them together. And as for the extra binary, that's hardly an obstacle if you already have to ship Deno itself anyway (and that ain't even considering the possibility of statically-linking it into a custom Deno binary).
Greetings from Ukraine, country at war now, and one of main foundation whale of USSR at not too far past.

I'm not too old, but I born in USSR and seen from inside, how it steal western technologies and where it stuck.

We now chosen democracy way, mostly because Russians are Nazi and think Ukrainians not nation of their level, but my youth spent in hot speech battles, on how we will deliver own totally independent semiconductor industry.

Systems, you mentioned, are from my view, something in best case 2017 year desktop technology on steroids for West - not bad, but already outdated, and far from professional systems. Modern professional systems, should be something like latest IBM Power9 or Power10, somewhere near 3.5..4.0GHz cores, Terabytes RAM and hundreds megabytes of L3 cache.

And also very important, I have not seen anything comparable to IBM or even to Microsoft in China. Fortunately I also don't seen much enough from Russia.

So, what I release, this is really serious threat, they could kill many people, but it is not parity with West even within one industry.

And yes, you could say, I'm too subjective, but I think, for West now is more important to save Ukraine as independent country (sure, same I consider about Taiwan and Israel, which are also under serious threat), to show how West values allies, not to win race by total domination for all cost.
I don't think it's that surprising given the demographics of HN posters that I've observed. Many will immediately reach for the big JS framework du jour when they need anything more than a little DOM selection stuff, because that's what they've always done.
Go get a cluster manager like Rafay or Spectro cloud. There are a lot of footguns in cluster management: cert management, ingress controller, IaC (TF versioning is a pain), etc.

a cluster manager isn’t cheap but it sounds like you are getting buried. If you’re on 1.23 or up though, you at least have a year now to fix it.
Looks awesome! Isn't there one of these for laptops as well?
Honestly when I dug into the podman/buildah code it was just differently cursed. It was reallly disappointing.
Just in case folks aren't familiar, this site breaks down jQuery features into web standard code:
https://youmightnotneedjquery.com/
One website that almost always gets mentioned when people talk about jQuery today is "You might not need jQuery" (https://youmightnotneedjquery.com/).

That site is the best ad for jQuery I've ever seen. For almost every task it describes, the jQuery code is shorter, cleaner, and more intuitive than the vanilla "modern" JS one.

And that's after almost 20 years, and I don't know how many billions of dollars invested into advancing JavaScript.
The fact that it, well, works doesn’t help with the React world domination either.
OP here, you're getting down-voted, but you are actually correct. Seeing that meme reminded me I once owned a cable like that, and got me wondering how it worked.

Weird what a small place the internet is.
The core of Optery's search functionality is "person" centric. Meaning we start with searches by name, city, state, and age to find "you" regardless of which underlying email or phone number the data broker has on record for you. Because in many cases data brokers may have no email or phone on file for you at all (only home address), or they may have a really old phone or email you have forgotten about. When data removal service scans focus only on phone numbers and email addresses, a lot can get missed. Many people search sites are not even queryable by phone or email, and are only queryable by name, city, and state. Optery does search for phones and emails, but you are correct in that it currently limits them to just one each from the customer at this time. We plan to release the scan on demand feature you referenced in the next few months.

That said, Optery recursively searches through data exposed by data brokers to alleviate the need to input numerous old phones and emails by the customer. In PCMag.com review they said this of Optery's recursive phone number search functionality:

"It uses data found in data broker profiles to recursively expand its reach. For example, in my latest testing, I only gave it my current phone number, but it found records associated with an old number that I used for some 25 years."

source: https://www.pcmag.com/reviews/optery
> 14% Chinese, over 21,000 people, and mostly high income tech salaries. It would be bad business not to have Chinese speakers on staff.

What language do these Chinese tech workers speak at their jobs?
https://supreme.justia.com/cases/federal/us/219/219/

> The words involuntary servitude have a "larger meaning than slavery." "It was very well understood that, in the form of apprenticeship for long terms, as it had been practiced in the West India Islands, on the abolition of slavery by the English government, or by reducing the slaves to the condition of serfs attached to the plantation, the purpose of the article might have been evaded if only the word 'slavery' had been used."

If there wasn't a distinction between the two, the Amendment wouldn't need to mention both.

If I see forced unpaid laborers, I'm entirely comfortable deeming them slaves. (They'll probably learn about similar forms of slavery in history class; https://en.wikipedia.org/wiki/Slavery_in_ancient_Rome, for example. In current affairs, https://en.wikipedia.org/wiki/Slavery_in_the_21st_century)
> Or maybe you finally find a good instance but your admin dislikes Meta so you're defederated from threads.net now. That's a bummer.

If you don't agree with your admin's choices on such important matters, your instance is not a good one for you.

The differentiation between instances, the way each can have their own community with its own morals is a strength, not a weakness. As the fediverse gets bigger, the bigger platforms will diversify more and have more of their own identity. For example beehaw, it's not really a Lemmy instance with some policies configured, it's beehaw. As the fediverse gets bigger, instances will develop their own identities more and it will be easier to choose.

And gab, for the cesspool it is, you can't deny it's got its own identity. Of course it's one that almost nobody wants to federate with but that's their right too. Freedom of speech doesn't mean everyone has to listen to you. The system works as intended.

The thing is, if you're aligned with your platform you probably agree with most of the choices your admin made. If not you can just pick another one.
I think a fair amount of "common advice" is wrong. Things like "work hard", "you can be whatever you want", "persevere"
.

There are truths in there; success does take hard work, but hard work does not lead to success. Success takes perseverance, but perseverance does not lead to success.

Baking bread requires time, but having time does not lead to bread.

You can do all the work, you can have most of the ingredients, but without yeast you don't get bread. It doesn't matter how much time, perseverance, work or dreams you put in.

Finding the right advice is hard because unless someone can see what you are doing right, it's hard to know what is missing.

Yes, sometimes the yeast is luck. But even knowing that is helpful. Luck (aka chance) can often be improved. I was lucky to land in the job I did, but I am least put myself in the right place at the right time.

The worst advice is something you are already doing (hard work perseverence) without success. It's the equivalent of "what you are doing is not working, but keep doing it anyway" which is terrible.
I really like the f-string updates - particularly that you can use quotes of the same type within the f-string.

For example, from the documentation:

> f"This is the playlist: {", ".join(songs)}"
Lots of old tools are mysterious. Like any piece of modern tooling, found discarded, can be baffling too I guess.

My Dad was loading gravel at the quarry years ago, the site of the local Meskwaki campground in the 1800's. Found a rock sitting there with a cross-hatch pattern worked into the surface, about half an inch deep! Six or eight inches across. A stone the size of a cantaloupe. Each groove seemed to be rubbed in the stone (a very hard stone) and overlapping. That is, one groove would cut across another, as if they'd been rubbed in serially and not all at once. Each about a finger-width.

Almost like somebody had taken their thumb and rubbed the lines in the surface, though that is impossible, it was far too hard.

Kept it in his office on a shelf for years, just a conversation piece. Never figured it out.