skysight-inc/HackerNews huggingface dataset:
Have you tried the alternatives? We went with Odata, and it's hell. It's fine on the client side, but it's terrible to work with on the server-side. We went down the C# path because everyone else is either using RPC or GraphQL, but even Microsofts own libaries don't work together. The model creatirs for Odata and Entity Framework sort of work the same, but are also different enough to cause some real annoyances and once you add asp.versioning it becomes even worse. We went with Odata because we had a hefty client that consumed Odata through a client library that we build ourselves, and at the time it seemed like it would be fine. A year later it turns out that it would've been better for us to rewrite everything to work with GraphQL, and, we may actually end up doing that eventually because the Odata .NET support is so terrible that we're constantly having to rewrite parts of it to get it do things that are trivial in GraphQL.

You can of course go other routes, we took a serius look at tRPC, but it seemed like it would end up being a lot of work. Actually quite similar to how doing the things you want from a frontend perspective is a lot of work if your backend is "just" rest.

> Last, I don't understand what Netflix does that is so complex that would warrant something like gql. I just don't.

If you dig into the other blog points that the OP link to you can see that it's because they needed better performance, more security and better control of the flow. I think you may underestimate how much you get for "free" when using graphQL. It has so much adoption, that there are so many tools that you won't have to build from scracth, even if you're Netflix. You can see our Odata library as an example of this, there are client libraries that we could've used, but they're bad. So we had to build our own. With GraphQL we wouldn't need to do that.
> If the marketplace has a gradient of options,

Unfortunately, we're starting from a default position where there really aren't, not in terms of the scope of supply and demand. Instead, the base position is in-office work, and the RTO's and Management would all argue they're the ones doing what you're suggesting here, and it's the WFH people being unreasonable, afterall, the workplace policy explicitly says to come into the office, at exact times, with exact places for you to go and do your work, and that's a policy that's been the default since the modern incarnation of "employment" and office work came to be.

So you can't just quit and go work somewhere else that matches your "culture", because the policies in place at most of these companies aren't crafted to fit, synergize or otherwise work with the companies culture. Their largely born out of legal liabilities and ongoing service contracts and legal agreements and leases and stuff that would be expensive to break.

Doesn't mean it can't be done, but they take one look at all that and start to panic as that is such a huge fundamental shift in organization, because the worst shift of all for going WFH for existing offices is that fear that middle management has that their employees can't be trusted, because they haven't trusted them or treated them with respect or really treated them as anything other than a disposable cog in the machine. Sure, plenty of places do care, and are transitioning/embracing WFH great. But we're talking about corporate America here and the trend setters and large employers that tend to set the pace and policy of the rest of the corporate world. There is no empathy when the bottom line is threatened for many of these institutions, and while they may even agree the end result would be superior to the previous way, they all too often view the cost of transition too high to be worth it, or at least, too high to be able to sell it too investors.

I am glad the discussion is happening though, that alone is such huge progress that me in 2019 wouldn't have expected in the next few years.
I love that the FAANG companies claim to be "data-driven" and AFAIK not a single one of them has shared any data to prove it makes sense to RTO (because it doesn't, they're trying to get people to quit, not be more productive).
The iteration is faster than asking a person to do the same tasks. I've started toying with the API to address the interface bit, though.
Not 80 GB/mo, but they're still pretty huge after compression. Zstd compressed comments and submissions for Feb 2023 were ~34 GB.
What am I missing here? Sick, homeless people somehow linked to the gay community?

Can you connect these dots for someone who is not in the know?
> selling glyphosate for residential use

What's wrong with glyphosate?
something like tinymediamanager?
I don't really know about the current state of hiring in the different sectors. What I can say from my experience doing some IT projects for manufacturing, is that the one thing they surely would never do was over-hiring of IT people and other support functions.
This is one reason I’m glad I came from a research background into software. If something doesn’t work it doesn’t upset me and I don’t personally feel aggrieved, you just chalk it up to experience and move on. The number of times I worked on a study that had to be abandoned either because it didn’t work or because another research group beat us to it!
Hydrothermal Fluid Activity on Asteroid Itokawa
You could ask the same of yourself, presumably you have a retirement account invested in things that grow…
Someone posting “Why is X?” questions, should first have to show that X is happening before we have to argue about the why of it.
I’m less interested in “objective good” and more in “I know I have agreed to something and I am not doing it for [reasons]”.

