skysight-inc/HackerNews huggingface dataset:
In my experience, i've seen the modular code approach more often than separate deployment approach, quite possibly because the latter is still a bit harder to do when compared to just having 1 instance (or people are just lazy and don't want to take the risk of breaking things that were working previously for future gains), but sooner or later the question of scalability does come up, at least in successful projects.

Let me tell you, as someone who has delivered a critical code fix for business continuity after midnight a few times, slapping N instances of an app runtime in a data center somewhere is way easier than having to struggle with optimizations and introduce more complexity in the form of caches, or write out Hibernate queries as really long and hard to debug SQL because people previously didn't care enough about performance testing or simply didn't have a feasible way to simulate the loads that the system could run into, all while knowing that if your monolith also contains scheduled processes, none of your optimizations will even matter, because those badly optimized processes will eat up all of the resources and crash the app anyways.

In short, the architecture that you choose will also help you mitigate certain risks. Which ones you should pay attention to, however, depends on the specifics of your system and any compliance requirements etc. Personally, as a developer, fault tolerance is up there among the things that impact the quality of my life the most, and it's pretty hard to do it well in a monolith.

In my eyes the problem with contracts is also worthy of discussion, though my view is a bit different - there will always be people who will mess things up, regardless of whether you expect them to use modules someone else wrote and contribute to a codebase while following some set of standards or expectations, or whether you expect them to use some web API in a sane manner. I've seen systems that refuse to acknowledge that they've been given a 404 for a request numerous times (in a business process where the data cannot reappear) and just keep making the same request ad infinitum, whenever the scheduled process on their side needs to run.

So, having a web API contract can make managing responsibility etc. easier, however if no one has their eye on the overall architecture and how things are supposed to fit together (and if you don't have instrumentation in place to actually tell you whether things do fit together in the way you expect), then you're in for a world of hurt.

To that end, when people need to work with distributed systems of any sort, i urge them to consider introducing APM tools as well, such as Apache Skywalking: https://skywalking.apache.org/ (sub-par interface, but simple to set up, supports a decent variety of technologies and can be self hosted on prem)

Or, you know, at least have log shipping in place, like Graylog: https://www.graylog.org/ (simpler to setup than Elastic Stack, pretty okay as far as the functionality goes, also can be self hosted on prem)
been using pass for more than 3 years now never had an issue, great CLI tool
I've argued for a long time that microservices should grow out of a monolith like an amoeba. The monolith grows until there is a clear section that can be carved off. Often the first section is security/auth, but from there it's going to be application specific. A modulith could be just another step in the carve up process.

But, there is no right answer here. Application domain, team size, team experience, etc... all matter and mean a solution for one team may not work for another and vice versa.
Testing changes here could mean progressing through several seasons of career mode in order to test out a change

That's like the Groundhogs Day of programming. Living the same season over and over again, changing things until you get it right and can move on. Sure, ai guess that's kind of programming in general, but on this level it's most of your day. No developed cheat codes?
There is a more serious downside that you don’t mention: splitting things into modules takes time and involves making decisions you likely don’t know the answer to. When starting a new product, the most important thing is to get something up and running as quickly as possible so that people can try it and give you feedback. Based on the feedback you receive, you may realize that you need to build something quite different than what you have. I’ve seen plenty of successful products with shoddy engineering, and I’ve seen plenty of well engineered products fail. Success of a product is not correlated with how well it’s engineered. Speed is often the most important factor.
According to this[1] post, that might not always be the case. I also have this assumption about alexa devices, and I haven't seen any other evidence to say that voice recognition can happen locally. Personally, I find the claim in the thread a bit hard to believe, but...

[1] https://community.home-assistant.io/t/local-voice-control/29...
Having worked on some cloud native/ cloud first apps, I would love to see a language or framework a long the lines of a class being a lambda/cloud function, and when calling a method of that class (it doesn’t have to be OOP, someone smarter than me must figure that out) the language itself will sort all the http requests and deployments and junk for you and your project becomes scalable, serveless services but with code that is actually coherent and readable.
The pricing page defines how many page views you can have

https://www.plasmic.app/pricing
10K monthly page views
250K monthly page views

If they dont handle hosting the page themselves do they have
code to record every pageview on my server stack?
Diamonds are a proof of waste.

Havans are a proof of waste.

superbowl ads are a proof of waste.

But waste is proof. Proof is valuable (not a waste).
Replace "normal/natural" with "idealized": yes, free market theory promises quite strongly that if there is a more efficient way to produce something, eventually some contender will discover that way and begin pushing out competition until that competition adapts. That mechanism does not require demand elasticity at all, it can work just fine in a perfectly inelastic market. Food is the closest thing we have to an inelastic market and it's certainly not a market characterized by lack of price competition caused by that absence of demand elasticity.

Yes, expanding markets work different than stable or contacting markets. But that difference is that the expansion can gloss over certain failure modes. Yes, Intel might have occasionally pushed out a new Pentium generation if x86 had been the only CPU architecture in the world and AMD (and Cyrix) had not existed, because the demand for instructions per second rises with availability (this abstraction conveniently groups demand from replacement upgrades and demand from new use cases into a single bin). But that would have still been a broken market, even while the brokenness was temporarily hidden by demand elasticity/expansion.

Model T wasn't the most efficient moment of car manufacturing, not if you include features in the equation. A car with the performance of the model T wouldn't sell today for a dollar beyond scrap value, and even Tatas and Dacias can e.g. be started without cranking and so on. The closest equivalent to a Model T would be a Tuktuk and those are cheaper today even before adjusting for a full century of inflation.
Show HN: High Converting Landing Page that even no coders can do?
Landing Page should have one clear goal. It has to convince users to take specific action (e.g., purchase, booking a visit, leaving contact details). Landing Page can give a great boost of conversion. But if it is that simple to do?

It can be. In BOWWE, you can develop such a Landing Page. How? It depends on you. You can start from scratch or through one of over 200 ready-to-use templates. Everything is getting easier and better with 570+ widgets, sections, and blocks. A developing high-converting Landing Page doesn’t have to take that much work and time! Even for no coders…

Feel free to check it on BOWWE. All feedback is welcome.
The improvement here is that it can go as high as 300m (1000ft) and winds are much stronger there. And once you're done or approaching the harbor you can furl it in and never think about it again. Sails... not so much. Especially on ships of this size!
I believe the etymology of 'router' (sending network packets along a route) and 'router' (cutting wood) are different. They are pronounced differently in British English, at least.

Rout, via Old English 'wrotan'

https://www.etymonline.com/word/router

Route, via Old French 'rute'

https://www.etymonline.com/word/route
> Reddit can fit nicely into the metaverse

I agree. But first they'll have to get on the blockchain, and then build up their autonomous vehicle division. No big deal, just use CRISPR.
Both of those, and also regular M-x shell, work remotely with TRAMP.
Looks like future-proof already, for a while.
GitLab runs board meetings with Sid, Stella and Quinn from Sourcegraph
Which it does, as they dont pay any inheritance tax... for the upper tier in society it is openly called a voluntary tax that only the poor (what one might consider middle class I guess) or stupid get stuck with.
Here are some suggestions.

- Designing Data Driven Applications - Kleppmann

- The Art of Unix Programming - Raymond

- Pretty much any of the programming books published by No Starch Press

And more pieces of advice.

1) Learn SQL. I mean really, really learn SQL. And then learn the basics of how relational databases work. I'd recommend Postgres for the dialect because of its quality and maturity.

