skysight-inc/HackerNews huggingface dataset:
After watching Putin's first interview in two years, I naturally turned to Hacker News (HN) to gauge public opinion. However, to my surprise, I found no discussion whatsoever. Whether biased or not, this interview marks a significant event, yet it seems HN, typically a vibrant hub for diverse discussions, remains silent.

If I overlooked the conversation elsewhere, I'd appreciate being directed to it and apologize for any redundancy. However, if there truly isn't a discussion, it begs the question: has HN become so polarized that it shies away from engaging with viewpoints that challenge the status quo?

Before someone dismisses this as purely a tech community, let's remember that HN has historically delved into political matters, evidenced by the extensive discourse surrounding Russia's invasion of Ukraine in February 2022, which garnered over 1800 comments. Yet, a mere mention of Putin's interview yields only two comments.

It's a disheartening observation, prompting reflection on the dynamics of online discourse and the potential erosion of open dialogue within communities like HN
I thought the same reading it – is it really this hard to build an app these days?

Things were more far more manual and much less secure, scalable and reliable in the past, but they were also far far simpler.
I tend to agree that for most things on AWS, EC2 + ASG is superior. It's very polished. EKS is very bare bones. I would probably go so far as to just run Kubernetes on EC2 if I had to go that route.

But in general k8s provides incredibly solid abstractions for building portable, rigorously available services. Nothing quite compares. It's felt very stable over the past few years.

Sure, EC2 is incredibly stable, but I don't always do business on Amazon.
By tiny you mean massive.
I expect that hundreds of years ago there was also much gnashing of teeth about people overusing the new technology of literacy.
> "As we begin to shift focus to our shared efforts with Notion, we will be closing down Skiff's product suite after a 6-month sunset period"

I had high hopes for Skiff, but once again it became yet another incredible journey and an entire VC grift racing to an acquisition only for it to be shut down just like the majority of VC fuelled startups who probably ran out of money.

The end users are always left holding the bag and continue to lose in the process of anything VC funded these days.
To fit the necessary tech in, the glasses are scaled up 2x.
Or you're realistic about what you're doing. Will you ever need to scale more than 10x? And on the timescales where you do grow over 10x, would it be better to reconsider/re-architect everything anyway?

I mean, I'm looking after a 4 instance Aurora cluster which is great feature wise, is slightly overprovisioned for special events, and is more likely to shrink than grow 2x in the next decade. If we start experiencing any issues, there's lots of optimisations that can be still gained from better caching and that work will be cheaper than the instance size upgrade.
It's barely mentioned on the website (just a tiny reference in the roadmap section) but looking at the Windows nupkg, it's Chromium-based.

I wish the devs best of luck and it looks like a cool design, but the Blink / Chromium dominance is too dangerous for the health of the web for me to ever support. It also seems a little ironic for the website and developer's Twitter to lambast VC and data brokers while basing the product around a browser engine made by a trillion-dollar advertising company.
Yeah I could definitely see that something should be done about IT people having to work overtime without compensation, and that is company specific. So unless there's a larger push to change that culture, some companies (like what EA used to be) will happily exploit their workers.
Your GitHub link is broken, fyi. It goes to “.github.com”
Yeah what a pity. I really want to watch him go back to keen and program game engines on DOS again.
Some orgs are looking at moving back to on prem because they're figuring this out. For a while it was vogue to go from capex to opex costs, and C suite people were incentivized to do that via comp structures, hence "digital transformation" ie: migration to public cloud infrastructure. Now, those same orgs are realizing that renting computers actually costs more than owning them, when you're utilizing them to a significant degree.

Just like any other asset.
Bandcamp is the standard go to — if they’re on there you can get lossless quality. Alternately I believe Apple Music is now selling the highest quality digital downloads of all the major providers at the moment.
…no?

There’s still a defined cost to swapping your DB code over to a different backend. At the point where it becomes uneconomical, you’re also at a scale you can afford rewriting a module.

That’s why we have things like “hexagonal architecture”, which focus on isolating the storage protocol from the code. There’s an art to designing such that your prototype can scale with only minor rework — but that’s why we have senior engineers.
What’s wrong with uuidv4 as PK?
bad phrasing on my part, "marketing relationships" is one thing, "partnerships" another. Marketing is not always ads. J&J might be interested in adopting AI but they aren't going to announce a partnership (<- marketing for themselves and for OpenAI) with a product that doesn't meet their needs for something boring and inoffensive.
Just careful with how "brown" it is. I saw stores selling sliced brown bread that differ from white bread only due food coloring. FWIW the packaging doesn't state it's more fibrous or healthier...

