DandyDev

I have used 1Password since way before the cloud version became the default. I loved the product... and I still do! I moved to the cloud version and the experience has been really slick.

I actually think the product is well thought-out and designed. There are some website where it refuses to work, but these are in the minority, and I blame the websites for breaking 1Password, not 1Password.

Also "a nightmare" -> this feels like an unnecessary hyperbole

Because you'd like use the Python ecosystem, for example for writing ML code, but you'd also like to write typesafe code (or rather typechecked, using mypy)

This is very cool. Sad that it only works for NPM packages. Would love this for PyPI packages

The "covidiots", as you call them, seem to be everywhere, at least going by what's happening on social media right now.

House prices are also a common and global problem. At least in urban areas around the world.

The lack of mountains is objectively true.

The lack of nature is subjective. If only you dare go outside of the Randstad. I originally lived in Limburg and I now live in Zandvoort. Both have plenty of non-farmland nature.

With regards to the bad weather: it only rains for 10% of the time in The Netherlands, so it's not that bad.

Article author here. To me the big advantage of Protocols as opposed to ABCs, is that you don't have to have your classes implement a special base class and can instead focus on the _consuming_ code. Using a Protocol for a function parameter works even for passing in objects of classes you don't control.

Article author here. You're absolutely right of course! Thanks for pointing this out. I immediately fixed it.

Super informative article, thanks for that!

It comes to the same conclusions that I intuitively had as well:

- EKS if you really have to use k8s - ECS if you have a modicum of complexity but still want to keep it simple - AppRunner if you just want to run a container

My experience with ECS is quite okay. You start a cluster, stick a container on it through a task and optionally a service + load balancer and it just works.

It doesn't seem any harder than EKS, and it's mostly cheaper.

I also find some comments on this article about vendor lock-in dubious, because in the end it's a bunch of containers created from Dockerfiles, which you can easily reuse elsewhere.

Even without using reserved instance pricing, ECS on EC2 is much cheaper, isn't it? At work we use Hasura, which is written in Haskell and cannot be (easily?) run as a Lambda. Our alternative solution is to run it as a container on ECS. Given that it's a permanently running service, with Fargate we'd pay just to have it sit idle for half of the time, and Fargate is not cheap.

Even when running non-reserved EC2 instances to make up our ECS cluster, it is cheaper than using Fargate.

Is this sort of sweeping generalization really necessary? I can tell you that it's not true in any case. I'm one of those Mac users that doesn't complain about performance, because I rarely see the spinning beach ball.

Localstack Pro looks quite nice and comprehensive, but the CI pricing seems to really discourage proper continuous integration best practices. At 10 cents per run you're encouraging developers to run their CI pipelines as little as possible, while ideally you'd run CI on each commit and you'd commit often, probably 10s is times a day. In that case Localstack Pro for CI would get costly very quickly.

Why not have CI pricing per project/repo. Regardless of how often it runs.

I don't think the claim is that Python is a good replacement for C. But there are probably more (business) problems for which Python is the right tool to solve it then problems for which C is the right tool.

C is also a lot harder than Python to learn.

So for these reasons there are more Python programmers than C programmers.

For some subset of problems for which C is a good tool, Rust is a good alternative, arguably with less foot guns. For some other problems that are solved with C, Golang is a good alternative.

So in the end C is losing marketshare because of all these reasons.

I'm pretty sure that will not happen for the whole ML and data ecosystem in Python. And it's also pretty questionable if everything ported to golang is 10x better. 10x more verbose? Sure!

Source.ag | Software Engineer | Amsterdam, The Netherlands | OnSite | https://source.ag/

Source is creating a sustainable and fair food system by accelerating the transition to greenhouse agriculture. We are making greenhouses more scalable by developing the world’s most advanced artificial grower. Our software and AI models help growers to define optimal seasonal crop plans and provide greenhouse autopilot functionality to ensure flawless daily growing operations.