2) Absorb everything you possibly can by Rich Hickey and Stu Halloway. "Simple Made Easy" is a talk that you can watch dozens of times over a decade (I have) and still come away with new insights at different levels of experience. The Clojure community has very mature engineers and they work on extremely hard problems. They're concerned with fundamentals.

3) https://www.ribbonfarm.com/2013/07/10/you-are-not-an-artisan...

4) You're going to learn most by immersion in an ecosystem, and the best way to learn is to find a job at a solid tech organization. It doesn't have to be a FAANG (and probably shouldn't be honestly), but find practitioners working on problems you like and show up to help. There is no shame in having entry level grunt work on unglamorous projects: you will learn the most on messy projects other people do not want to work on.

5) Do the work. I've worked in software for 20+ years and my first job was in a tiny cube making $5.15 an hour and I retired a year ago. It's popular to talk about work+life balance and lots of creature comforts, but the truth is hard work and forcing yourself to constantly solve harder problems (depth) and learn more languages/techniques/practices (breadth) is what you need. There is no substitute to persistence and pushing yourself to accomplish harder things. Have pride in your work and humility in what you do not know, which for all of us is quite a lot :-)
curl -H/--header itself also takes a file name prefixed by @, including - for stdin. So you could go curl -H@- <<<'API-Key: Foobar', or if you need to specify multiple sensitive headers, curl -H@<(echo API-Key: Foo) -H@<(echo Pre-Shared: Bar)
> 3 lines of code shouldn't take all day

Sure they should. I often spend all day on negative numbers of lines (I always say that the best code I write, is the code I don't write).

The complaint seems to center on CI/D services that provide inefficient build times. These increase the pain of "round-trip" implement-test-refactor.

That's quite valid, as this is how we tend to work, these days (at least, that's how I work). I often take it a step further, and iterate the design as I progress[0].

But I am one that got their start in the waning days of "big iron," when compute time was the costliest and most time-consuming part of the whole process. You'd need to schedule for computer runs, which would often happen overnight. This meant that it was very important to have your code complete, and debugged, before submitting it for compilation.