This is, I guess, the same trap people walk into, as with the "100% natural" (therefore assumably healthier) juices.
lol no it’s not.
I just watched a solid mid-90s documentary about African art on YouTube. It focused on the colonial Europeans and subsequent anthropologists wild misinterpretation of beautiful African objects, and how that was used to justify the oppression. In many African traditions, the idea of "art" as it exists in the European cultural vein doesn't even exist: the aesthetic imbued into the practical everyday objects like masks used in ritual is inextricable from its function and the tradition of craft that informed its construction. It would be ridiculous to say it isn't art, but equally ridiculous to interact with it using Western philosophical conceptions of art.

People in dominant positions justified steamrolling people whose humanity was inconvenient, in part, by insisting on the universality of the rigid, outdated, old Western conception of art... and they clearly still do.
I agree. I’m afraid I’m one of those 00s developers and can relate. Back then many startups were being launched on super simple stacks.

With all of that complexity/word salad from TFA, where’s the value delivered? Presumably there’s a product somewhere under all that infrastructure, but damn, what’s left to spend on it after all the infrastructure variable costs?

I get it’s a list of preferences, but still once you’ve got your selection that’s still a ton of crap to pay for and deal with.

Do we ever seek simplicity in software engineering products?
Quoting several others here: “We have blue LEDs because one guy bet many years of his life on his ideas, against significant opposition.”

This is great for us, but it’s important recognize the real cost of this success: probably hundreds, maybe thousands, of others also worked hard, and bet years of their lives, and… failed. In the words of Willy Wonka, they lost - they got nothing.
This. As soon as I need something it is quick online search away. Amount of stuff available for C++ is staggering
Not convinced, but sounds like you know what you are talking about

nginx has quic support now
https://nginx.org/en/docs/quic.html

Do you fancy knocking up some benchmarks of typical server loads on accross some 100mbs/1gbs/10gbs connections and chrome headless?
I think the point is that it's not really a "tiny" error.

Phrasing it as "91% vs 98% efficient" makes it seem like it's only 'off' by a factor of 1.08x, but what really matters for the climate is 9% vs 2% leak rate — a whopping 4.5x!

Perhaps surprisingly, this 'simple math' for us isn't obvious to a large fraction of the population. For better comprehension it would be nice if the article had pointed it out specifically.

Methane is a great low hanging fruit to tackle first. Its atmospheric half-life is 8-12 years, which means slashing emissions now can 'bend the curve' in decades, not centuries. Upcoming satellites will monitor all emissions globally, with day-by-day and well-by-well granularity.
Pattern matching is fundamental to programming in elixir/Erlang the way go channels are in Go and super clean metaprogramming interfaces are in Ruby or types are in Haskell etc, you can do those things in other languages but when it's fundamental to the design of the language itself it filters down (or up) to every layer, where it significantly impacts how useful/powerful it is.

Elixirs pattern matching is the one thing I wish every language had from day one. Besides maybe an Optional/Maybe concept for error handling / data enclosures.

It makes for some very readable code and encourages passing return values that are easily consumed in a simple/functional way. Not capturing random error objects or unpredictable data structures.

Although I'm biased towards functional style, even though I code JS/Ruby for a living.
Any DB is fine as a queue depending on requirements, design and usage.
Are you saying when they can impose burdens without cost to themselves, they won't abuse that shamefully?
As someone who was in finance before moving to tech, there are still many days I believe Excel is the best IDE I've ever used
Languages Google Cannot Translate
How baby deer learns to walk in a few hours after birth? It needs to control four limbs to keep balance. Animals tend to have some forms of behavior that they learn in a few tries or even from the very first try. But at the same time they may be very bad at learning other kinds of behavior that seem no more difficult for us.

Homo Sapience is special in this regard with almost all their firmware broken. Homo Sapience needs to learn hard how to focus their eyes or to hold head or to walk and even how to crawl. Seems like our abilities to learn are linked with brokenness of our innate software, probably it is a double headed causal arrow: our software is broken because we could overcome it with our general abilities to learn, and our general abilities to learn evolved because without them and without working genetic programs for specific forms of behavior we would be doomed.

I can't help but think that autism is the next step at breaking innate software and developing more robust general learning mechanisms.
It is a shame karpenter is AWS only. I was thinking about how our k8s autoscaler could be better and landed on the same kind of design as karpenter where you work from unschedulable pods backwards. Right now we have an autoscaler which looks at resource utilization of a node pool but that doesn’t take into account things like topology spread constraints and resource fragmentation.
K8S is a disastrous complexity bomb. You need millions upon millions of lines of code just to build a usable platform. Securing Kubernetes is a nightmare. And lock-in never really went away because it's all coupled with cloud specific stuff anyway.

