509 karma · joined October 13, 2024
I know my editor (emacs) could do some of the more advanced things you mention, but it needs a bit of setup and I'm lazy. It's not really a blocker.
I look at the docs if I'm doing something new to me or have forgotten a function call. I google more complex things which often gets me more useful info than an IDE could give me, unless it's drowned by AI-slop.
If I want to dig around in a codebase I can grep for things, or just open a likely looking file and isearch for the thing.
I do git etc from the commandline, which I could probably do from emacs too but I never really bothered to.
I have nothing against IDEs and have used some at places where it was harder not to because they'd standardised on a common one. I kinda enjoy the simplicity of just having a familiar editor for any language I encounter though.
What I mean is that it's costly and the benefits are at best emotional.
And if you personally assign a large value to having unicode characters in your login name specifically, I posit that you have the wrong priorities in life. You're free to disagree with that opinion
If you instead think of each dreamed about great AR application as a smartphone app, an uncomfortable realism creeps in about how apps work and that someone has to build and integrate them
"But if I could put on glasses and see what’s going on with my car and then be guided through that process, that would be cool. "
It would. And if we built that smartphone app, it would be really useful today. But doing that, for the general case of "what am I looking at, and how do I fix it" is AGI-hard
It's very true that there are many areas of ML where considerable progress has been made and is delivering value
Are companies using QC? It's not like it can do much currently, as I understand it
We're making a lot of progress all over the engineering side of computing. A lot of it is incremental, but a faster or more energy efficient processor is very practically useful in a way that QC isn't yet. We might well get optical interconnects on cpu dies before we get anything tangible from QC
AI – being practically applied in many areas where it doesn't seem to be working well
I really do hope these aren't our best lanes of progress
Because then it to be normalised in the right way for comparisons to work, or it will only match if your input method happens to produce the exact same variant.
... And unicode is an evolving standard where this normalisation sometimes changes between standards, so the names as normalised in the old version of your standard library might disagree with the new version. So you need to care for that transition.
... And often this is implemented separately for different languages, so you can get names that won't match if you normalise them in python, java or C.
... And as all implementations, these unicode implementations sometimes have bugs, so you need to think not only about matching supported unicode versions, but matching bugs.
... And any change in these normalisations can in theory lead to two usernames that used to be distinct becoming identical.
It's a deep well
There is a field for the full name of the person if you want to, and at least on my linux it warns for non-ascii characters but allows them
Also, for a lot of the areas where languages like python or ruby aren't great choices because of performance, they would also not be great choices because of the cost of maintaining untyped code, or in python's case the cost of maintaining code in a language that keeps making breaking changes in minor versions.
Script with scripting languages, build other things in other languages
What language that's been around for long enough to have a large ecosystem doesn't have a terrible history of poor api design?
But sure, if you pick a really new language, you do get the chance to be that history for future generations
It's a language built to make it hard for new joiners to mindlessly add complexity, as the language itself will fight you. It makes it hard to add dependencies that aren't very visible and vendored in, it makes it hard to change how the language behaves with overloading, preprocessor magic or macros, and so on.
It's built to fit Google specifically, with their army of new grads, and deep investment into reinventing all the dependencies themselves, and having a huge monorepo.
If you're not google, you're gonna have a bad time, which is also good for google.
People have an irrational hate for it based on the enterprise cruft and horrible third party frameworks you can just completely ignore if you build a new thing
It's not good for commandline stuff but for a long running small service it is pretty great
If you force people into camps, human rights organisations will start expecting you feed them and generally keep them alive.
If you just allow them to camp somewhere without getting bulldozed, you have less liability