2,050 karma · joined November 22, 2011
On the one hand, it's a very comprehensive ORM (support for different DBs and types of queries, joins, associations, etc). On the other hand, the documentation is not very good and often its behavior leaves you baffled (updates of columns and the associates in different times, for example).
Overall, I think I'd still choose an ORM over writing SQL or quasi-SQL in the code for the sake of maintainability and readability of the code. GORM is the best one around but I wish there were more options.
In k8s for example, you can use Docker and won't need a proxy for ZDD (while you might want one for Ingress and other uses)
I don't know why Kamal chose Swarm over k8s or k3s (simplicity perhaps?) but then, complexity needs a home, you can push it around but cannot hide it, hence a home grown proxy.
I have not tried Kamal proxy to know, but I am highly skeptical of something like this, because I am pretty sure I will be chasing it for support for anything from WebSockets to SSE, to HTTP/3 to various types of compression and encryption.
We also wrote about this https://blog.cloud66.com/hetzner-connectivity-issues-due-to-...
There are so many tools that make it easy to build and deploy apps to your servers (with or without containers) and all of them showcase how easy it is to go from a cloud account to a fully deploy app.
While their claims are true, what they don’t talk about is how to maintain the stack, after “reclaiming” it. Version changes, breaking changes, dependency changes and missing dependencies, disaster recovery plans, backups and restores, major shifts in requirements all add up to a large portion of your time.
If you have that kind of team, budget or problem that deserves those, then more power to you.
The same is happening with Redis after their license change.
In a way, their original open source license was suppressing innovation. I know this is not a popular opinion in some circles of pure OSS aficionados but it seems the evidence is to the contrary
Also there is content in the article stating that Tesla only uses vision whereas other manufacturers use radar and ladar to identify objects where ML trained vision fails to detect them.
There is a shadow army, government and economy in Iran, created and tightly controlled by the office of the supreme leader, Khamenei and enforced by IRGC. They have a chokehold on the economy, imports and exports as well as almost exclusive control over critical foreign affairs. While lifting of sanctions will marginally reduce the pressure on the IRR in the short term, it will feed this cancerous growth which is not in the interest of the Iranian people and the world.
Then recently they made a change to Telegraf that broke all our data collection because they changed the environment variable replacer and their Jsonnet parser broke.
Now this. Shutting down a region without brownouts and only emails is not operationally acceptable.
We’ve moved on from influxDB for a while and only rely on telegraf now.
That's why I always look for profitable companies that have built a business around solid foundations rather than raising external capital in round B, C, D all the way to Z.
If you want to see how those companies *really* were doing, look at their stock prices after they go public. Very few go up or even stay flat. Most of them crash right after the stock handcuffs come off and the investors have passed the bucket to the general public. I even have an anti-portfolio of public companies with investors who wouldn't shut up for a minute about how amazing they are doing, when they were private companies. All of them have done considerably worse than the market average or any basket of tech companies, even excluding the big five.
Making decisions about infrastructure is as much about day-2 as it is about the initial deployment. I see fly.io and render in this camp. Shiny day-1 docs and demos and then wishing you good luck when you need a `rails c` to see something in the DB
Please, educate me, those who upvoted it.