Many of the core concepts of Kubernetes should be taken to build a new alternative without all the footguns. Security should be baked in, not an afterthought when you need ISO/PCI/whatever.
> Atlassian also just launched an integration with OpsGenie.

Given Atlassian bought OpsGenie in 2018, this either somewhere between quite late and unsurprising.
Just use a dedicated tool. It is not that hard. If you want higher level abstraction, you have a whole spectrum of next gen queues, like Temporal, Trigger.dev, Inngest, Defer, etc.
Axios and Politico

Both of these, in my experience, are dreck-tier sources and Politico was bought vaguely recently by Axel Springer which emits Business Insider, which is also a reddit-tier publication.
> I'm unaffected because I'm well into paying off this house that I got cheap after the bust at a tiny interest rate;
What are the current gaps for PWA?

PWA should be viable for a pretty large percentage of applications nowadays, right?

I don't know, but could Discord be a PWA instead of an Electron app?

The biggest gap is something capable like SQLite vs IndexedDB, but even then I bet most apps wouldn't require the sophistication of a higher level query language compared the "b-tree" model of IndexedDB.
Everything Is Chrome (2023)
Postgres as a queue is one of the worst decisions I've seen made and I and others I've worked with have spent years of our lives unwinding the consequences.
Yes incredibly dark pattern. Kind of thing everyone who worked on should be ashamed of.
But if the Rust versions are as safe as claimed, then you're making the critique of C++ stronger, by pointing out that the pitfalls are easier to fall into than the blog post presents -- for the second, you don't even need threads! (And aliasing is one of the things that Rust's borrow machinery at least tries to address, even in a single-threaded context.)

So, is he wrong about the Rust part?
It’s not just you. That site is not consistent with any other US gov design language. It also looks cheap and like a QAnon conspiracy news site.
> The difference between the assumed efficiency of flaring and the efficiency found in Kort and his colleagues’ results is a matter of a few percentage points. However, the researcher said that this seemingly small difference could be a big deal when extrapolated over the whole fossil fuel industry. Further, methane has more than 80 times the impact of carbon dioxide when it comes to warming the planet—at least during the first 20 years it spends in the air.

Isn't this enough? Yes, the article could make the point more explicit at the expense of brevity, but most readers can infer the implications of marginal changes.

I'll do you one better. The article doesn't state the loss to taxpayers given the billions+ of permanently lost tax revenue!

/OT

I don't understand why this "point in time" article is meaningful years later, given it's been a known issue (far prior to the article) and the regulatory story has evolved.
I was just addressing the "tracked my whereabouts just because I was in an organisation where a couple of other members have suspicions raised about them" bit.
I personally found it well-written, if a bit wordy; the first few sections are indeed refutations / literature review, but that’s, uh, that’s the point. The whole essay is about how we use the word loosely and existing definitions don’t fit well enough, so publishing a paper that didn’t cover all the (recently, semi-prominently) proposed definitions would be seen as lazy or incomplete. Personally, I think it’s a fun exercise to read through and update your own personal definition as you go. If you’re like me, all these papers start with a “oh well that word is simple and obvious” reaction that slowly disintegrates!

Materially; I couldn't c/p it, but I think their line about “indirect or diffuse danger” that gets right at the crux of the issue. So I’d say I’d find this analysis convincing
I've flagged this comment and others. Spamming is absolutely not allowed on HN and your comment history is exclusively (off by 1) posting this this link. I suggest you don't because people on HN do not take kindly to this type of advertising and you'll likely get the opposite effect.
No, you’ve achieved an illusion of that as now your spending hours wasted on discovering where a developer forgot to call NewUsername and instead called Username{“broken”}. I cant see the value in this abstraction in Go.
I wish guix was a little more mainstream.
Wow! https://www.lightpollutionmap.info/s/jhwGSJJbskO4Lrzwt1btDQ
https://microservices.io/patterns/data/transactional-outbox....

It allows you to wrap it all in a transaction. If you separate a database update and insertion into a queue, whichever happens second may fail, while the first succeeds.
Hey. Author here.
Yeah, the Go style guide at Google (the setting for the dcode review) is quite prescriptive. I don't mind labeling things "anti-patterns". It doesn't mean there's a law against using said pattern (if you're in a healthy org). It just means you should be able to justify why you go against the guideline. The whole reason I was comfortable attempting that approach in the first place is because I had successfully used that pattern before and was able to provide a rationale. It just happens that this case differed enough that using this pattern would've been unwise.

