skysight-inc/HackerNews huggingface dataset:
> simply replacing REST adds resolver complexity [...]

To put it simply, even with REST, you're already dealing with the concept of "how does clients get a handle of a particular entity?" With REST, the answer is usually muddled by client data fetching mechanisms and backend architecture that you've opted to use - so just because two projects are doing REST does not mean they're handling these entities in a similar, understandable nature and it requires a lot of background context, same with auth.

graphql makes all that a deliberate matter instead. So take whatever's in your db, decide which fields are you going to expose, and write resolvers that return just that - you can't get any more foolproof than that, it's basically the same thing you do with REST, just without all the client-side fumbling and coordination.

But what I'd argue the thing it does best, is that with REST, you'd probably write code for handling Entity A, and if Sub-Entity A and B rely on Entity A, you'd probably write specific code to ensure the right entities are returned in your endpoints. With graphql, you just reference that entity and it's resolved automatically, because you have written the resolver for that entity already. Resolvers have access to the parent entity that's referencing it, so if Sub-Entity B has stricter controls in what it should expose, the Entity A's resolver can be written to accommodate that (see directives among other ways for how to scale this better).

As for auth, whatever middleware you're already using in your REST endpoints can also be reused one way or another for the gql endpoint, no issue.

> this hyper graph thing is only valuable with other graphql services.

Even without other graphql consumers/services, there's huge value in not having to write multiple ways of handling a certain entity anymore, among other things.

> So, I guess graphql can be good if you marry it and go 100% all in?

All of my recent work related to graphql happened in projects that incrementally adopt it - there's no requirement whatsoever to fully commit to it 100%. It definitely helps that you can reuse whatever your REST endpoints use to comprise code that builds up towards resolvers, like util/helper fns. Nothing stops you from serving the same entity in both REST and graphql forms, heck there's specific usecases that benefit from it (i.e. maybe your mobile app can't keep up with it yet, and you're trying it out for web for now etc)

Say, in such kinds of projects, what I can recommend is identifying a subset of entities that your backend serves that you think (at least superficially) will benefit from it e.g. a relatively new entity that is essentially WIP across releases, and you'd benefit from at least not having to redo the entire REST API endpoint subset for this entity whenever you're making drastic changes, or a particularly old one that could use a rethinking anyway, among other use cases. After a couple of releases you'll get a feel for how it works, and then it'll be enjoyable to port more of the entities later on.
There is an option to block media elements larger than a set size[1]. When a media element is blocked through this setting, the element is replaced with a click-to-load widget, so the layout shouldn't change with this option.

[1] https://github.com/gorhill/uBlock/wiki/Per-site-switches#no-...
> I'm not simplifying; many have not learned of the concept of software licenses in the way many FOSS contributors have.

Just give it sometime and you'll see many examples of that in this very thread. Everytime the topic of opensource license comes up, there will surely be a comment that conflates "source available" with "opensource" or even worse insist that "source available" also qualifies to be "opensource". It is like words don't mean anything anymore. It is like apple is apple and pear is also apple because it looks round and we can eat it. stops ranting. Coming back to this post, I think it is valuable to explain opensource from first principles like this.
> The worker in the article doesn’t say that a foreman forced her to work without a break explicitly

Okay, so because it doesn't specifically use those words, you'll just disregard the statistics cited?

And that's ignoring the fact that worker intimidation is rarely so explicit.

Not much point continuing to discuss if the confirmation bias is that strong.

> The article also links a report I can’t download due to too many redirects so I’m not able to determine how many workers were surveyed etc

Does that matter?

Your claim is it never happens. I cited a study that says it clearly does.

So now we're at the nitpicking the statistical analysis phase? Oh no, maybe it's actually 30% plus or minus 10% 19 times out of 20 because of sampling errors and that somehow invalidates the fundamental point that yes, in fact labourers do experience this type of abuse? Thanks, I'll pass.

Once again: did you think these bylaws got passed for no reason at all?