Argh. I miss it like I miss a case of food poisoning. It did teach me to do my homework, though.

[0] https://littlegreenviper.com/miscellany/evolutionary-design-...
The goal is to sustainably build software, which only can be done if ops and maintenance is regarded a goal, a pillar to build upon.

Like TDD the design of software changes when you have experience with ops/maintenance. Take logging/tracing: what to log or trace is first and foremost a matter of experience with maintenance/ops!
Building in logging/tracing/monitoring from the get-go because you know that you want to know what goes wrong, when it goes wrong etc...

can one regard oneself as expert if you know only a part of the domain- I think not!
"Don't do the crime if you can't do the time" is pretty authoritarian, as far as quips go.
Did someone say Microservices?

https://www.youtube.com/watch?v=y8OnoxKotPQ
I've enjoyed developing in the language professionally for many years. Truly, few things allow as rapid prototyping with such efficacy for so few lines across so many domains in a unified interface. There are some brilliantly innovative things across the language and, once you really get into the weeds of how to write efficient functional code, some of the things you can do are incredible.

Two things, though. Firstly, they are very stubborn on condoning a community to coalesce around the language other than through 'official' Wolfram channels. This comes from the big man himself, no doubt. As much as they want to drive adoption by coming up with (what they think are) "cool" sounding initiatives, they will never get devs to break from their core workflows and tools to do things the Wolfram way. There is no first-class support for daily-driver editing (vscode, emacs etc etc) for large-scale projects (other than an ancient eclipse package). Brenton Bostick at Wolfram has done some truly first class work in closing this gap though.

Secondly, this is the first major release that is a bit 'ho-hum' for a while. And it's reflective of the fact that whatever Stephen's pet interests are at a particular point in time will get attention in a release. For example, V11 was huge on Machine Learning and AI...now it barely gets a mention or extra development. Because SW is so focused on his Physics Project, this will likley be the case for a while.

To anyone thinking about using the language -- dive in. It's brilliant and expressive and fun. It's satisfying. You can do cool stuff. It just becomes very difficult when you want to scale it.

Anyone from WRI reading this: please, please, please let the community develop organically and support the toolchain everyone has wanted for so long. Or don't. But you need us more than we need you. Oh, and simplify the product line -- what a nightmare for newcomers to navigate. :-)
Functional Programming a Starting Point
Season 2 should really be part of the title, I thought these might have just been the old season 1 notes which I liked when I stumbled on them years ago. But I'm glad I clicked through, the little details the author goes through are always interesting.
I worked at ibm research last century. They spent 6 billion on research. They had a chip fab in the building and still were making chips at the time. They had a wide range of researchers (mathematicians, physicists , software). working on all sorts of stuff (very motivated). Lots of cooling gasses.

The problem was trying to turn those inventions into something they could sell. Chip tech was sold to whoever they could.
I had a same kind of situation. I had only one video 7 year old and no activity. Appeal did not do anything.

Not even getting response. After the appeal they deleted also my YouTube account which was even more scaring.

It is crazy how much playlist, channels and history was in the account. I am really puzzled that my mobile version still works with my user data.
At some point during the early days of this site someone started drawing a very long ascii line which you could scroll for many many hours and not reach the end of. It became a satirical – or who knows these days, maybe literal – cult. Here’s the best summary I can find with a few minutes of lazy searching:

https://yourworldoftext.fandom.com/wiki/The_True_Diagonal

I seem to remember someone posting a screenshot of a short inspirational essay you would find if you reached the end, but looking around it seems like folks are posting various different screenshots of what’s at the end, so I suppose that adds to the mythology a little bit.

--

Edit: I found the screenshot of the essay in my filesystem so there's no context, but for whatever it's worth here it is:

https://raw.githubusercontent.com/aboxwithrocksinit/test-buc...
Test Containers and Clean Architecture
The real pattern is to write a separate service for user auth and then put everything else into a monolith. The auth service is almost always the first one to be "broken out" so just get that out of the way first. Now you have maximum flexibility.
I'm happy to hear you're a security engineer. I'm sure you're the only one here.

> No it isn't. Security by obscurity is a very valid defense-in-depth measure.

No-one has said otherwise. I said this in the gp of the comment you're replying to.

> Show said evidence, please

