skysight-inc/HackerNews huggingface dataset:
Its really not that complicated. Sure its some software you have to make, but lets not pretend this is some incredibly complex thing.

And they don't have to pick all subscribes now, they just need to continually grow subscribers over the next couple of years and add 1 country after the other. Exactly as they have been doing so far.

They don't have enough terminals anyway.
As a startup founder that's not VC funded, I would totally recommend you look into building with kubernetes from the get go. The biggest learning curve is for the person setting up the initial deployments, services, ingress etc Most other team members may just need to maybe change the image name and kubectl apply to roll things out. Knowing that rollouts won't bring down prod and that they can be tested in different environments consistently is really valuable.

I started out with Iaas namely Google App Engine and we suffered a ton with huge bills especially from our managed db instance. Once the costs were too high we moved to VMs. Doing deployments was fine but complicated enough that only seasoned team members could do it safely. We needed to build a lot of checks, monitoring etc to do this safely. A bunch of random scripts existed to set things up and migrating base operating system etc required a ton of time. Moving to kubernetes was a breath of fresh air and I wish we'd done it earlier. We now have an easy repeatable process . Infra is easier to understand. Rollouts are safer and honestly, the system is safer too. We know exactly what ports can allow ingress, what service boundaries exist. What cronjobs are configured, their state etc with simple kubectl commands.

Using kubernetes forces you to write configurable code and is very similar to testing: it sounds like it'll slow you down and shouldn't be invested in until the codebase is at a certain size but we've all learned from experience how is actually speeds everything up, makes larger changes faster, cheaper customer support and saves you from explaining why a certain feature has been broken for 10 without anyone's knowledge
Gnome’s focus has been creating a desktop environment that is consistent and easy to develop for. Which requires minimal testing and is not exceedingly buggy.

Which is why Gnome is extremely popular across the spectrum. With users, distros and developers.

Gnome makes Linux an OS that can compete with the likes of Macos and Windows and actually best them.
Why would I use this instead of make? I read a bit of the guide to “beast files” here and haven’t seen anything different from make other than some slight syntax differences. https://gauravdawra.github.io/Beast-docs/mainDocs/writingABe...

You should make your value proposition clear in your project README, especially if your syntax and overall model appear to be quite similar to an existing tool. Saying you focus on “ease of usability and speed” doesn’t tell me much.
website with Microsoft word is like websites with notion...
I don't understand why anyone would fly Ryanair ;)
Doesn't sound like an "exchange". How did they generate the cash interest?
Not the parent, but this is exactly what happens. ArgoCD is pointed to an "application" chart which just points to a path of a helm chart (of your app/sevice) in Git. So when your CI changes the image hash in the values file in your helm chart, ArgoCD with notice that, and change the deployment resource's image hash. It is just a nice system to have resources in sync between your git repo and what you have live in the cluster. Of course, if you change anything else, ArgoCD will change it too.

You're also right, rolling back just includes changing the hash back to whatever you had, or to a new hash which was a result of a git revert or whatever. Also the good thing is that if that newly deployed service is very broken (that it doesn't pass the k8s health check), ArgoCD will hold on to the old ReplicaSet and will not let your service die because of it.

What's also nice about ArgoCD is that you can play a bit with some service/application in a branch. Say you have some live service, and you want to adjust some configuration of it. Usually third party services have a lot of options to set. The problem is that you're not 100% sure how to get what you want, so doing a pull request for every small change can be very slow and exhausting. To work around that, you can point your ArgoCD's application chart to a chart which is in a branch, test/dev/fiddle with just pushing to that remote branch, and when you're satisfied, you merge your branch, and at the same time point your ArgoCD application manifest to point to the master/HEAD for that chart. In effect, at this step, only your Git repo will be updated, your service already has all the changes so ArgoCD will do nothing. That way you can iterate faster, and undo whatever regression you've introduced just by pointing ArgoCD to watch the master, not your branch (or you can just reset your branch to be indentical to master).
Gnome was always faster than Unity. Which is not surprising considering Unity was a bunch of hacks on top of Gnome.
Just a small correction here. Millions of people use the Fediverse.

Whilst Mastodon brands itself as it's own platform, it's really just one of the many freely available solutions that are used to socialise on the fediverse.

It's a shame that they seem to make an effort to hide this fact when other solutions such as Pleroma and Misskey make it very clear what the Fediverse actually is and that you can use a vast array of software to connect to it.
"Torx: not lots of experience, and there's the rub. At the moment they're a hard bit for a layperson to find, regardless of their advantage ..."

In the US Torx is everywhere.