Edit: but you know, here, I'll do the work, anyway, and give you the 2023 report:

https://workersdefense.org/wp-content/uploads/2023/01/Build-...

They surveyed over 1,000 labourers, by far enough to generate a valid statistical sample. 28% of US born workers reported no breaks. Among undocumented workers that number rose to 46%.
> - Vendor Lock In. Yeah, it's there. If we have a service that uses data from S3, there's egress costs from S3 to <other provider>, but not with EC2. We've consciously accepted this lock in for the time being.

This is where I think the FCC should take action.

To the extent that this issue is a mutually agreeable arrangement between you and Amazon, it seems obnoxious but does not seem like it rises to the level where regulators should take action. But it affects third parties too: specifically, it prevents non-AWS-hosted vendors from effectively marketing their services to you. In that regard, I think the FTC should try to put a stop to this. AWS should not be permitted to effectively subsidize its and its partners’ services over outside competitors.

(And the US Government should never have accepted cloud deals with excessive egress costs. Part of the bidding process should have been a requirement for networking outside the winning provider to be priced competitively with internal networking)
I've only seen usenet clients stuck in the past. A bit like RSS and IRC. Quite the reminder how lucky we are with the success of web browsers. Email made it something like 1/4 of the way which is still nice.

The functionality of the www also changed quite a bit over the years. If we could do the same with the other clients and protocols it would be quite the something.

edit: How is it that all desktop apps had to morph into web based apps while with phone apps it is the other way around? It cant both be right.
Even better, why not go back to modularity? Many microservices could be just that: self contained modules that you can swap in and out as you see fit.
Article Title: Text to SQL for Free, powered by AI

As per HN guidelines, “please use the original title, unless it is misleading or linkbait; don't editorialize”
> I'd benefit from honing in my skills while working on my own project.

You can do these things while at university, I wouldn't take a year off.
Clean, sustainable fuels made 'from thin air' and plastic waste
The cause of action is, essentially, Twitter violated its contracts with its employees. That is sufficient grounds for a class action, assuming the contracts and the nature of the violation is reasonably standard among the class.
I'm assuming you try to keep all dependencies on the nixpkgs version?
Wow, that Flutter Doc page is beautiful... and seems fairly comprehensive, kudos to them.
Sure, but why would the code ever do anything that could result in failures of longer passwords? I'm struggling to think of a mechanism that could do that inadvertently. You almost have to do .length don't you?
In part. But also consider that because they have site-wide data along with votes and moderation-actions to train on, they're in a position to build a very competent botspam filter.

Like even as a moderator of a popular subreddit, it's actulaly pretty very rare to see the sort of link spam that would plague old fashioned forums or comment sections.
Open-source benchmark to evaluate skills of assembly robots
In terms of “just giving up and taking simple mobile notes” I can also endorse Google Keep iOS - natural affordances match my typical eng/Phil related use cases better than Apple notes.
Investors have no idea what thickness the wall should be in their building either.

Clients not being experts at the job they are getting somebody else to do is not a new pattern. So while some trust is required, it's best if you can get somebody else to verify.

I've seen a few smart clients over the years which when faced with some excuses from a software house hired another one to give them opinion about the codebase and capabilities. It seems pretty intuitive. It seems like a money well spent.
That does look cool. Would this work fine if presented with my Obsidian "vault", eg a folder full of markdown files? Looks like both apps like to operate on the same data.
And what is that reason? That they are entitled to a job at a company where 85% of people are redundant?
The term "free software" as defined by FSF always included permissive open source licenses. Do you have any link or evidence to present that supports your claim that FSF's free software definition excluded permissive licenses?
I hope Apple loses the rights to use anything related to apples in the EU for wasting taxpayers money and time. They can fuck off just as all other large companies that tries to turn the world into a corporatocracy.

EU's relatively large fines to the US tech sector has been a breath of fresh air, lets do more of that on a global basis.
MPL 2.0 is copyleft. A weak copyleft, slightly weaker than LGPL, but still copyleft.

