They did this while introducing a lot of compiler magic and automatic dependency discovery that not always works. I’m not sure I’m sold on it. Code you write is not code you execute.
Yeah, looks like a “poor man” docker swarm. And I would just go with swarm. It’s very good. And very easy to move to from compose. Too bad k8s won the hype battle here.
I was running one of my products on 7 5$ instances from DigitalOcean. Which includes load balancer (Apache), database with replication, static site hosting, web app and 2 backends. It was happily serving hundreds of concurrent users with quite a lot of space to still grow. With their s3 clone and few volumes we rarely paid more than 45$ per month. You really can get far with cheap cloud machines.
This would be really cool. If there would be a more modern version of C, made by C standard committee. Without UB and with small, but robust stdlib. It would have to stay compatible on ABI level, but source level I think we can skip.
For me Zig looks like something that could become a new C. They aim for great C binary and source compatibility (both ways - called and callable from C). It’s planned to be small and lean. And avoid preprocessor and UB as much as possible.
I think that even when you plan to just manually deploy dockers on raw hardware, it’s still worth it. There’s plenty of stuff you can ignore if you do so. Ex: do I test with exactly the same versions of libs/binaries that I have on production? You can also easily do rolling deployments even if you have a single machine. There’s plenty of value while staying reasonably simple. Not something you can say about k8s. It’s nowhere near simple.
And also makes it easy to test with different database versions, gives you 5 minute onboarding for the new devs on team (run this docker compose and you have everything in place). Lets you test your software in exactly the same environment as in production. Switch between stack versions in no time. Etc. It really solves real problems. Not only enterprise level bullsht.
I also have mixed feelings about Rust. It gives me too many flashbacks from Scala. Complex types, a lot of generics, same elitist attitude. I just think it will end up the same way as Scala. Few years of hype and now we have plenty of unmaintainable codebases from wannabe functional zealots.
I think that biggest issue with page size is not due to client side rendering, but rather thanks to bundling and idea that you need to download the same minified Lo-Dash on each and every page. Why can’t we just use public CDNs is beyond my understanding.
I really like client side apps. They are so much more responsive. The only problem is with bundle sizes.
For me, whole DOM is a useless overhead. Why don’t we just have some nice transactional browser API? Client side frameworks don’t really need to generate HTML that is immediately parsed. It’s a total waste.
From what I know React does not register event handlers on individual nodes, but rather on root component. Then it uses virtual events from it’s pool in your callbacks.
I’ve set up a PI Hole at work with blocklist of social media, YT and similar sites exactly for that. Whenever I want to check any of them I need to go to PI Hole admin site, log in and disable blocking. Having to do that is in 90% cases enough to stop me from procrastinating. When I really need it for work, these few more steps don’t make a difference.
Yeah, I mean it’s not exactly the same price. But after you pass a certain price point adding few hundred $ is not making a big difference. While what you get - mobility, battery, great keyboard and display, speakers, webcam, touch-id, etc is quite a lot of stuff for 700$. If you just add a good external display, it’s easy to pass the price of MBP. At the same time you loose nothing. It’s not really a desktop machine, that would be much faster or allow part replacement. It is just a laptop without a lot of parts.
I really love the idea of Mac mini, but when you add some more RAM and disk price is almost the same as for MacBook PRO, where you get almost the same hardware a superb display and a keyboard built in. And you can carry it around with you. These machines almost make no sense because of that.
ReiserFS was really good. Too bad that nobody continued it. I’m not sure it was due to the original author story or due to it’s code being really hard to work with. But the FS was so much faster than ext3/4 on machines from 2000’. And I never lost a file with it. Something you cannot say about xfs or jfs. I’ve had to reinstall os so many times after system crash due to them getting corrupted.
Thanks, been thinking about it. It looks really nice, but it’s really hard to beat how easily you can go from compose in local development to swarm on prod in small team.
This is kind of cool, but it all makes sense if your app is a very simple CRUD that spends 99% of time just passing json around. I have this feeling that when you add some more logic there you’ll start noticing that you’re not in a compiled language any more. Your requests will get slower and your memory usage will explode.
Saying that Python is faster than Go with this as a proof looks like overreaching for
Me. It only proves that wrapping C code in Python is fast. It’s an achievement, sure, but your app probably won’t be faster when you add thousands of Python lines between request and response.
Oh man, it reads like a homework of my kid. The style is so poor. Whatever magical power there is, please save us from future with novels written like this. There’s no way I can convince any kid in the future to read if we’ll have only stories with this quality. It’s so bland.
I plan to work on an idea I’ve been thinking about for 2 years already.
It’s a mix of Intercom and Bugsnag, but made for technical people. For indie-hackers and small dev-houses where developers themselves have to support users and are not affraid of code and stack traces. Especially for mobile apps.
All these customer support tools are web only and focused mostly on marketing and sales. But my experience from my failed startup is that it works really well to get in touch with your users when you’re an indie hacker. Or to bugfix while on live chat with the user who can reproduce a bug.
Also I don’t know why, but all these support tools except Intercom have really bad ux and are slow and buggy. They also neglect mobile apps, all is web only. Or maybe I’ missing some real gem on the field…
This is a really cool site. I’ve been using it extensively when learning to touch type. It’s maybe less efficient, but much more enjoyable than plain typing exercises.
Shameless plug: I’ve also made a somewhat similar site: https://typingtool.app/ because I didn’t really like the look of it.
For me photos are solved problem now. I no longer do any cleanup on them, just assume that Apple AI will show me best photos when I search for them. I think that it is simply good enough already.
While I totally despise Electron it might be a great moment for new OSes and UI toolkits to emerge. In near future it might be enough to port Electron and a web browser and your niche OS might become actually usable on daily basis.
It’s slow and a total memory waste, but web became a new UI toolkit that actually solved OS compatibility issues. Who would have thought…
Oh man. I don’t get this complaint. There’s a quadrillion of Windows only software, basically 99% of games are Windows only. Most of Gnome and Kde apps are Linux(BSD) only. Yet they don’t scream on the home page “Watch Out! It’s Windows only!”
Yet everyone assumes that Mac users dream of using their apps on some other OS. Why? I have no idea.
I think you should get just that with Notepad++ on Windows or TextWrangler (BBedit) on Mac. On Linux I think that all stock editors have it (GEdit, etc…). All that for free and without Electron madness. You should be much better with any of them.
It might sound controversial, but for me Atom was almost a 1 to 1 Sublime copy with worse performance and quality. It was slow and ugly. It’s only quality was that it was 0$.
It was the first editor I’ve seen to choke when opening 1M file (it even had a warning that it’s a too big file - lol). There simply was not enough RAM in the world for this memory hog.
I’m not really sad to see it go. It was another free toy of a big company that people used not to spend 60$ on real thing made by small company and waste thousands of dollars on lost productivity and time.