You're right that things shouldn't just be classed as an anti-pattern without explaining why. And that's enforced in most Go-heavy orgs at Google. If you're gonna say something is bad without providing an explanation and linking to the relevant sources, the comment is likely to be closed or argued.

I didn't provide an explanation for why this is considered an anti-pattern in this post because that wasn't the topic. But it appears most persons here are interested in that, so maybe I'll write a post on that next week :)
powershell.exe -executionpolicy unrestricted -file ./setup_windows.ps1 -InstallPSWindowsUpdate -UpdateWindows -UpdateChocoPackages
powershell -ex bypass -f ./setup_windows.ps1 -I -UpdateW -UpdateC

(or whatever are short enough to uniquely identify parameter names for your script)
Some answers from my perspective:

240/4 is already useful in sdns, vpns, and networks like AWS as a hop along the way. Merely moving it on the IETF/IANA ledger from reserved to unicast would recognize reality since 2008. It is hilarious how hard that has been.

Universal connectivity need not be a goal - can you imagine a portion of the internet completely immune from 30+ years of windows borne worms and viruses? :)

240/4 support in modern windows is a patch tuesday away which I would hope happen after it is moved from one side of the ledger to the other, officially. It (and 0/8) saves nanoseconds.

In doing these patches we noticed that NO IoT OS actually did the 240/4 or 0/8 check, and in deleting the checks for it in Linux, etc, 5 and 16 years ago, the internet did not melt down.

I see a lot of resentment from the router community that bemoans the extra work it will take to block these addresses, when if they don´t bother, nothing will change. Deleting code and acls for it, will actually speed things up.

The flack I took for the 0/8 patches from thousands of people and the 3 weeks it took to patch that out of everything were outweighed in terms of saving nanoseconds on every packet the first weekend that kernel deployed. 5+ years ago in the case of 0/8. Enforcing a stupid policy for decades for no reason seems silly. 0/8 should have been reclaimed in 1986.

As for what doesn´t work, who cares? Enough networks do already to make the 240/4 space usable. However AWS and google and perhaps others squatting on it!? and turning it into RFC1918 space, was certainly not my intent - I had thought that these addresses should be added to the global internet, for all mankind. Jon Postel would be spinning in his grave if he saw this abuse of this space.

I had delusions of setting up 255/8 (the most junky space available, much like 2.4ghz was for wifi) as a test, as a place to innovate, as a place to perhaps perfect udp-lite natting, and other protocols, within the open source community.

Lastly, everybody misses the most important draft of all, finally retiring the .0 broadcast idea (with no users since 1986) which will free up oodles of real world IPv4 address space. Most of that work is already done, it would take very little to finish it. Why is it so hard to get people to pay attention to that? https://www.ietf.org/id/draft-schoen-intarea-unicast-lowest-...

IPv6 also has a stupid idea about the zeroth address, only implemented in a few places that needs to be depreciated, which would shrink a lot of routing tables.
I mean they did leave a message... Your friend will also generally tell you that they listed you too, so you'd know to expect unknown numbers.
Aonther submit posted, but for once again I support this thing.
240/4 for windows is a patch tuesday away.
There are several proposals. The most current one merely advocates that 240/4 be moved from reserved for future use to unicast status, which is the deployed reality today.

I hate the idea of wasting 6% of the original internet on rfc1918 space.
You need to understand (well) what the kernel is going to do. That's more difficult than if you call read/write yourself (because their semantics are well defined). Otoh the problem is significantly less than it was back in the day because there's really only one kernel now.
https://github.com/Azure/karpenter-provider-azure there is this in the works for karpenter on aks
I imagine for working with non-low latency producers or consumers, such as network requests?
Dreamhost too. Dreamhost will let you run a continuously running process.

The amount of work you can get done on low-end shared hosting is really quite impressive.
The incident angle was previously optimised for insolation over the course of a year - so halfway between winter solar apogee and summer solar apogee.
28 for me, apparently?
> the amount of code and level of risk taken would be exactly the same.

The amount of code might be the same, but that doesn't guarantee that the level of risk is the same. A lot of bugs are introduced at interfaces -- the provider of an API makes a subtle change without realizing how it affects some of the API consumers -- and that's inherently more likely to occur if the two sides of the API are developed separately.

In the FreeBSD world we've found that it's incredibly useful to develop the kernel and libc and system binaries together; all sorts of problems Linux trips over simply never happen in FreeBSD.