I quite like it. It's much simpler to understand and easier to comply with than LGPL.
“ uBiome was essentially trying to growth-hack their way to a higher revenue number without at the same time providing additional value to their clients (and at the expense of medical insurers).”

This seems more like fraud or theft as currently described by the article?
Appreciate the info, thanks!
That's largely correct! To use more precise language, let's discuss two distinct phases: building and activation.

Nix will always "build" x, y, and z. But x and y might turn into a no-op by being cached in the nix store.

System activation is when all those things are symlinked into place. If x, y, and z are, say, systemd services, then there might be some logic that checks if x and y have changed and if the services are already running and decide what to do -- this is probably the most similar to how Ansible works. But this is also a small part of the big picture. Activation is pretty fast even starting from nothing.
Discord and Slack are just IRC with a bunch more features. The IRC protocol just stagnated and never improved (because it's a function of it's time). I believe there was talk of a new version with more features, but that honestly defeats the purpose of IRC: its simplicity. All of these modern protocols have more complexity built into them because that's what the average user expects.

But yeah, the fall of Discord is coming. The enshitification process has begun. Their forcing users to use unique usernames still baffles me.
To me Cinnamon and some configurations of XFCE feel closer to a traditional Windows-style desktop than KDE does, but very few distros ship either as their flagship DE.
> Ruinous Empathy is seeing somebody with their fly down, but, not wanting to embarrass them, saying nothing, with the result that 15 more people see them with their fly down — more embarrassing for them. So, not so “nice” after all.

It's not the empathy here that's ruinous but the tactic that it motivated. By that standard any feeling can be ruinous and there's nothing special about empathy in that. So why single out empathy?
Maybe I am dense, but in the examples given, the code this feature is meant to replace looks much more straight forward and easy to reason about. I get the use case here: automatically manage resources that need to be opened/closed like files etc but the syntax is way too convoluted IMO.
i should have been more explicit: "licensing fees and support for foreign companies"
You mean non-competition on the buyer side. Oligopoly baby!
This is not TypeScript-specific, it’s a stage-3 ECMA-262 proposal.

https://github.com/tc39/proposal-explicit-resource-managemen...

It’s a shame the author insisted on it looking like C# and sabotaged attempts to combine disposal with destructuring.

Also, there is no move operator without futzing around with DisposableStack. Though that could be introduced later; it’s not a day-zero design issue.
Seems that even though Towerfall was indeed the best-selling game on the OUYA, it only sold 7000 units there, while making actual money on other platforms [0].

[0] https://www.engadget.com/2014-04-29-towerfall-tiny-sales-ouy...
Which superhuman will be the first to suggest a nice game of chess instead?
The figures in the paper you linked below are log_10 scale on one axis but not the other. Thus even without quite understanding what all these figures measure, it seems to me that answer the question about "linear growth" is a hard no: double the size will not be twice as good. Or am I misunderstanding how to read these graphs?
It's hard to imagine why they would ever need to get everything out. That would be extremely wasteful. If they wanted to move off of S3, they'd rely on the same type of analysis they present in this post + perhaps creating a mechanism whereby they permanently move an asset off of S3 if/when accessed.
Net payment terms really are not part of the problem here.
Lowest friction, but yeah I agree. Reddit was useful because it was searchable and self-discoverable, and Discord does not have any of that.
Show HN: Write encrypted notes from your terminal
With just open source someone can steal your house and lock you out. With copyleft they can still "steal" your house - but not lock you out, so you can still enjoy any improvements. Company owners hate GPL because they don't control the keys.
Power companies fight Maine’s proposed non-profit utility
I keep finding conflicting information on this. It looks to me like all 50 states do have at-will employement, except when they don't. Which appears to be a long list of strange and specific exemptions. Do we know what jurisdiction these firings occurred under and whether anyone has an actual case due to these exemptions?
Might want to continue reading to the very next paragraph...

I also find it illuminating the statements Mike (TechDirt) choose to provide sources for, and statements he just declares as gospel and hopes no one notices.

