skysight-inc/HackerNews huggingface dataset:
I'd need days to detail it all specifically enough, but I'll give you a simple example...

A "monolithic" solution usually relies on a basic (e.g. LAMP) stack that can all be run on one server if the need arises... Your web and database server can be migrated from AWS to Azure much easier if pretty much all of the functionality relies on a close-knit local server architecture that can have a less complicated security, code, and endpoint design as well.

If you create an app that works based on a highly distributed architecture, suddenly, migrating a solution is far more complex - Platforms like AWS and Azure do not run all of the same services, and those services often require lots of refactoring to work properly with your prior data, you'll also need to do many test cycles after migrating to ensure that solution integrity is maintained.... At that point, a simple migration might as well be a total refactor.

After implementing policies like zero trust and working out whitelisting, if your solution is complicated or large-scale, you also have to deal with service-specific nuances in your code and in your architecture design that don't translate well to the completely different tools available on an alternate cloud hosting platform, because usually they have completely different nuances and conventions on their service architectures.

To put it simply, it's like buying a ford pickup truck and installing an aftermarket 6.34 x 9.85ft camper top (and other ford-specific aftermarket parts) on it, and then trying to install that custom Ford camper top and the other Ford aftermarket parts onto a Toyota which only fits a 5.77 x 8.34ft camper later on... It usually doesn't work out well, and usually provides very unexpected results and more financial loss than using a universally sized 5.55 x 8.20ft camper (The monolithic option that fits in both trucks, albeit not perfectly).

Each platform is very specialized in their own way... Just as with Ford any Toyota pick up trucks, they have completely different build dimensions, and that's why the parts aren't interchangeable between the two trucks.

Monolithic solutions were originally designed to work agnostic of platforms, so they can work on either provided that they are implemented correctly...

