Subbed

i didnt understand half of this but god damnit i wanna get to that point

instant sub! F```UCK CRAPITALISM and these neofeudal techno serfdoms!

11:19 in a union, only one field can be active at a time. you tried to get the `Pointer` property of the `Type` union when whatever you got the type of isn't a pointer. Since this happened at compile time, it prints out the error when compiling. yeah, zig error messages do need a bit of work

For what it's worth, kotlin has runCatching in the standard library, which effectively gives you either successful result or exception as a value if that's what you need. So it's more a style choice in kotlin. And if can allow 3rd party libraries, there's one that allows you to get even more functional (namely Arrow)

BSD, C, httpd, SQLite is better

thank you for the no music (thats a lie i have nothing to do with the music version i clicked because topic)

I love it, just a bit sad that you didnt include a github link to the scripts or whatever! Thanks tho, really

Actually, Kotlin did not inherit unchecked exceptions from Java. All exceptions in Java are checked.

So if password manager is the best solution, how do password managers manage their auth? 😂 Do we need another password manager to login to another password manager and so on?

A multi million dollar company ain't doing that home self hosting crap. Too risky and not secure

This works only for startup, enterprise company would be hurt very hard to maintain & scale on-premise. 1. Adding new hardwares will not as simpler as you buy laptop on Amazon. If your want to scaling business, you must be struggling to do it 2. The cost that you pay to the cloud is to pay: risk, hardware team, virtualization team, man-days of your employee

Good luck getting Soc 2 compliance with this one let’s see how far your startup can get with this one

Very interesting points !!

Nice video about self hosting but you obviously never worked in any actual business or had to maintain an actual service that the business relay on. Many times it is about SLA, identity management, security, backup, Dr, audits, a team working on the app that has more than two people, another team doing administration and maintenance. And of course it is about scale, let's say your app actually did start generating revenue, how would you scale, buy some servers and put them in your drawer! Or you would have do deploy on cloud (so why not deploy on cloud from the first place) Your entire app could have easily (and quickly) been deployed on Amazon ECS/Google Cloud Run/Azure ACI and cost pennies per month (including the public ip and domain name). If you are worried about cost, all clouds let you set up budget limits

I have some issues with the claims in this video as someone who have designed, developed and operated solutions on prem, in private clouds and on public clouds. If you go with a linux VM or even physical server, then these are the costs you will end up with (and this is not exhaustive): 1. Shit security or an expensive employee that is an expert, preferably a team of expensive security employees. The cloud provide far superior security than most can provide for free or with little training, comparatively. 2. Constant over paying for the hardware or fighting an underperforming system as you always have a fixed capacity. You have to upscale the system sufficiently to take most of the spike loads, or you have to accept poor UX. It is not trivial to go from one linux box on your desktop to having several linux boxes when you scale up. It is not a linear relationship as you need load balancers at the very least. Saying hosting your own linux boxes is "more scalable and cheaper" is as incorrect as you get. 3. Flexibility and speed drops drastically. Setting up a new server because you need capacity is expensive and takes weeks or months. In the cloud, that is a few minutes, tops. This lets you start and do whatever you want to do as you figure out what your business is going to be. 4. Availability and resilience drops drastically. Your service and your data can go poof because someone spilled one cup of coffee or someone broke in or someone made an oopsie in the configuration or operation. You need redundant internet connections with dedicated corporate lines, and those are expensive. You need backup and redundant linux boxes just standing there, on the ready, to handle failures. You have to reset the servers manually, and code in monitoring that lets you trigger events. You have to set up a dedicated linux box that handles logging and notification by sms, phone and many other things. 5. ECS is not "just docker". There are no servers under docker for you to maintain. No patching, no updates, no multi-server clusters that must be scaled up. It has direct and automatic integration with many other services that you also might need. Docker and containers are not the best solution to all use cases. You can not just "build and run" a docker image on the PC either. You have to manage your images locally, maintain versioning of your artefacts, and pay for the diskspace and maybe the registry system as well. Both building and the storage of the images have to be done locally as well, just like in the cloud. 6. Key management and access control is much more difficult, and much easier to fuck up on a local environment. As part of this, this setup does not have IDS or IPS, which is trivial in the cloud, and often comes for free. There is no way to be notified about any intrusions or alterations, something you can get trivially in the cloud. There are a thousand things like port disabling, encryption and key management, regular backups, enforcement of security practices, automatic security scans, etc. that this "simple" self-hosted linux PC does not have. 7. S3 being replaced with just your HDD costs you some features like resilience, event driven capabilities, petabytes of space, disaster recovery options, automatic versioning, simple and separate access control, global reach, separate API access, and more. 8. Separate management of your domain and DNS, which is automated and integrated in the cloud. 9. You need a lot of diverse knowledge to run all this, and a lot of development of different config and script files. 10. You can get all the access you need to set up your own VM in the cloud. Just build an image, upload it and deploy it. If you have a standard distro it is a one click operation. You do not WANT click ops, you want IoC for various reasons, but it can be done. 11. The first claim that it costs millions to run on the cloud is highly suspect for the small use cases you talk about. There is a free tier, that lets you set up a service in the cloud for FREE. That is cheaper than your setup, but about infinite times. To reach a million dollars, a year I assume, you have to have a substantial amount of traffic, data or processing that most companies never reach throughout their entire lifetime. Yes, the big ones like Sony, Nike, McDonalds etc. will require so much that a cloud system would cost them a million bucks, but for a startup I would expect to scale to a few hundred thousand customers for less than 10 grand a year, even with some heavy processing in the background. If it is just a website it will cost them a few dollars. Is the cloud for everyone? No, and you can host it yourself if you are just starting out and want to see if your business is viable. There is a fixed cost that you pay for once, except for electricity and internet costs, and you can get something to experiment with, iterate over and reset until you have a viable product. I do not disagree with these facts, but I find the video to be highly misleading in its current form. Side note, I like how you complain about something being overpriced and expensive and then you use an Apple product.

This is so true😂, if sufficient time nad effort is put into it, then for any company with more than 1000 developer it would be better host on their own.

That was really helpful. I can tell you know your stuff 💪

you forgot to mention that you need static ip which most ISP provides dynamic IP

This video is great. No dragging, no padding content. Just straight to the point. Must KZfaqrs should take notes. Thanks!

When I heart the voice cracking at the end of a sentence I couldn’t ignore it for the rest of the video..

Great write up, there's some great tools out there. I definitely push towards non-vendor locked OpenSource solutions for most of my tasks, even when using the cloud. Especially in larger teams, with lots of projects going on, using closer to baremetal rather than abstracted solutions generally improves the costs and reduces vendor lock even on the cloud. That said, like everything there's always use cases for both. But I'm definitely a "use native K8s over AKS/EKS/Fargate" whenever possible because then you're not stuck.

I'm in love with Rust

The void at the end was great ❤

No it is not and you don't know what you are talking about. Comparing your pet project deployment with a million dollar cloud cost startup. Ridiculous. Why do people press thumbs up on terrible videos like these?

Cars are expensive, just build your own! If you've ever built, maintained, and scaled a datacenter, you know exactly why the cloud is NOT expensive. It is easy to put you as one person spinning up a few instances on your home network, but imagine having to server 10's of thousands of employees and millions of customers at the same time. The electrical and mechanical alone cost more than your cloud bill. Then your IT and mechanical refresh every 5 years is millions of dollars. Your staff to maintain it all is millions of dollars. The cost of scale is passed down to the customer. The benefit of scale is that cost is shared between customers. This inherently makes it cheaper.

Great tutorial, thanks bro And one thing that I've actually did was to move from using Google drive and google photos and instead i sat up an old machine to host Nextcloud service locally And with the mobile app am able to sync all of the mobile data, laptop backups with only the cost of the machine electricity

I'd love to see you review Clojure the same way, and if you do, I'm looking forward to a shockingly low "tooling" score

AWS DynamoDB is relatively cheap if you need a database but don't need it all the time. It's even cheaper if you can minimize API calls by delaying writes so if changes are reverted within that time window, you can save on API calls. I couldn't imagine being able to run a stateless server on my spare Android phone for free, otherwise

I just spent 2 hours today on AWS trying to figure out why I am getting charged $.02 per day even though I don’t have anything running

Nice video but what if you don't have a static ip or worse your router sits behind a carrier grade NAT ? In this case things start to get annoying

I avoided clicking this video but now I regret it. I recently got into trying to setup my on self host and this video is exactly what I want. Never heard of nix either and it seems quite interesting.

It's always about selling unnecessary middle men. Be it in Cloud, AI or Consulting.

9:45 Systemd timers are better in this situation imo. Systemctl status / journalctl is pretty legit when you want visibility on your timer services - especially if you're tracking when it's been activated.

Kubernetes single node is better. But also a bit more complicated.

Is not easier to use Vercel? Yes yes I know the drawbacks of Vercel but the Hobby plan is pretty good for your small website that is going to get just a few hundred visitors each month

This is just awesome! I always wanted to do something like this ( said every engineer ever) 😀

What we really need are transpilers. Creators of new languages should create transpilers from the most common current languages to the new language. Little investment is made in this area.

After uni I started as a big international it consulting firm. I realised that we are basically sells personnel for AWS, Azure etc. setting up a company for microserviced makes them an infinite cash cow.

Idk you asked to like and subscribe, but I did it anyway 🤭

What the hell made you give Kotlin a 4 for readability?

Scala 3 deserves to be on that video

And Kubernetes

with regards to security (and here i am referring mainly to security of other devices on your LAN, including e.g. your mobile phone, laptop, desktop and so on with personal data), you might check out the concept of VLANs

Excellent video thank you!

Lichess is beter :)

The first "real" project written in zig I've seen is RiverWM which probably is going to be my next wm of my choice so I have interest in zig Tooling is OK, but yeah errors are awful. I feel like I returned into c++ where you don't read error messages and just try to figure out what's wrong on your own by commenting code out until you find the line with error Prototyping with it is hard as it has strong dislike towards unused vars. Also it is uncanny valley of c syntax. For some reason I didn't have that problems with rust. I know very basic of ocaml which helped tremendously. Though I also haven't worked with established app in rust. Writing from scratch is very different than hacking around. My main problem with rust is its very shallow mutability check. In general case its impossible to write unmut helper functions and use them later in mut contexf even if functions are safe and can be copypasted instead being called.

Julia mentioned, lets go!

There are some SaaS worth it (Like Outsourcing your backups is actually best practice) Running your system locally is very viable

What about scaling