I wonder how the poster feels about telling his employer about his decision to stop working on some days? Maybe he would be fine with it?

Again I don’t care about his employer, it could be the biggest prick in existence and deserving of whatever ugly came to him. This is about your own soul, so to speak.
Ask HN: Does your home ISP use NAT/PAT or CGNAT?
I just upgraded from cable to fiber and while I was glad to finally get symmetric, I was shocked that not only do I even not have a public IP, I can't override their DHCP or DNS settings without adding my own double-NAT. Cable had a dynamically assigned public IP and let me use the modem as a bridge.
Put this into the "my code is self-documenting" bin.
Unlimited on our scales! Anyway I was making a pedantic comment about how 100% reused material is unreasonable given the laws of our universe.
Because even in the 70s gynecologist practices were already significantly changing due to women doctors entering the field. Claiming that something so easily changed isn't done because "the entire field of gynecology is founded upon intentional sadistic torture of women by male physicians" is totally ridiculous. It's so far divorced from reality that it's lands you in troll territory.
Myrmecophytes (Ant-Plants)
Furthermore, in this case there were actually two commits related to the bug. An older commit that introduced the race condition, and a second commit that triggered it (by subtly changing how long a certain function took to run).

The long bisection process identified the second commit but it took further work to identify the true cause of the bug.
Exactly, they don’t wanna pay it either. Plus, the negotiated rates have nothing to do with whether or not a patient bill will be “approved”.
That's why I have it iterate on a spec first, and then an outline, and then specifics. The point is to have it produce something that narrows the scope so I can feed it specific sections back in again and have it fill in the details.
UN to unmask fossil fuel lobbyists at climate talks
> juniors asked to implement the architecture but don't really understand it?

Can you reasonably expect a junior engineer to push back here and generally get traction? If this architectural decision has been made, it’s been made. At higher levels.

>If everyone had better system design knowledge

I don’t think this is a junior devs fault - they’re junior, after all.

> but then it doesn’t work because the organization…

Bingo.
You’re comparing it to what is probably the most realistic game since the PT Silent Hill demo came out, and heavily based on photogrammetry. The paper also focuses on natural textures, not built up environments, so it’s a pointless comparison in multiple ways.

Again, not a contest. The paper is exploring new techniques for generating content. Why all the negativity?
> surely people understand that those messages aren't private to begin with, right?

For some reason, this is really hard for people to get. The discord company is super paranoid about scraper bots joining through public links, and people themselves are continuously in awe when someone digs up an old message about whatever, asking the mods to ban them for doxing.

I completely agree with the sentiment, however, and I think it should become more socially acceptable for some chats to be viewable online, like forums used to be back in the day. Even then, people would close certain subforums off from appearing for people without an account (e.g. in public searches). As it stands, however, people are not comfortable with this because nobody is doing it.
“Failed” Antibiotic Repurposed as Herbicide
> A 20 minute in person chat over a whiteboard can save weeks of back and forth on written communication.

We noticed this as well. Now we come in at least once a week. Is there any way that the same level of speed of collaboration can be achieved remotely? We use all sorts of tools but we've not been able to achieve that kind of productivity and it honestly irks me.
If you’re a team of 6, and 66% of you can go into a room and without prompting, why can’t you just dial in the people who are working remote (if they’re available). If they’re constantly not available, maybe there are other reasons they can’t come that should be followed up on. I just don’t believe that most of your team is not busy and then all of the remote workers are never available at the same time.
Working remotely is a culture. It is very easy to turn your ad-hoc in-person meetings into ad-hoc “here’s a link to an online meeting”. Get your work to buy you an iPad Pro and an Apple Pen and you even get the whiteboard experience.
I have worked in many places where teams are located in different states or offices (but still work in the office). Is it okay to not engage a 1/3 of your team because they work at a different office? What if you’re the app team and your network has issues, but the network team is in another building? Do you just not dial them?
Lemmy.world is 31k users alone. Beehaw.org is 12.k users (and each of those users at Beehaw.org were manually curated)

Maybe 150,000 is wrong, I saw it posted somewhere but I'm not sure what the methodology is. But between Lemmy.world and Beehaw.org we're already at 43k+ users.

27k is a gross underestimate.

-------------

EDIT:

https://kbin.social/nodeinfo/2.0

https://fedidb.org/software/lemmy

Lemmy-fediverse is claiming 159,000+ users today.

