skysight-inc/HackerNews huggingface dataset:
> I started out with Iaas namely Google App Engine and we suffered a ton with huge bills especially from our managed db instance
Are you factoring in the salaries of the people setting up Kubernetes? And the cost of those people/salaries not working on the actual product? And the cost of those people leaving the company and leaving a ton of custom infrastructure code behind that the team can't quickly get up to speed with?

> ton with huge bills especially from our managed db instance

This doesn't have much to do with App Engine, right? Last time I used it, we were using a PostgresQL instance on AWS and had no problems with that.

> Doing deployments was fine but complicated enough that only seasoned team members could do it safely

I just plain don't believe this. I bet you were doing something wrong. How is it possible that the team find too difficult to do an App Engine deployment but then they're able to setup a full kubernetes cluster with all the stuff surrounding it? It's like saying I'm using React because JavaScript is too difficult.

> 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

This is far, far, far from my own experience.

Some other questions:

How did you implement canary deployment?

How much time are you investing in upgrading Kubernetes, and the underlying nodes operating systems?

How did kubernetes solve the large database bills issue? How are you doing backups and restoration of the database now?

If I were to found a company, specially not VC founded, dealing with kubernetes would be definitely far below on my list of priorities. But that's just me.
I've made a k8s 101 webinar a while ago that I think explains the basic concepts pretty well https://www.youtube.com/watch?v=qQw91VeJMGY
#helix-chat is that the keyword for the chatbot?

I dont get it VIP??? Really?? AEM Sites? Whats that?

Are you from marketing?
Collaboration Platform and Git Hosting
> I have never seen a square (Robertson?) screw in the wild, I assume that's regional.

Almost exclusively Canadian I believe.

You can get them though, I bought a Kreg pocket hole jig in the UK which came with some for some reason, and had no problem getting bits for them (Amazon I think).

I'd never seen them (IRL) before that either.
Probably you refer to the "forced" passage to Unity-Qt, who was not mature at that time, witch means buggy and laggy.

BUT such move was not bad, was needed because too much people do not want to evolve, keeping on menus-based systems who start to age, without this move GNU/Linux would probably lost many new users who want modern desktops...

Unfortunately modern desktops are still crappy floating WM with a completely lost design underneath but that's another story...
> 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.

This is a huge redflag.

It's basically admitting that you expect most later employees to not understand k8s or how its being used. You may think they don't need because it works, but you have to think about what happens when it doesn't work.

The shops I've been to all had the same mindset: the docker/k8s infra was setup by one guy (or two) and no one else on the team understands what's going on, let alone have the ability to debug the configuration or fix problems with it.

Another thing that might happen is some team members understand just barely enough to be able to "add" things to the config files. Over time the config files accumulate so much cruft, no one knows what configuration is used for what anymore.
The New American Micro-SaaS Dream
I upvoted this but honestly feel like that isn't a strong enough recommendation for Poweramp. It blows every other player out of the water, there's no competition.

I also just checked their website and as of v3 it doesn't even require google services to buy, so even if you have a degoogled phone you can still use it.
So I've read through this, but the docs seem to assume you already know what it does. (Which I'm still not sure that I do)

It seems to be a way of generating a website from a shared google drive or MS sharepoint setup.

The google drive documents act as content which is mixed with templates to generate a website.

But it doesn't seem to be static site generator, more like wordpress with google drive (or sharepoint) as the content database?

But then it also talks about the helix team doing work for you? So it's maybe more of a service to create websites than a technology stack?

It seems like there are some interesting ideas, but it also feels like there should be more explanation.
There's quite a bit of crowdfunded open content. It just tends to not work as well for the most costly to produce kinds of content.
The key point is that if you know how to grow your publication without Medium’s help then Ghost is a great option.

I’ve been using Ghost for my newsletter for actuaries using Python and Medium’s distribution would add no value for me at all. Plus the flexibility of Ghost’s integrations - eg with Discourse - is very useful.

[1] https://www.joveactuarial.com
Well said. The reality is that even in our current work without copyrigh a lot of value is added by creators who never see any real reward for it. Yet instead looking at how we can better reward creators we continue with continue with this insane system that has been shown be easily abused to concentrate wealth while having a massive cost for society by restricting what we all do and making everyone pay for enforcing those restrictions.
You get fined by your ISP (cough Virgin cough)
Insecure non-frontend devs continue to see frontend as an easy programming environment, and therefore assume the problems in it should instantly make sense to them and be easily solvable. Because after all it’s easy, and they’re smart, and if they were a frontend dev, they wouldn’t even need this tooling because it’s so much easier to start from first principles of an index.html page.

