These may be objectively superior (I haven't tested), but I have come to realize (like so many others) that if you ever change your OS installation, set up VMs, or SSH anywhere, preferring these is just an uphill battle that never ends. I don't want to have to set these up in every new environment I operate in, or even use a mix of these on my personal computer and the traditional ones elsewhere.
Learn the classic tools, learn them well, and your life will be much easier.
I'm really torn. A while ago I made the decision to abandon linux and use a BSD as my daily OS. In almost every way I prefer FreeBSD over OpenBSD, except when it comes to the source code. The clarity of OpenBSD source seems unmatched, and for me that's really important as I have picked up interest in contributing to the kernel of the BSD I choose. Also in some naive way it gives me a warm feeling knowing that the code of my operating system is in tip top shape.
I don't usually like participating in bikeshedding, but the @ annotation feels like PHP's $ to me in that I don't see why it needs to exist. The language design could've easily just left that out and I don't think anything would be lost.
Other than that, I'm definitely excited for Zig as a potential C++ replacement.
Seemed interesting based on the amount of languages the editor supports on paper, but a quick trial showed that at least C# support is very, very barebones, even theoretical, as I couldn't get any kind of autocomplete to work, for example. After few minutes of usage Im unsure of what it provides aside from some syntax coloring. Maybe I did something wrong?
I really like the new UI (and all the other similar modern UIs) and I just can't pretend like I dont.
I'm a very visual and a design oriented person and I want my tools to look good. If I'm going to spend countless hours using a product/tool I want to enjoy it's looks as well. Too many tools in my opinion are designed by people who want to maximize productivity with very utilitarian and practical user interfaces (which is great!) but don't seem to have enough care for making something that looks beautiful at the same time.
With only a quick look into this project it looks very interesting and appealing, but I'm afraid it might be an evolutionary dead-end in the Javascript world similar to Facebook's Flow and CoffeeScript. Any opinions to the contrary?
I've personally witnessed several unnecessary and costly refactorings in my job that were done due to this weird perception the blog is talking about. All those weeks and months that were spent removing a perfectly fine tool that was working without issues.
Interesting stuff, I've recently got interested in databases and did some toy programming related to them, trying to understand how they work.
I just wish the author had gone closer to the nitty gritty details of _how_ the data is actually fetched from the disk. How does Postgres store the data? What do the data files look like, how is the parsing done?
In any case I appreciate the effort. I guess I might have to dive into the source code myself.
Are you me OP? I've been working exactly on the same project myself, and also got demotivated.
First I planned to make it as a desktop app, but then I realised desktop apps are thing of the past and nowadays you need to make web apps to be accessible and portable.
Then I got demotivated by the number of great and established products.
Now I'm trying to figure out a new (developer oriented?) product to develop in my free time.
It's tough not being among the first at something.
Hopefully this client will be less toyish and geared towards more advanced users. The existing client really feels like a one button solution to everything.
Learn the classic tools, learn them well, and your life will be much easier.