skysight-inc/HackerNews huggingface dataset:
There are a few gripes I have with microservices.

I think most places rearchitect to microservices because it’s the new shiny. They don’t do the engineering necessary to create a detailed cost/benefit analysis, they just feel it will be better and so they jump in.

For the same reasons the companies don’t do the cost/benefit analysis they don’t spend much time thinking about how they could benefit from rearchitecting their monolith into various libraries, modules, packages and interfaces.

Because they don’t think much about these code boundaries, they end up turning their monolith into a distributed monolith. In doing so they don’t get the major benefits microservices are meant to provide, such as independent code deployment. They also lose the benefits of a monolith, such as less ancillary complexity. This situation is the norm and is evidenced by “deployment parties” where you can’t just deploy one microservice because 11 of them need to go to prod together.

What I have seen a lot of over the past few years is a push to get off main frames and into the cloud. This is a valid driver for rearchitecting but microservices are just one of a number of solutions as the cloud is very flexible these days.

I assert that a lot of rearchitecting to microservices can be attributed to the fact that our industry, as Alan Kay has said, is a Cargo Cult.
What happened 3 days ago?
I don't know of anyone measuring it but the service lines and infrastructure providing gas leak GHG's in the process all over the place. The stoves themselves leak a little.

Modern induction stoves are far superior anyway you would be doing yourself a favour upgrading. That gas is somehow "qualitatively better," is propaganda from the gas companies to keep people choosing gas. "Now you're cooking with gas," is from a gas propaganda short aired decades ago... to keep people choosing gas when people were starting to convert to electric.

There's no good reason I can think of to keep using gas stoves.
Yes, but this sort of problem exists with other 'standard APIs' too which change much more frequently than POSIX.
A strategy for battling your mind’s “open loops”
Transitioning into a state of deep work while fighting interrupting thoughts
Root problem is the lack of namespaces in C, making collisions inevitable and painful to deal with
We like ChatGPT and use GPT-3 as our backbone too.

I think the major difference is we provide a tailor-made interface makes it simple for users to customize and fine-tune their reviews.

You can sign up and use free credits to try it out! :)
...and if you've had a team of developers eagerly using microservices for pretty much everything in production code for any significant period of time, microservices become like a big ball of mud held together by a lot of hair. I shudder in horror when I think about how impossible it will be to maintain all that code in the future.
Got it, thanks for the information! I hadn't known it was all VRAM for model serving.
I've found the nuance is in the middle somewhere. We've all seen the madness with web scale infrastructure for a personal blog, but one gigantic compilation unit will eventually bite you in the ass too (i.e. rebuilds get very slow).

What you probably want is something where everything lives in the same repository, but as separate modules/dlls which can be included in some common execution framework the team previously agreed upon.

If you have something approximating microservices-as-dlls, then you are essentially eating cake while having cake when you really think about it. Function calls are still direct (sometimes even inlined), but you could quickly take that same DLL and wrap it with a web server and put it on its own box if needed.

Establishing clear compilation unit boundaries without involving network calls is the best path for us, and I suspect it's the best path for anyone to start with. We take this "don't involve the network" philosophy into our persistence layer too. SQLite is much easier to manage compared to the alternatives.
Seems more like asking, "How can I make sure that if there are layoffs, I'm not included in them?"
Drone-mounted Apple Watch Ultra used for gunshot detection
Ask HN: What's a good home router?
I have an Archer A20 3.0, an AC4000 home router. It's abandoned: latest firmware is from October 2019. Feature set is limited and dodgy, and it isn't rock-solid reliable.

I'm having a lot of trouble wading through options. Finding a good price-to-performance ratio is hard.

I'd prefer to future proof with AX. I'd like robust features that include VPN, parental control, reporting, and more.

I'd prefer something that could use OpenWRT or similar as a fallback, in case the vendor abandons it or I loose confidence in its firmware. (I've done DD-WRT on a WRT54G, so generally familiar with what all this means.)

I think "just a router" is best. I have a single-story house where the A20 permeates everywhere I need with no issues, so I don't think mesh has value. Also, I have no Ethernet wired in, so mesh devices would have to be wirelessly connected.

I'm open to Unifi and have helped with some corporate installs of it, but I am concerned it may be too much for my needs.

What works well for you?
That's the hardware it runs on, not the software architecture of GPT. I could equally say that transistors are faster than synapses by the same ratio that marathon runners are faster than continental drift.
There is one more case, for your list at the end. The names could start colliding when you get to add interaction with a posix system.

That is, most of the point of that was for some standards to give a "follow these rules, and you will have an easier time integrating with this standard if that is in your plans."