It’s funny because I’m a frontend dev and I can do the job of a backend dev better than most backend devs. Yet I don’t go into every thread about Python and complain about what a horrible experience it is to install and manage.
I think Slack has a place in communication but it has a really poor balance. It's so easy to create and send a message to a channel and tag a few people. As a result it moves quickly and makes it hard to digest and reply slowly. It's also extremely hard to find things again later, even with the improvements to search.

Back in the days of IRC a lot of people thought lack of history was a "missing feature" but now we have it with Slack I think it was probably the best feature of IRC. When the platform has no memory you're often pushed away from it for anything that's deeper. No one can come along later and find your messages so you know you can't put anything that requires wide visibility or input there.

I'm not going to shill for IRC and say everyone should go back to it or anything, it's not really practical. But that said, I do think Slack has a huge flaw in it's design of making it so easy to send messages and pretend everyone's going to see it.
> Right now, we'd be getting remakes from every piece of pop-culture that was semi-popular in the 80s-2002 time frame

That's exactly what we are getting right now though. Looking at the top ten of the box office right now, only three are not part of an existing franchise. Three of them are reboots of 80s movies, four if you count comic books. Large IP holders recognize under the current system, it is much more profitable to exploit their existing IP than to come up with new concepts. If the copyright terms were significantly shorter, the pressure to be original would be far higher.
I get why they chose to do this in Javascript, but I can't help but feel it's an awkward choice. Many of the examples (e.g. currying) look unnatural in javascript.

https://github.com/hemanth/functional-programming-jargon
I really don't understand all these complaints about how Kubernetes is so complex, how it's an investment etc. I am a single developer that uses Kubernetes for two separate projects, and in both cases it has been a breeze. Each service gets a YAML file (with the Deployment and Service together), then add an Ingress and a ConfigMap. That's all. It's good practice so still have a managed DB, so the choice of Kubernetes vs something running on EC2 doesn't change anything here.

Setting up a managed kubernetes cluster for a single containerized application is currently no more complicated than setting up AWS Lambda.

What you get out of it for free is amazing though. The main one for me is simplicity - each deployment is a single command, which can be (but doesn't have to be) triggered by CI. I can compare this to the previous situation of running "docker-compose up" on multiple hosts. Then, if what you're just deploying is broken, Kubernetes will tell you and will not route traffic to the new pods. Nothing else comes close to this. Zero-downtime deployments is a nice bonus. Simple scaling, just add or remove a node, and you're set.

Oh, and finally, you can take your setup to a different provider, and only need some tweaks on the Ingress.
Technically, you don't need an exchange. Practically, you do at some point in the chain.

Say this Sargon guy or some other personality with a rep takes payments/donations in BTC. Okay, and what then? You can't pay your rent with that, unless you're renting from some crypto fan, and they also can't pay for their taxes/groceries/gas/etc with crypto. At some point, if crypto is used as money there has to be an exchange.

And since crypto is very traceable it's very possible you won't be able to exchange coins with some sort of murky history to them. If you'd have a problem, then your landlord likely also has a problem. And you probably don't want to be on the wrong side of your landlord.
If your apps are simple enough to use PaaS then all power to you. :)
Sounds like a waste of months that could have gone into building product by choosing simpler operational tech
Interesting.

A few days ago I read how DevOps failed because people didn't understand it meant devs should do their own ops, instead they rebranded their ops roles to DevOps and called it a day. Here we are, talking about just that happening.

Anyway, lately I was working with SaaS and serverless systems and had the impression that there wasn't much difference anymore between infra and code. Configuring and deploying an auth service, or a isn't much different from writing code for FaaS and deploying it.
UK signs deal to share police biometric database with US border guards
Not one of the companies i know have an ipv6 only service.
> finding errors or inappropriate algorithms or datastructures

when I interview developers, folks coding in Java can usually tell me what an appropriate datastructure would be, while half the JS developers can't explain how an array is different from a linked list. Because most of the time JS developers. dont have to think about it much.
Yeah this is exactly what I was thinking of, that software was truly awful. I owned 3 MiniDisc players. I thought they were so neat!
Not many distros ship KDE as a main and first class DE. On the ones which allows KDE during install (meaning it was at least somehow tested, probably), in my anecdotal experience KDE 5 often run horribly with severe visual bugs. AND then community says this "why did you pick distroname+KDE, it is cutting edge, go pick Mate/Gnome/Cinnamon/XFCE". And both of these things together are rather frustrating.
> Right now, we'd be getting remakes from every piece of pop-culture that was semi-popular in the 80s-2002 time frame. Not just movies, but TV series, books, theatre, musicals, ...

We are getting these things anyway, except that the originals are far less accessible than they should be. Entertainment trends are cyclical.
Location: New Delhi, India