In fact, when I consider doing any kind of construction project or building outside of the US (in Europe, for instance) one of the major downsides would have to be my near total reliance on GRK screws and Simpson fasteners.

I would not want to have to build things without easy access to products from those two firms.
I have one screwdriver that works miracles like that on Philips head screws--the one on my ~40 year old Victorinox Swiss army knife. I've always wondered what the heck they did different from every other screwdriver I've ever owned to make theirs work so much better.

Now I'm wondering if they are actually following some other standard like that Japanese one.

Speaking of screwdrivers, anyone else here also have way more screwdrivers than you can explain? I can only remember ever buying a small number of screwdrivers, but I have several times that number. Most of them don't match any of the others in handle shape and color and material, so it isn't like I bought a couple or so sets that I've forgotten buying. I seem to have somehow individually acquired a bunch of screwdrivers.

I'm not now nor have ever been a very DIY person and all my screwing needs are easily met by just a handful of screwdrivers.
You'll note that it's unclear whether the author actually confirmed that with the police, or whether they're just uncritically repeating the claim in the press release from the lawyers.
> The power of the typescript toolchain is that a macro framework like ts-macros can be a package and doesnt have to be part of the core language.

Lisp can do the same, but macros are so central, that everyone uses it including the core of the language itself and anything written on top. It's not optional, since syntactic meta-programming is one of the core features of Lisp.
Tolower() in Bulk at Speed
> - There is almost no need to use any VPN service on these sites.

You most definitely need a vpn at least if you are here in Germany.
My main gripe with 1Password is that it used to be a great product. It worked well, was relatively fast and stayed out of the way.

All those things have gone in later versions though.

Now it's very laggy and keeps getting in the way of my browsing, and I have lost passwords for new websites just because the modal to create the entry would "freeze" although not completely - I could still press the cancel button which would then ... cancel the creation, but also delete the temporary password item.

This modal stops you from using anything else on the browser as well, so there's no way out of it.
> At the most advanced levels of pure web dev

And what's that level exactly? Creating one's own markup language or browser engine from scratch?
Doesn't every mainstream language these days allow you to pick what style you want according to the situation?
Linus Torvalds says Rust is coming to the Linux kernel 'real soon now'
Control! We must have control!
Helix is currently made available to select AEM Sites customers in the Helix VIP program. If you are interested in learning more about Helix, getting a personalized demo, and want to understand how Helix can make your site better, reach out to your Adobe account manager and mention the keyword #helix-chat.

If you are impatient, a developer, or both, take a look at the Helix Developer Tutorial in the meantime.
Tim Hockin (one of kubernetes creator) supports the idea to use something as much managed and automatic as possible if you don't have time for it [1]. He probably refers to use Cloud Run [2], over a (managed?) Kubernetes cluster (such as EKS or GKE)

[1] https://twitter.com/thockin/status/1539987108521054208

[2] https://twitter.com/the_thagomizer/status/153975704907180032...
You’re right that nginx is also complicated , but seems like we are talking about different alternatives.

The solution I went with, given my limited knowledge of some of these things, was to use elastic beanstalk. You write your flask application, upload the zip and that’s it pretty much. You get a UI to do all the configurations and for the most part nothing there is hard to decipher or google. The only hiccup might be when you’re trying to connect it to RDS and to the external internet but even that is straightforward as long as you follow the right instructions. We run apps that power entire SaaS organizations and this system seems to be more than sufficient. Why complicate further? We have other fish to fry anyway.
At least the Torx driver sizes are the same for metric and imperial (unlike hex heads where you need a separate set if you need to do anything with imperial screws/bolts). I find three good drivers are enough for 95% of what you need for electronics, and then a cheap interchangeable head set gets you the rest of what you normally need.
The comments are kind of hilarious: You can't speak of Wayland's issues as reasons to not do this and then the discussion becomes "well we are just a client anyway". If you just want to do something, why pretend to have a discussion? It's just frustrating for the reader - just drop it so everyone can either show you that they agree or move on from what you are maintaining.
Some people put years of their life into fixing plumbing, should they and their heirs also profit from that plumbing?

