skysight-inc/HackerNews huggingface dataset:
> maybe I'm just ignorant

Never that, but maybe inexperienced? Nothing you say is wrong, but you need to look at it from the organizational point of view. The way we build (most, all of them where I work, but I'm sure people can point to places) "enterprise" apps today, is that we have a frontend that's build in Typescript, and then something behind it to move the data.

Your frontend engineers are going to want a query language that allows them to pick and chose the data they need. You can do that with rest, but you really, really, don't want to build it yourself. Some frameworks have options for parts of it, but in general you're out of luck when it comes to things like inheritance trees on objects. So you have Odata, RPC, GraphQL, and while Odata is nice on the client side, it's not nice on the server side. RPC's work great, but they are also a lot of work, and then you have GraphQL. What GraphQL allows you to do is the combination of having an engine that makes your frontend engineers happy, while allowing your backend engineers a lot of visibility on resource drains. This means that you can work on the heavy load areas, and "leave" the others, more easily than you can with Rest where you're likely going to "over engineer" a lot of your backend. RPC is sort of like Rest in that department, but because it's intended to be like that, its rarely an issue because you chose it for that reason.

Or to put it more simply. You use Odata and GraphQL and not Rest because they lessen the "working together" burden.
> Especially how the Ukrainian speaking part of Ukraine has treated the Russian speaking Ukrainians

I live in Poland. I was in Ukraine many times. I work with Russian- and Ukrainian-speaking Ukrainians. My cousin married an Ukrainian. There's millions of them here. Literally nobody except for Russian propagandists ever complained about abuse of Russian-speaking Ukrainians.

Kyiv (the capital) was mostly Russian-speaking till very recently. Most of Ukrainian politicians up to this point were Russian speaking. 5 of 6 presidents of Ukraine so far come from eastern Ukraine and were speaking Russian as their first language - including all the western-leaning ones (Yushchenko, Poroshenko, Zelenski).

Eastern ("russian-speaking") Ukraine is much more wealthy, almost all big cities and universities are there - because it's where the natural resources are. Western Ukraine is mostly countryside. Most of the Ukrainian elites come from the east.

Most Ukrainians speak both languages and switch depending on the context.

Ukrainian got more popular not because of some imagined persecution, but because Ukrainians started to associate Russian language with invaders and genociders after Russians:
- poisoned presidential candidate
- falsified elections
- invaded Crimea and Donbas
- annexed Donbas
- invaded the rest of Ukraine

This didn't started in 2014 - it started in 2004.

As for neo-nazis exerting control - neonazis tried to run for parliament after 2014. They got 0.7% of votes. That's lower than in most countries in the western Europe, including Germany (AfD has ~15% support) and my own country Poland.

Not to mention that Russia currently is a totalitarian dictatorship that actively promotes killing Ukrainians on the TV. There's more neonazis in one russian division than in the whole of Ukraine.
What new language features did python get recently that make it harder for newbies?
> I do not believe that end-to-end encryption means anything at all when the network and the client are the same entity.

That's textbook black-and-white thinking, and it's bullshit. I agree that network and client being controlled by the same entity raises questions, but that doesn't imply that E2EE "doesn't mean anything".

A very basic argument that shows why you are wrong: It's much easier for the government to compel a company to hand over data from their servers than it is to compel the company to write and publish a backdoored client. The two scenarios are not equivalent in practice, and this is what matters. Threat models that ignore how the real world operates are useless.

Please read up on the concept of "defense in depth", central to modern information security, which is built around the insight that security mechanisms can be valuable even if they don't work perfectly in all circumstances.
I've worked at a place where it was a case of choose what you want - there's lots of C#, Python and Javascript, some Go but there's still Scala and CoffeeScript lurking around, as well as some other more esoteric stuff that seemed like a good idea at the time.
At its largest extent the Danelaw covered only about half of england, and it lasted around a century before the Kingdom of Wessex conquered first the other remaining Anglo-saxon kingdoms, then retook the Danelaw, and created a unified Kingdom of England.
> I’m thinking the actual outcome of this protest is that reddit has to replace all moderators with paid staff. Since free mods are all insane.

Paid staff would indeed be a huge, huge improvement over ideologically driven no-lifes.

What tipped me over to Reddit's side regarding the API change is the possibility that it will end the practice of mods sharing automated block lists (if you post in a wrongthink subreddit, many other subreddits will preemptively ban you regardless of your actual activity in them, if any). If so, and if there are fewer handfuls of powermods that control dozens/hundreds/thousands of subreddits, I'm all for the change.

This is not to say that I condone what /u/spez did regarding editing /r/The_Donald comments, or misrepresenting what happened on the call with Apollo's owner. Paid staff can and do unduly push their own ideological bents. But when there is a name and a face attached to a company employee, there is some hope of holding people to account. The Challenor mess should never have happened, but at least the person was fired by Reddit. I have never, ever seen any evidence in more than a decade on Reddit of any level of accountability from faceless, nameless mods when they misbehave.
Yeah, we had cold and hot summers before, I'm not convinced. This is another attack on the crackpot comunity..

In all seriousness it depends on the simalirity of the organs and chemical cycles modeled from mice and men. The bloodbrain barrier and neurons are very similar. And for alot of other systems there are mice bred specifically to recreate human disease simulacra. There are differences and they can be cited when catching a erroneous experiment. https://pubmed.ncbi.nlm.nih.gov/14978070/

Just hinting at the difference as a catch all is insufficient.
Yeah for sure on the server side it's not set up with that knowledge, and Plexamp as an audio client is very radio-music-centric, but I agree with Arn_Thor that 3rd-party clients can help bridge that gap.

I've fully switched my audiobook client on iOS to Prologue, it's as full-featured as BookPlayer (playback speeds, chapters, remembered place, sleep mode, etc) but instead of managing media on my phone manually, I'm hosting it in Plex.
ByteDance has gobbled up $1B of Nvidia GPUs for AI
Yeah, hazard pointers address one of the very common sources of memory safety problems (iterator invalidation). It's definitely not a magic solution that solves all problems, especially given that none of the standard library containers will use them, but they're a very useful tool.
Of course, there's a whole continuum of complexity between microservices and monoliths in real life. Much of that continuum is labeled as "microservices".

I personally think that if microservice is doing something so complicated that the rewrite would take we-cannot-afford-that amount of time, then it should be split into multiple parts.
I work at a consulting firm.

Our salary is loosely linked to what percentage of our work is billable (with leniency for inexperienced staff, who aren't expected to be profitable while they're learning their craft).

If you spend three hours figuring out why things fall apart on the 31st of the month... that generally can't be billed to the client, and therefore it's bad for your salary.

On the other hand, if you spend three hundred hours writing tests and implementing an awesome multi-stage deployment process that avoids one production bug a month? Your manager can totally bill that work (with the right client).
Dancers?
You can add custom pages to your login and registration flows by implementing an SPI and customizing your flows in the admin interface.

( We offer consultancy for this..., info@actidoo.com )
Why should you run it on windows and Mac? On the other hand would I expected it to run in docker nowadays
Been waiting for my Spectrum Next since I ordered it in Nov 2020. That’s been 31 months and the current “promise” on the Kickstarter page is shipping in Q3.. but the goal posts have been moved so many times that the Q3 shipping date looks like a cruel joke like the Daikatana shipping date.
First the Ouya, which turned out to be a total flop, and then the Wii U, which Nintendo marketed so badly many people thought it was an extension for their Wii. This company sure made some unlucky bets!

Throughout the article I kept coming back to how generic the name sounds. It conjured pictures if the digital slot machines that are free mobile games, with gameplay loops mostly consisting of waiting or paying money to skip wait timers. The name "Toto" being associated with gambling sure doesn't help either. I would've never clicked a link with that name no matter how good you make your game look.

A lot of genuine effort and care went into this but with an uninviting name and, by their own admission, a complicated control screen, no amount of art or advertising would've convinced me as a consumer to buy it.

This would've been a smash hit on a flash games site, and it would've probably sold well if Ouya had succeeded.

One thing I find interesting is that online multi-player wasn't added as a feature during development. I understand how overworked the lone dev must've been, but adding an easy way to play with friends would've surely boosted sales.

I also wonder if the game would've gotten more sales on a handheld. I think the 3DS might've made this a great little party game, especially if you follow the "stream a limited version of the game to your friends" model that made DS local multi-player so interesting. Now, with the Switch out, with its built-in local multi-player features, the game might've gotten a popularity boost as well.

It's sad to see a game made with so much love fail, but with problems in do many key areas I'm surprised it took them this long to admit defeat.
> That was shutdown over bureaucratic disputes.

> What a monumental waste

So French.
To be honest I'm finding it a great alternative to HN too.
> 4 out of 5 pharmacy-filled prescriptions is not 4 out of 5 prescriptions

As opposed to the non-pharmacy filled prescriptions people pick up?

Your argument is that the statistic only works because so many people don't pick up meds their doctor calls in for them?

I'm not a statistician so maybe I'm not understanding correctly, but that seems like a very weak argument.
Sounds like a standard Creole language. I know that phenomena related to merging languages of populations in contact are well studied, but don't know enough to link to any relevant lit. sorry.
While I don't follow Python development super closely, as a scripting language it is still pretty simple and user friendly. I'm sure once the complexity rises... well, the complexity rises.
https://archive.is/Jh9S0
The Mig top speeds quoted always involve a plane that had no ordinance and was essentially empty. Even then the plane couldn't handle mach 2.83 for longer than 5 or so minutes due to heat generated by air friction damaging both the engines and the air-frame. Meanwhile the SR-71's top sustainable speed was mach +3.

So basically a mig25 would have to be in the perfect spot and ready to have a chance at shooting down a SR-71. Even then the odds of success wouldn't be that great. The way bigger threat were the new generation of SAMs coming online that COULD give the SR-71 a lot of trouble.

The spin off industries related to the SR-71 was massive and well worth the research.

I'm not aware of a mig25 actually shooting down a F15. The only incident I'm aware of was the "ambush" in Samurra. So I'd like to know what incident you're referring to.
99.181.66.216 belongs to AS46489 [0], mainly used to serve Twitch. AS16509 is your standard AWS cloud AS hosting data center IPs.

[0] https://ipinfo.io/AS46489

[1] https://ipinfo.io/AS16509
My problem isn’t that graphql can’t do X. It’s the opposite, that I don’t know what it’s supposed to do really well – the core value prop. I still haven’t heard any one-sentence explanation of what it is, and importantly, what it isn’t.

To me it sounds like they try to solve numerous problems: (1) be a query language, ie an improvement over sql, (2) a type safe alternative to REST ie web APIs (3) allow frontend developers to write queries without having to write endpoints, (4) keep clients lightweight, (5) be a single entry point to this hyper graph thing, and more.

None of these things seem compelling in isolation: simply replacing REST adds resolver complexity and doesn’t handle things like file uploads. Substituting sql restricts you to whatever sql is generated and you end up with two query planners. Allowing frontend to query db directly is insecure so you must have fool proof row level security or more resolver complexity. Clients I guess started out thin but now there are all these intelligent caching layers. And this hyper graph thing is only valuable with other graphql services.

So, I guess graphql can be good if you marry it and go 100% all in? But to me it’s a smell when technology claims that your pains can be resolved by using more of the same tech. How am I wrong?
Is this gatekeeping?
My LDAP server is the source of truth for my org's user/password (authentication) and user-group membership (authorization) data. I'd like upgrade to an IdP like Keycloak.

It seems straightforward to have Keycloak proxy the authentication via OIDC but it's less clear to me how to get apps to check with Keycloak to determine if user X is in group Y and is therefore allowed to access resource Z. The main benefit in a setup like this is the ability to query a single source of truth when it's necessary to audit a user's capabilities within the org.

Is this an achievable or reasonable use case for keycloak? Or should I integrate my apps around a different Zanzibar clone which is designed to quickly serve granular permissions?
>> We were told that Ms. Sohn’s political statements made Democratic Senators Catherine Cortez Masto, Joe Manchin, Kyrsten Sinema and Mark Kelly uneasy.

> It's not just the GOP blocking her.

Is this supposed to be a real opinion? Manchin and Sinema are your cornerstones? LOL
If you are waiting for a Rust-like feature that guarantees memory safety - this won't happen. Changes to the language required for this would break too much. Also, existing code wouldn't compile anymore because it contains a ton of memory bugs.
Historically and culturally, the west is absolutely a meaningful entity.
It's not only about newbies in the end. When I started learning C++ back in ~2000 the semi-joke was that "C++ takes about 10 years to learn". The language is far bigger now, with more things you either need to know to cut out or somehow just not learn, but then you need to learn it if you end up working with code that uses it, etc.. This stuff, to use properly, usually comes with a list of "dos and don'ts" in C++ so it's not feasible to just on-demand learn the additions to the language and call it a day.
Two-time conference organizer here.

People are incredibly fickle; moods and motivations seem to ebb and flow and there's no way to predict whether people will buy tickets even when they look you in the eye and swear that they will. That's because we've been trained from birth to tell people what they want to hear.

Our first conference was sold out and highly-lauded, with GOAT being thrown around. So we did a second one that aimed even higher and while we still managed to break even without sponsors - assuming we donate our time as organizers - we actually only sold about 60-70% of the available tickets.

I remember asking a guy who had said that our first conference had changed his life why he wasn't coming to the second one. "The economy, man." (ooohkay)

Doing these two conferences was a lot of fun, and encapsulate some of my proudest memories. They really helped cement our credibility at the time. However, it probably cost my partner and I half a year of productive time. Not only did we not make money for the hundreds of hours we poured into our labour of love, but that was hundreds of hours that we didn't spend building our actual business, which more than defeated whatever growth goals we had when we started.

All of which is to say that running a conference is a vanity flex, and it's basically all but guaranteed to lose money unless you have such a large social following (see: XOXO) that it literally doesn't actually matter if you lose money because your YouTube check that month could pay for everything.

So, would-be conference organizer, you have ask yourself two potentially awkward questions: why on earth do you actually want to run a conference, and why do you think anyone would pay to come?

Remember: the easiest way to get $100k running a conference is to spend $200k.

These days in particular, it's incredibly likely that the market is conferenced out. There's just so damn many events people can go to. At some point, a lot of people seem to realize that they don't need to make any new buddies. Invent a way for them to get an uninterrupted weekend of hacking time and you'll be rich.
Don't create a custom context type. This will make it more difficult to interop with any other library that uses the normal context.Context.[0]

Furthermore, why is that code using string keys for the context? It's recommended in the context package documentation that context keys should always be an unexported type, so that the key can never collide with a different key.[1] It's common to define accessor functions which are type safe

[0] https://google.github.io/styleguide/go/decisions.html#custom...

[1] https://pkg.go.dev/context#WithValue
You don’t have to, though over time some of them will start to appear in other peoples’ code.

A lot of features aren’t fully fleshed out when they enter the standard. For example the building blocks of coroutines appeared in C++20 but the user friendly affordances aren’t there yet — but with the building blocks in place people can work on that.

Likewise a lot of features are there for library developers and aren’t needed by regular code.

So your position is sorta consistent with what’s mostly approved by the committee. Even ranges, which are exciting, I’m still waiting on to see if some things get shaken out.
Oh, I read it. I'm commenting on what you chose to emphasize and what you left out, because that speaks volumes about what you value.

Almost all of the advice was around superficial, self-centered things.

All of it was about you getting something you want, and none of it was about being a net positive in someone else's life.

It comes off as cold and selfish.
I know a bit of Chinese so I was surprised how handy it was in Japan when there was no English signage.

Obviously it didn't convey the whole message, but sometimes just enough to understand what it meant.
Let me be more precise: Swing, Tango Argentina etc.

They all need bars to dance. They all use the same argument. And quite often they are politely asked to find somewhere else after a few months.
Parcheggio and parcheggiare are used in Italian too, I'm pretty sure they're not derived from English, but from "parco" (park), which has Indo-European roots.
I do recall speaking to people at a betting company many moons ago who tried to recruit me with the claim they were so open with microservices that they had a key system written in Erlang that only one engineer in the company understood.

I politely explained my position on why that seemed suboptimal.
But newbies typically don't need to learn the whole mountain.

* Some new features are typically added to handle very specific cases that will rarely be encountered but can't be easily handled by existing mechanisms. These are typically used by library authors to make an API clearer or easier to use, and new developers won't need to interact with them at all.

* Some new features are added to replace existing features either partially or entirely (because the old feature had issues, or a better way of handling it was found). In that case, new developers just don't need to learn the old feature at all, or if they do, they can learn it later as a more advanced technique.

I don't know a huge amount of C++, and I haven't been following Python much recently, but to use some examples from Rust:

* GATs and a lot of the newer trait features are very much in the former category. Very few Rust developers will be directly using the new tools, but library authors can use them to create easier-to-use APIs which benefit everyone.

* The `try` mechanism is often simpler to learn than all the Result/Option combinators, which drastically reduces the amount a new developer needs to know about to get started. You'll still probably need those combinators later, but you can now get started without them.

There are definitely some features that don't fit clearly into these two categories, and add a kind of overall complexity to the language. But I think a lot of people look at a big list of features and think "but that will be so much to learn", forgetting that (a) you probably don't need to learn a lot of it until you're already very advanced, and (b) a lot of it will be making other parts of the language obsolete and overall simpler.
Well yes, helicopters with internal combustion engines have been working fine for a while now. But if the engine is mechanically coupled to the rotor then it will need variable pitch blades in order to maintain control. Combustion engines can't change speed as quickly as electric motors can.
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/ has all the papers. To follow discussions, it's probably best to attend the standard meeting online or in person.
> Scarcity of what?

Attention and logistics. The cost of getting things where they need to go, the administration of an empire, frequently dwarves by orders of magnitude the cost of the materials being transported to and fro. The problem is not solved by localisation given the increased exposure to volatility that brings.
I think that it might be because the difference is mostly in how we work together. With GQL your frontend and backend engineers are always happy, with Rest they are always at each others throats to deliver. This is because GQL gives your teams the tools they want. On the frontend you get the data access without ever having to talk with your backend, on the backend you get the load data without ever having to talk with your frontend. So both your frontend and your backend can focus on what they do best without ever talking with eachother.

Obviously that's not exactly how it works, but if you give your frontend engineers the full query abilities of GQL and your backend the ability to monitor and then fix bottlenecks through the GQL load tools you simply remove a lot of the conflict zones in modern development.

You can do everything you can with GQL with Rest, but you're not going to want to do it. And speaking from experience, you're not going to want to do it with Odata either unless Microsoft magically improves the experience after 10 years of it sucking.