The Gawker lawsuit (and then the 2016 election) really broke TechDirt's ideological position of impartial reporting. Any "reporting" involves Musk or Thiel on TechDirt I instantly have my BS Detector on full throttle.
There is no on-going work to support Metal apart from the work done by Miles. There's an old issue about it: https://github.com/diku-dk/futhark/issues/853#issuecomment-5...
To me starlink was always a way for the US department of defense to have a fleet of low altitude satellites available all over the planet

https://www.reuters.com/business/aerospace-defense/pentagon-...

Through history, CIA used plenty of front companies as cover

So no wonder criminals are using them, it's very useful to have anywhere on the planet

If it's useful for people, it's useful for everyone
Explore HDR rendering with EDR (2021)
I don't know if there is a name for it, but this is a plague for every security-related thing, or any jobs where the more skilled you are, the more people forget you (like a sound engineer for a movie production).

An ex-director of a French national security agency complained about exactly that during an interview, that you get more budget after a terrorist attack, or after you stop one that was well under way, but never if you avoided the condition to create a terrorist cell altogether, or nipped it in the bud.
GPT4 Airbnb Description Generator
Classes aren't the only way to define types?
Survey: Job Seekers Beware of Ghost Jobs
It’s ideological and not rational. Once you understand that, everything makes sense.
Am I that commentator?

I'm not advocating for anything, I guess the original phrasing of the question was ambiguous- I read it as "I don't know why my boss cares how fast I work if my work is not critical" and am answering that question.

But it can also be read as "why is it to my benefit to work as fast as I can?", which is apparently how you interpreted it.
I think the concept of being less wasteful is pretty uncontroversial, and I like the idea of creating economic activity based around reuse and recycle. But I imagine like many things, diminishing returns will make the 100% circular goal unrealistic. That being said, why not shoot for the moon? If they fail and only achieve a 50% reduction in raw consumption, that still seems like a big win.
Apparently, 5 persons onboard.

https://www.theguardian.com/uk-news/2023/jun/19/titanic-tour...
What's that got to do with the price of tea in China?
Looks good. I love how Elixir is "finished" and all these new updates are tweaks and performance improvements and stuff like that.

Is there an overview of the new standard library helper functions it mentions anywhere?
Meta Unveils Voicebox, Text-to-Speech Generative AI Tool
My V2 got stolen and I continually morn the loss. It was such a fun way to get everywhere.
>If you call it X but it has no nutritional similarity to X, that could be dangerous to consumers.

And yet nobody seems to have been harmed by the existence of these terms:

(1) Sweetbread

(2) Coconut Meat

(3) Coconut Milk

(4) Nutmeat

(5) Headcheese

(6) Welsh Rabbit

(7) Rocky Mountain Oysters

(8) Boston Cream Pie

(9) Scotch Woodcock

(10) Cold Duck

None of which refer to the nominal food definition of the term in their name.
TFA mentions as much: TypeScript 5.2 will introduce a new keyword - 'using' - that you can use to dispose of anything with a Symbol.dispose function when it leaves scope. This is based on the TC39 proposal, which recently reached Stage 3, indicating that it is coming to JavaScript.
Most of the time the pinch doesn't evoke much pain as the emotions. The pain of joblessness is not on lack of money to pay the education loan and other bills, but is caused by emotions to live a stable life after school. There are several graduates out there healing depression, not because they do not have money, but because their dream seems shuttered.
When I finished schooling and suspected that the quagmire of joblessness was staring at me, one thing I did was to develop emotional stability. I knew that if I give in easily I can ruin my life that I had went to school to better. It is not that I do not dream, I'm a dreamer and I dream big. But I ascertain my mind that keep dreaming till the dream shall come true. I can't hold out my dreams, so I have to toil to realize it and each day when the sun raises, I assure myself that this is the day. This is how I have survived to easily for these 6 years.
Upon graduation, I was expecting a good with high salary. Things turned awkward and have been hunting for job for 6 years now without success. But I have to survive and so I have been working as a freelancer for upkeep and to paying essential bills. I have tried several startups in the past but my mingle income cannot sustain them. I have a dream, and a valid one. I have researched a lot and having put my little effort in this, I believe I will have a very strong motivational story to share one day. I have started a Tech Company with prospect to grow to create employment for a couple of jobless graduates.
Which instance is that, if you don't mind my asking?
But won't Franz Kafka International airport be flooded?