I'm all for finding ways to reward people for creating things but that should not include restricting what others can create.
Context does matter, but the context is that the podcaster in question wasn't someone cleverly deconstructing white nationalism, but an edgelord who routinely says offensive things for attention (choice cuts: the video in which he tackles statements as apparently in need of contesting as "it's not OK to call me a fag" with such ingenious ripostes as "I don't even know that you're gay, but you're still a fucking fag" and his much-publicised comments about an MP being too ugly to rape) losing his temper at the white nationalist he'd invited on for a cosy chat because they were more interested in mocking his posh accent than finding common ground with him. A podcast persona he defends with the statement "Personally, I find racist jokes funny" . If a corporation decides it doesn't want to be associated with his content any more, it's not because they've completely misunderstood where he's coming from.
Users with IPv6 will usually find a small speed increase, a few milliseconds faster for new connections. The difference is greater if the user's ISP has an overloaded CGNAT router.
It would be cool if this also told you why you might want to do the thing it’s describing.
It took a year, but that was somewhat on the side of also building an OpenAPI based Web service, the gRPC based workers. So, it wasn't just the infrastructure stuff. If I were to estimate how much time for just the infrastructure and devops tooling, then two months. It's been up and running with less than 15 minute downtime over the course of two years.

I do consider this impressive. And, to be clear, I wouldn't say this is because of a "super-developer". In fact, he had no prior k8s experience. But rather that there are thousand upon thousand of infrastructure hours devoted to the helm charts, often maintained by the people who develop the services themselves. It is almost mind boggling how much you get for almost free. Usually with very good and sensible default configurations.

In my precious work place, we had a team of 5 good engineers purely devoted to infrastructure, and I honestly believe that all five would be able to spend their time doing much more valuable things, if k8s had existed.

As for whether or not such devops solutions could be done in a day. Hm. I don't know. These things should be tailored to the problem. If you've done all of this a few times, then maybe you can adjust a bunch of charts that you are already familiar with and do what took a couple of months and impressed me, in a couple of weeks. It's a lot more than just "helm install. Done", that goes into architecting a scalable solution. Implementing monitoring, alerting and logging. Load testing stuff. Etc.
They are used pervasively in Haskell, less so in other functional languages.

In Haskell, you can't write a "Hello world" program without using monads, so you cant really avoid learning about them.

IMHO monads are only really useful in Haskell because it has specific built-in syntax sugar to support them. Without this syntax sugar, they would be very cumbersome to use. So it's not really the monad type per se which is interesting, it is the code style which the syntax sugar enables.
Now can someone do the same for web dev? I just started getting into it for a hobby project and the terminology is so incredibly idiosyncratic.
General: https://www.youtube.com/channel/UCBa659QWEk1AI4Tg--mrJ2A

General: https://www.youtube.com/channel/UC2C_jShtL725hvbm1arSV9w

Logistics: https://www.youtube.com/c/Wendoverproductions

Art: https://www.youtube.com/user/Nerdwriter1

Woodworking: https://www.youtube.com/c/laurakampf

Workshop stuff: https://www.youtube.com/channel/UCPO4D4-UeeFQceK8XrgwXug

Workshop, manufacturing: https://www.youtube.com/channel/UChWv6Pn_zP0rI6lgGt3MyfA

Electronics: https://www.youtube.com/c/DIYPerks

Machining: https://www.youtube.com/c/ThisOldTony

Cars: https://www.youtube.com/c/Petrolicious

Science: https://www.youtube.com/c/veritasium
Kubernetes is the React of devops. You wont get fired for picking it. And there will be a tonne of support available online, as well as courses, and experienced people you can hire. Also there is cloud managed k8s which takes most of the pain out of it. And plenty of out the box stuff.

It is not a bad choice if you want to do the ops yourself for some reason. If you don't then use a BaaS or PaaS, that might be easier and probably not much more expensive, but will lock you in.
I wonder how traceable they are?
It's a lot of work that they don't want to do.
Automata from 250 years ago which writes text, draws pictures
Agree the author is wrong on that specific point, though thankfully the bulk of the article content deals with the headline, and is mostly fine wrt k8s.

Rather than the author "not knowing" what they're talking about, I suspect they're taking narrow experience and generalising it to the entire industry. Their background is selling k8s as a solution to small/medium enterprises: it strikes me that there may be a strong correlation between startups interested in that offering and those deploying failed overengineered multilang micro-architectures. Suspect the author has seen their fair share of bad multilang stacks and not a lot of counter examples.
> I think the set of cases where "we need to scale up rapidly if it succeeds" and "Kubernetes solves all of our scaling needs and we aren't going to have problems with other components" is almost empty.

I agree, but so what? K8s isn't magic, it won't make all your problems go away, but if you have people who are genuinely skilled with it, it solves a lot of problems and generally makes scaling (especially if you need to move between clouds or move onto bare metal) much smoother. Of course you'll still have other problems to solve.

