skysight-inc/HackerNews huggingface dataset:
> front ends independent of any of the existing frameworks that exist today, which I think is probably controversial

Not sure controversial is the right word, in fact I think it is quite a common sentiment among developers, especially those that originally come from back-end. The only problem is finding a company that is willing to forgo the frameworks.

They do exist though. Here's a short list of companies that use vanilla JavaScript, most notably GitHub and Netflix:

https://gomakethings.com/companies-that-use-vanilla-js/
I've been using WebComponents a lot lately.

My biggest gripe with them as a technology is that they have no way to associate a `<style>` tag in `<head>` with a ShadowDOM tree (short of cloning and injecting w/ JS).

The only way to say "this CSS goes with this <template>" is to nest the `<style>` tag in `<template>` itself or painstakingly expose `part`s on everything you want to style.

I'd really like a template selector for CSS where I can say something like `::template(#id) button` to select all buttons inside the `<template id="id">` for whatever ShadowDOM it is mounted to.

Without this, I either have to do CSS in JS, CSS in HTML, or I have to use special build magic to take my standard index.css files and inject them into my HTML or JS. All of that is kinda gross.
Is not just a removal, you know right? They rewrote taskbar entirely. It's actually coming soon the feature :)
VanillaJS/web standards all the way. I love being able ship something knowing exactly what’s going to end up in the browser. I really don’t get the react cargo cult fad, and when it finally dies it won’t be too soon.
Running Foundry on a $20-40/yr KVM VPS from LowEndBox seems to be the best balance between cost and convenience. Performance seems fine.
I just installed Windows 10 on a laptop using the official USB creation tool. You just gotta leave it disconnected from the internet and you can make a local account with no restrictions.
awesome work to the organizers and congratulations to the employees!
more direct source in this one https://news.ycombinator.com/item?id=35188953
I don't use YouTube TV or Cable. Does this price include having 3 minutes of ads every 10 minutes like cable? If not, it being the same price as cable seems like it would still be a good deal.
> If you don’t upgrade to a paid subscription, Docker will retain your organization data for 30 days, after which it will be subject to deletion. During that time, you will maintain access to any images in your public repositories, though rate limitations will apply.

Specifically (emphasis mine):

> During that time, you will maintain access to any images in your public repositories

So, the logical conclusion, which literally everyone else on HN had, was that after that time you will lose access to images in your public repositories; access meaning "we can get to the image" in this context, because that's what people f-n care about.

Not to mention the other part, about how Docker will still have images available for pull that can't be changed, for which there is no way to "forward" user pulls elsewhere if the developer chose to not pay the fee; so in affect you're capturing their user base with old software and almost no way to know that.

"DevRel" at Docker failed this week. Just own up to it, take the hit, and don't be evasive. Evasiveness is shady and no one trusts that bullshit.
Twilio is a dumpster fire. Trying to use it 100% legitimately, respecting "STOP"s, and bending over backwards to comply with every request they've made and they still randomly block us. So not only do they fail at keeping spammers off their service they are actively driving away paying legitimate customers.

I used to love them and they still might be good for a little personal projects (though your story says otherwise) but I would never pick them to use at scale. At one point they said they needed the /exact/ text of every message we were going to send ahead of time to approve before we sent it... Yeah that doesn't work when you send OTPs (yes, yes, I know, we have to have it as a fallback) or a user-specific/transaction-specific url. So pretty much they only thing you could send is generic marketing trash, cool...
I claimed intelligence was orthogonal to sentience. I still don't know what you mean when you say "understanding", but I guess it's something involving sentience? :)
I'm sure there are cases where doing a specific thing (e.g. buying another company, or paying off particular debts) with the money is part of the deal. And sometimes an investor will demand a board seat which gives them a way to influence other decisions. But I'd be amazed if a VC wanted a "spend the money on something" provision - if you really can't think of anything to use the money for, letting it sit is better than burning it. You're always obliged to use your best business judgement on behalf of your shareholders, which would seem to cover making use of the money if you have a good use for it, and not if you don't.
Ask HN: Adversarial AI for Job Applications
Is there an adversarial model for resume screeners?