https://www.youtube.com/watch?v=gEyFH-a-XoQ

(On second thought, maybe that's a good thing).
> but in reality there isn't much you can do, as a rider, to become visible.

But there's one distinct thing you can do that will help you in one of the most dangerous circumstances motorcyclists are likely to encounter.

Colloquially known as the SMIDSY weave. SMIDSY is "Sorry Mate, I Didn't See You", and the most significantly manifest as someone making a left turn (in the US) in front of a rider. This exact situation killed actor Treat Williams just the other day.

The SMIDSY weave is when you approach an intersection with someone waiting to turn, weave the bike across the lane. A simply swerve. This makes the bike stand out against the background clutter. Combined with the headlight, that swerve makes you look more dangerous than you were before so the drivers brain will highlight you. Going from one side of the lane to the other makes you "suddenly" appear someplace you weren't before.

It honestly takes a lot of concentration to do this, being aware of where you are, that there is a driver waiting to turn, and actually making the maneuver. Seems simple, but riders are in this situation more than you think.

But it is a simple technique that can reduce one of the most dangerous situations modern riders frequently encounter.
> We can clean this up with “abbreviations” (:h abbreviations):

It’s probably almost a decade since I last used an abbreviation; I consistently found I just didn’t quite like them, and migrated to other ways of doing things. It was digraphs at first, still a Vim feature, and then Compose key sequences, which is where I’ve stayed ever since, preferring them mostly because they work everywhere, not just Vim. Now I type apostrophes, quotation marks, dashes, and other interesting things as I go perfectly casually, and would hate to be without a Compose key. (I’ve typed every non-ASCII character in this comment with my Compose key—just as well I still remembered · even though I practically never use it any more.)

> You can use x and o as well, but × (U+00D7, MULTIPLICATION SIGN) and · (U+00B7, MIDDLE DOT) are more … gourmet.

I’d go more gourmet than that: I use • (U+2022 BULLET) and ‹ugh, gobbled by HN› (U+2713 CHECK MARK) for lists. If you really wanted a cross, you could also go with ‹ugh, gobbled by HN› (U+2717 BALLOT X). The ordering holds, either way: 0x2022 < 0x2713, though I cringe at unbridled sorting of these lines.

(I do all my own writing in a lightweight markup language I’ve been developing, one property of which is that it leans on CSS Counter Styles for lists for spectacular matching of source and compiled result, so that you can write “(i) ”, “17. ”, “• ”, “‹CHECK MARK› ”, &c. and get matching appearance in the HTML output—or will, when I finally get round to finishing the parser and implementing HTML conversion. I write lists with mingled •, and bullets and it’s great.)

Anyway: back to the abbreviations matter: you could also enter all these characters with digraphs (CTRL-K …) or Compose key sequences (Compose …, but since your keyboard lacks a Compose key you’ll need to map one—I use RAlt on my current laptop because that’s conveniently positioned, but I really wish my spacebar was just split into at least three keys):

• · is digraph .M or ~. and Compose sequence .- or .^ or ^.

• × is digraph *X or /\ and Compose sequence xx

• • is digraph oo and Compose sequence .=

• ‹CHECK MARK› is digraph OK and a popular Compose sequence is @/ (present in kragen’s list, as included out of the box by WinCompose, but not standard on other platforms)

• ‹BALLOT X› is digraph XX and a popular Compose sequence is @X

You can define your own Vim digraphs too (:digraph), and make your own ~/.XCompose to set your own Compose sequences.