Remote: Yes

Willing to relocate: Yes(anywhere in india)

Technologies: Java, Kotlin, Spring, Spring Boot, multithreading, distributed system, Mysql, MongoDB, Postgresql, Linux, Docker, Bash Scripting, MacOS, Git

Résumé/CV: https://docs.google.com/document/d/1162mKIlIieLBTWPFUWZBtlCn...

Email: yours0182@gmail.com
(I agree with your overall points, but when the GP said "Doing deployments was fine but complicated enough that only seasoned team members could do it safely" they were referring to their post-App Engine, pre-Kubernetes "manually managed VMs". I have no problem believing that deploys are very complicated in that scenario)
Tom Scott did a video on this, "The Nuclear Reactor Run By Students":

* https://www.youtube.com/watch?v=pLBcp3nJlFQ
> Side note: mistakenly using a smaller torx driver demolishes both the screw head and the driver... and it usually fits well.

Ahh yes, I learned this the hard way. T20 bit for a T25 screw, for example. It might work for a few screws then all of a sudden the next one gets destroyed.
It's not clear to me exactly why the wound got infected, as currently all the parties involved are blaming each other.

The surgeon who performed the mesh repair did clearly state it was a possibility, but the hernia wasn't suitable for non-mesh repair, which would have been his preference.

There was no indication of infection or contamination at the time of the hernia repair, and the surgeon who performed the mesh believes the infection was most likely caused by poor aftercare, which was handled by the local hospital due to covid travel difficulties. Of course, he could just be saying that to cover his ass.
aw, "phage therapy" isn't on the list...
It’s really complicated when something goes wrong. That is my only criticism. Particularly in the various CNI layers out there. You really have to know exactly how everything works to get through those days and that is beyond the average person who can create a docker container and push it into the cluster which is the usual success metric.
I LOVE Fraidycat but it hasn't seen any updates in quiet a while. It badly needs some more love.
Amazon: E-cargo bikes to replace thousands of van deliveries in London
That side note problem surely ranks as the #1 downside of torx. The practical solution seems to lie in restricting torx sizes to a much smaller subset, e.g. jump right up to T25 if T10 isn't enough (I think some fields actually do this?). But if you have the full set of drivers you can still mess up, no doubt.

I wonder if the pin/hole tolerances of the "tamper proof" variants are tight enough to keep the slightly smaller out? Then it's not so much about keeping out people who don't own the right tools (gatekeeping) but about keeping out hands that happen to not hold the right tool at the moment, which is very well possible even if one should know better, and the right tool is available as well. You should never blame the user for a mistake that could have been prevented by better UI.
Those companies use ML algorithms that inflate the ranking of harmful content, which can lead to this. They hold some responsibility for profiting off of this.
There was no criticism of the tool itself, but how landing page is not instantly clear to developers who are not even frontend-related devs.

What's positive about that? A complaint with proposed action is what can be considered positive, but most complaints here were "I am not frontend dev, I clicked the link, I don't understand anything. They need to telepathically understand what I want and make the page that's to my liking".

It's just pseudointellectuals trying to pose as experts in a field they're not even working in. And here we are, a bunch of bottom feeders arguing over a landing page in year 2022. Oh, how entitled have we become. This situation is absolutely disgusting and not positive.
You missed that its not below market price, its below market price for the quality. But most companies don’t buy based on quality of credits but based on how cheap they are so they can get away with polluting. This is counterproductive and pricing those credits higher will lead to them not being as useful as they can be.

And honestly: I find it very arrogant to think that you can show up and propose this “crazy idea” that “hey what if you guys made more money you could do more good”, as if that hasn’t been considered…
Nothing on the page linked even describes what ‘Helix’ is, much less why I would want it.

That whole site seems like excessive marketing fluff written by someone who’s been living and breathing whatever this project is for years.

Assume I have no idea what it does or why I’d want it. Use small words and no acronyms. Also, less words. Then, as simply as possible, tell me what it is and what it does for me from a technical standpoint. I’ll decide for myself if it’s useful.
Friend of mine tells me a headhunter perked up when he mentioned he used this for his last project, and told him crazy salaries if he wanted a job as the Helix specialist at several corporations. Says he's investigating.
> The Whole advice of using same language is especially silly - iOS is stuck with Swift, and the web is stuck with JS, and maybe you need an applitation that scales using actors across mutiple machines with Golang or Java, or maybe you need to plug into Windows tightly and need C#

And you're also forgetting Android and macOS and Linux.