I'm pretty tired of trying to figure out whatever the correct number of keywords is, or what the trendy buzzwords are. I imagine this as like a triplet loss problem for JDs, resumes, and screening passes.
I suspect it was a combination of technical limitations and the nature of the developers. The USB 1.0 standard was finalized in 1996, seven years before PCIe 1.0 (2003), and was one of the first (maybe the first?) consumer protocols to fully support automatically-enumerated hot-swappable devices. (Having worked on USB drivers a bit, I still kind of hate the protocol, though.) Keep in mind too that there is a massive difference in computing power, memory, etc. between 1996 and 2003. Similarly, I get the impression that "low-power wireless" was a herculean effort when Bluetooth was developed in ~1999.

It looks like PCIe 1.0 was designed solely by Intel, which probably accounts for a lot of the coherence and editing. SATA (2003) was designed by committee.
Great project, exactly what I've been looking for - a truly minimal JS "Framework*!
Someone who uses an LLM as a tool to perform a useful service
What's the rationale behind not breaking up the accounts of large depositors into FDIC-insurable accounts? Apparently this is called a 'cash sweep'. Typical ad blurb:

> "Insured cash sweep is a safe and convenient service that provides FDIC insurance on large balances while giving you access to your money, as well as the ability to earn interest. Choose between demand accounts, which offer unlimited withdrawals, and money market accounts that permit up to six withdrawals per month."

I've heard some claims that SVB was offering incentives to depositors who kept their funds in one lump account, is this true and if so what's the benefit to SVB from doing that?
I'm surprised there was a 12-month program to become a sourcer.
I think there's a personality aspect to it as well.

I've noticed that some programmers live for the front-end of a project. When you have a clean slate, are doing design, developing the data structures, approaches, all of that creative stuff. By the time the project is mature and the big problems have been resolved, they tire of it and want to move on to another new thing.

But there are others who hate that front-end stuff. They love taking a mature product and maintaining it. Debugging, adding new features, etc.

A successful product absolutely requires both kinds of people. A company who devalues one or the other is a company that is shooting itself in the foot.
To give a different perspective, I applied to Triplebyte when they announced their project track for people who don't do well in interviews. They told me I had done a great job on the project, but that they couldn't move me forward because they needed candidates who could do well in interviews.

(What was the project track for??)