EDIT2: kbin link must have been glitched. kbin.social's specific nodeinfo is "only" claiming 35k users, which is still substantial.
I work at bandwidth and would also love to know what you don’t like with messaging at least.
I preemptively attempted to respond to this:

> (Ok, there are sharded reader count variants that reduce the cost of the reader count, but they're still only useful for relatively long reader lock sections.)

RW locks are a code/design smell, even with a cheap reader count.
"Thanks God" from "Gracias a Dios"

^^^ this is kinda weird considering Cuban Spanish omits the S (and often half the rest of the letters in any given sentence, lol, at least to my lower intermediate Spanish ears), resulting in "Gracia Dio"
It is surely solving a promotion problem and a bonus-getting problem for someone in their hierarchy. Plus it is making the world a better place through constructing elegant hierarchies for maximum code reuse and extensibility and through minimal message-oriented transport layers.
Maybe. Would prefer to approach it differently before cutting out so fast
Stone OffRoad Design
Rent it out to strangers, let friends live there for free if you want. Do anything other than letting a home sit vacant when there are tons of unhoused people sleeping in the street.
Demolition man as well.
I'm not a big fan of context variables: they're basically a super clunky kind of goroutine-local global variable, with all the problems you might get with these kinds of mutable global variables. I would argue that if you're having to pass dependencies down, you should be explicitly dependency injecting them instead rather than implicitly via context.
I feel that perhaps you prefer, or simply didn't notice, the changes. Maybe you've always worked for huge companies.

Remote work requires that Zoom calls and chat are used for almost everything, even if only 10% of people are not present.

Prior to coronavirus this was not how any of the companies that I dealt with worked (small companies with <5 offices). Some meetings were remote, but most were in the break room with real faces.

As a result, I left software development during the pandemic to pursue a life with more social interaction.

The cerebral element was balanced out for me before, then it wasn't.
I have the same experience as you - there's very little obsession with productivity with anyone I knew.

Hacker News, the very forum this person is commenting, has far more comments complaining about an "obsession with productivity" than actually obsessing over it.
1 IPv4 (and thus my router (not ISP-provided) does NAT), /56 for IPv6, both rotate every 24h
One of the pros of monoliths is that each individual functionality it provides is so simple that it doesn't need to be rewritten.

Micro services replace your unmaintainable bean injection XML abomination with 50 reimplementations of database access and a salary for the one guy who knows his to make your kubernetes setup work.

It's not a technology problem, it's a people problem. Micro services make it a distributed people problem.
True. My full frustration behind this question is that some people oppose regulation saying that the free market will solve the problem, then later when the free market has not solved the problem I ask my question, then they say that it's not something the free market can solve or we just have to wait longer for the solution to arrive (meanwhile, people are suffering or dying). There is a balance to be found here, free markets have their merits, but I do hate to see ideas dismissed because of a hand-wavy claim that the market will fix it.
Totally possible that it was an invalid denial, too. I don’t know if insurers face any consequences for just denying some percentage of claims initially, and then only paying out for customers who push back.
I might be the luckiest person in the world, but my first real job (full time), was during the pandemic and straight WFH (I have worked on premise for years before that. Part time, as a student). I feel such a good connection to my colleagues, some of whom I have never met in real life. Honestly thinking of inviting a few of them to my wedding. We always tattle before and after meetings, we have our own injokes, I've been welcomed and cared for really well as a new employee by them. Work is going really well, and even in stressful times I always feels like my colleagues have my back and I have theirs. And every once in a while when we do meet up, its like a family reunion.

Jeez, now that I'm thinking about, I really do have struck gold. Maybe I should stick around a little longer before I make the jump to a (even) better paying job...
> Lemmy's current bottleneck seems to be RAM

Rust seems like a sound choice in that regard because it's not garbage collected, so you're not wasting some RAM overhead just to avoid needing to do extra work, and it doesn't have C-style struct packing issues. If you don't specify the layout you need for a user defined type, Rust will assume you are OK with it re-arranging your data structure to be smaller / faster.

If you're willing to put in some work you can often go further with this in Rust than in other "systems programming" languages too. For example C++ Strings have the "Small String optimisation", exactly how this works varies but e.g libc++ (on a modern 64-bit server) String is a 24 byte data structure which can hold up to 22 bytes of textual data inline without yet needing a heap allocation. So if you do a lot of work modifying small amounts of text, Rust's built-in String isn't as efficient as a libc++ String, but the CompactString type from a popular Rust crate is also a 24 byte data structure yet it holds a more impressive 24 bytes of text before needing heap allocation.
Atmos is a scam to sell more speakers. The spacial audio is the same lame fake surround sound trick that never sounded good. Either listen to Atmos mixed music, famously hated by artists and producers alike, or just listen in stereo and enjoy the music.
> I think you might be talking about "false sharing." This is real contention on the cache line due to co-location of apparently unrelated variables.

You’re right. And cache lines are quite small, so this is probably less common. Yet, it’s another potential source of perf regressions in concurrent code, as if it wasn’t incredibly complex already.

> Ehh.. only the hot ones matter.

Well.. first atomics have even more non-local effects, such as barriers on instruction reordering. So Arcs that are cloned willy nilly can still be significant, with no contention.

But let’s ignore that and focus on the contended case: when you hear “uncontended X are basically free” it (subjectively, imo) downplays the issue, like contention is some special case that you can compartmentalize and only worry about when you consciously decide to write contended code. The blog post demonstrates exactly how this is so easy for contention to creep in, that you have to be superhuman levels of vigilant and paranoid to spot these issues upfront. Extremely easy to miss in eg code review.

I think both compile- and runtime tooling could help at least partly here. I’d also give rust some credit for having explicit clone instead of hiding it.
It would be wise to disclose that messages are archived publicly. But you also don't need to archive the identity of everyone in the chats, you can replace their usernames with generic identifiers in the public archive.
Got it. That makes sense. Thank you. But what about the quality then? Can the quality of 13B model be the same as the quality of, say, 30B model?
What makes you think the US like it? I don't have a link readily available but I would bet my shirt that a large majority of the country is tired of the 60/70+ people running for president. But hey, you only get to pick between the 2 that were already pre-picked for you (out of the dozen that was already vetted).
Umm, uOps are exactly like the old horizontal microcode, down to the ability to jump out to patched out instructions...

The simplest horizontally microcoded CPUs had their "decoder" be essentially mapping into microcode ROM, where said microcode contained instructions that directly drove various components of the CPU, coupled with some flags regarding next micro-instruction to execute.

Many instructions could in fact decode to single "wide" instruction, with sequencer-controlling bits telling it to load the next instruction and dispatch it. Others would jump to microcode "dispatch" routine which usually was uOP(s) that executed advancing of program counter and triggering load of next instruction to appropriate register then jumped based on that.

Usually multiple wide instructions per macroinstruction happened either for complex designs (there were microcoded CPUs whose microcode was multitasking with priority levels!) or when decoded instruction mapped into a more complex sequence of operations (take for example a difference between an "ADD" between two registers and an "ADD" that does complex offset calculation for all operands - or PDP-10 style indirect addressing, where you'd loop memory load until hitting the final, non-indirect address).

To make it simpler, it was common to make microcode ROMs have multiple empty slots between addresses generated by sequencer, so that you avoided jumps unless you got really hairy instruction (largest possible VAX instruction was longer than its page size).
I´ll take your negative and raise a positive:

Substantial global progress has been made in reducing childhood mortality since 1990. The total number of under-5 deaths worldwide has declined from 12.8 million in 1990 to 5 million in 2021. Since 1990, the global under-5 mortality rate has dropped by 59%, from 93 deaths per 1000 live births in 1990 to 38 in 2021. Globally, the number of neonatal deaths also declined, from 5.2 million in 1990 to 2.3 million in 2021.

https://www.who.int/data/gho/data/themes/topics/topic-detail...
> If you say "get down from the car," you're (likely) using that phrase only to people outside your environment. It's lack of fluency.

Fluency doesn't mean you never make such mistakes, and it also doesn't prevent you picking up unusual phrasing from your environment, even when it might have originated as a mistake. In a heavily German but English-speaking workplace, it's not just the Germans who use “until” to mean “by”.
IMHO, Rest works just fine. If you are serious about performance I don't really get how you do that with GQL. maybe I'm just ignorant but the apps I've worked on were medium to large size and it was a fricking nightmare (apollo-based, a couple of years back).

Here:

https://hackerone.com/hacktivity?querystring=graphql&filter=...
> This obsession with grinding and hyper productivity is out of hand

This is ridiculous. There's far more overdramatic denouncements of an "obsession with productivity" than there actually is obsession, especially on HN where one regularly sees hyperbolic comments like the above.