That's why cross-platform frameworks like Electron and React Native are so popular. The time wasted in going native for every single platform is just infeasible for most non-huge companies.
I think 30 years is a decent base in my mind. Let it be renewed a couple times for an extra years if the owners think it’s worth it. That way most stuff flows into the public domain but some works can keep creating value for their creator.
Kubernetes is the standard for infrastructure, everyone should use it instead of VM or all others singular infrastructure. All others options are costly on the mid and long term.
SEEKING WORK | REMOTE

Technologies: Java, Kotlin, Spring, Microservices, Spring Boot, multithreading, distributed system, Mysql, MongoDB, Postgresql, Linux, Docker, Bash Scripting, MacOS, Git

Résumé/CV: https://docs.google.com/document/d/1162mKIlIieLBTWPFUWZBtlCn...

Email: yours0182@gmail.com

Notes : Work < 25 hours will be free of cost.
[Article author here]

He does amazing work. I did a little profile piece on him a few months ago:
https://www.theregister.com/2022/02/04/rudra_sarsawat_ubuntu...
Seems that with calibre-web[1] we can have nice web front-end. But it doesn't have full-text search inside the content of the books though, unlike google books.

[1] https://github.com/janeczku/calibre-web
Adobe used to be such a behemoth. They didn't switch to subscriptions due to unprofitability. They just wanted more and more. Same with Microsoft. They're a behemoth switching to subscriptions now. But that's not because they're running low on money. And most games are still one-time payment today. So you can count Ubisoft, EA etc. Of course there are other sources of payment for them than just the nominal price of the game, but most gamers only pay for the game and ignore everything else.

Besides, I don't think I want a market dominated by behemoths. If popularity of one-time payment model would lead to a market dominated by <25 person companies with an odd behemoth here and there, then I'm in.

Also, most software companies today are startups which exist only thanks to investor money. It's hard to say what a customer-driven market would look like. Although maybe recession is going to clear this up.
I'm not an expert on the protocols I can't imagine there's any reason you couldn't serve near-live content using HLS or MPEG-DASH over BitTorrent.
There are cloud providers, I have personal experience using sendgrid.

For small scale / personal stuff you can use gmail's SMTP.

https://support.google.com/a/answer/176600?product_name=UnuF...
Is there a set of magent links? Seems a bit OTT having to log in to tor to get the torrents when they could be DHT.
Which can also create another problem.

The second company might think there is a market for 100k users, and price accordingly at $10, but only sell 10k copies and go out of business.

Now, however, people see the product as only being worth the lower price point of $10, and won't pay $100 for it anymore. So company A can only sell 1000 copies at $100, and also goes out of business.
I doubt very much that that anecdote is true.

I was involved in the development of Unity at Canonical, just as I was involved in the development of the Eee PC at Xandros before that. Unity developers were very well aware that there was a small but extremely vocal minority of users who expressed their strong dislike and contempt for their work. We were also aware of the much larger and quieter plurality of people who liked and appreciated it, and maybe the majority of people who just turned on their computer and got to work without a second thought about the desktop environment. A part of my job was managing the negative feedback from users... I think would have been aware of any decision to change back to Gnome based on the strident and biased opinion of some rando on the internet.

For the record, Unity was discontinued as a business decision to make Canonical more profitable for its investors. Plain and simple. Normal everyday business.
I have a set of these. They do work well, as the original post says, but I tend to use them more for holding flats or removing 8-sided plastic nuts and such.

One downside is they gunk up pretty quick if you're working with messy stuff. My 40 year old car has so much grit and grime underneath it (that I'm afraid to spray for fear of knocking something loose) that nearly every job is a dirty one. The teeth for the adjustable part are very fine unlike a typical channel lock, so they get packed with grime and hard to set sometimes until I clean them. I had the same problem with another push-button fine adjustable channel lock with a similar mechanism. The old C shaped channel with 5 positions never has this problem.
That's seems like a very negative take in my opinion. This 'simpler operational tech' would still need to be able to scale, correct? If you think that there is a good and easier way to deploying 10-15 services, all of which can scale, and all of it defined in rather neat code, to be anything but "simple operational tech", then I believe you are confusing "solving a complex problem", with "simplifying the requirements of a complex problem". The latter of which has been stripped of many important features. K8S isn't anything magic, but it certainly isn't a bad tool to use. At least not in my experience, though I've heard of horror stories.

That does remind me that when that employee started, the existing "simple operational tech" was in fact to SSH into a VM and kill the process, git pull the latest changes, and start the service.

The only way you can solve the actual problem (not a simplified one) would in my opinion either be k8s or terraform of some kind. The latter would mostly define the resources in the cloud provider system, most of which would map to k8s resources anyways. So, I honestly just consider k8s to better solve what terraform was made for.

I'm sure the "simpler operational tech" meets few requirements for short disaster recovery. Unless you have infrastructure as code, I don't think that is possible.