They recommended practicing on interviewing.io, a site with closed membership that kept me waitlisted for over a year (and only then let me in because I complained about the situation on HN, not because I'd actually waited long enough to get off the waitlist).

So as far as I could see, Triplebyte advertised one thing, delivered the opposite at every opportunity (I'm also still bitter that the site with the tagline "No resumes, just show us you can code" opened its interviews with "So, where have you worked in the past, and what did you do there?"), and didn't even pretend to be interested enough to give you advice that was, theoretically, possible to follow.
TypeScript is like having a glass of ice cold water in hell.
That's after the fact, though. If you want to actually interact/modify with a work in progress, you have to be in the cattle car channel and watch for it to show up, yes? (except maybe by having your own server and inviting the bot, as the OP suggested).
> no one will ever be able to credibly claim that they need thousands and thousands of people to maintain a single app ever again

I don't think they'd ever claim this because these companies do way more than "maintain a single app".

If companies don't attempt to innovate, even big ones, they lose in the marketplace. Meta for example has multiple apps to support, each serving hundreds of millions of users. On top of mere maintenance, they experiment and add new features. On top of that, what about the occasional greenfield/skunkworks type projects?

It's a shame your friend worked on three consecutive projects that got axed, but that's a separate problem from him being able to coast without getting fired for it.
*legally.
There are plenty of ways to watch live HD sports.
Now that you mention it, I also have a gas stove and that day the temp. was in the 30's. I was still able to stay warm at night. So it's the same problem.
white collar workers detest these jobs

the only reason they studied, went to university etc was to avoid doing manual labour. this has been happening for decades, a century. they ll be depressed
I hear this a lot but I think it's bullshit. Neither of those are goals that anyone would realistically pursue. It was almost certainly middle managers wanting to demonstrate impact by leading a larger team.
I can't figure out why anyone chose to use react...

I understand the "it's dominant and has a large ecosystem" argument, but I just can't wrap my head around how enough people chose it for it to reach this position.

I've evaluated it a couple times and it just looks poorly conceived. Fixes and "improvements" have rolled in, but they are also poorly conceived and themselves need fixes.

Of course I know it might just be me... I didn't get the point of tailwind either, until I used it.

But I've also used react for a reasonable sized project and I still don't get it.
I work on xFormers and we definitely appreciate the candid feedback:

- We partnered with our PyTorch colleagues and some of the PyTorch 2.0 kernels for efficient attention actually originated from xFormers, so glad to read that having this now built-in into PyTorch is something users are really eager to use.

- While xFormers was originally targeting a pure researcher audience, we were aware of the installation problems: we started end of last year gradually making it easier to setup and use the library (both internally and externally). We have recently introduced non-dev conda packages, pip wheels and are also trying to release more often,

- We very much welcome hearing about any issue with the library and would certainly love discussing more the specifics of your experience (or others' who read this) if you have time (maybe via our GitHub to start with). Thanks again for the feedback here!
ClickHouse Common Lisp Client Library
So many replies but few actually addressed steps the FCC indeed is taking. Eg; the implementation of STIR/SHAKEN: https://en.wikipedia.org/wiki/STIR/SHAKEN to prevent caller ID spoofing.
TIL; when researching breathing gases I found "Hydrox". And yes, it's exactly what it sounds like and divers have successfully used it.
I'm not involved, but they were recently sold to Epic Games, which, I imagine, represents a fairly large shift in character of management. It might be a defensive move to protect the worker culture that evolved before then.
The problem is not that automation will eliminate our jobs.

The problem is that we have created an economy where that is a bad thing.
> I want the decisions I make to last decades, not just a few years. I don't think that's a sentiment appreciated by most, though.

Clojure and ClojureScript very much appreciate that sentiment. re-frame, a library for creating React apps with ClojureScript is rock solid, many years old, and still on version 1, meaning no breaking changes so far. 5 years old re-frame code still looks the same today.
This is not an event that calls for pithy adages. The fruits of ML are not a fad just like personal computing was not a fad. It's a watershed event that cuts across every knowledge worker's domain. If you're not currently using these LLMs it may not be obvious to you but those of us that have tried to apply them to our current fields see huge gains in productivity. Just in my own little slice of knowledge work, I've seen yield increases that have saved me multiple days of work on a single project.

Everyone is going to feel this, most prominently people in the sorts of industries that frequent HN. If you haven't yet, you will or you will be forced to when you discover everyone in your field is out-producing you armed with these tools.
Here’s a good recent podcast episode on countering some of the common anti union rhetoric that you might get in response[0].

It would be great to unionize tech workers to fight for an end to abusive practices like on-call, uncompensated overtime, abuse of foreign workers, unhealthy work environments, and poor wages (remember the vast majority of tech workers aren’t at FAANGS on the coasts).

0: https://citationsneeded.libsyn.com/episode-177-popular-anti-...
Microsoft unveils AI office Copilot in fast-moving race with Google
This is an interesting place for this to come from, since bandcamp has really been a model for fairness in how artists can distribute their work and get paid. And it was sadly recently bought by Epic Games. I know nothing about Epic, but I know the game industry is far from the paragon of fair labor or fair content distribution. I wish them luck.
Using react server components these days and don’t see much about it.
It's not a wildcat strike if you're not in a union. It's just refusing to show up to work.
Unions are not necessarily a response to bad management. Often they can be because the workers want to force the good management to stay good.

It’s far more effective to unionize when things are going well rather than when things are going bad.
They obviously don't see the advantage.
This is really harshing my "build/test in production" mellow
SVB should have decided not to grow so much so fast. More companies have gone kaput for fast growth than for any other reason.
> it's one of those features that outside of Rust you only really find in ML-family languages

Or in Scala, technically not an ML, but is as close as you'll get in a nominally typed language.

enum RGB:
case Red, Green, Blue

def log(x: RGB) = x match
case Red => print("red")
case Green => print("green")
// error, not exhaustive

Obviously Scala can do a lot more, including GADTs, which Rust will never have until HKTs are supported.

Ton of powerful languages to choose from these days, good times...
You keep arguing for keeping it exclusively in the hands of tyrants and sociopaths by pointing out how bad it would be if tyrants and sociopaths had it.
> There's a world of difference between

No there isn't. This is entirely subjective and you're acting like they said "Fuck our customers" when they just shared data. Anything you want to imply beyond that says more about you than it does about any part of Docker.

> The first implies that they have up to 2% of users which they don't respect, and undermines their apology.

Where does this implication come from? Why is Docker not given the benefit of the doubt when they are already extending an olive branch...? This isn't Microsoft.

I guess if you want to change things, you should shoot for a position in PR at docker. Otherwise, you look like a rube for acting as though they "could have done better with one sentence." I bet you're fun at parties.
The UK's only orbital rocket launched from Australia. https://en.wikipedia.org/wiki/Black_Arrow
> The FCC already requires similar blocking of voice calls from these types of numbers.

In other words, it won't change anything. I still get just as many scam voice calls as I ever have.
Only because the govt promised to protect unions. They’re not really keeping their side of the promise.
All my regional sports got moved to Bally's and my subscription price to Hulu did not change :(
The Oxford Handbook of Spontaneous Thought: Mind-Wandering, Creativity, Dreaming
Literally all this shows is that women are more likely to say that the workplace is toxic nothing else; they literally just analyzed a lot of glassdoor reviews and that’s their entire base for this claim.

Also for some reason I’m pretty sure that men are unlikely to backstab their former employer and instead silently move on, because they’re very likely not interested in having their future employer see them as a liability?
Edge did, though would be nice a better integration (context menu?)
From TFA, one bright side is that they're reducing the 4K addon to $9.99, down from $19.99. So if you were already paying for that, you come out $2 ahead/month.
Why are so many comments about class components, I thought we ended that debate 3 years ago?

Hooks are better because they allow you to reuse component logic, impossible with class components. They solve all the issues and gotcha's of HOC's.

Don't compare class components with hooks, compare HOC's with hooks.

The best way to grow appreciation for hooks is to try wrapping many HOC's and deal with conflicting props and "innerRefs". People seem to very easily forget the horrors of the old.

Also lets be real, hooks aren't that bad. Yes dependencies arrays and useEffect take some getting used to, but I rarely get into situations where I actually get into questionable territory. Use react-query/swr for fetching, use Zustand (or whatever) for state, and you cut out 95% of the problems.

Anyway, the new docs are great, well done, nice work!
Combat Veteran Reacts Cancelled for Covering Ukraine
Patreon has pulled the plug on Combat Veteran Commentary on Ukraine/Russia war.
Yeah I thought my copy of stable diffusion was broken at first because all my results were awful.

Then I copied someone's prompt and got really great ones.

I suspect eventually there will be tools you can just fire up with no knowledge, but all of them I've seen so far still do require a bit of expertise and time.
I think it's sufficient to say that having been exposed to hundreds of thousands of lines of code across different industries and programming languages, I don't like React Hooks, and I don't even like them repurposing the word "hook" which is otherwise known as a trampoline in other programming language contexts.

React Hooks, if anything should have just been called React Callback Queues.

As for emotionally charged words, maybe it's not appropriate in the current zeitgeist to post without some degree first of self-censorship, but it's how I feel, so I'm going to say it.

React Hooks were fanatically adopted, in my opinion. Side effects are a regular part of programming. I find it, thusly, infantilizing to hide those details.

I wish people would stop this sort of thing, but if you want to say your part and that's how you feel, say it too.

Edit: You've apparently even been downvoted for expressing this sentiment, which I hate on HN, because it's how you felt. I wish social sites wouldn't do this. No one should be able to invalidate that.
You don’t run heaters when the weather is moderate.
The other way to think about this, how much of our phone use when driving is because of lack of public transit and the requirement to commute to work? There are different ways of addressing the same problem.
But good pay and benefits can be taken at any time in a right-to-work state. And the pay is not consistent or transparent to quote adjectives from that section.
This was flimsy all the way through, but loses all credibility when this part rolls around:

> It risks poisoning the well of collective thought, and of our ability to think at all. ... To place all of our trust in the dreams of badly programmed machines would be to abandon such critical thinking altogether.

The author seemingly couldn't resist leaning all the way into hyperbole and made the ridiculous claim that human beings will no longer be able to think once AI really takes off. The unnecessary name calling in saying that LLMs are "badly programmed" is the cherry on top.
Did you look at CSS-in-JS/TS that is exactly this?

https://styled-components.com/

https://vanilla-extract.style/
Unionisation, I'd wager, will come to the tech world a lot more.

No one cared about unions when they could easily find new jobs.

Now that's not so certain with the rise of AI. (Edit: and all these redundancies, yes)
Every now and then when I've got some time to kill I'll go look at old comment sections (particularly when Dang links previous iterations of a discussion) and compare it to what I see today. It turns out that the quality hasn't changed greatly, though viewpoints, popular gripes, etc may have. I've discovered that a lot of my thoughts about "hn is going to shit" are usually better phrased as "I dislike that this viewpoint is popular now" or "I've come around to seeing that differently". Particularly when it turns out I preserved my old viewpoint in the form of a comment on the old article.

A related thing is: look through places where the crowd skews young/newb like r/programmerhumor. You'll see arguments, discussions, etc about things that might make you think "I thought that was settled ages ago" but in reality were just things you got experienced perspective on, and/or grew out of.

People grow and change - usually in a slow and steady way that's hard to see in the mirror. I suspect you've picked up a lot of knowledge and some new perspectives - a few years is a long time!
This hoary take irks me. There were still places for human endeavour to go when the looms were automated.

That is no longer the case.

Think of it instead as cognitive habitat. Sure, there has been habitat loss in the past, but those losses have been offset by habitat gains elsewhere.

This time, I don't see anywhere for habitat gains to come, and I see a massive, enormous, looming (ha!) cognitive habitat loss.

--
EDIT:

Reply to reply, posted as edit because I hit the HN rate limit:

> Your job didn't exist then. Mine didn't, either.

Yes, that was my point. New habitat opened up. I infer (but cannot prove) that the same will not be true this time. At the least, the newly-created habitat (prompt engineer, etc.) will be miniscule compared to what has been lost.

Reasoning from historical lessons learned during the introduction of TNT was of course tried when nuclear arms were created as well. Yet lessons from the TNT era proved ineffective at describing the world that was ushered into being. Firebombing, while as destructive as a small nuclear warhead, was hard, requiring fantastic air and ground support to achieve. Whereas dropping nukes is easy. It was precisely that ease-of-use that raised the profile of game theory and Mutually Assured Destruction, tit-for-tat, and all the other novelties occurrent in the nuclear world and not the one it supplanted.

Arguing from what happened with looms feels like the sort of undergrad maneuver that makes for a good term paper, but lousy economic policy. So many disanalogies.