Obviously, if you have no plans to head to posix, they accomplish nothing for you. Similarly, not following the rules doesn't prevent that direction, just adds some extra work. Potentially.
You should see the other article they published.
Yeah, on the one hand there is public good, on the other hand, this is like regulating cigarette smoke in your own home. I suppose they can regulate manufacturers but they cannot go and inspect your home for violations that would violate the 4th amendment to the American constitution.
There is something else that points to. Not everything is measurable.
Done.blocked.todo
Hi. I'm Will from done.blocked.todo.

Happy to take any q's
Thank you Andrej Karpathy for the work on ai and gpt models. It really helped me solve a problem as entrepreneur. I started making first few grand from ai.
> Any time you lean on code in a random GitHub repository, where you never speak to the author and just use the API you're given, you're doing microservices. This works well enough so long as the product does what you need of it.

No. That's not what a microservice is.

I understand you are trying to draw analogies, but a library is not a considered a microservice.
That's crazy! Aren't most U.S. homes single family units? Adding a range vent is just a matter of making a 3x10 hole in an exterior wall and sticking a $40 external vent through it.
When I worked on video systems at Apple I got dinged on a performance review for negatively comparing their kernel to Linux too many times. I’m pretty sure they still have a dogshit IO scheduler but I haven’t used a Mac in ages.

I suspect it’s not that people can’t do the work and more that Apple’s silos mean their already employed engineers are not allowed to try or even talk about it.
Bash is ~okay for small and simple enough tasks. But, above a certain complexity, I think probably anything else is going to be easier to maintain & have fewer footguns.
I think to summarize.

BS is not in the picture as long as you are alone, not interacting with anybody and betting on a far away outcome which you cannot influence.

Say sports betting

As soon as one of the above ceases to be true, then BS enters the picture if you allow it too.
Natural gas leaks are responsible for way more greenhouse gas effects than stove CO2. That is, it's not the stoves, it's the transmission infrastructure.
Drones, iWatches and Guns
Norwegian startup Triangula using Apple Ultra Watches on drones as prototype for their gun shot detection system.

https://apple.news/AYdMJlQ2rSGKFEXcjBcXeXw
Some cars also use unevenly spaced tick marks on an analog dial. Nice in that it gives you the sweep needle and range of scale without overly compressing the range of most interest.

Analog tachometers for race cars do/did the the same thing:

https://www.primusracingparts.com/Racetech-tachometer-0-8-rp...
A recurring question I have is: how many microcontrollers/CPUs are in a modern personal computer? There are clearly a lot, but just how many?
My educated guess would be that creating the list and, in particular, doing the shuffle using ‘random’ take most of the time.

It’s 100 times 10,000,000 items, so going through a billion items. Iterating over that shouldn’t take more than a few seconds on modern hardware.

Shuffling probably adds a billion calls to a random number generator.

See also https://stackoverflow.com/questions/53378699/random-shuffle-...
Two things:

1. The default recommendation may likely be "use gas stoves with a good ventilation solution" rather than "throw out all gas stoves"

2. A change does not need to occur immediately. It's not unreasonable to expect that a shift in usage over a 10-15 year horizon can be planned out as part of larger grid considerations. Might be an awkward energy demand to manage, however, as it's all focused on meal times and not spread throughout the day.

For my household we've read the current material as a reminder to use our vent hood more often. We weren't doing so for a convenience (noise) reason, but of course burning things indoors can create all sorts of air quality issues that are remedied in part by the ventilation system so we now do.
For the purposes of my analogy, please assume the police are on the scene already and directing you to continue driving past.
Ironically, the post is also lying about climate change. Gas stoves have very very little to do with climate change, the use of fossil fuels for cooking is a rounding error and irrelevant. Gas stoves are worse for your health and an inferior product in every dimension except wok cooking.
Funny, I was thinking of linking to that page myself in support and decided against it. I particularly was thinking of:

"What does this muddy code look like to the programmers in the trenches who must confront it? Data structures may be haphazardly constructed, or even next to non-existent. Everything talks to everything else. Every shred of important state data may be global. There are those who might construe this as a sort of blackboard approach [Buschmann 1996], but it more closely resembles a grab bag of undifferentiated state. Where state information is compartmentalized, it may be passed promiscuously about though Byzantine back channels that circumvent the system's original structure."

and

"Such code can become a personal fiefdom, since the author care barely understand it anymore, and no one else can come close. Once simple repairs become all day affairs, as the code turns to mud. It becomes increasingly difficult for management to tell how long such repairs ought to take. Simple objectives turn into trench warfare. Everyone becomes resigned to a turgid pace. Some even come to prefer it, hiding in their cozy foxholes, and making their two line-per-day repairs."

Superficially it may seem like these criticisms apply, but they don't.

Microservice architectures can't have big global variables typing things together, structurally. Even if "everything talks to everything" (which is actually unlikely, sarcasm aside, even the absolute worst systems have more structure than that in a microservice architecture), it does it through a defined mechanism of RPC. State can't be passed through "back channels" because no back channels exist; you must go over the network, which is the "front" channel, not a back channel.