Ultimately, the business need should be carefully evaluated by an experienced architect to determine which architecture fits the need best, and then other factors should be reviewed (like if you'll need to migrate any time in the future for example) to make the final call.
And then the whole claim that keto was a diet of ancient people before the agricalture looked more like a fantasy. Modern hunter-gatherets in Africa get at least 50% percent of their calories from starchy vegetables and honey with latter supplying at least 10% of calories. This became apparent after scientists measured it rather than guessing based on earlier observations.
Has bugs, is way too complex for the given functionality, and is completely unneeded in the first place--yes, get rid of the damn thing. Unless of course you enjoy getting "your" system OWNED and dominated by bad actors.

My custom distro beats the brakes off junkware like Ubuntu and (lol) Windows in startup time and responsiveness, and has all of the functionality I need, with half the code and as a result much fewer gaping security holes.

Computer security is an absolute nightmare these days. Intelligent people should be simplifying things and stripping everything down to the bare minimum, instead of stacking more crud on top of endless crud.

Those who fail to SECURE their systems and workflows will one day in the near future be surprised as shit to find that the entire "cloud" has been hacked and destroyed by worms and their system trashed right along with it. At that time, the world will be divided into two camps: computer owners (me and my kind) and non computer owners (everyone else.)
Just use the Japan map emoji as shown next to the Japan headline in the article. The image of Japan country looks like the increasing chart enough and is green.
> Are you making this more complicated than it needs to be?

I'm not sure. I guess if one trusts the default logging settings on the server software to be compliant, and only uses static HTML, maybe that's adequate? But as soon as any third-party code or data provided by some other server gets involved, it's hard to know what might be logged elsewhere as a result of visiting your site.

I mean, would an old-fashioned web visitor counter be compliant? It's tracking something in order to provide that number.
Show HN: Micro CMS for social profile banner images
I get the nostalgia but not the sentiment. You can still set up a website, you can still post content on it, you can still link to that content on social media to get viewers, if you attach Google Analytics to your site, that traffic then improves your search rankings which brings you more traffic.

Hundreds of people a day read my rantings (and I probably owe most of them an apology for that) but the point is you can still make a 'personal' website and grow an audience even now, you don't need an 'alternative' web to do that, you just need to put in the effort.
I wouldn't read too much into it. He talks about the next step of people freshly out of college being offices where they grow to be adults with careers.

I don't think that he is trying to make a sociological statement but to emphasise the impact of the offices on peoples development.

IMHO open plan offices are a fermenting ground for burned out adults asking themselves at what point they will have a personal space like a grown up.
Like any other brassica leaf - really similar to broccoli leaves, if I had to nail it down. Nutty, savoury, hint of bitterness. The leaves are pretty tough though, and have some fascinating hydrophobic properties, so need chopping finely and then either frying or boiling until they’re soft.
I remember the glory days of UNIX/Usenet/etc. in the 80s at college too. I had an email address at Compuserve in the mid-80s, though I mainly used it for talking to other Compuserve members (when we weren't using 'CB channels', for those that remember). I remember all the various things like Usenet before the 'Internet' too; I don't recall anybody in my group ever calling it the Internet until after the WWW came along.
Hug of Death.
Who is giving 5 year olds 100% pure ethanol or ethanol at all for that matter?
The totalitarian state that is necessitated by the communist political system always turns out to be as hellish, selfish, and mismanaged as any late capitalist dystopia—except usually with more murder. So I would say the political problem is very much not solved and post-scarcity Utopianism isn’t going to get us there.
I don't think the old internet ever went away, instead the commercial internet exploded, in some ways good in some ways bad.

If you want to create and showcase your own stuff you have a ton more options than you used to, it could be nostalgic HTML pages with blinking colors or some slick thing on a prefab site builder, up to you.
That's a problem with a particularly dogmatic (and kind of useless) misapplication of the principle. "Single Responsibility Principle" is better understood in relation to the same concept as my comment elsewhere in this thread: cohesion. The capabilities and state contained within a module (as an abstract, not strictly technical, concept) should be cohesive, that is: They belong together.

So a class with only one function may be appropriate, but it's not the logical conclusion of SRP itself. For instance, in a project you may want to draw something to the screen. It is not the concept of SRP that you should have one module per function, and have a module which draws circles and another which draws lines (that isn't to say this couldn't be a logical and sensible result, but it probably isn't). Instead you have a module (likely with submodules) which is responsible for drawing to the screen, period. You pass it a description of a shape (however that may be done: data objects, objects which can "draw" themselves in some abstract sense, dedicated procedures/methods for each shape that take shape parameters) and it draws to the screen. This is in contrast to spreading the screen drawing routines across a many thousands or millions of lines codebase.

The other thing SRP discourages is, say, that screen drawing module also being your input module. They could appear to be in the same module from a high enough level, but ideally only because a high level module has submodules that contain the separate responsibilities. For instance, ncurses does both output and input, but hopefully (I've never looked at the internals) it's divisible into two sections (each section composed of some number of modules, probably) that clearly are responsible for either input or output, but never (or rarely, and only where it is necessary due to some underlying technical reason) both.
That's true, but often the things it erases are what's confusing you. For instance, it can remove highly abstracted C++ templates and dead code. Or if you don't know what a construct does, you can compile code with and without it and see exactly what it does.

Often new programmers think asm/low level programming is scary, but because it's so predictable it's actually quite easy to work with… in small doses.
> These types of automation have been in place for decades, and all of them cut costs for the owners of them and reduce the number of workers needed.

They reduce the number of workers needed to produce the same amount of output. What is slightly counterintuitive is that having done so, they may actually increase the demand for workers, because they now can produce far more output in the same amount of time.

Modern languages and tools have made programming much more productive, and now there are lots more programmers and they get paid more.
Go work at a summer camp. It'll be good for you.
Monolith almost sounds cool to me. To be honest.

I remember hearing a story (from a person inside said company) about a reasonably sized company with a 2 (really 1) man dev team (they contract for most of their needs) and how excited the company was to move their internal stuff to microservices and off a monolith.

He looked at me like i was insane when i said a monolith would work better for them.
Think tank sources will attribute DF17 and other HGVs to CASIC. Who has their own wind tunnels. DF17 was developed years before AVIC FL64, which was undergoing calibration testing around the time of the glider/fob news, it's not suppose to be operational until this year. AVIC might be pursuing hypersonic delivery platforms like drones etc, they might share testing infra with other branches but rocket boost glide vehicles isn't their wheelhouse. This article and it's source doesn't pass the smell test. I guess we'll see if it makes way in other reporting.

https://missilethreat.csis.org/missile/df-17/

>China’s 10th Research Institute is responsible for developing the DF-17 and other Chinese HGVs. Also known as the “Near Space Flight Vehicle Research Institute,” the organization operates under the China Aerospace Science Industry Corporation (CASIC) 1st Academy.3
I would argue it isn't very custom. Using fully qualified URLs predates Node.js and CommonJS. It was also one of the big debates when we all were doing AMD. Node.js has realised that _mistake_ of eliding extensions and is headed that direction as well.

We have been adding a Node.js compatibility mode, but I am not sure that qualifies as "_very_ custom module resolution".

Both the triple-slash reference and @deno-types were solutions to problems to not have opaque type resolution with TypeScript. They do not impact the runtime resolution, only the type check resolution. Instead of opaquely searching for these by reading the `package.json` and probing the file system like `tsc`, Deno is explicit.

I would be glad to work with you to explore how we can figure out how to resolve your implementor concerns. The door has been open for a long time, and I have mentioned it in passing to Daniel a couple times. Let me know if you would like to talk.
There is no need to fall back to HTML1. Before HTML5 and even before HTML4, there was a web markup language that was much more powerful than HTML1, was widely deployed and used, did everything we needed, and worked fine. It was called HTML3 and it was great. That is where we should be right now.
Yes, good point - I mean 'desk-bound' as in culturally tied to a physical location while working. I say that in contrast to software jobs that don't particularly care where or how you work as long as you deliver results.
"The Internet itself seems to many to have degenerated into a giant advertising tool. And, a high percentage of websites load as slowly as a sick turtle awaking from a long slumber."

Is there a connection between these two statements?
I think there's some kind of fallacy there.

Nothing's really changed, in the sense that there's nothing stopping you (or anybody else) from running your own server that serves up simplehand-written HTML, if that's what you want to do.

You can probably even do it on your phone, but I wouldn't hold my breath for the app to get accepted to any official app stores.

Personally, I think the UI on phones is atrocious, and would never want to use one for any kind of development work, but to each their own.
This highlights the fact that the average person has no idea how seriously methanol should be taken. I started distilling my own moonshine / hand sanitizer at the beginning of the pandemic, and before that I really hadn't heard the horror stories and had no idea how common accidental poisoning was.

Horrifically, the US government actually increased methanol in industrial spirits during an prohibition with what seems to have been clear intent that more people would die as a result[1].

https://www.vox.com/2014/8/8/5975605/alcohol-prohibition-poi...
Plenty of studies on ketogenic diets on rats are based on adding an incredible amount of fat on top of carbohydrate heavy and call it ketogenic. /r/ketoscience has these crappy studies posted and debunked daily. Serious research on low carb is sorely lacking and plenty of interested parties really do not want for good science to be done around high fat/meat: the money's on plant based these days. I am still salty about that sorry excuse for a study the Lancet posted a few years ago and is still making headlines.
It's the most that Apple's paid out for a bug bounty, as far as I know. The previous highest was $500 less ($100,000).
There’s nothing new about marketing your product, and make no mistake that DynamoDB and Route53 are products.

> Those names appeal to non technical product owners that then force adoption onto development teams

Route 53 is a pun on the DNS port—not exactly common knowledge among nontechnical product owners. Anyway, DynamoDB and Route 53 succeed on merit. There are certainly better examples of shitty technologies that win on marketing or other nontechnical considerations. E.g., Oracle anything (of course Oracle aren’t know for being purveyors of microservices).
Being able to scroll out swipe left and right would be quite enough. Foobar2000 has swipe gestures, but that brings you to the "now playing" view (for that one I'd prefer an always-visible area at the bottom, like VLC does, since it's only a single track).
I know Japan likes red, but I'm surprised that the TSE uses green for a negative/falling connotation. That's not a Japanese cultural thing generally, AFAIK.

Is this just a historical path-dependent thing — e.g. stock-exchange trading floors traditionally all buying their sign boards from some specialty company that produced boards specialized to have exactly two "color channels" — red and green — and then, when the TSE got theirs, it was all they could do to just wire the color channels up backwards?

(I guess there are a few types of meters that always use red as high and green as low — e.g. pressure gauges. But that's because red in those cases means danger. A high stock value isn't dangerous!)
>> I have natural immunity too. Got it by being vaccinated, instead of taking the much larger risk of being infected.

> That is referred to as "vaccine derived immunity", look it up. Drastically different from natural immunity.

Uh, what now? "Drastically different"? Are people who get vaccinated aliens with different kind of immune systems?

Natural immunity and vaccine derived immunity are quite similar, since they arise from the same mechanisms. IIRC, the main difference is vaccine derived immunity is more consistent and predictable (e.g. in a lot of cases natural immunity can be inferior).
Well, if you're comfortable with functional programming, that's great. Seriously, awesome! But you're in the minority.

Hard disagree on the "decent programming language designer", though. Nix-the-language is beautiful. It's tiny, with a minimum of concepts to learn, and very simple, regular syntax. At the same time, it's not so spare as say, Lisp or Scheme. It's really good. The implementation of that language could use some work - interpreter speed and debugging tools come to mind rather quickly.

I think the problem you've encountered is nixpkgs. It's a huge, sprawling code base with a lot of legacy code and a number of paradigms that were enthusiastically adopted and then later supplanted. In contrast to the language and tools which are well documented, there's basically no documentation, and what little there is hasn't been kept up-to-date as things change.

Still though, I think the biggest issue facing nix users is that the rest of the computing world works on the assumption of mutable software installations. The way pip assumes that the python interpreter and the python packages that have been installed are locked in a death grip drives me nuts. Even if you don't go full nix-store, could we at least separate those things? Even node gets that right.
The OP was pretty explicitly arguing in favor of monolithic architecture.

> The term "Monolith" was devised by people who wanted to brand microservices as newer and superior. It's almost as if in order to succeed these days you need to discredit and disparage your competition rather than simply having a better product, and that's why I don't buy into buzz words at all.
News agencies worldwide suppressed the 'lab leak' theory. Facebook actively censored it. Fact checkers 'disproved it'. Leading scientists called it a conspiracy theory.

Yet it appears to be a perfectly valid theory.
https://www.amazon.com/Viral-Search-COVID-19-Matt-Ridley/dp/...

It is not the first time that this has happened. We were told that Irak had weapons of mass destruction. It was announced at the United Nations. All mainstream news agencies reported it.

For many, many years, the US was 'winning the war' in Vietnam. All news agencies agreed. The US was not winning.

The mere fact that many, even most, people agree with something does not make it true.
Stumbled upon this site recently, https://funwhileitlasted.net/. It made me nostalgic for the days where there were sites dedicated to one fairly narrow subject. I this case it was defunct sports leagues and teams.
Depends on the eco system, I've found this straightforward with maven / sbt + GRPC / Akka / Thrift, and then more difficult in environments that don't have baked in concepts of packages and module deployables, but from experience the mention of any of those technologies can start a flamewar of good and bad experiences therein :).
Identifying Bot Traffic with SQL
My team built an application using a multiple not so well thought out microservices, and it ended up creating a lot of unnecessary maintenance and complexity and has been a long term pain. I wish we had just built within a single service.

But, my company split out a much older, larger monolith over many years into separate services with clear ownership across a variety of teams. This has been a huge benefit, coming from clear ownership, API boundaries, and separation of concerns.

So neither monolith or microservices are a clear winner. It depends on context. An easy litmus test, IMO, is that a single dev team will get little to no benefit from managing many microservices, but a company scale problem will get a lot of benefit from having each team manage and deal with an independent service.
And this distinction is very important. Organizational scar tissue can and does develop, where things are a certain way and no one for sure knows why, but there are {vibes, superstition, ego, whatever} that develop into maintaining them.

It's really important to challenge these things, but they're tricky specifically because no one owns the decision (the person who chose left, or forgot, or who knows) so a naïve application of "don't change what you can't figure out the reason for" fails when there may be no clearly documented reason, beyond a shared hunch that it mattered at some point.

Sure you should still investigate, but if after a decent investigation you can't figure out why, yes, change the thing. Sometimes you'll be wrong, but this is what we have error budgets for.
And then let's have daily progress meetings to report on the status of each chunk of the investigation! Please update Jira at least once a day!

This is a great example of the perverse incentives built into the "everything should be done in one day chunks that you report on daily". The team is incentivized to ignore highly important but challenging / hidden work, and instead only focus on things that are highly visible to management.
The kernel shares some pieces with FreeBSD/NetBSD, but they're mostly very old and have developed separately since then.

The userland and libc are actually a lot more similar and some pieces are even up to date with them.
Commonly used vaccines are known to cause widespread temporary myocarditis?
The simple work-around is not even possible on Fedora CoreOS:

$ sudo chmod 0755 /usr/bin/pkexec
chmod: changing permissions of '/usr/bin/pkexec': Read-only file system

Security preventing security I guess...
But it's ignoring the human psychology involved. "Ignorance is bliss" is true. Yes ok, I could have invested in $GOOG and earned a bunch of money that would be worth more to me today, but that just isn't how we process information. What happens instead is that I buy the coffee because I want it and now I can't even enjoy it because I know it's "stupid."
The alternative would be (almost) everyone just using the font with most emoji in order to support messages from other platforms, so sort of a standardization that nobody can rely on. I don't see how that's preferable.
> shadowbanned within 15 minutes

I'm not about to defend any commentariat anywhere, but you really have to make a stinker of a post to get that kind of thing here.
Maybe if vendors were more open to allowing third-party applications on their platform, people wouldn't be so motivated to increasing the capabilities of the web. Instead, app distribution has turned into a living nightmare, so it's unsurprising to see the web evolved into the monster it is today.
> Such a step back in power user features these days; being able to say "create a playlist of all songs in genre X with 4+ stars" or "Play 5 star songs I haven't listened to in at least 12 months" was amazing.

Possibly ironically, both of those examples work on current versions of the Music app on macOS, and will work with both local and cloud files in your library. There are many valid reasons to dump on The Application Formerly Known As iTunes, but it remains more capable at library management than I think it's usually given credit for.

(N.B.: the same cannot be said for its iOS counterpart, which can sync smart playlists but not create them, and seems to have dropped support for star ratings completely.)