You're just forcing me to be a vimer at this point. :)
By normal macos experience I mean key bindings for regular text fields, not regular terminal (whatever they're supposed to be). Afaik, Warp was the first one ever to treat terminal input as a regular text field input.
> Weak engineers are often surprisingly active in work-related discussions.
Hits the nail on the head. I don't think it's an engineers fault though.
If the company culture rewards buzzwords over code and endless meetings over real progress this kind of behavior becomes inevitable. When shipping features takes a back seat to writing "thought leadership" blog posts or chasing pointless metrics, people adapt to survive in that environment.
It's not about bad engineers, it's about a system that incentivizes all the wrong things.
I often see engineers from other teams ask for a "non-blocking endpoint" because they don’t want to block while waiting for a response from the server. What is a "non-blocking endpoint"? If you are making the request, just do not block...
Conclusion by author:
> Now Go loses by over 13 times to the winner. It also loses by over 2 times to Java, which contradicts the general perception of the JVM being a memory hog and Go being lightweight.
Note that Go and Java code are not doing the same! See xargon7 comment.
“An idiot admires complexity, a genius admires simplicity, a physicist tries to make it simple, for an idiot anything the more complicated it is the more he will admire it, if you make something so clusterfucked he can't understand it he's gonna think you're a god cause you made it so complicated nobody can understand it. That's how they write journals in Academics, they try to make it so complicated people think you're a genius” ― Terry Davis
Please note, no offense intended, I just like this quote to describe Go success.
“Know when you’re testing the framework’s capability. If you are, don’t do it. The framework is already tested by people who know a lot more than you.”
How many times have you had to roll back a minor version upgrade because the library maintainers *absolutely don’t* know what they are doing? Spring, Netty, and Java ecosystem, I'm looking at you...
How well does Flox work out of the box? I would really like to introduce Nix to the dev environments in my company but the struggle of maintaining nix files and flakes is too large. I've looked at DevBox and it looks quite accessible but Flox also looks like a nice way to sneak some of the Nix goodness into the company.
imo: In Europe, almost every significant issue has layers of legislation designed to protect large industries and corporations. These laws often prioritize corporate interests over solving real societal problems. I would argue that more freedom for startups to innovate in spaces like Pharma, Industry, Resource Efficiency, Public services... would benefit society as a whole. However, this requires two key things: 1) substantial investment $$$, and 2) navigating through the mentioned layers of bureaucracy and "protective" (protecting who) laws.
For me, again my opinion, It’s been really frustrating trying to find investment for some MVPs, only to have ideas shut down by these barriers.
Related project: https://bellard.org/nncp/ and https://bellard.org/nncp/nncp_v2.1.pdf If any one wants to read more about how it's implemented.