Given that most startups never need to scale up much, it's not surprising that k8s is mostly used where it's not needed. But people usually prefer not to plan for failure, so it's also not surprising that people keep using it.
I suggest you just do it. You can generate the indexes on some cloud VMs and save them. It would cost under 100$.
For a time, Robertson drive was often used for decks and mobile homes in the USA.
Yes. I had easily as many issues with Windows and OSX when each was my d at driver. I don’t really have anything bad to say about Fedora + Gnome except that occasionally, my 5k thunderbolt monitor is finicky when waking from sleep. It’s a simple enough fix, but it’s still a minor inconvenience maybe once a month.

Linux package management alone puts it ahead of both Windows and OSX in my book.
I know your comment is light-hearted, and you're probably aware of the below, but nevertheless....

Presumably you use the good forks more often than the weird old forks? So each good fork's exposure to 'times when it might be lost' - being used for dinner, cooking, etc. is greater (perhaps once every two to three days) than a weird fork which you may only use once a month or less (when other forks are exhausted, or you need a tiny shrimp fork!)
The startup I am working for has seen entire engineering fired after they hired a lot of people and spun an enormous amount of infrastructure, spent tons of cash and produced absolutely nothing useful to the company (presumably because they were engrossed in spinning the infrastructure). The company isn't very large and does not provide software products to the clients. The systems are mostly business intelligence, billing, ERP-like, etc.

Now we are restarting lean (but wiser for the experience). 10x less people and technology accomplishes more and faster.

Most companies with that kind of problem DO NOT need Kubernetes because they don't have problems for which Kubernetes is the cheapest solution.

Most companies do need focus on keeping things simple, minimise amount of stuff to make it possible to hire a development team that has a shot at understanding what is happening.

For example, we made decision to restrict ourselves to only one cloud provider (AWS), to only one backend language, one frontend language, etc.

Our prod environment is simple, too. No effing microservices. One application on one application server easily serves the needs of a company of over 200 employees and our clients.

Simplifying the environment made wonders to productivity in many different ways, the most important being that the discussion now focuses on what the company needs and the functionality that would solve the problem rather than on technical trivia.

All this makes possible following things:

* having one development team where everybody can contribute to everything (no need to Zoom with local K8s guru to accomplish anything or spend time in endless meetings with "frontend people".)

* hiring a relatively simple developer profile. This does not mean hiring bad developers. But it means I am looking for people who know X and Y very well rather than X, Y, Z, A, B, C each a little bit... It is stupid to assume a person will know well every one of 50 different technologies listed on their LinkedIn profile -- most likely they only really know couple of things and everything else only superficially.

* hiring from talent pool that has a lot of experience but not necessarily in the stuff that other companies require. Other companies may hive overlooked them because they don't know a bunch of new tech, but we don't care. We only care that they are great people that get shit done, fit our company, and know how to design and implement functionality in their core programming language.

* engineers being able to accomplish their individual tasks from start to end, right after joining the company. No need for a long learning period.

* company needs main center of attention rather than spending large part of the effort on technical trivia.

My take? If you need to add something, first ask yourself what are the costs and better understand what you get in return for that cost.
Is it still lagging on slower machines? I'll keep using XFCE for the time being, like many other in this thread.
There’s a Clever Strategy Behind the Flash of Fireworks Packaging
> Kubernetes is actually pretty great for the vast majority of use-cases.

From my brief glances at it, it seems like a great solution for very complex use-cases. But "vast majority"? The cost-benefit seems way off unless you have a very different sense of "typical use-cases" to me.

Most people are building simple web sites and apps that run on a single server, surely?
The reason for the "expert" is rather complicated.

Essentially my mum lives on an island nation where there is only a singular local hospital with a fairly poor reputation.

In order to get it looked at, we had to find a hospital in the UK, as that's where the private insurance covered treatment. The local hospital refused to even write a referral for further diagnosis as they considered it unnecessary as it "definitely isn't a hernia", so we had to find a surgeon that takes self-referrals. That rules out the normal NHS routes, even if attending privately.

So ultimately we found a team that specialise in treating hernias, who agreed to have my mum in after they saw a photo of her abdomen.

I think one thing to understand here is that a local hospital with a poor reputation isn't going to have the same standards as a large academic health centre. The reputation is such that good clinicians will avoid the local hospital, as they don't want to be seen to be associated with it.

Unfortunately, when you live there, you don't really have the same luxury.
I'm aware of these products, but do not fit my use case.

I need to run some services on premises and have set up a self hosted Kubernetes instance on a physical server in a rack.

It could be overkill and maybe I could use something like Docker Swarm. Apart from this I am unsure what I can use that isn't K8s to orchestrate my containers on site.
They still sell Phillips screws in the UK. Drywall screws for example are Phillips (IME).