You'll be working on the core backend systems of our artificial grower products where you'll be responsible for all aspects from architecture and building the software to actual deployment and operations. You will also help with frontend-related tasks. Next to that, you will work closely together with data scientists to understand the data needs and translate these into data pipelines to ensure the availability of relevant and up-to-date data. You will also help the data scientists with industrializing their models, integrating them into our products and bringing them to production.

Tech stack:

- Python, Typescript and a bit of Golang

- AWS (combination of Lambda, ECS, S3, RDS, SQS and assorted other services)

OnSite/Remote: we work 50% from home and 50% in the office, which is located in Amsterdam

Apply: https://source.ag/careers/

And what kind of person you think we are talking about here for 60k in Amsterdam? Is that a senior Software Engineer? Or even an engineering lead (responsible for a bunch of other SEs)? Because 60k per year in Amsterdam equates around 4.6k per month + holiday pay. I can hire at most a medior - senior SE for that in AMS (let's say 4-5 years of experience) and I really don't believe a person with that kind of experience would earn 300k a year in SV.

We _are_ running out of public IPv4 addresses. I routinely see articles shared on HN about companies buying or selling blocks of IPv4 addresses for increasingly insane prices. I think the market rate is now $40 for a single IP address?

To me, loud motor cycles seem like a sign of compensating for small genitals. Like many others in this thread, those loud sounds induce a huge amount of physical and mental stress.

Did you consider using existing API Gateway solutions, either OSS or commercial? Why did you decide to build your own?

Given that Uber is an engineering heavy and tech-centric organization, why did you choose to do configuration through the UI? Why not configuration and infrastructure as code?

Great initiative and very generous!

My pet peeve with READMEs: usage of excessive adjectives to oversell your project. Famous culprits: "blazingly fast" or software that is "beautiful" or creates "beautiful" things.

To be fair, I think we're talking about READMEs for technical projects here, probably hosted on Github/Gitlab/... And in that context your example is totally clear to me: it's a framework for running (background) jobs asynchronously (i.e. code that does not need to run on the main thread of your program and block) and you can use it both on the server and the browser (so probably JS/TS) and it's not intended to be feature rich.

How does it compare to Swiftbar[0]? Any reasons to use Xbar over SwiftBar given that the latter was built with a stack that is more "native" to Mac than Golang?

[0] https://github.com/swiftbar/SwiftBar

This is an excellent overview. Thanks for sharing!

Thanks for your insightful reply! The discussions I see on GH seem to be mostly about software architecture (by which I mean: how to solve a certain problem with code). How do you design and discuss systems architecture? (ie. how do you choose components/technologies like databases, API protocols? How do you discuss the interconnectedness of components/systems?)

That's an excellent point. I hadn't thought about it that way.

Thanks for your response, very useful! May I ask you what companies you work/have worked for where you experienced what you described? (I understand if you cannot say)

Regarding "business architecture": your question is in a way already an answer to my question. "Business architecture" doesn't seem to be something that is done at digital-first companies like FAANG, but is something that is prevalent at brick & mortar enterprises that have IT. In my understanding it involves breaking down business processes and assigning them to different business domains so that applications/systems can be built to support those processes. It does not involve any technical choices.

> Traditional monolithic web frameworks such as RubyOnRails

It's interesting that these kind of false premises come up often on HN. Don't get me wrong, I don't like PHP either, but nowadays. PHP is just as "modern" as many other languages in use. And with frameworks like Laravel and Symfony, it stacks up well against the likes of Ruby on Rails, Django or any NodeJS based stack. And let's not forget that the majority of websites and webapps runs on PHP.

It would be friendlier to phrase this as a suggestion:

> Looks promising! Have you thought about supporting a light theme as well? I generally don't like dark themes

Genuine tip then: write your story on Twitter, then copy paste the compiled story from Threader into a proper blog post and replace your tweets with a link to the blog post. Problem solved!

I'm subscribed to Porter and I really like it! Between Porter and Github Explore I feel I have a pretty good picture about new projects arriving on the scene. One request though: I'd love to see direct links to the Github repos in question from the email and the web digest. It takes too many clicks to reach the actual repos and I'm not really interested in the trend graphs that porter offers