By structural necessity, a microservice confines the scope of changes in the microservice code itself. There are then of course still scopes of changes that are even harder with microservices at the global level, but for refactorings that aren't behavior changes a microservice necessarily confines the scope of changes to the microservice itself, a small fraction of the whole. As long as the API accepts the same input and returns the same output, it can not blow up another service three layers away because it has no access. But that's a distinguishing characteristic of a Big Ball of Mud.

Big Ball of Mud isn't just a slur; it's a distinct pattern as described in that paper. At best a microservice architecture can be a lot of smaller "balls of mud" hooked together, and that's still a problem, but it is its own problem. This is proved by the fact that the solution to a Big Ball of Mud won't work for an microservices architecture disaster... indeed, they aren't even sensible. If two problems require separate solutions and the solution to one is not even conceivably applicable to the other (that is, not even a "bad" solution but simply no solution at all), they are clearly not the same problem.
Windows Vista was introduced in January 2007, and was the first version of Windows to include User Account Control (UAC).
House Republicans Ready to Give Big Tech the Benghazi Treatment
I 100% relate to your question and feeling. I too am in my early 30s, and overcame those same thoughts. Those thoughts plagued me from about 26-years old to about 30-years old.

I remember endlessly googling, "Is 26 too late to start programming?", "Is 27 too late to get rich?", etc., etc. Now, my age doesn't worry me one bit. My perspective has changed dramatically when I truly realized a couple of things:

1. 30s is not old. If you live until you're 65 or 70, that means a career change right now would amount in 30+ years in that field. I felt like my life had passed me by at 28. Now I look at a 28-year old and think, "That dude doesn't know how young he is." So now, I have enough experience to know that right now, I am very young, within the grand scheme of things.

2. My thinking was heavily influenced by social media. All it takes is seeing a kid who is 10-years younger than you making double or triple your salary for you to feel like you're too behind. The reality is most people are not making those types of salaries.

3. Do research on people for whom success came later in life -- there's a bunch of them. And we're only talking about public cases; not cases of late success that never made it into the public eye, which I'm sure there's even more of.

4. I've learned to focus on my quality of life (health, financial security, relationships, learning, growing, pursuing things that I'm into, traveling). My goals are not "getting rich", but rather, getting to a point financially where I don't have to work. That will probably take me 10 - 20 more years, and I'm okay with that. I just don't want to have to work when I'm 65.

5. When we find ourselves in this situation, feeling that life has passed us by, we have to throw time out the window. The problem is, we start thinking of ways we can "remediate" the situation quickly. But progress takes time. So do your best to just stop thinking about doing something quick, and really try and change your thinking to putting in the work daily (even if just a little bit), but being consistent.

I feel like I'm ranting, but I relate a lot to this question, and after really coming to an understanding of my personal situation, I was able to truly free myself by coming to grips with the truth.
Is there some broken screen effect on this website? or am I going insane?
Programming language designer here.

I'm currently making a language, and yes, I'm reserving words for it because I want an easy C ABI. But I'm also making them easier to avoid.

Here's my list of reserved words:

* Anything that begins with `y_`.

* Anything that begins with `yc_`.

* Anything that begins with `YC_`.

* Anything with three or more consecutive underscores.

* Edit: Anything that begins with an underscore. This is because my language will be able to transpile to C if necessary.

