skysight-inc/HackerNews huggingface dataset:
> likely to make the land it stands on completely worthless.

Sorry, what? Are they building the pylons with nuclear waste? How could land depreciate?
In 1982 I got a Commodore PET 2001 which my mother rented-to-own when I badly injured a leg and would be immobile for quite awhile. I started playing the games off of the cassettes included with the machine and at some point I typed "List" for the first time. That opened a world that redirected my entire life. I started trying to understand the code and alter the games so I could cheat. Then tried to replicate how the games worked, then made new games, and on and on. The accessibility of that process is rare today.

While countless computers have come and gone in the ~40 years since, I still have that PET in my basement.
Overall I'm excited to see this, as much as I don't need one more subscription (and have a very legacy, free, personal GSuite for a custom domain so I can't use One anyway).

Maybe this is a strategic transition to a more consistent, less advertising dependent Google.
That's alot of people for the Netherlands. in 2019 there were 661 traffic-related deaths. The relatively new e-bike is already 10% of all traffic deaths. E-bikes cannot become new death machines on cyclepaths. The cyclepath is for cycling and assisted cycling.
The newer benchmark would be "how many hours does it compile Chromium?"
> And how exactly would that have competed with five hundred other brands that didn't pull that trick?

I think I agree with the point you're making but I still feel obligated to point out that cheaper and better printer (like the brother laser pointed in the other thread) isn't stopping HP from making huge bank with their ink scam for decades.
Client side caching with a normalized cache implementation is very hard to get right. I see why you would want that feature and if it were simple to implement I'd always want to use it. However I think we can get away with a solution that is a lot simpler than normalized caching. With persisted Queries we can apply the "stale while revalidate" pattern. This means we can invalidate each individual page and would have to re-fetch each page in case something updated. This is some overhead but the user experience is still very good. Normalized caching in the client can get super hairy with nested data. In addition, normalized caching adds a lot of business logic to the client which makes it hard to understand the actual source of truth. From a mental model it's a lot simpler if the server dictates the state and the client doesn't override it. If you allow the client to have a normalized cache the source of truth is shared between client and server. This might lead to bugs and generally makes the code more complicated than it needs to be. Is it really that bad to re-fetch a table? I guess most of the time it's not. I've written a blog post on the topic if you want to expand on it further: https://wundergraph.com/blog/2020/09/11/the-case-against-nor...
Terminals are interesting vs the history of our industry. AFAIK the VT52 was a random logic design (as is this reproduction), while it's successor VT100 had a CPU. Terminals were one of the driving applications for microprocessors. The PC is essentially someone noticing that the terminal now has a useful CPU in it and asking why not run applications on it?
"progressives... have a complete monopoly over the relevant cultural power"

Can you really make that claim, in light of the current political climate and in-progress election results?
This problem is solved at the db layer. If your data is not queryable in an efficient manner from the DB then it doesn't really matter if you use REST or GQL.
Btw, how specific is the American CAN-SPAM act in terms of how the unsubscribe link should work? In my country I sometimes get emails with unsubscribe links that require you to log in first, which can be a pain to pull out the credentials when you don't really remember signing up for it in the first place. Does CAN-SPAM specify, say, that an unsubscribe link 1)must not require a login? 2)must lead to completion of the subscribe process within x steps?
Many Apple Products Have Revenue Whole Companies
- Hardware support out of the box

I can be given a work laptop, slap some Debian or derivative along with XFCE, and I know that most hardware will work out of the box without much fuss (including but not limited to: webcams, video cards, wireless/bluetooth, thunderbolt docking station).

- Containers

They're just very good. FreeBSD looks like it has most of the pieces to get containers going but it's not their priority to get that going. The people at Joyend did that, reimplementing the docker server APIs to manage underlying zones. I wonder why don't FreeBSD do something similar.

- Reference documentation

I like to use RHEL and derivatives (CentOS) when I can, and the reference documentation its so, so, so good, ample and complete. The FreeBSD reference guide is good, but not as thorough and/or up to date as the RHEL documentation.

- systemd & NetworkManager

They're rock solid, battle tested and well-thought. systemd is much more than init and does a lot of system management, stuff that previously was simply not being done by anything else. BSDs lack that completely -- see https://www.youtube.com/watch?v=o_AIw9bGogo
The Worst Lessons I Learned from Silicon Valley
> progressive movements like BLM and MeToo are absolutely attempting to preserve the existing order

I so wish this were true. If we lived in the world BLM envisions, George Floyd and while lot more people would still be alive.
They aren't.

There is just a lot of anti-patterns floating around because of tightly coupled API / DB's.

People apply this same logic to GQL and get confused.
I have worked in Coventry for a year and I stayed in Birmingham as the hotels in Coventry and area are depressing. As the restaurant options are much better in Birmingham compared to Coventry.

Did enjoy the small Chinese place in the city centre though :)
The important idea here IMO is that "free markets" don't exist and don't drive anything. States create policies (Ideally, these policies would be entirely democratically chosen, alas that's rarely how it works). Markets appear. No market can make any meaningful decision on what to do and where to go at any time out of day to day operation.

Unfortunately the EU commission (and most of our governments) seem to believe that "let the magic invisible hand of the market work, and all will be great". Not.

On another note, it's fascinating to see that about 80-85% of our energy in Europe is from fossil fuels. A very large (and rapidly increasing) part of these fossil fuels are imported (because North sea is in rapid decline), often from quite unpleasant countries (Russia, Saudi Arabia, Qatar, etc). But apparently noone in power seem genuinely interested in sorting out this big problem in a way that would be advantageous to the European public (not even mentioning the climate). Some actively behave like foreign agents, in fact. Go figure.
I’m glad more attention is being shed on the anti-liberal and fascistic impulses of many of the modernists. That doesn’t mean they didn’t write or think valuable things, but it’s something that sometimes gets elided in discussions about them.
"but there is no current, concrete data on the effects that the rehabilitative training or manual approaches could have on the patient; in particular, on his/her cognitive and cerebral aspects in general."
Except emulation has a good bit of a performance penalty.
But since when does using a known word for it's intended meaning is adopting ? It's just the right word. They did not adopt the word camera for their camera, it is what it is.
1. CLOCK Freq if any

2. Idle and active power consumption.
I agree. Sometimes it seems like GraphQL degenerates into a generic REST API where you construct and pass the SQL directly from the client.
Thank you for your input. If you happen to be on a machine that doesn't have your usual setup, please consider using our platform. It's super useful if you work with other people remotely as you're able to work on the same notebook in near real-time[0], see each other's cursors and changes, etc.

[0]: I've received some remarks about the fact I say "near real-time" and not "real-time". We have too many people from an Electronics Engineering background, including myself, on the team to dare use the term "real-time" for a web service. That's why we say "near real-time".
somebody's going to tell you that you're using it wrong, probably.

I swear by XFS and ZFS.
I tried Hasura's GraphQL implementation. I liked the ease with which you can set row/column-level permissions.

However, REST is so much easier to build and query. Normal APIs use GET requests which are easy to cache in a cdn. GraphQL uses POST by default and to cache that you need to convert the request somewhere, either in the cdn or your web server.

At the end I realized I was just messing with it for a small project to learn it. It really isn't worth it IMO. The problems it claims to solve can be solved with REST provided you understand the issues.
Think it's important we set the context to be around Arch Conf, where we're talking about hosting recordings from the conference.

In this case: Yes, if they do run their own servers for storing the content, they are self-hosting. No, doing your own peering is not needed to be classified as self-hosting. No, you don't need to run your own data center to be self-hosting. Unless you want to self-host the servers themselves, then yes, running your own data center is needed.

I think the most important point is "hosted" vs "self-hosted" here, where hosted is letting someone else run the servers where you put the content, while self-hosted is you running the servers where you put the content.
The future is REST APIs wrapping custom JSON APIs, exposed with GraphQL on serverless k8s all wrapped in a VM on a Raspberry12 in some kid's locker, which itself is simulated on a large instance on AWS.
I have never once in my life "signed up" to a mailing list. The only reason I can think of that I receive so much spam is from sites where I've used my email address selling that information to others, or otherwise leaking it.
You can use tools that will automatically generate GraphQL schema and operations from a database or it should be you design the schema & operations and control how the queries and mutations operate. The former is where some of the original concerns may come from, but the latter isn’t different from REST design.
Does anyone know if there's any projects underway to make a mechanical version of this? I would pay a lot of money, and I know several internet communities that would crowdfund DIY or prebuilt versions within instants.
I very much appreciate the author's approach, and giving a sober perspective on GraphQL. Working within the Shopify ecosystem, they have invested heavily in GraphQL and I don't like the UX, nor do I find the reasoning to promote it over REST particularly convincing. It has been much more difficult to grok GraphQL over REST and I don't think I'm alone.

There are likely specific use cases where GraphQL > REST but the barrier to entry is so much higher that I think you'll continue to see the interest wane[1] unless something dramatic changes

[1](https://trends.google.com/trends/explore?date=today%205-y&ge...)
For better or worse AMD has always been much more willing to quickly throw everything out to go with a completely new design paradigm. Something it was a massive bust like X2 or Bulldozer. Sometimes it's the Athlon or the Zen.

The only time Intel really did that was with the end of the P4 and frankly even then they waited as long as they could before doing it. The rest of the time it's all carefully planned stepped increase and safe design change.

Both have their advantages, but for your question it means Intel will have to take a leap they clearly don't like taking.
Wow this is a fairly harsh reply to the parent. Their point was merely that LIDAR is already a known thing; you would say “Apple adopted the term GPS for their location device” either. Why would anyone need to “adopt” a term that’s industry standard?

I agree that it’s not as if the author claims that Apple invented the term, but asserting the parent lacks “basic reading comprehension skills” is a bit mean, don’t you think?
Facebook, the inventors of GraphQL, didn't just invent the language itself. At the same time they invented the Relay client. This client, back then, persisted all Queries at compile time. They never had actual Queries at runtime. It's Apollo with their Apollo client who made it popular to not follow this path. The devs at Facebook never said you must use GraphQL their way but I think if you don't follow their best practices you're kind of on your own. Why not follow their advice? They must have learned this lesson already.
Could this be a situation where politicians have faulty data and use that to guide how they act? I would have assumed that a majority of these states - and my home state of NJ - would be very anti-drug but these votes with >60% in favor of legalization show that significant portions of America think drug-related activities are not "immoral" or "wrong" and should not be criminalized.

If you had asked me a few years ago if I thought this was what the general American populous thought I'd have said no because, of all of the politicians who advocated for legalization of drugs, very very few got elected.

Maybe now that politicians see that people are very against drug laws we'll see some of them renege on their hard anti-drug stances.
Regardless, Google charging for these services bodes well for other consumer software shops because it is otherwise an uphill battle to compete with "free".
> Twitter "threads" need to die.

I would even remove "threads". Sick of all the hate and fakedom.
GitHub warns of bans for users still distributing YouTube-DL
Yeah if you have a fixed number of well-known queries that you support then a plain old REST API is superior in pretty much every way
They do, actually. Consumers make choices, you know. They want things. Them not caring about the environment is a very realistic and actual theme, because that is exactly what is going on. No one giving a substantial shit, only talk, no walk.
Failure Demand
Yours is much better/cheaper
> But you can't move out of the global village.

Elon would like a word with you.
Or simply not running the hydro. Which if there is sufficient reservoir capacity is even better.
Podcast Apps Generate Revenue
No we don’t know how to use them. The abilities of single systems have far outstripped our ability to manage all those resources. It takes a lot of work to drive a system like this to the rails, and very few people even bother trying. The closest most people come to exploiting a machine this large is by carving it up into normal-sized virtual machines with independent operating systems. This makes the utilization look acceptable but in reality much of the resources are just being squandered.
Do you have ideas on how the situation could be improved at Shopify? What makes it hard to understand? What's missing?
If you were guessing valid tokens why would DoSing be more valuable to you than use of the token?
Drash v1.3.0 – A REST microframework for Deno
How many features do teams tend to build that use exclusively existing data, versus new data? How much existing data is lying around that isn't already exposed via API?

I'm not sure that the query layer solves team collaboration and prioritization problems.
The cost of decommissioning a wind turbine is a simple disincentive, approximately the same as installing it in the first place (although data on this seems scant and dependent on several factors.)
Trying to use millions of generated tokens is not really feasible.
Most services will throttle or block you quickly. Also often you would need to know the permissions the token has to get any access.

Writing millions of generated tokens to a text file and pushing them to Github is easy.

There is obviously no meaningful benefit to doing this, except potentially breaking some random deployments until they can replace the keys.
Rational order from ‘irrational’ actions
In an ideal world, this is how
Depending on which branch of the company you're talking of (fab design, chip design, ...), and based on what info you can actually get on it which is less fact and more "large amount of anecdotical evidence", Intel's is between more and a lot of than 15% behind.

And while I agree with your proposed first step of the solution, and the urgency to do it given the delay between that and any impact on results, their tendency to look only for short term gains and benefits will probably impede them.

They've learned to love easy money, and they didn't need to really pay their people well because there was no serious competition, not in fab, not in chips. Now they're fallen behind on both, as easily predicted, but for a short while they extracted massive amount of money from their margin.
So scanning is only done on public repos?
Fibonacci Retracement Trading Strategy Explained for Beginners
I honestly don't think there are any use cases where GraphQL > REST. It's just a new format they convinced people to build new backend layers in, and since those tools are new, some of them do address longstanding db-admin useability issues. But GraphQL as a spec is not revolutionary. It is simply a proposed structure, more constrained than REST. GraphQL is a form of REST.

Perhaps the benefit is what ryanar writes here [1], that it exposes a useable db-admin UI to front-end teams. It seemed to me this could have been achieved with something based on REST but maybe I'm just not thinking it through.

Now that I think more, it wouldn't really be sufficient to produce SQL for a front end team because you don't want them to be able to create inefficient queries.

I guess my main gripe was that GraphQL uses POST requests and nobody told me how this makes cdn caching harder so I started hating on GraphQL :-/

[1] https://news.ycombinator.com/item?id=25015221
Show HN: Built a Draggable Menu for Vue. Adjusts orientation automatically.
For one, you have an enormous block of concrete there now.
Exeter is a very livable small city (130k people) in a lovely part of the country. I'm not saying you should have uprooted your life to move there, but for many people it would be a great lifestyle move.

There's a wider issue with UK businesses being a bit unambitious, and staying in locations where availability of employees affects their ability to grow. But there are far worse places than Devon.
Craigslist? EBay?
Well yeah, it is.
> > But you can't move out of the global village.

> Elon would like a word with you.

Really? Because to all evidence he is acutely aware of that fact.
GraphQL is great when you have multiple apps (e.g. web/android/ios) querying the same set of backend services.

It is quite hard to define REST interfaces in a way that is optimal for all clients, unless you want the client to do a bunch of extra work (n+1 queries or other type of aggregation).

The author mentions the BFF pattern which could work quite well along with REST, but has not worked out for us in large teams. We ended up with BFFs specific to each client type which all do the same things in slightly different ways and it was hard to share code and do things consistently.

With GraphQL, all the previous BFF logic was centralized in one place but each client could still fetch data in different shapes.
> uses POST by default

I've found that this leads to a huge miss on the observability side. The ecosystem of tools doesn't solve for this well today, especially when it comes to the various vendor integrations.
Is there a pure notebook version stripped of the application? I'd like to play with this on iko.ai. Already have the Coco dataset, GPU support, and most of the dependencies in our image.
I really like your answer. I think that's a very good argument if you want to convince someone to start adopting GraphQL. Do you have anything beyond that?
The 'Deep Fake' Scare Is More Dangerous Than AI-Tech Behind It
This seems to throw up the issue of a higher degree of the DB structure getting exposed to the frontend. Faster iteration of the front-end (presumably during a period of more rapid change) comes at the cost of forcing the backend to remain more static.
Yeah, exactly what I was talking about. There is no way to say this just by looking at the genome, all you can do is to say that is not very probable, and that would still be a dubious claim. There is a plenty of gnome manipulations that leave no trace. Having said that, lab origin does not neccesarily mean genetic manipulation. Serial passage through animals (say, minks) will leave no trace of genetic engineering, but may make the virus contagius to humans (minks and humans have similar ACE2 receptor). Or just poorly handled sample from the would do.
For Millions Deep in Student Loan Debt, Bankruptcy Is No Easy Fix
Oh, I did not think about that. On Android 8, you make firefox the default ... (renderer ?) for other apps but idk if it's the case for older versions of Android.
On the other hand, as others have said, these devices are generally quite painful to browse on so accessing the wweb version of many apps could be a solution, plus firefox will let you place shortcuts on your home screen . I also wonder how LineageOS works on those old devices. Could be another solution.
In an ideal world, this is how things would work. The problem is, those features were created for customers. They will not take kindly to those features being removed. And no-one wants to lose customers.

This is why the second law of thermodynamics applies also to software engineering. Entropy only increases.
Thanks for saying that. I haven’t used GraphQL but when I read about it I was like “Isn’t this basically RPC again? Like XML-RPC (for those that remember that) and SOAP?”

To me the acid test, since getting burnt by both XML-RPC and SOAP has always been “can I drop a standard HTTP proxy Like nginx between this thing the layer behind or in front to cache reads?”

GraphQL _seems_ like you can’t really do that so you end up having to build caching into your app, which in turn - in my experience - always leads to systems you can’t predictably reason about
The GPL gives you multiple options to comply with it. Roughly summarizing, either you put the source code onto the same medium that contains the object code, which is what xyzzy_plugh is alluding to, or you can put it onto a web server and accompany the object form with a written offer that it's on that web server. See section "6 Conveying Non-Source Forms" of the GPL.

The GPL only requires you to make the source code accessible to those people who also get the binary from you, not everyone, but most entities just allow downloads for anybody. It's more expensive to implement checking than it's to just allow downloads for everyone. xyzzy_plugh is splitting hairs here.
I think it would be a nice feature @tanmaigo should add to Hasura if it's not alredy there. Hasura could automatically detect slow queries and suggest indexes.
> However, I'm under no illusion that it'll prevent my unpaid work from being used by billionaires.

There's plenty of evidence that AGPL is reasonably effective at that. SaaS providers are clearly afraid of it.

> not every business model relies on keeping their source code secret.

I was never talking about secrecy and business model.

It's about allowing end users (including myself) to have some reasonable chances to inspect / update / reflash their devices.
Ad hominem attacks like this one calling him insane and questioning his ethics illustrate the author’s thesis quite effectively.
Of course there is no way. I think people need to start relaxing. Trump has lost, so stop being afraid talking about the lab origins of Covid.
> Senate Judiciary Committee Chairman Lindsey Graham (R-South Carolina) and U.S. Senators Tom Cotton (R-Arkansas) and Marsha Blackburn (R-Tennessee) today introduced the Lawful Access to Encrypted Data Act

Lindsey Graham is a turtle.