No need: you've just shown two good examples yourself. Bugs found by scrutinising open source software. I'd be curious to see how many examples you have of the same found in closed-source software (or are you suggesting there's no closed-source software out there with vulns of the same vintage as Heartbleed).

> No, they're arguing that there is no guarantee that these 99 white hats are somehow better than the 1000 black hats

This sentence seems to make the same assumption others have: that "black hats" are exclusively looking at open source software.

> 1-2 unpaid volunteer white hats might inspect the source if they have time

This might be true of a library noone uses (in which the impact of an exploit is limited by it's popularity). For popular libraries, there's an entire SCA industry of commercial vendors selling products that disprove this (transient dependency reporting is done throughout large corps that rely on open source supply chains). Admittedly this industry is more mature in some areas than others (e.g. package-managed language ecosystems -vs- orchestrated system deps), but it's still not insignificant. There's absolutely no comparison between this effort and the number of eyes looking at proprietary products internally in any given org.
December Major Update of ImmuniWeb Discovery
> A microservice runs as some (somewhat) privileged user, you may want some auth.

Auth can be a very broad term in the case of services, especially in the cloud. IAM could only allow access from certain other machines, etc...
Buy an induction stove. Everyone I know who complained about this stopped afterwards.
First part is correct, the second part is not. GPT Neo is a 2.7B param model, the largest GPT is 175B (they have various flavours, up to 175B). I appreciate the sentiment and what ElutherAI is doing with GPT Neo, but there is no open source equivlenet of the full GPT-3 available for the public to use. Hopefuly it's just a matter of time.
Chess.com does benefit from their collection of training bots with different strategies and more forgiving play style which are pretty neat to play against. Though most of them are behind a paywall so eh.

Lichess only offers stockfish levels when it comes to bots, and even the lowest level seems more brutal than bots with x2 its ELO on chess.com.
Yeah rich people travel all over the place, sure, but equating the inability to visit Florida or Hawaii with jail time?!
Yeah, maybe next time don't "cancel" wikileaks just because they leaked something from your political side(referencing the DNC & Democratic leaks here).

The vault7 was mind-blowing and somehow reinforced what was de facto knew but until then no solid proof was there[merely that quite everything is compromised directly, and when that's not the case, your output is mined],available to the large public.Again, if the Media was more keen on that issue (Privacy, 3-letter agencies being abusive,etc) then people would remember the issues that exist in most computing systems today.

For people who at least skimmed through those vulnerabilities,tools, and leaked documents, it's not surprising at all that these kind of exploits are still out there.It's actually disappointing and frankly pathetic that people don't pay attention to some things because they disagree with the source of information(By the way WL revealed things from the entire spectrum: right/left, Russia/western countries/Asia/etc).These 'NSO leaks' are not eye-opening exploits/techniques, but don't let me spark the bubble of "modern infosec journalism".
Giving bug-like bots a boost
There are solutions to problems hidden in these chats that will never be found. Personally, I've been using Discord as a powerful search engine. Luckily, the search functionality works well enough to where I can often find what I'm looking for. But this might only be a short term solution to an issue that needs an archive.
1-click to run VS Code on Google Colab
But the problem with this is it's a technical solution to a social problem.

If your developers are writing crap code in a monolith they're going to continue writing crap code in microservices but now you have new problems of deployment, observability, performance, debugging, etc etc.

As an aside I have a sneaking probably ahistorical suspicion microservices hype happened because people realised Ruby (or similar trendy dynamic languages) often ended up being a write only framework and rather than try and recover some codebase sanity people would rather abandon the code entirely and chase the new codebase high.
I suspect Ukraine was told quite clearly what they can expect, and as you say, it comes short of NATO boots on the ground, or wings in the sky.

I'd say no one ever really wants to defend an ally, it's more of a pros-and-cons balance. For smaller countries, solidarity within NATO is building goodwill capital for when they need help (e.g. with allies following US into Afghanistan). For large countries, this is part of their empire-building: showing allies you support them makes them more favourably disposed to you. All-around, even for the US, it raises the bar for anyone contemplating an attack on a NATO member.

Ukraine is a colleague but not an ally, so these don't really apply as much.

That said, the West wants an independent, pro-western Ukraine (just not enough to fight a direct war with Russia over), and seems unusually resolute, so I wouldn't be surprised if some truly punitive actions were to be taken. Exclusion from SWIFT was one proposal, interfering with Russian energy exports would be catastrophic for Russia. The latter is very difficult for Europe in winter, but who knows; the US could open the tap with their gas, also if the whole thing gets delayed by a few months, it could be a very different perspective.
> Not getting vaccine threaten everyone around you

I am kind of tired of hearing that when ACTUAL DATA shows that vaccinated people transmit the virus just as well.
This is freakin EPIC. A hat that captures audio and then decides whether or not to relay it to the physical Alexa / Google / etc speaker. I struggle to believe it'd be super reliable, but the concept is ultra cool!
And making food harder to get reduces obesity.
I think this information and clarity exists and is private in the countries' domains of external affairs. Publicly there is always a facade that needs to be held. I am sure some smart people can prove that it's very hard or impossible for any reasonably sized society to function with complete transparency.
They stop being mere 'domestic voices of dissent' once they start threatening my family.
Yeah that doesn’t sound fun at all