The first is for types and items in the standard library (the language's name is Yao, so a `y` makes sense). The second and third are for the C ABI (hence, `yc`) and for historical reasons. `YC_` in particular is for C macros.

The last is for name "mangling." I put it in quotes because my language's standard name mangling (it will be the same across every implementation) will not really mangle the names. Instead, it will concatenate them, using five underscores between package names, four underscores between packages and items in a package, and three underscores between an item and its suffix. (For overloaded functions, the programmer has to define a suffix for each one. That suffix is how their names will be different in the C ABI.)

My hope is that these rules will not be too onerous. I don't think the reserved prefixes are used much, and I haven't seen anyone use more than one consecutive underscore, though I'm allowing one more, just in case.
We won’t stop having slave children mine cobalt if we don’t stop making EVs that need it.
> Have you ever seen a JS project without any sort of build in a professional context?

Imagine a world that pre-dates typescript, node, webpack, browserify, gulp, grunt. You were lucky if you had a server framework that concatenated files for you, otherwise you were stuck with 6000+ line "global.js" files. Then you had to fix merge conflicts in that file because SVN.

Whenever someone complains that frontend JS is too much, I just think back to how it used to be.
Oh yes, that's because natural gas is renewable source of energy, I have completely forget.
I got bit by this last night (C++), and had no idea that it was a thing. What a timely post!
>Context matters so much.

Well that point that just makes %90 of web articles moot.
The blog author also takes umbrage at the paper's authors' other work and biases. Since the blog author is anonymous it's not as clear what their biases may be, but the only other blog they have posted comes to the conclusion that "whatever travails American Blacks suffered during slavery no longer matter for their socioeconomic attainment today," citing an infamous eugenicist.

Take that as you will.
Totally agree on this point.

I don't think either need to be villified. I still smoke meats with wood a few times a week and we don't fret over burning anything. Since we cook at home daily we shoot to minimize it though.
I agree completely. The current FAA outage is a good example of this. What if the system responsible for NOTAMs was the same system responsible for sending system outage messages. They weren’t so that status could be communicated while mitigation was done on a system with unrelated concerns.

At the same time, a few person startup should probably focus on what allows them to deliver the fastest. I’ve seen that work with relatively monolithic systems and with SOA, tooling choice makes a huge impact.
I've been working on a project with flask + sqlalchemy. I have those sql queries returning a bit of rows (up to 20k) and that are quite slow. SQLalchemy does not seem to support caching the results and I've started to use flask-caching[1] with redis using the @cache.memoize() decorator.

Just wondering if I am taking the right path or if there is better alternative.

[1]https://flask-caching.readthedocs.io
Airlines aren't the only things doing "air missions" - there is software that filters out much of it, but it IS quite archaic (similar to how the "official weather" notifications are set out).

Look at the Ukraine one for a pretty scary example.
It's especially interesting to contrast this rise in the brutality, violence, and realistic physicality of western Christianity's art with traditional Byzantine iconography. My first thought goes to Myshkin in Dostoevsky's The Idiot. Seeing an image of the dead Christ from Holbein [1]:

"At that painting!" the prince suddenly cried out, under the impression of an unexpected thought. "At that painting! A man could even lose his faith from that painting!"
"Lose it he does," Rogozhin suddenly agreed unexpectedly. They had already reached the front door.
"What?" the prince suddenly stopped. […]

By contrast, I once read or heard somewhere that in Byzantine depictions of the crucifixion, one cannot really know if it is the cross that holds up Christ's body or He who holds up the cross.

[1]: https://en.wikipedia.org/wiki/The_Body_of_the_Dead_Christ_in...
Java has goto and const as reserved keywords. Source: https://docs.oracle.com/javase/tutorial/java/nutsandbolts/_k...
If you could bring that up with cloud providers that would be great ;-)

The reality is infrastructure is commonly in unknown states, whether we like it or not.
Nice I like the concept of turning around Graphviz dot files and turning them from an intermediate representation of visualization into the actual source of truth for the system. Cool idea.
To be fair the problems with gas stoves have been known for a while now. It's even made its way to HN a few times. https://news.ycombinator.com/item?id=25332332
Do you happen to have a source on that? The last one I found that was actually linked to domestic terrorism was Feb 2022. As far as I can find, the more recent ones have not been. In fact the police had to make a release saying the media made up the link and they had no evidence of it in the recent Georgia ones. In fact they have no idea the motive at all in those ones. The ones in Washington state were so a couple people could rob stores (they have made arrests already).

I assume you are implying the right is doing the attacks here? A quick googling for attacks on infrastructure seems to mainly return cyber stuff. However most of the results on non cyber attacks are for multiple fires and train tracks that were sabotaged in past couple years in Washington state. The people that have been arrested for these attacks are not right wing, in fact for the most part they are from the left.
It is amazing that gas stoves as something to think about have entered into the public space so rapidily from nowhere.

It's so deeply deeply bizarre. Am I the only one wondering not about the topic but about how these topics occur?
Thank you for your encouraging words. Indeed we will gradually introduce paid tiers. Pinggy is in alpha stage. With your feedback we will work towards a mature offering.
Protein Poisoning
Hey Hackernews,

One of our community members recently wrote an article on something they are really passionate about: using Rust and Next.js together to deploy web apps that are both super fast and super fun to work on.

In the article, they give you a step by step walk-through of how they did it. They cover everything from setting up your project to deploying it in production using shuttle, and even share some tips and tricks that they learned along the way. It's perfect for anyone who wants to learn more about using Rust and Next.js, or for anyone who's looking for a new way to level up their web development game.

Love to hear your thoughts on it!
If they think gas stoves are dangerous, I wonder what they think about ventless gas fireplaces?
To be clear, my comment wasn't a critique - if you're an early-stage startup, it makes sense to try new things and attempt to catch new trends early, since they can carry you past your established competitors.

I think the search engine with citations is a great idea - you're grabbing onto a big trend while solving a clear, hugely-discussed problem (you can't trust LLMs to give truthful answers, and that's exacerbated by the fact that you can't see where their info is coming from). Hope it works out for you.